Research Data Metadata - DEPRECATED

**AS OF OCTOBER 2018 - THIS DOCUMENT HAS BEEN SUPERCEDED BY XXXX **


Scope

This document describes the required and recommended metadata fields for research data materials for deposit in the Duke Digital Repository. These fields are intended for description of the data package as a whole, but elements may be propagated down to items within that package if desired.

PLEASE NOTE: This document describes the metadata profile to be used in the DDR platform, NOT the Hyrax-based RDR. For that metadata profile, see this document.

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.


FieldLabelPredicateObligationShowFacetUsage Guidelines
titleTitlehttp://purl.org/dc/terms/title

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

0-n

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

1-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

 0-n

YYPerson(s) or organization(s) who contributed to the resource but who are not directly responsible for its creation.
affiliationAffiliationhttp://repository.lib.duke.edu/vocab/asset/affiliation0-nYYDepartmental or other campus affiliation of the creator(s). Note: values for this field are maintained here; please leave a comment if you wish to amend a value in or add a value to the list. Non-Duke organizational affiliations are maintained in the tab labeled "NON-DUKE AFFILIATIONS"
publisherPublisherhttp://purl.org/dc/terms/publisher

1

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

 1

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

This field records the date the resource was made available in the DDR.

temporalTemporalhttp://purl.org/dc/terms/temporal0YYThe dates of data collection.
descriptionDescriptionhttp://purl.org/dc/terms/description

1-n

YNA free-text description of the content of the dataset. The abstract from a related publication may be used.
subjectSubjecthttp://purl.org/dc/terms/subject

0-n

YY

Subject headings or keywords, preferably from a controlled vocabulary or thesaurus such as Library of Congress Subject Headings (LCSH) or Medical Subject Headings (MeSH).

spatialLocation; Spatial Coveragehttp://purl.org/dc/terms/spatial

0-n

YY

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.

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

 0-n

YNThe ISO 639-2 code representing the language of the resource. UI displays the human-readable label.
typeTypehttp://purl.org/dc/terms/type1-nYNOne or more values from the DCMI Type vocabulary
formatFormathttp://purl.org/dc/terms/format

0-n

Y

Y

The file format(s) of the resource.

relationRelated materialshttp://purl.org/dc/terms/relation

0-n

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

1

YNOne URI from Creative Commons Licenses

Use the URI itself (e.g., https://creativecommons.org/licenses/by/4.0/) - the application will render the human-readable text and graphic elements.

provenanceProvenancehttp://purl.org/dc/terms/provenance

0-n

YNFree text statement relating to ownership and custody of the resource.
citationCitationhttp://purl.org/dc/terms/bibliographicCitation1YNCitation in the following format (per DataCite guidelines): Creator (Date): Title. Publisher. Identifier (permalink)