| LABEL: | Access Rights |
| NAME: | [dcterms:accessRights] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | Information about who can access the resource or an indication of its security status. |
| PROJECT DEFINITION: | A statement of any access restrictions placed on the collection, including allowed users, charges, etc. |
| COMMENTS / EXAMPLES: | The World Intellectual Property Organization, the MPEG-21 initiative, and others currently are jointly developing a Rights Data Dictionary and Rights Expression Language to adequately express:
However, these standards are not yet to the point of being a recommended standard. For more information on current choices and emerging standards for expressing digital access rights, see Karen Coyle’s 2004 Rights Expression Languages: A Report for the Library of Congress For the MetaArchive project, a controlled list of access categories will be established (Restricted, Unrestricted] |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Two mutually exclusive options (radio buttons): restricted and unrestricted |
| [back to top] | |
| LABEL: | Accrual Periodicity |
| NAME: | [cld:accrualPeriodicity] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | The frequency with which items are added to a collection |
| PROJECT DEFINITION: | Frequency with which items are expected to be added to a collection |
| COMMENTS / EXAMPLES: | This element is meant to indicate whether items are actively added to the collection. Choices are: Examples: |
| ENCODING SCHEMES: | http://www.ukoln.ac.uk/metadata/dcmi/collection-DCCDAccrualPeriodicity/ |
| OBLIGATION: | Mandatory if applicable |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Since this is primarily a freetextual field, the choices do not have to be enforced by data entry template, but those creating metadata should have access to their list of recommended terms. |
| [back to top] | |
| LABEL: | Accrual Policy |
| NAME: | [cld:accrualPolicy] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | The policy governing the addition of items to a collection |
| PROJECT DEFINITION: | Approach adopted to add items to the collection or a statement about anticipated growth of the collection, including quantity and frequency |
| COMMENTS / EXAMPLES: |
Use proposed DC CD Accrual Policy terms Examples |
| ENCODING SCHEMES: | DC CD Proposed Terms: closed, active, passive http://www.ukoln.ac.uk/metadata/dcmi/collection-accrualPolicy/ |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Accumulation Date Range |
| NAME: | [rslp:created] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/rslp/schema |
| SOURCE DEFINITION: | The range of dates over which the collection was accumulated. |
| PROJECT DEFINITION: | The range of dates over which the digital collection was accumulated. |
| COMMENTS / EXAMPLES: | A date range should be supplied in the form of a time interval conforming to ISO8601. Start and end dates should be separated by a forward-slash (/). Each date should be entered according to the W3C note on 'Date and Time Formats', http://www.w3.org/TR/NOTE-datetime. Null dates may be used to indicate open-ended date ranges. All the following are examples of valid date ranges: 1999/2001 |
| ENCODING SCHEMES: | ISO8601, Dublin Core Terms [dcterms:ISO8601]: http://purl.org/dc/terms/ISO8601 |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Alternative Title |
| NAME: | [dcterms:alternative] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | Any form of the name given to the resource used as a substitute or alternative to the formal name of the resource. |
| PROJECT DEFINITION: | Any form of the name given to the resource used as a substitute or alternative to the formal name of the digital collection. |
| COMMENTS / EXAMPLES: | Values may include acronyms that are used in addition to the name of the collection. As an example: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Associated Collection |
| NAME: | [dc:relation] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | Any other collection(s) that is associated with or complements the current collection |
| PROJECT DEFINITION: | Any other collection(s) associated by provenance or content with the current collection. |
| COMMENTS / EXAMPLES: |
Enter here names of collections associated by provenance or content, preserving the original wording, order and spelling of associated collection titles. Example: Arthur Y. Ford Albums |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Associated Publication |
| NAME: | [dcterms:isReferencedBy] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | A publication that is based on the use, study, or analysis of the collection |
| PROJECT DEFINITION: | A publication that is based on the use, study, or analysis of the collection. |
| COMMENTS / EXAMPLES: |
Enter here names of publications based on use, study, or analysis of the collection. When available, use Library of Congress authority files to establish uniform headings. Example: A Kentucky album: Farm Security Administration photographs, 1935-1943 / Beverly W. Brannan and David Horvath, editors; with a foreword by Jim Wayne Miller. Lexington, KY: University Press of Kentucky, c1986. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Bytes |
| NAME: | [dcterms:extent] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | The size or duration of a resource. |
| PROJECT DEFINITION: | The total calculated file size, expressed in computer bytes, of the digital collection being described. |
| COMMENTS / EXAMPLES: | Enter the calculated total size, expressed in bytes, of all electronic files in the collection being described. Do not punctuate this number with commas, to facilitate easier machine manipulation of the numeric string. Do not enter the word "bytes" nor any abbreviation, to aid with automnated calculations. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Integer |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Cataloged Status |
| NAME: | [ma:catalogedstatus] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | |
| PROJECT DEFINITION: | Indication of level of cataloging of the collection beyond the collection level. |
| COMMENTS / EXAMPLES: |
Describe cataloging of items in the digital collection (not hard copy originals), at levels below the "collection level". Select: Comments (optional) may describe the type/nature of cataloging, for example: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Have 3 radio buttons: 1) cataloged, 2) partially cataloged, 3) uncataloged. Then also a comments field. |
| [back to top] | |
| LABEL: | Catalogue or description |
| NAME: | [dcterms:hasDescription] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | The identifier or name of a second collection that describes the current collection (for example, the catalogue for the current collection). |
| PROJECT DEFINITION: | Finding aid, published catalogue, or other publication which describes or provides intellectual access to the collection. |
| COMMENTS / EXAMPLES: | Enter here the names of any finding aids, exhibition catalogues or other publications providing intellectual access to the collection. Preserve the original wording, order and spelling of the finding aid or catalogue title. Example: For love of learning: an introduction to special collections and primary sources at the University of Louisville Libraries and Archives. Louisville, KY: University of Louisville, 2001. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Collection Size |
| NAME: | [dcterms:extent] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | The size or duration of the resource. |
| PROJECT DEFINITION: | A statement of the size or duration of the digital collection being described, expressed in terms such as total file count or genre of material. |
| COMMENTS / EXAMPLES: |
When possible use separate counts for different types of items (examples: 200 books ; 150 photographs ; 25,000 images ; 2,000 files) Local database reporting functions may generate different size indicators such as the total number of files and intellectual objects by type. Local system configuration and statistical generation (such as the LOCKSS manifest system being used in the MetaArchive project) may be able to generate this information automatically. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Contents Date Range |
| NAME: | [cld:dateContentsCreated] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | The range of dates over which the individual items within the collection were created. |
| PROJECT DEFINITION: | The range of dates over which the individual items within the digital collection were created; date of creation of the digital resource. |
| COMMENTS / EXAMPLES: |
A date range should be supplied in the form of a time interval conforming to
ISO8601. Start and end dates should be separated by a forward-slash (/).
Each date should be entered according to the W3C note on 'Date and Time
Formats', http://www.w3.org/TR/NOTE-datetime.
Null dates may be used to indicate open-ended date ranges. All the following
are examples of valid date ranges: |
| ENCODING SCHEMES: | ISO8601, Dublin Core Terms [dcterms:ISO8601]: http://purl.org/dc/terms/ISO8601 |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Creator |
| NAME: | [dc:creator] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | An entity primarily responsible for making the content of the resource. |
| PROJECT DEFINITION: | A person or entity primarily responsible for creating the intellectual content of the resource. Examples of creators include authors of written documents, artists, photographers, collectors of natural specimens or artifacts, organizations that generate archival collections, etc. |
| COMMENTS / EXAMPLES: | Input Guidelines: 1. Enter multiple creators in the order in which they appear on the resource or in order of their importance. Use separate Creator elements to enter multiple creators or clearly separate each entry by a semi-colon and a space within an element. Secondary authors, editors, etc. may be entered using the Contributor element. 2. If using established cataloging rules to construct Creator elements, follow those rules. Some examples of established rules include: Anglo-American Cataloging Rules (AACR2); Describing Archives: A Content Standard (DAC); Cataloging Cultural Objects (CCO) If not using such rules, then use the following guidelines. 3. Determine the correct form of the name when possible. The Library of Congress Authorities (http://authorities.loc.gov) or locally-specified bibliographic utilities (OCLC, RLIN, ULAN, etc.) should be consulted when possible. 4. Enter personal names in inverted form in most cases: Last name, First name, Middle name or initial. If it is not obvious how to invert or structure the name, use the name form given in an authority list or enter it as it would be in the country of origin. Birth and/or death dates, if known, should be added, in accordance with authorized form of the name when possible. 5. Enter group or organization names in full, direct form. In the case of a hierarchy, list the parts from the largest to smallest, separated by periods. 6. If a group or organization name includes subordinate units, the name may be shortened by eliminating some of the hierarchical parts not considered necessary for uniquely identifying the body in question. For example, to enter the CIA as a creator, use the form of the name as given in the Library of Congress Authorities (United States. Central Intelligence Agency) instead of the full hierarchical name (United States. National Security Council. Central Intelligence Agency). 7. If there is doubt as to how to enter a name and the form of name cannot be verified in a controlled vocabulary, enter it as it appears and do not invert. For example: Sitting Bull. 8. Optional: The function of a creator may be included in parentheses after the name. For example: Ansel, Adams (photographer). 9. If the creator is unknown, leave the element blank. |
| ENCODING SCHEMES: | [n/a] |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Custodial History |
| NAME: | [dcterms:provenance] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity and interpretation. |
| PROJECT DEFINITION: | A statement of any changes in ownership and custody of the collection since its creation in digital format, that are significant for its authenticity, integrity and interpretation. Other provenancial information such as the custodial history of a physical source for the digital collection may also be included. |
| COMMENTS / EXAMPLES: |
The statement may include a description of any changes successive custodians made to the collection. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Description |
| NAME: | [dc:description] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | A summary of the content of the resource. |
| PROJECT DEFINITION: | A summary of the content of the digital collection. |
| COMMENTS / EXAMPLES: |
A free text summary of the collection. Although a description might contain detailed subject-specific information, at least part of the description should be understandable by an end-user with no specialist knowledge of the subject area. e.g. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Format Characteristics |
| NAME: | [dc:format] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | The physical or digital manifestation of the resource. |
| PROJECT DEFINITION: | The digital manifestation(s) represented in the digital collection being described. |
| COMMENTS / EXAMPLES: | Use the first level of the Media Type (i.e. image, text, audio, video, application) if you cannot find the specific media type for your digital items. Examples: |
| ENCODING SCHEMES: | Internet Media (MIME) Types http://www.iana.org/assignments/media-types/ |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Needs two level drop-down picklist capability, first level is mandatory, second level is optional and also allows manual write-in entry. |
| [back to top] | |
| LABEL: | Institution Collection Identifier |
| NAME: | [dc:identifier] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | An unambiguous reference to the resource within a given context. |
| PROJECT DEFINITION: | An institution assigned identifier for the digital collection, according to local conventions. |
| COMMENTS / EXAMPLES: | Examples: |
| ENCODING SCHEMES: | ASCII letters and numbers |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Is Available Via |
| NAME: | [cld_gen:isAvailableAt] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | The service that provides access to the digital collection, such as an OAI data provider or a Z39.50 target. |
| PROJECT DEFINITION: | The service that provides access to the digital collection, such as an online searchable database. |
| COMMENTS / EXAMPLES: | This is the URL to the collection for a publicly available collection or the URL to the holding entity. It is for the use of the end user. e.g. for a collection not available via the Web: |
| ENCODING SCHEMES: | URL |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Language |
| NAME: | [dc:language] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | A language of the intellectual content of the resource. |
| PROJECT DEFINITION: | A language of the intellectual content of the digital collection. |
| COMMENTS / EXAMPLES: | Enter language names in the form of the three character code defined by ISO 639-2.
Where more than one language is provided, a repeated attribute should be used for each. |
| ENCODING SCHEMES: | ISO639-2, Dublin Core Terms [dcterms:ISO639-2] http://purl.org/dc/terms/ISO639-2 |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Should be a scrollable list of multiple selections. |
| [back to top] | |
| LABEL: | LOCKSS Manifest Page |
| NAME: | [ma:manifest] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | A web page, provided by the publisher, that supplies key information describing a particular Journal. At a minimum, this would include top level URLs for the journal and a statement of permission allowing LOCKSS to collect and save the content. |
| PROJECT DEFINITION: | This is a URL specifying the location of the LOCKSS manifest page associated with the collection in question. |
| COMMENTS / EXAMPLES: | This manifest URL may not exist at the time the collection record is created, but can be entered subsequently when it is available. |
| ENCODING SCHEMES: | URL |
| OBLIGATION: | Mandatory if applicable |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Manifestation |
| NAME: | [mods:physicalDescription] |
| DEFINED BY: | http://www.loc.gov/standards/mods/v3/mods-3-0-outline.html |
| SOURCE DEFINITION: | |
| PROJECT DEFINITION: | The role of individual files within the described digital collection as part of a digital preservation strategy. |
| COMMENTS / EXAMPLES: | Choose from three choices defined by MODS standard for the "reformatting quality" attribute of the physicalDescription metadata element (access, preservation, replacement). May contain more than one choice, to indicate that files of varying quality or purpose are contained in the collection. |
| ENCODING SCHEMES: | http://www.loc.gov/standards/mods/v3/mods-3-0-outline.html#physicalDescription |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Check boxes: access, preservation, replacement. |
| [back to top] | |
| LABEL: | MetaArchive Collection Identifier |
| NAME: | [ma:collectionid] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | |
| PROJECT DEFINITION: | A unique formal identifier for the proposed source collection within the context of the MetaArchive project. |
| COMMENTS / EXAMPLES: | MetaArchive collection identifier will be a unique number generated by the conspectus database system. Examples: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Integer |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Unique, integer assigned by database. |
| [back to top] | |
| LABEL: | OAI Provider |
| NAME: | [ma:oaiprovider] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | This is the URL that specifies the location of the OAI data provider for the collection, if one exists. |
| PROJECT DEFINITION: | Specification of the OAI data provider URL |
| COMMENTS / EXAMPLES: | Some collections will be harvested via OAI-PMH. In this case, this field must be filled out. |
| ENCODING SCHEMES: | URL |
| OBLIGATION: | Mandatory if applicable |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Publisher |
| NAME: | [dc:publisher] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | An entity responsible for making the resource available |
| PROJECT DEFINITION: | The institution primarily responsible for making available the particular digital collection being described. |
| COMMENTS / EXAMPLES: | For the MetaArchive project, this element will contain only the name of the partnering university. By providing content to the archive, each partner assumes the administrative responsibilities and serves as the main contact for any questions regarding contributed collections. Examles: Auburn University, Emory University, etc. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Provide a drop-down list of all 6 partnering institutions. |
| [back to top] | |
| LABEL: | Recommended Harvest Procedure |
| NAME: | [ma:harvestproc] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | Harvest procedure to be used by MetaArchive preservation network, either LOCKSS web crawl or LOCKSS OAI harvest |
| PROJECT DEFINITION: | Indication of whether web crawl or OAI-PMH is the recommended method for harvesting the collection. |
| COMMENTS / EXAMPLES: | This will record the harvest mechanism for the collection content. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Radio box options: 1) web crawl, 2) OAI harvest |
| [back to top] | |
| LABEL: | Rights |
| NAME: | [dc:rights] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | Information about rights held in and over the resource. |
| PROJECT DEFINITION: | A statement of any rights (copyrights, etc.) held in/over the collection. |
| COMMENTS / EXAMPLES: |
Can include a URL linking to a rights page. Examples: 1) See http://palmm.fcla.edu/lfnh/copyright.html for copyright and conditions of use information. 2) Copyright has not been assigned to the holding institution. This collection is included in the MetaArchive project primarily as a digital preservation strategy. Permission to publish or quote from portions of this collection will require written permission from both the owner of the physical or digital items and from the legal copyright holder. Commercial use is strictly prohibited without permission. 3) Copyright has been assigned to the holding institution. This collection is included in the MetaArchive project primarily as a digital preservation strategy. Permission to publish or quote from portions of this collection will require written permission from both the owner of the physical or digital items and from the legal copyright holder. Commercial use is strictly prohibited without permission. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | The rights statement area on the data entry form should include a freetextual capability, or allow catalogers to choose from the following: |
| [back to top] | |
| LABEL: | Risk Factors |
| NAME: | [ma:riskfactors] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | A narrative description of the risk factors relevant to this collection. |
| PROJECT DEFINITION: | Describes in a clear way the risk factors that put this collection at risk. |
| COMMENTS / EXAMPLES: | This narrative field provides notes and details about why the digital collection is at risk. Should clarify why the collection was assigned a particular risk rank. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Risk Rank |
| NAME: | [ma:riskrank] |
| DEFINED BY: | MetaArchive metadata |
| SOURCE DEFINITION: | |
| PROJECT DEFINITION: | A numeric ranking of the degree to which the collection is at risk. |
| COMMENTS / EXAMPLES: | This numeric ranking will be used when producing and ranking lists of collections for consideration by the content committee. Examples and criteria: 5: Extreme risk, no one is responsible for preservation, no other copies of the digital content are preserved beyond the available copy under consideration, no regular backups or data migration. 4: Significant risk, responsibility under discussion, curators fretting about who will take responsibility for preservation. 3: High risk, only one backup copy of digital masters on CD-ROM, no regular backups or data migration. 2: Moderate risk, some danger that collection backups might be lost in future. 1: Low risk, copies are backed up regularly with a long term maintenance plan in some other trusted digital archive. |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Integer |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | Radio buton options for 1-5. |
| [back to top] | |
| LABEL: | Spatial Coverage |
| NAME: | [cld:spatial] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | Spatial characteristics of the intellectual content of the resource |
| PROJECT DEFINITION: | The geographical place(s) or area(s) associated with most or all of the items in the digital collection. |
| COMMENTS / EXAMPLES: |
The IMLS DCC project has provided a list from the top hierarchy of the Getty Thesaurus of Geographic Terms. Projects are encouraged to add refinements to this from the Getty Thesaurus. Examples: Suggested format for the MetaArchive project: Elements would be applied as appropriate. Examples: |
| ENCODING SCHEMES: | The use of the Getty Thesaurus of Geographic Terms is strongly recommended. |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Include a link in the entry form to the Getty Thesaurus mentioned above. |
| [back to top] | |
| LABEL: | SubCollection |
| NAME: | [dcterms:hasPart] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | The identifier or name of a second collection contained within the current collection. |
| PROJECT DEFINITION: | The name or identifier of any other collection(s) contained within the current collection. |
| COMMENTS / EXAMPLES: |
Enter here the names of identifiable collections contained within current collection. Example: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Subject |
| NAME: | [dc:subject] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | The topic of the content of the resource |
| PROJECT DEFINITION: | Terms that describe the topic(s) of the content of the resource. |
| COMMENTS / EXAMPLES: |
Enter here terms that describe the content of the collection or concepts associated with the collection. Use Encyclopedia of Southern Culture (ESC) terms and, if available, Library of Congress Subject Headings (LCSH). Examples: |
| ENCODING SCHEMES: | ESC; LCSH |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | SuperCollection |
| NAME: | [dcterms:isPartOf] |
| DEFINED BY: | http://purl.org/dc/terms/dcterms |
| SOURCE DEFINITION: | The identifier or name of a second collection that contains the current collection. |
| PROJECT DEFINITION: | The name or identifier of a second collection that contains the current collection. |
| COMMENTS / EXAMPLES: | Enter here the name and/or unique identifier of the collection containing the current collection. Example: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Temporal Coverage |
| NAME: | [cld:temporal] |
| DEFINED BY: | http://www.ukoln.ac.uk/metadata/dcmi/collection-application-profile/2004-02-01/ |
| SOURCE DEFINITION: | Temporal characteristics of the intellectual content of the resource. |
| PROJECT DEFINITION: | The temporal coverage of the intellectual content of the items in the collection. |
| COMMENTS / EXAMPLES: |
A time period(s) associated with most or all of the items in the digital collection. Projects should use spans of years rather than names of periods. (i.e. 1861-1865 instead of Civil War). Examples: |
| ENCODING SCHEMES: | n/a, though the IMLS DCC project has developed a list of often used terms for use on the collection registry form. |
| OBLIGATION: | Optional |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 0 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Make sure that entry is two years (that are sequential or a single year). |
| [back to top] | |
| LABEL: | Title |
| NAME: | [dc:title] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | A name given to the resource. |
| PROJECT DEFINITION: | A name given to the digital collection. |
| COMMENTS / EXAMPLES: |
Enter the name of the collection preserving the original wording, order and spelling. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by a colon, for example: |
| ENCODING SCHEMES: | |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | 1 |
| DEVELOPER NOTES: | |
| [back to top] | |
| LABEL: | Type |
| NAME: | [dc:type] |
| DEFINED BY: | http://purl.org/dc/elements/1.1/ |
| SOURCE DEFINITION: | The nature or genre of the content of the resource. |
| PROJECT DEFINITION: | The nature or genre of the content of the resource; the name of the object(s) or resource(s) represented by the digital item(s) in the collection. |
| COMMENTS / EXAMPLES: | Here is a suggested list of collection types, based on http://www.ukoln.ac.uk/metadata/dcmi/collection-type/: Computer Animations These could be used in a drop-down list in the database. |
| ENCODING SCHEMES: | Based on Collection Type Vocabulary, Collection Type Vocabulary [cld:CLDT] (http://example.org/cld/terms/CLDT) |
| OBLIGATION: | Mandatory |
| DATATYPE: | Character String |
| MINIMUM OCCUR: | 1 |
| MAXIMUM OCCUR: | unbounded |
| DEVELOPER NOTES: | Want checkboxes for these 13 types, along with a positive integer entry field. |
| [back to top] | |