Element Description
Represents Internet sites that contain information related to the data, as well as related Internet sites such as project home pages, related data archives/servers, metadata extensions, online software packages, web mapping services, and calibration/validation data.
Best Practices
<>
Examples:
<>
Element Specification
An unlimited amount of Related URLs may be listed (Cardinality: 0..*)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | RelatedUrls/URL | String | n/a | 1 - 1024 characters | Yes | 1 | The GET DATA URL should point the user to a location where data files may be directly downloaded. |
UMM-Common | RelatedUrls/Description | String | n/a | 1 - 4000 characters | No | 0..1 | It is strongly recommended that a description be provided for each URL. |
UMM-Common | RelatedUrls/URLContentType | Enumeration | CollectionURL PublicationURL DataCenterURL DistributionURL DataContactURL VisualizationURL | n/a | Yes | 1 | "DistributionURL" is the only valid option for links used to obtain the data. |
UMM-Common | RelatedUrls/Type | String | KMS controlled | n/a | Yes | 1 | "GET DATA" should be provided as the Type. |
UMM-Common | RelatedUrls/Subtype | String | KMS controlled | n/a | No | 0..1 | The Type and Subtype are part of a keyword hierarchy specified in the KMS. Any Subtype listed get after GET DATA in the keyword list is a valid option. If none of the available Subtypes are appropriate for the URL, then it is okay to leave the Subtype field blank. |
UMM-Common | RelatedUrls/GetData/Format | String | KMS controlled | n/a | Yes | 1 | Are we keeping this field? The format of the data provided via the associated URL. |
UMM-Common | RelatedUrls/GetData/MimeType | String | KMS controlled | n/a | No | 0..1 | The mime type of the associated URL. |
UMM-Common | RelatedUrls/GetData/Size | Number | n/a | n/a | Yes | 1 | Really only makes sense to provide if the link is a direct download. Is this going to remain a required field? The size of the data obtained via the associated URL. |
UMM-Common | RelatedUrls/GetData/Unit | Enumeration | KB MB GB TB PB | n/a | Yes | 1 | Really only makes sense to provide if the link is a direct download. Is this going to remain a required field? Unit is required if information is provided in the 'Size' element. |
UMM-Common | RelatedUrls/GetData/Fees | String | n/a | 1 - 80 characters | No | 0..1 | The fee (if any) for ordering the data. The fee should be a number in U.S. dollars. |
UMM-Common | RelatedUrls/GetData/Checksum | String | n/a | 1 - 50 characters | No | 0..1 | Does it only make sense to provide a checksum if the link directly downloads a file? Or should you provide one if the link just takes you to another web page e.g. a 'data tree' type of page? Would like to provide some guidelines for when use of this field is encouraged. |
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
UMM Migration
None
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | <> |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 6/13/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |