DDR Metadata Application Profile

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.

Cross-Repository Fields

All fields listed below may be used to describe any DDR resource. Mandatory fields are indicated in bold. 

*Obligation Key:

DC: Digital Collections

1Required; Not repeatable
1-nRequired; Repeatable
0Optional
0-nOptional; Repeatable
FieldLabelPredicateObligation*ShowFacetUsage Guidelines
titleTitlehttp://purl.org/dc/terms/title

DC 1

YNFree text name of the resource.
alternativeAlternative Titlehttp://purl.org/dc/terms/alternative

DC 0-n

YNAlternate free text name of the resource, often used for translated titles.
creatorCreatorhttp://purl.org/dc/terms/creator

DC 0-n

YY

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.


contributorContributorhttp://purl.org/dc/terms/contributor

DC 0-n

YYPerson(s) or organization(s) who contributed to the resource but who are not directly responsible for its creation.
publisherPublisherhttp://purl.org/dc/terms/publisher

DC 0-n

YNEntity responsible for making the resource available.
dateDatehttp://purl.org/dc/terms/date

DC 0-n

YY

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.

descriptionDescriptionhttp://purl.org/dc/terms/description

DC 0-n

YNFree-text description of the resource.
subjectSubjecthttp://purl.org/dc/terms/subject

DC 0-n

YY

Terms indicating what the resource is about. Choose headings from Library of Congress Subject Headings or other appropriate authoritative source.

category[custom]http://library.duke.edu/metadata/terms/category

DC 0-n

YYUse to create a facet/browse lists for local headings of importance within a collection or set of collections.
spatialLocation; Spatial Coveragehttp://purl.org/dc/terms/spatial


DC 0-n

YY

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.

languageLanguagehttp://purl.org/dc/terms/language

DC 0-n

YNThe ISO 639-2 code representing the language of the resource. Displays the human-readable label.
typeTypehttp://purl.org/dc/terms/type

DC 1-n

YNOne or more values from the DCMI Type vocabulary
formatFormathttp://purl.org/dc/terms/format

DC 0-n

Y

Y


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).

mediumMediumhttp://purl.org/dc/terms/medium

DC 0-n

YN

The material or physical carrier of the resource.


extentExtenthttp://purl.org/dc/terms/extent

DC 0-n

YNThe size or duration of the resource.
identifierIdentifierhttp://purl.org/dc/terms/identifier

DC 0-n

YNIdentifiers external to the repository used to identify the resource. Displays with Local ID and ARK values in the UI with label "Identifier".
rightsRightshttp://purl.org/dc/terms/rights

DC 1

YNOne 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.

rights_noteRights Notehttp://repository.lib.duke.edu/vocab/asset/rightsNote

DC 0-n

YNUse 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.
provenanceProvenancehttp://purl.org/dc/terms/provenance

DC 0-n

YNFree text statement relating to ownership and custody of the resource.
relationRelated materialshttp://purl.org/dc/terms/relation

DC 0-n

YN

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.

isFormatOf[custom]http://purl.org/dc/terms/isFormatOf

DC 0-n

NNUse 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.
isPartOf[custom]http://purl.org/dc/terms/isPartOf

DC 0-n

YYUse 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.
hasPart[custom]http://purl.org/dc/terms/hasPart

DC 0-n

YYUse 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.


Digital Collections/Rubenstein Library Fields

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.

FieldLabelPredicateObligationShowFacetUsage Guidelines
ead_idSource Collectionhttp://repository.lib.duke.edu/vocab/asset/eadId1NNThe 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.
aspace_id[not displayed]http://repository.lib.duke.edu/vocab/asset/archivesSpaceId0NN

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.

seriesSerieshttp://library.duke.edu/metadata/terms/series0YYThe series title from the collection guide.
local_idIdentifier

http://id.loc.gov/vocabulary/identifiers/local

1YN

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.

sponsorSponsorhttp://library.duke.edu/metadata/terms/sponsor0YNUsed to record free text statement indicating sponsorship of the digital collection.
productProducthttp://library.duke.edu/metadata/terms/product0-nYYUsed for Advertising collections; records the product depicted in advertisement.
companyCompanyhttp://library.duke.edu/metadata/terms/company0-nYYUsed for Advertising collections; records the company responsible for advertisement.
headlineHeadlinehttp://library.duke.edu/metadata/terms/headline0-nYNUsed for Advertising collections; records the headline on advertisement.
publicationPublicationhttp://library.duke.edu/metadata/terms/publication0-nYYUsed for Advertising collections; records the publication in which the advertisement was placed.
toneTonehttp://library.duke.edu/metadata/terms/tone0YYUsed for Advertising collections (specifically outdoor advertising); records whether advertisement is in black-and-white or color.
settingSettinghttp://library.duke.edu/metadata/terms/setting0YYUsed for Advertising collections (specifically outdoor advertising); records whether advertisement is in a rural or urban setting.
placement_companyPlacement Companyhttp://library.duke.edu/metadata/terms/placement_company0-nYYUsed for Advertising collections (specifically outdoor advertising); records the company responsible for placing the billboard.