The DDR metadata application profile is based on Dublin Core Metadata Terms along with a set of locally-defined fields.
Depositors to the DDR may use the metadata fields as described below. If a depositor has a need for a field not defined below, they may request a consultation with the MAG to consider alternatives. Please note: alterations to the DDR metadata application profile are carefully considered and infrequent.
In addition to the fields listed below, a system-provided ARK is assigned to all repository objects. This identifier is used to construct the permalink to that object. DOIs may be assigned when requested.
Other administrative metadata fields are enumerated here.
All fields listed below may be used to describe any DDR resource. Mandatory fields are indicated in bold.
DC: Digital Collections
|1||Required; Not repeatable|
|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).
Note: the type of date recorded depends on the context - for Research Data, this field records the date the resource was made available in the DDR. For Digital Collections, this field records the creation date of the original resource.
|Y||N||Free-text description of the resource.|
Terms indicating what the resource is about. Choose headings from Library of Congress Subject Headings or other appropriate authoritative source.
|Y||Y||Use to create a facet/browse lists for local headings of importance within a collection or set of collections.|
|spatial||Location; Spatial Coverage||http://purl.org/dc/terms/spatial|
The location where the resource was created, or terms describing spatial characteristics of the resource. 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. Displays the human-readable label.|
|Y||N||One or more values from the DCMI Type vocabulary|
The file format, physical medium, or dimensions of the resource.
For RDMP, record the file format.
For DC, 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.|
|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".|
|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.
|Y||N||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.|
|Y||N||Free text statement relating to ownership and custody of the resource.|
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.
When the value is a LibGuide url placed on a collection level object, eg, 'https://guides.library.duke.edu/...', a link to it labeled 'Research Guide' will appear on the collection page below the 'Browse all items' button.
|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.|
The fields listed below are specific to objects in the Digital Collections & Rubenstein Library collecting areas.
Depositors may prefer to consult Digital Collections Metadata, which provides a full list of fields and documentation specific to Digital Collections in the DDR.
|ead_id||Source Collection||http://repository.lib.duke.edu/vocab/asset/eadId||1||N||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.
|series||Series||http://library.duke.edu/metadata/terms/series||0||Y||Y||The series title from the collection guide.|
The Digital Production Center (DPC)-provided identifier for the object.
PLEASE NOTE: Collection and item objects in the Digital Collections admin set MUST have local_ids set prior to publication of the collection.
Additionally, while it is technically possible to change a collection-level local_id after it has been set, developer intervention will be required to ensure all links to items in that collection will function properly. Therefore, it is important that the collection-level local_id be firm before it is set on the object.
|sponsor||Sponsor||http://library.duke.edu/metadata/terms/sponsor||0||Y||N||Used to record free text statement indicating sponsorship of the digital collection.|
|product||Product||http://library.duke.edu/metadata/terms/product||0-n||Y||Y||Used for Advertising collections; records the product depicted in advertisement.|
|company||Company||http://library.duke.edu/metadata/terms/company||0-n||Y||Y||Used for Advertising collections; records the company responsible for advertisement.|
|headline||Headline||http://library.duke.edu/metadata/terms/headline||0-n||Y||N||Used for Advertising collections; records the headline on advertisement.|
|publication||Publication||http://library.duke.edu/metadata/terms/publication||0-n||Y||Y||Used for Advertising collections; records the publication in which the advertisement was placed.|
|tone||Tone||http://library.duke.edu/metadata/terms/tone||0||Y||Y||Used for Advertising collections (specifically outdoor advertising); records whether advertisement is in black-and-white or color.|
|setting||Setting||http://library.duke.edu/metadata/terms/setting||0||Y||Y||Used for Advertising collections (specifically outdoor advertising); records whether advertisement is in a rural or urban setting.|
|placement_company||Placement Company||http://library.duke.edu/metadata/terms/placement_company||0-n||Y||Y||Used for Advertising collections (specifically outdoor advertising); records the company responsible for placing the billboard.|