This document describes the required and recommended metadata fields for Digital Collections in the Duke Digital Repository.
A note about digital collections with full text that are represented in CONTENTdm as well as DDR.
Digital Collections resources are modeled as follows:
- This is the top level organizational unit for a Digital Collections collection, and typically corresponds to a single collection from the Rubenstein Library.
- Some metadata is applied at the collection level, to provide context on collection portal pages and enable portal page features. See Collection Level Metadata for a list of the properties to be used at the collection level.
- Collections contain items, which represent the resource as an intellectual item. This refers to the item as modeled in the DDR, so, for example, an item could be a photograph consisting of a single digital file or a letter consisting of multiple digital files. An item in the DDR could also be a folder that itself contains multiple intellectual items. Descriptive metadata is applied to items in the DDR.
- All metadata properties may be applied at the item level.
- The digital file level of the object model. Components are not discoverable via the Digital Collections interface, and so no additional metadata beyond system-generated technical metadata is applied to them.
The following metadata properties should be used on collection-level metadata metadata records to enable portal page features:
- title - Required. Name of the collection.
- abstract - Enables the presence of short contextual description of the collection to appear below the title on the collection portal page.
- admin_set - Required. Value: 'dc'. Assures the collection is a part of the Digital Collections collecting area of the DDR.
- local_id - Required. The collection slug - forms part of the URL. When there is a corresponding collection guide, the local_id should be the same as the ead_id.
- ead_id - Enables the Source Collection section on the collection portal page.
- description - Enables the About the Digital Collection section on the collection portal page.
- research_help_contact - Required. Enables the center/unit name and contact information to display on the collection portal page.
- aleph_id - Enables the View Details (Catalog) link to the catalog record for the collection.
Collections in the Digital Collections Admin Set may be configured or unconfigured.
Unconfigured collections share a standard set of portal display and metadata configurations.
- See this list of fields that will display or function as facets in unconfigured collections.
Configured collections may have custom configurations including:
- Custom featured images.
- Configurable metadata properties, labels, and facets.
How to read the documentation
Field: the name of the metadata property. Mandatory fields are indicated in bold.
Label: this is the label of the field as it will display in the end-user interface.
Predicate: this is the URI for the metadata property to which our local use conforms. Adhering to broadly accepted standards allows our metadata to be shared and crosswalked to other standards. We use the Dublin Core metadata element set when appropriate.
Obligation: this refers to the requirement status of the field.
- 1: Required, single value allowed
- 1-n: Required, multiple values allowed
- 0: Optional, single value allowed
- 0-n: Optional, multiple values allowed
Show: indications whether or not the field displays in the UI.
Facet: indicates whether or not the field will display as a facet for browsing on the collection or cross-collection level.
Usage Guidelines: a brief description of the way the field is to be used, including content type and source.
|Y||N||Free text name of the resource.|
|Y||N||Alternate free text name of the resource, often used for translated titles.|
Person(s) or organization(s) responsible for the creation of the resource. Authoritative headings preferred. Invert personal names (last name, first name) when constructing name headings.
|Y||Y||Person(s) or organization(s) who contributed to the resource but who are not directly responsible for its creation.|
|Y||N||Entity responsible for making the resource available.|
The date of the resource in ISO 8601 format. Displays the date in human-readable format. For uncertain or approximate dates use the Extended Date/Time Format extension to ISO 8601 (notes on our local implementation of EDTF).
|Y||N||A free-text description of the content of the dataset. The abstract from a related publication may be used.|
|abstract ||[not displayed]||http://purl.org/dc/terms/abstract||0-1||Y||N|
A free text description of the collection, to display on the collection level portal page. Not used on item level records.
Subject headings or keywords, preferably from a controlled vocabulary or thesaurus such as Library of Congress Subject Headings (LCSH) or Medical Subject Headings (MeSH).
Use to create a facet/browse lists for local headings of importance within a collection or set of collections.
This field may be used for configured collections only. The label used may be defined at the collection-level.
Terms indicating the spatial characteristics of the dataset, if applicable. Use Library of Congress Subject Headings, using broad and narrow terms separated with pipes, rather than as single constructed vales. E.g., use 'United States| New York (State)| New York (N.Y.)', not 'United States–New York (State)–New York (N.Y.).
Note: For locations the resource is about, use the Subject field.
|Y||N||The ISO 639-2 code representing the language of the resource. UI displays the human-readable label.|
|type||Type||http://purl.org/dc/terms/type||1-n||Y||N||One or more values from the DCMI Type vocabulary|
|The physical medium or genre of the resource. Use the Art & Architecture Thesaurus to choose appropriate term(s). |
The material or physical carrier of the resource.
|Y||N||The size or duration of the resource. E.g., number of pages or volumes, or length of recording.|
|Y||N||Identifiers external to the repository used to identify the resource. Displays with Local ID and ARK values in the UI with label "Identifier".|
|series||Series||http://library.duke.edu/metadata/terms/series||0||Y||Y||The series title from the collection guide.|
|Y||N||One URI from either:|
Use the URI itself (e.g., https://creativecommons.org/licenses/by/4.0/) - the application will render the human-readable text and graphic elements.
See Rights Management Metadata for detailed information.
Use to store a free-text statement about the rights status of the resource. May not be in conflict with the required rights statement stored in the Rights field.
See Rights Management Metadata for detailed information.
|Y||N||Free text statement relating to ownership and custody of the resource.|
|Y||N||Use to store references or links to related resources. If the related resource is a DDR object, storing the ARK will enable the functionality which displays thumbnails and links to related repository resources from object records.|
|N||N||Use to store references or links to resources that are substantially the same as the resource, but in different formats. If the resource is a DDR object, storing the ARK will enable the functionality which displays thumbnails and links to related repository resources from object records.|
|Y||Y||Use to store references or links to resources that are a logical or physical part of an entity. If the resource is a DDR object, storing the ARK will enable the functionality which displays thumbnails and links to related repository resources from object records.|
|Y||Y||Use to store references or links to resources that are a logical or physical part of the resource being described. If the resource is a DDR object, storing the ARK will enable the functionality which displays thumbnails and links to related repository resources from object records.|
|sponsor||Sponsor||http://library.duke.edu/metadata/terms/sponsor||0||Y||N||Used to record free text statement indicating sponsorship of the digital collection.|
|admin_set ||[not displayed]||http://repository.lib.duke.edu/vocab/asset/adminSet||1||N||N||Used at the collection level. Always 'DC' to ensure resource is part of Digital Collections.|
|ead_id ||Source Collection||http://repository.lib.duke.edu/vocab/asset/eadId||1||Y||N||The EAD ID is stored but the human-readable title of the archival collection is displayed. At the collection level, the EAD ID enables the 'Source Collection' inset. At the item or component level, enables the 'Source Collection' feature in the sidebar, as well as the link in the metadata record.|
The ArchivesSpace identifier corresponding to the appropriate component level for the resource as represented in the collection guide. Enables the 'View item in context' feature in sidebar as well as for item and component level objects.
PLEASE NOTE: The 'View item in context' link will only render if both ASPACE ID and EAD ID values are present. Additionally, both values must be present for links from collection guides to DDR objects to work.
Stores the DPC ID (item level) or collection slug (collection level - use the same value as ead_id when applicable), which is used to construct a custom URL. The DPC folder ingest process dictates that a local_id must be set on items/components.
If no local_id is present, the PID will appear in the URL.
Local IDs do not have to be unique.
|research_help_contact ||[not displayed]||http://repository.lib.duke.edu/vocab/contact/assistance||1||N||N||Used at the collection level. Enables the center/unit name and contact information to display on the collection portal page.|
|aleph_id ||[not displayed]||http://repository.lib.duke.edu/vocab/asset/alephId||0||N||N||The presence of a value in the aleph_id field triggers the presence of the 'View Details (Catalog)' feature in the sidebar, which links to the resource's catalog record.|
|display_format||[not displayed]||http://repository.lib.duke.edu/vocab/display/format/||1||N||N||Enables the appropriate image viewer/player in the Blacklight/public interface. More information: Display Format Field|