Element Description
Choice of:
DOI/DOI: The DOI element stores the DOI (Digital Object Identifier) that identifies the collection.
DOI/Authority: The DOI organization that is responsible for creating the DOI is described in the Authority element.
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.
Best Practices
Just the DOI string should be provided in the DOI/DOI field. The DOI URL should not be stored here; it should be stored as a RelatedURL. The DOI value should start with the directory indicator.
For ESDIS providers:
- The directory indicator for ESDIS is "10"
- If the DOI was registered through ESDIS, the beginning of the DOI string should be "10.5067"
- The DOI/Authority element value should be "https://doi.org/"
- 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. In the case that a DOI is not applicable for a dataset, the DOI/MissingReason element should be used to indicate this; and the DOI/Explanation element should be used to describe why the dataset was not assigned a DOI.
- A list of DOIs registered through ESDIS can be found here: EOSDIS DOIs Status and Listing
Examples:
DOI/DOI: "10.5067/ISS/CATS/L2O_N-M7.1-V2-01_05KMPRO"
DOI/Authority: "https://doi.org/"
DOI/DOI: "10.5067/MEASURES/GWELD/GWELDYR.003"
DOI/Authority: "https://doi.org/"
or
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."
Element Specification
Choice of:
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | DOI/DOI | String | ? maximum number of characters | Yes | 1 |
UMM-C | DOI/Authority | String | ? maximum number of characters | No | 0..1 |
or
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality |
---|---|---|---|---|---|---|
UMM-C | DOI/MissingReason | Enumeration | Not Applicable | N/A | Yes | 1 |
UMM-C | DOI/Explanation | String | N/A | ? maximum number of characters | No | 0..1 |
ARC Priority Matrix
Priority Categorization | Justification |
---|---|
This element is categorized as highest priority when:
| |
This element is categorized as medium priority when:
| |
This element is categorized as low priority when:
| |
The element is provided, and follows all applicable criteria specified in the best practices section above. |
Dialect Mappings
UMM Migration
None
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.0.0 | Initial Release |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 4/18/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |