Page History
Table of Contents | ||
---|---|---|
|
Element Description
The Related URLs element, when accompanied by the 'get data' sub-elements, is used to link directly to a data access point. This is different from a GET USE SERVICE API URL, which relates to methods of sub-setting and/or transforming data before obtaining it. For details concerning GET USE SERVICE API URLs, please see the Related URLs (GET USE SERVICE API) wiki page.
For general Related URL guidance (not specific to data access links), please refer to the Related URLs wiki page.
Best Practices
The GET DATA Related URL metadata element allows for the linkage of a metadata record to a location on the web where data may be directly accessed. As mentioned on the Related URLs wiki page, there are several sub-elements which are used to identify the purpose of the URL. For GET DATA links specifically, best practices for these elements include:
URL Content Type: The URL Content Type is a keyword which, at a high level, describes the content of a link. This is a controlled vocabulary field maintained as an enumeration list within the UMM-Common schemaKeyword Management System (KMS). For GET DATA URLs, the URL Content Type should always be "DistributionURL".
URL Type: The URL Type is a keyword which specifies the content of a link. URL Type keywords are maintained in the Keyword Management System (KMS). For GET DATA URLs, the URL Type should always be "GET DATA".
URL Subtype: The URL Subtype is a keyword which further specifies the content of a link. Together, the URL Type and Subtype keywords create a keyword hierarchy which is used to identify the URL. Providing a Subtype for GET DATA URLs is optional, but should be used when applicable. Currently (as of 7/25/2018) the following Subtype keywords are valid under GET DATA: <insert list> Should we include examples/ a brief description of each subtype?Subtype keywords can be found in the URL Content Type keyword list. For access links, any Subtype keyword after GET DATA is a valid option.
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 that the link goes to a data access point. The descriptions should be unique to the link. While descriptions can be repeated for the same type of URL 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 GET DATA URLs with the same URL Type and Subtype.
A GET DATA URL is required for all NASA data sets. For NASA EOSDIS data, data access should be behind URS authentication. For NASA EOSDIS data, it is also recommended that data access not be provided via FTP protocol, in favor of the HTTPS protocol.
There are several sub-elements specifically designated for GET DATA URLs. The following provides definitions and best practices for each of the sub-elements:
RelatedUrls/GetData/Format: The format of the data provided via the associated URL.
Providing the format is required??Format is an optional sub-field. Format is a controlled vocabulary field and should be chosen from the
<insert GCMD data format keyword list>GCMD Data Format Keyword List. If data is provided in a compressed file format
, recommend listing(e.g. .zip, .tar), it is recommended that the format of the data once it is uncompressed be provided.
RelatedUrls/GetData/MimeType:
The mime type of the associated URL. Mime Type is aMIME stands for "Multipurpose Internet Mail Extensions". Mime types are used to identify the nature and format of files provided on the Internet, and are typically used by internet browsers in order to determine how to properly process or display a document or file. Providing the Mime Type element in the metadata helps ensure that the URL contents will be properly displayed on the Web. Mime Type is an optional sub-field. Mime Type is a controlled vocabulary field and should be chosen from
the <insert GCMD mime type keyword list>. Providing a Mime Type is optional.the GCMD Mime Type Keyword list.
RelatedUrls/GetData/
SizeFees: The fee (if any) for ordering the data. The fee should be a number in U.S. dollars. This is an optional field.
The following GET DATA sub-elements only apply when the data access Really only makes sense to provide if the link is a direct download. Is this going to remain a required field? RelatedUrls/GetData/Unit: Really only makes sense to provide if the link is a direct download . Is this going to remain a required field?
RelatedUrls/GetData/Fees: The fee (if any) for ordering the data. The fee should be a number in U.S. dollars. This is an optional field.
RelatedUrls/GetData/Checksum: 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.
Examples:
URL: https://hydro1.gesdisc.eosdis.nasa.gov/data/FLDAS/FLDAS_VIC025_C_EA_M.001/
URL Content Type: DistributionURL
URL Type: GET DATA
URL Subtype: DATA TREE
Description: Use the link to access the data via HTTPS. Files are organized by date.
Format: NetCDF-4
Mime Type: text/html
Size: Is this element getting updated?
Unit: MB
Fees: 0
URL: https://daac.ornl.gov/cgi-bin/download.pl?ds_id=465&source=dsviewer
URL Content Type: DistributionURL
URL Type: GET DATA
URL Subtype: DIRECT DOWNLOAD
Description: Downloads the NPP Boreal Forest: Canal Flats, Canada, 1984, R1 data set directly to your workstation.
Format: Text File
Size: 91.8
Unit: KB
Fees: 0
Checksum: f2 aa 78 d6 82 5e c4 2d 78 35 81 a8 d5 ea 1f 68
Element Specification
An unlimited amount of Related URLs may be listed (Cardinality: 0..*)
1 - 1024 characters
CollectionURL
PublicationURL
DataCenterURL
DistributionURL
DataContactURL
VisualizationURL
"DistributionURL" is the only valid option for links used to obtain the data.
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.
Are we keeping this field?
The format of the data provided via the associated URL.
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.
KB
MB
GB
TB
PB
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.
The fee (if any) for ordering the data. The fee should be a number in U.S. dollars.
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.
title | GCMD Metadata QA/QC |
---|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- A GET DATA URL is not provided in the metadata
- The link labeled as GET DATA is broken
- The link is mislabeled as GET DATA (i.e. the link serves a purpose other than data access)
- The GET DATA link is labeled incorrectly (i.e. a data access link is provided in the metadata but it is labeled as something else)
- The GET DATA link is provided via FTP
- The GET DATA link fails to take the user as directly as possible to the described data
- The URL Type or Subtype provided does not align with the KMS
- The Type or Subtype does not exist in KMS
- The Type or Subtype is placed in the incorrect position of the hierarchy (e.g. GET DATA should not be provided in the Subtype field, because it is categorized as a Type keyword in the KMS)
- There is an invalid Type/Subtype relationship (e.g. Type: GET DATA, Subtype: USER'S GUIDE, is not a valid combination in the KMS)
- The URL Type or Subtype provided does not accurately describe the link
- The mime type provided is incorrect
- The data format provided is incorrect
This element is categorized as medium priority when:
- The 'Description' element is left blank. It is highly recommended that a description be provided for each URL.
This element is categorized as low priority when:
- A description is repeated for multiple GET DATA URLs
ARC Automated Rules
<insert>
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
(i.e. when clicking on the URL results in an immediate download). For example, the following URL is a direct download (warning: clicking on this link will result in a file to be downloaded to your work space (203.6 MB). An Earthdata login is required to access the file): https://daac.ornl.gov/cgi-bin/download.pl?ds_id=1574&source=dsviewer
These GET DATA sub-elements include:
RelatedUrls/GetData/Size: The purpose of this element is to inform users of the size of the data that will be downloaded to their local work space if they click on the data access URL. This element only contains the numerical value of the size, not the unit. The unit (e.g. KB, MB, etc.) should be provided in the 'Unit' element.
RelatedUrls/GetData/Unit: The unit accompanying the size specified in the 'Size' element. Together, Size and Unit indicate the size of the data file(s) to be downloaded via the provided URL. Unit must be provided if 'Size' is provided. Unit is a controlled vocabulary field and must be selected from the following options: KB, MB, GB, TB, PB.
RelatedUrls/GetData/Checksum: A value used to verify the integrity of a file or a data transfer, such as the integrity of a downloaded file. The checksum provided in the metadata may be used to compare the original data file to the copy of the data downloaded to a user's local work space. The checksum provided in the metadata should be that of the original data file. The user is responsible for generating a checksum of the file on their local work space. If the checksum generated on their local work space does not match the checksum in the metadata (i.e. the original file), the data may have been altered or corrupted. Note that there are a variety of checksum algorithms available for use. Some examples include: MD5, CRC-8, CRC-16, CRC-32, Feltcher's checksum, Alder-32.
For NASA EOSDIS datasets:
- At least one GET DATA URL is required for all NASA EOSDIS datasets.
- For NASA EOSDIS data, data access should be behind Earthdata Login authentication.
- For NASA EOSDIS data, data access should not be provided via FTP, in favor of the HTTPS protocol.
Examples:
URL: https://hydro1.gesdisc.eosdis.nasa.gov/data/FLDAS/FLDAS_VIC025_C_EA_M.001/
URL Content Type: DistributionURL
URL Type: GET DATA
URL Subtype: DATA TREE
Description: Use the link to access the data via HTTPS. Files are organized by date.
Format: NetCDF-4
Mime Type: text/html
Fees: 0
URL: https://daac.ornl.gov/cgi-bin/download.pl?ds_id=465&source=dsviewer
URL Content Type: DistributionURL
URL Type: GET DATA
URL Subtype: DIRECT DOWNLOAD
Description: Downloads the NPP Boreal Forest: Canal Flats, Canada, 1984, R1 dataset directly to your workstation.
Format: Text File
Size: 91.8
Unit: KB
Fees: 0
Checksum: f2aa78d6825ec42d783581a8d5ea1f 68
Element Specification
Related URLs is a required metadata element. It is required that a data access point be provided in the metadata as a GET DATA URL. Multiple data access URLs may be provided (Cardinality: 1..*).
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 | Keyword Management System (KMS) | DistributionURL | n/a | Yes | 1 | "DistributionURL" is the only valid option for access links. |
UMM-Common | RelatedUrls/Type | String | GET DATA | KMS controlled | Yes | 1 | "GET DATA" should be provided as the Type. |
UMM-Common | RelatedUrls/Subtype | String | GCMD URL Content Type 'Subtype' Keywords | KMS controlled | 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 | GCMD Granule Data Format Keywords | KMS controlled | Yes | 1 | The format of the data provided via the associated URL. |
UMM-Common | RelatedUrls/GetData/MimeType | String | GCMD Mime Type Keywords | n/a | No | 0..1 | The mime type of the associated URL. |
UMM-Common | RelatedUrls/GetData/Size | Number | n/a | n/a | Yes | 1 | The size of the data obtained via the associated URL. Size should only be provided if clicking on the URL results in an immediate download. |
UMM-Common | RelatedUrls/GetData/Unit | Enumeration | KB MB GB TB PB | n/a | Yes | 1 | Unit is required if information is provided in the 'Size' element. Size and Unit should only be provided if clicking on the URL results in an immediate download. |
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 | Checksum should only be provided if clicking on the URL results in an immediate download. Note that there are a variety of checksum algorithms available for use. |
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).
Lucidchart rich-viewer false autofit true name Copy of Wiki Page Metadata Evaluation Workflow-1939-51df84 width 1102 pages-to-display id 98e5dc28-3252-4209-953f-66f1378e1cf4 align Left height 299
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
<> |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Rules URL: Information provided in the Related URLs/ URL element will be passed through the URL checker. Description: |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Related_URL is a required metadata element. It is required that a data access point be provided in the metadata as a GET DATA URL.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Constraints | Required in DIF 10? | Cardinality | Notes | DIF 10 | /DIF/Related_URL/URL | URI | No | 0..* | The GET DATA URL should point the user to a location where data files may be directly downloaded. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10 | /DIF/Related_URL/URL_Content_Type/Type | String | KMS controlled | No | 0..1 | "GET DATA" should be provided as the Type. | DIF 10 | /DIF/Related_URL/URL_Content_Type/Subtype | String | 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. | DIF 10 | /DIF/Related_URL/Description | String | No | 0..1 | It is strongly recommended that a description be provided for each URL. | DIF 10 | /DIF/Related_URL/Mime_Type | String | KMS controlled | No | 0..1 | DIF 10 | /DIF/Related_URL/Protocol | String | No | 0..1 | DIF 10 | /DIF/Related_URL/Title | String | No | 0..1 | DIF 10 | /DIF/Related_URL/Application_Profile | String | No | 0..1 | DIF 10 | /DIF/Related_URL/Function | String | No | 0..1 |
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
DIF 10
|
title | ECHO 10 |
---|
ECHO 10
1 - 1024 characters
1 - 80 characters
Translation
Direction
Example Mapping
Section | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Providing an Online Access URL is optional. However, it is strongly recommended that one be provided.
N/A Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSRelated URLs is a required metadata element. It is required that a data access point be provided in the metadata as a GET DATA URL. Multiple data access URLs may be provided (Cardinality: 1..*). Note: These ISO paths only apply to DistributionURLs. Please see the RelatedURLs wiki page for ISO guidance specific to other types of URLs. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Notes | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString | Where the DOI string is provided. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.doi | String | The value of "gov.nasa.esdis.umm.doi" should be provided here so that CMR can properly parse out the DOI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString contains DOI | String | The value must contain the string "DOI" so that CMR can properly identify and translate the DOI. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/gmd:title - empty element | String | Leave this element empty. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/gmd:date - empty element | String | Leave this element empty. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/ gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString | String | Provide the authority here. For ESDIS providers, recommend listing "https://doi.org" as the DOI authority. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:authority/gmd:CI_Citation/ gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="" = authority | Codelist | Choose the "authority" codelist value so that CMR can properly identify the DOI/Authority element. This codelist value does not directly map to a UMM element - choosing 'authority' indicates to CMR that the Authority element should be mapped. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO MENDS | Translation Direction | UMM | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
inapplicable | ↔ | Not Applicable | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Column | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
No Format |
Column | ||
---|---|---|
| ||
UMM
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString
String
Where the DOI string is provided.
UMM-C Element | ISO 19115-2 MENDS Path | Type | Notes |
---|---|---|---|
/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:linkage/gmd:URL | String | Where the access URL is provided. Maps to the UMM element RelatedUrls/URL. Note: This path only applies to DistributionURLs. | |
/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Description: " | String | Maps to the UMM element RelatedUrls/Description. It is highly recommended that a description be provided for each URL. * The character string should always start with the prefix "Description: " in order for CMR to properly parse out the URL description. | |
/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType: DistributionURL" | String | Maps to the UMM element RelatedUrls/URLContentType. Providing the URL Content Type is required in CMR. * For data access links, the character string should always read "URLContentType: DistributionURL" | |
/gmi:MI_Metadata/gmd: |
distributionInfo/gmd:MD_ |
Distribution/gmd: |
distributor/gmd: |
MD_ |
Distributor/ gmd: |
distributorTransferOptions/gmd:MD_ |
DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd: |
description/gco:CharacterString= |
"Type: GET DATA" | String | Maps to the UMM element RelatedUrls/Type. Providing the URL Type is required in CMR. * For data access links, the character string should always read "Type: GET DATA" |
/gmi:MI_Metadata/gmd: |
distributionInfo/gmd:MD_ |
Distribution/gmd: |
distributor/gmd: |
MD_ |
Distributor/ gmd: |
distributorTransferOptions/gmd:MD_ |
DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString |
="Subtype: " | String |
Maps to the UMM element RelatedUrls/Subtype. Providing a URL Subtype is optional, but is encouraged if an appropriate URL Subtype exists. URL Subtype is a GCMD controlled vocabulary field and must be selected from keywords in the KMS. Please see the best practices section (above) on guidance on choosing the correct URL Subtype. * The character string should always start with with the prefix "Subtype: " in order for CMR to properly parse out the URL Subtype. | |
/ |
gmi:MI_Metadata/gmd: |
distributionInfo/gmd:MD_ |
Distribution/gmd: |
distributor/gmd: |
MD_ |
Distributor/ gmd: |
distributorFormat/gmd:MD_ |
Format/gmd: |
name/ |
gco:CharacterString ="MimeType: " | String |
Leave this element empty.
Translation
Direction
Maps to the UMM element RelatedUrls/GetData/MimeType. Providing a mime type is optional. Mime Type is a GCMD controlled vocabulary field and should be selected from keywords in the KMS. * The character string should always start with with the prefix "MimeType: " in order for CMR to properly parse out the mime type. |
Enumeration/Code List Mapping
N/A
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Example Mapping
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
None
Future Mappings
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
ISO 19115-1 | ||||||||||||||
Specification | Path | Type | Notes | /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:code/gco:CharacterString | String | Where the DOI string is provided. | ||||||||
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:codeSpace = gov.nasa.esdis.umm.doi | String | The value of "gov.nasa.esdis.umm.doi" should be provided here so that CMR can properly parse out the DOI. | ||||||||||||
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:description/gco:CharacterString contains DOI | String | Leave this element empty. | /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:authority/cit:CI_Citation/cit:title - empty element | String | Provide the authority here. For ESDIS providers, recommend listing "https://doi.org" as the DOI authority. | |||||||||
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:authority/cit:CI_Citation/cit:citedResponsibleParty/ cit:CI_Responsibility/cit:party/cit:CI_Organization/cit:name/gco:CharacterString | String | Provide the authority here. For ESDIS providers, recommend listing "https://doi.org" as the DOI authority. | ||||||||||||
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/ cit:identifier/mcc:MD_Identifier/mcc:authority/cit:CI_Citation/cit:citedResponsibleParty/cit:CI_Responsibility/cit:role/cit:roleCode codeList="http://standards.iso.org/iso/19115/resources/Codelist/cat/codelists.xml#CI_RoleCode" codeListValue="" value = authority | Codelist | Choose the "authority" codelist value so that CMR can properly identify the DOI/Authority element. This codelist value does not directly map to a UMM element - choosing 'authority' indicates to CMR that the Authority element should be mapped. | ||||||||||||
ISO 19115-1 | Translation Direction | UMM | ||||||||||||
inapplicable | ↔ | Not Applicable | ||||||||||||
Section | ||||||||||||||
Column | ||||||||||||||
| ||||||||||||||
No Format |
Column | ||
---|---|---|
| ||
UMM
|
2 SMAP
Related URLs is a required metadata element. It is required that a data access point be provided in the metadata as a GET DATA URL. Multiple data access URLs may be provided (Cardinality: 1..*).
Note: These ISO paths only apply to DistributionURLs. Please see the RelatedURLs wiki page for ISO guidance specific to other types of URLs.
UMM-C Element | ISO 19115-2 SMAP Path | Type | Notes |
---|---|---|---|
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:linkage/gmd:URL | String | Where the access URL is provided. Maps to the UMM element RelatedUrls/URL. Note: This path only applies to DistributionURLs. | |
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Description: " | String | Maps to the UMM element RelatedUrls/Description. It is highly recommended that a description be provided for each URL. * The character string should always start with the prefix "Description: " in order for CMR to properly parse out the URL description. | |
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType: DistributionURL" | String | Maps to the UMM element RelatedUrls/URLContentType. Providing the URL Content Type is required in CMR. * For data access links, the character string should always read "URLContentType: DistributionURL" | |
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Type: GET DATA" | String | Maps to the UMM element RelatedUrls/Type. Providing the URL Type is required in CMR. * For data access links, the character string should always read "Type: GET DATA" | |
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorTransferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Subtype: " | String | Maps to the UMM element RelatedUrls/Subtype. Providing a URL Subtype is optional, but is encouraged if an appropriate URL Subtype exists. URL Subtype is a GCMD controlled vocabulary field and must be selected from keywords in the KMS. Please see the best practices section (above) on guidance on choosing the correct URL Subtype. * The character string should always start with with the prefix "Subtype: " in order for CMR to properly parse out the URL Subtype. | |
gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gmd:MD_Distributor/ gmd:distributorFormat/gmd:MD_Format/gmd:name/gco:CharacterString ="MimeType: " | String | Maps to the UMM element RelatedUrls/GetData/MimeType. Providing a mime type is optional. Mime Type is a GCMD controlled vocabulary field and should be selected from keywords in the KMS. * The character string should always start with with the prefix "MimeType: " in order for CMR to properly parse out the mime type. |
Enumeration/Code List Mapping
N/A
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
None
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.16.5 | 7/13/2021 | Removed enumerations for RelatedURLContentType, RelatedUrlType, and RelatedURLSubType values, and indicating that KMS should be the source of the values. |
1.16.4 | 6/30/2021 | Changed RelatedURL that adds Sub-Orbital Order Tool , and CERES OrderingTool as new enumerations to the subtype field. |
1.16.3 | 5/19/2021 | No changes were made for Related URLs-Get Data during the transition from version 1.16.2 to 1.16.3 |
1.16.2 | 4/7/2021 | No changes were made for Related URLs-Get Data during the transition from version 1.16.1 to 1.16.2 |
1.16.1 | 4/7/2021 | No changes were made for Related URLs-Get Data during the transition from version 1.16.0 to 1.16.1 |
1.16.0 | 3/24/2021 | No changes were made for Related URLs-Get Data during the transition from version 1.15.5 to 1.16.0 |
1.15.5 | 12/3/2020 | In the transition from version 1.15.4 to 1.15.5 the values for Related URLs-Get Data-Format were changed from enums listed in the schema to a string. The valid values for this string are captured in the Granule Data Format scheme in KMS. |
1.15.4 | 9/15/2020 | No changes were made for Related URLs-Get Data during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Related URLs-Get Data during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Related URLs-Get Data during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Related URLs-Get Data during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Related URLs-Get Data during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Related URLs-Get Data during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Related URLs-Get Data during the transition from version 1.12.0 to 1.13.0. |
1.12.0 | 01/22/2019 | No changes were made for Related URLs-Get Data during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Related URLs-Get Data during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | During the transition from version 1.9.0 to 1.10.0, the subelement 'MimeType' was added, which provides the mime type for the associated URL. |
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 | 607/1326/182018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |