Links to information related to the data.
The Related URLs metadata elementa allows for the linkage of a metadata record to external resources or locations on the web. When used properly, this element allows users to quickly and easily access data, as well as relevant services and information about the data. At a minimum, the Related URLs section of the metadata should point to:
Several of the elements within the Related URLs section of the metadata serve to properly identify purpose of the link. When combined, these elements should provide the user with a good idea of where the URL will link to. These identifying elements include:
URL Content Type: The URL Content Type
URL Type:
URL Subtype:
Description: While not required, it is highly recommended that a description be provided for each URL provided in the metadata. The description should be kept brief and explain to the user where the link will take them. Descriptions should be unique to the link. While descriptions can be repeated for the same type of link across different metadata records, it is generally advised that the same description not be repeated within the same metadata record. I.e. the description should be used to further differentiate two URLs with the same URL Type and Subtype.
Examples:
<>
An unlimited amount of Related URLs may be listed (Cardinality: 1..*)
Only provide element specification tables on specific URL pages? E.g. Get data URLs wiki page?
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | RelatedUrls/URL | String | n/a | 1 - 1024 characters | Yes | 1 | |
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 | The DataCenterURL option is only valid in the Data Centers section of the metadata. The DataContactURL option is only valid in the Data Contacts section of the metadata. |
UMM-Common | RelatedUrls/Type | String | KMS controlled | n/a | Yes | 1 | Each Type keyword corresponds to a specific URL Content Type category. |
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. |
UMM-Common | RelatedUrls/GetData/Format | String | KMS controlled | n/a | Yes, if applicable | 1 | Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetData/MimeType | String | KMS controlled | n/a | No | 0..1 | Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetData/Size | Number | n/a | n/a | Yes, if applicable | 1 | Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetData/Unit | Enumeration | KB MB GB TB PB | n/a | Yes, if applicable | 1 | Unit is required if information is provided in the 'Size' element. Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
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. Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
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. Only applies to DistributionURLs with the URL Type of "GET DATA". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/Format | String | KMS controlled | n/a | No | 0..1 | Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/MimeType | String | KMS controlled | n/a | Yes, if applicable | 1 | Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/Protocol | Enumeration | HTTP HTTPS FTP FTPS Not Provided | n/a | Yes, if applicable | 1 | It is recommended that use of FTP and FTPS be phased out if possible. Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/FullName | String | n/a | 1 - 80 characters | Yes, if applicable | 1 | Are we keeping the full name field? Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/DataID | String | n/a | 1 - 80 characters | Yes, if applicable | 1 | Are we keeping the data ID field? "The data identifier of the data provided by the service." Typically, this is a file name. ← Providing a file name would only make sense for direct download Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/DataType | String | n/a | 1 - 80 characters | Yes, if applicable | 1 | Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
UMM-Common | RelatedUrls/GetService/URI | Array Composed of at least 1 String | n/a | 1 - 1024 characters (per string) | No | 0..* | Only applies to DistributionURLs with the URL Type of "USE SERVICE API". Please see the "???" wiki page for full details and examples. |
Will create separate wiki page for get data and get service links. DataCenterURLs and DataContactURLs details will be worked into the data center and data contact wiki pages.
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.
<> |
ARC Automated Rules <insert> |
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
DIF 10
Enumeration Mapping
Example Mapping
|
ECHO 10
Example Mapping
|
ISO 19115-2 MENDS
Enumeration/Code List Mapping
Example Mapping
|
ISO 19115-2 SMAP
Example Mapping
|
None
ISO 19115-1
|
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | <> |
1.9.0 |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 6/13/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |