The DOI element stores the DOI (Digital Object Identifier) that identifies the collection. The DOI organization that is responsible for creating the DOI is described in the Authority element. The DOI/MissingReason element can be used for datasets that do not have a DOI or which use a different type of persistent identifier.
Just the DOI string should be provided in the 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:
DOI Examples:
"10.5067/ISS/CATS/L2O_N-M7.1-V2-01_05KMPRO"
"10.5067/MEASURES/GWELD/GWELDYR.003"
"10.5067/3UGE8WQXZAOK"
Missing DOI Examples:
"The collection is near real time and only exists for a couple of days, therefore, the collection was not assigned a DOI."
"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."
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | Version | String | ? maximum number of characters | Yes | 1 |
Priority Categorization | Justification |
---|---|
This element is categorized as highest priority when:
| |
Not applicable | |
Not applicable | |
The element is provided, and follows all applicable criteria specified in the best practices section above. |
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
DIF 10
Enumeration Mapping N/A Example Mapping
|
ECHO 10
Enumeration Mapping N/A Example Mapping
|
ISO 19115-2 MENDS
Enumeration/Code List Mapping N/A Example Mapping
|
ISO 19115-2 SMAP
Enumeration/Code List Mapping N/A Example Mapping
|
None
|
Version | Date | What Changed |
---|---|---|
1.0.0 | Initial Release |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 4/18/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |