Page History

Element Description

This element stores the DOI (Digital Object Identifier) that identifies the data collection.   A DOI is a persistent identifier that is used to uniquely identify objects including datasets and documents.

This element also includes the option options to provide information on the authority that registers the DOI, as well as the DOI of the previous version of the record. 

Best Practices

For the DOI concept, there are two options for providing information. These options are:

DOI/DOI: The DOI (Digital Object Identifier) that identifies the collection.

DOI/Authority:  The The DOI organization that is responsible for creating the DOI.

or

DOI/MissingReason: This element stores the fact that a DOI is not applicable for a record. 

DOI/Explanation: This element describes the reason the DOI is not applicable.

For DOI/DOI and DOI/Authority

PreviousVersion: The previous version of this record's DOI, if applicable. Its sub elements are:

• DOI/PreviousVersion/DOI: The previous version of this record's DOI. - If the PreviousVersion element is used, then the DOI must be provided.
• DOI/PreviousVersion/Version: The version number if one exists.
• DOI/PreviousVersion/Description: A short description of what the DOI represents
• DOI/PreviousVersion/Published: The date or date and time the previous version was published.

or

DOI/MissingReason: This element stores the fact that a DOI is not applicable for a record. 

DOI/Explanation: This element describes the reason the DOI is not applicable.

For DOI/DOI and DOI/Authority

DOI/DOIDOI/DOI:

• • When providing information in the DOI/DOI field, only the DOI string should be provided.  The string value should begin with the directory indicator.
  • The DOI URL should not be stored in the DOI element but should instead be provided as a RelatedURL.
  • For ESDIS providers specifically:
    
    • DOI is a required metadata element for ESDIS providers. While the majority of ESDIS datasets will have a DOI, there are certain cases where having a DOI is not appropriate. These cases include near real time datasets and datasets that will soon be replaced by a new version. Please see the DOI/MissingReason and DOI/Explanation section for more information.
    • More details on the ESDIS DOI process can be found here: ESDIS DOI Process
    • A list of DOIs registered through ESDIS can be found here: EOSDIS ESDIS DOIs Status and Listing
    • The directory indicator for ESDIS is "10." Therefore, if the DOI was registered through ESDIS, the beginning of the DOI string should be "10.5067". 

DOI/Authority:

• • For ESDIS providers specifically:
    • The DOI/Authority element value should be "https://doi.org/"

DOI/PreviousVersion/DOI:

• • When providing information in the DOI/DOI field, only the DOI string should be provided.  The string value should begin with the directory indicator.
  • The DOI URL should not be stored in the DOI element but should instead be provided as a RelatedURL.

Examples:

DOI/DOI: "10.5067/ISS/CATS/L2O_N-M7.1-V2-01_05KMPRO",

DOI/Authority: "https://doi.org/",

DOI/PreviousVersion: {

DOI: "10.5067/MEASURESISS/GWELD/GWELDYR.003"CATS/L2O_N-M7.1-V1-01_05KMPRO,

Version: "1-01",

Description: "Cloud-Aerosol Transport System (CATS) International Space Station (ISS) Level 2 Operational Day Mode 7.1 Version 1-01 5 km Profile data product.",

Published: 2015-01-01T08:00:00}

DOI/DOI: "10.5067/MEASURES/GWELD/GWELDYR.003"

DOI/Authority: "httpsDOI/Authority: "https://doi.org/"

For DOI/MissingReason and DOI/Explanation

DOI/MissingReason:

• • This element should only be used for specific cases where assigning a DOI to a dataset is not appropriate. These cases include near real time datasets, provisional datasets, and datasets that will soon be replaced by a new version.
  • This element is controlled by the enumeration value "Not Applicable."

DOI/Explanation:

• • For translation purposes, a value of "Unknown" is provided for data sets that do not have a DOI or a MissingReason set.

DOI/Explanation:

• • This element should be used to describe why a dataset was not assigned a DOI.

Examples:

DOI/MissingReason: "Not Applicable"

DOI/Explanation: "The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI."

DOI/MissingReason: "Not Applicable"

DOI/Explanation: "A new version of this dataset will be released in a month (May 2018). This version will be removed from CMR, and the new version will be assigned a DOI."

AssociatedDOIs also exist so that data providers can add DOIs from either parent or other associated collections.  This allows users to cite a group of data products. 

or

ARC Priority Matrix

This element is categorized as highest priority when:

• The element is not included at all.
• The element is included but is empty.
• The dataset has a DOI but the metadata indicates that it does not.
• The incorrect DOI is listed for the dataset.
• The DOI listed leads to a broken link.
• The DOI is provided in the incorrect format (e.g. as a URL rather than just the DOI string).
• The DOI/Explanation includes spelling or grammatical errors.

This element is categorized as medium priority when:

• The DOI/MissingReason option is used but no DOI/Explanation is provided.

This element is categorized as low priority when:

• A DOI is provided but the DOI/Authority element is not provided.

Dialect Mappings

or

Note: only 1 DOI or DOI/MissingReason may be provided (Cardinality: 1)

Metadata Validation and QA/QC

All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).

Please see the expandable sections below for flowchart details.

Dialect Mappings

DIF 10

Choice of:

or

Enumeration Mapping

Example Mapping

<Dataset_Citation>
 ...
  <Persistent_Identifier>
    <Type>DOI</Type>
    <Identifier>10.5067/IAGYM8Q26QRE</Identifier>
    <Authority>https://doi.org/</Authority>
  </Persistent_Identifier>
</Dataset_Citation>

or

<Dataset_Citation>
 ...
  <Persistent_Identifier>
    <MissingReason>Not Applicable</MissingReason>
    <Explanation>The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI.</Explanation>
  </Persistent_Identifier>
</Dataset_Citation>

"DOI": {
  "DOI" : "10.5067/IAGYM8Q26QRE",
  "Authority" : "https://doi.org/"
},

or

"DOI": {
  "MissingReason" : "Not Applicable",
  "MissingExplanation" : "The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI."
},

ECHO 10

Choice of:

or

 or

Enumeration Mapping

Example Mapping

<DOI>
  <DOI>10<Dataset_Citation>
 ...
  <Persistent_Identifier>
    <Type>DOI</Type>
    <Identifier>10.5067/IAGYM8Q26QRE</DOI>Identifier>
    <Authority>https://doi.org/</Authority>
  </DOI>Persistent_Identifier>
</Dataset_Citation>

or

<DOI><Dataset_Citation>
 ...
  <Persistent_Identifier>
    <MissingReason>Not Applicable</MissingReason>
    <Explanation>The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI.</Explanation>
  </Persistent_Identifier>
</DOI>Dataset_Citation>

"DOI": {
  "DOI" : "10.5067/IAGYM8Q26QRE",
  "Authority" : "https://doi.org/"
},

or

"DOI": {
  "MissingReason" : "Not Applicable",
  "MissingExplanation" : "The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI."
},

String