Page History
Table of Contents | ||
---|---|---|
|
Element Description
The Related URLs element is used provides access to link to resources containing information related to a data setcollection. The Related URL may also link to data access points, as well as relevant tools and services.
Note: This wiki page pertains to Related URLs in collection level metadata. For guidance on Related URLs in granule level metadata, please see the RelatedURLs (GRANULES) wiki page.
Best Practices
The Related URLs metadata element 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 access relevant services and information about the data. At a minimum, Related URLs at the collection level should point to:
- A data access location
- A landing page for the associated data setdataset
- Any relevant services provided for the data (if applicable) such as: Web Map Services (WMS), OPeNDAP, THREDDS, Web Map Tile Services (WMTS), Web Coverage Services (WCS), etc.
- A user's guide and/or comparable documentation which provides important information about how to use the data set data
- The project home page
- Relevant software packages
- Relevant online data tools
- Relevant PI documentation
- Read-Me files
- Data citation policies
- Algorithm Theoretical Basis Document (ATBD)
- OpenSearch Description Document (OSDD) links
- Any other documentation directly related to the dataset (examples include: data recipes, micro articles, product quality assessment documentation, important announcements, documentation on dataset anomalies, etc.)
There are two special sub-sections within Related URLs. These include the GET DATA and the USE SERVICE APIThere are two special sub-sections within Related URLs. These include the GET DATA and the GET SERVICE sub-elements. A separate wiki page with full details has been developed for each of these sub-sections:
Related URLs (GET USE SERVICE API)
The details on this wiki page are for general Related URL guidance and do not include any of the GET DATA or GET USE SERVICE API sub-elements.
Several of the elements within the Related URLs section of the metadata serve to properly identify the purpose of the link. These identifying 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 schema with the following options: "CollectionURL", "PublicationURL", "DataCenterURL", "DistributionURL", "DataContactURL", "VisualizationURL". The URL Content Type helps specify how the URL will be displayed in the Earthdata Search Client.
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). A list of valid URL Type keywords can be found here: https://gcmdservicesgcmd.gsfcearthdata.nasa.gov/statickms/kmsconcepts/rucontenttypeconcept_scheme/rucontenttype.csv??format=csv
Note Note that the keyword list does not include the upper level URL Content Type keywords (specified above & maintained in the UMM schema). Please see the diagram below for details on the relationship between URL Content Type keywords and URL Type keywords.
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 is optional, but should be used when applicable. The URL Subtype keywords are maintained in the Keyword Management System (KMS). A list of valid URL Subtype keywords can be found here: https://gcmdservicesgcmd.gsfcearthdata.nasa.gov/statickms/kmsconcepts/rucontenttypeconcept_scheme/rucontenttype.?format=csv?
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 where the link navigates and the type of information it contains. 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. Ii.e. the description should be used to further differentiate two URLs with the same URL Type and Subtype.
Please see the below diagram for the full relationship between URL Content Type, Type, and Subtype keywords:
Examples:
URL: https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html
URL Content Type: PublicationURL
URL Type: VIEW RELATED INFORMATION
URL Subtype: USER'S GUIDE
Description: The guide document contains detailed information about the data setdataset.
URL: https://ghrc.nsstc.nasa.gov/home/micro-articles/lake-effect-snow
URL Content Type: PublicationURL
URL Type: VIEW RELATED INFORMATION
URL Subtype: MICRO ARTICLE
Description: Learn about how AMSR-2 data can be used to study lake effect snow in this micro article.
Please see the below diagram for the full relationship between URL Content Type, Type, and Subtype keywords:
Lucidchart | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Element Specification
Related URLs is a required metadata element. At least 1 Related URL must be provided. Multiple URLs may be provided if necessary (Cardinality: 0..*).
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 |
Element Specification
An unlimited amount of Related URLs may be listed (Cardinality: 0..*)
1 - 1024 characters
CollectionURL
PublicationURL
DataCenterURL
DistributionURL
DataContactURL
VisualizationURL
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 | GCMD URL Content Type 'Type' Keywords | KMS controlled |
Yes | 1 | Each Type keyword corresponds to a specific URL Content Type category. | ||
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. |
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-displayid 98e5dc28-3252-4209-953f-66f1378e1cf4 align Left height 299
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- No Related URLs are provided
- No data access URL is provided. For further details on data access URLs please see the Related URLs (GET DATA) wiki page.
- There is a service available for a collection but no service URL is provided. For further details on service URLs please see the Related URLs (GET SERVICE) wiki page.
- The URL provided is broken
- The URL provided is incorrect/ unrelated to the associated data set
- The URL Type or Subtype provided does not accurately describe the link
- The URL Type or Subtype provided does not align with the KMS
- The Type or Subtype does not exist in the 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 links to an FTP server (this only applies to NASA EOSDIS metadata)
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.
- A recommendation is made to change a valid URL Type or Subtype keyword for purposes of consistency with other similar metadata records
This element is categorized as low priority when:
- The 'Description' element is identical for multiple URLs
- If a recommendation is made to add a URL to the metadata, there will be accompanying blue recommendations to add the appropriate URL Content Type/ URL Type/ Subtype elements.
- A URL is provided via http when https is available
- The URL provided in the metadata redirects - it is recommended that the most current link always be provided
- A noted exception to this is DOI URLs (e.g. https://doi.org/10.3334/ORNLDAAC/1416) since these will always re-direct
ARC Automated Rules
<insert>
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
|
Expand | ||
---|---|---|
| ||
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
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. At least 1 Related_URL must be provided. Multiple URLs may be provided if necessary (Cardinality: 0..*).
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Usable Valid Values | Constraints | Required in DIF 10? | Cardinality | Notes | DIF 10 | /DIF/Related_URL/URL | URI | No | 0..* | The link is provided here. | DIF 10 | /DIF/Related_URL/URL_Content_Type/Type | String | KMS controlled | No | 0..1 | DIF 10 | /DIF/Related_URL/URL_Content_Type/Subtype | String | KMS controlled | No | 0..1 | The Type and Subtype are part of a keyword hierarchy specified in the KMS. 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 | Example Mapping
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
DIF 10
|
title | ECHO 10 |
---|
ECHO 10
An unlimited amount of OnlineResources and/or AssociatedBrowseImageUrls may be listed (Cardinality: 0..*)
/Description | String | No | 0..1 |
RelatedUrls/URLContentType = VisualizationURL | For all Multimedia URLs translated to UMM the URLContentType is VisualizationURL | ||||||
RelatedUrls/Type = GET RELATED VISUALIZATION | For all Multimedia URLs translated to UMM the Type is GET RELATED VISUALIZATION |
Example Mapping
Section | |||||
---|---|---|---|---|---|
DIF 10
|
N/A
Example Mapping
Section | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10ISO 19115-2 MENDSAn unlimited amount of Related URLs OnlineResources and/or AssociatedBrowseImageUrls may be listed (Cardinality: 0..*) Note: These ISO paths only apply to CollectionURLs and PublicationURLs. Please see the RelatedURLs (GET DATA) wiki page for ISO guidance specific to data access URLs. Please see the RelatedURLs (GET SERVICE) wiki page for ISO guidance specific to services. Please see the Data Center wiki page for ISO guidance specific to DataCenterURLs. Please see the Data Contact wiki page for ISO guidance specific to DataCenterURLs.
Specification |
Notes | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL String Where the URL is provided. Maps to the UMM element RelatedUrls/URL. Note: This path only applies to CollectionURLs and PublicationURLs. ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Description: " | String | Maps to the UMM element RelatedUrls/Description. A brief, unique description of the URL should be provided in this field. 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. ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType: " | String | Maps to the UMM element RelatedUrls/URLContentType. The URL Content Type is required in UMM and is used to specify how the link will display in the Earthdata Search Client. The URL Content Type must be selected from the following controlled vocabulary options: CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL. Please see the best practices section (above) on guidance on choosing the correct URL Content Type. * The character string should always start with the prefix "URLContentType: " in order for CMR to properly parse out the URL Content Type. ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Type: " String Maps to the UMM element RelatedUrls/Type. Providing a URL Type is required in UMM. Failing to specify a Type in ISO metadata will result in the field being auto-populated by the CMR, which could result in the URL being mislabeled. URL Type 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 Type. * The character string should always start with the prefix "Type: " in order for CMR to properly parse out the URL Type. ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/ gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/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. Enumeration/Code List Mapping N/A Example Mapping
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSAn unlimited amount of Related URLs may be listed (Cardinality: 0..*) Note: These ISO paths only apply to CollectionURLs and PublicationURLs. Please see the RelatedURLs (GET DATA) wiki page for ISO guidance specific to data access URLs. Please see the RelatedURLs (USE SERVICE API) wiki page for ISO guidance specific to services. Please see the Data Center wiki page for ISO guidance specific to DataCenterURLs. Please see the Data Contact wiki page for ISO guidance specific to DataCenterURLs.
ISO 19115-2 SMAP An unlimited amount of Related URLs may be listed (Cardinality: 0..*) Note: These ISO paths only apply to CollectionURLs and PublicationURLs. Please see the RelatedURLs (GET DATA) wiki page for ISO guidance specific to data access URLs. Please see the RelatedURLs (GET SERVICE) wiki page for ISO guidance specific to services. Please see the Data Center wiki page for ISO guidance specific to DataCenterURLs. Please see the Data Contact wiki page for ISO guidance specific to DataCenterURLs. Specification | Path | Type | Notes | gmd:DS_Series/gmd:seriesMetadata/
String Where the URL is provided.ISO 19115-2 SMAP | gmd:DS_Series/gmd:seriesMetadata
Note: This path only applies to CollectionURLs and PublicationURLs.
ISO 19115-2 SMAP | gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType:" | String | Maps to the UMM element RelatedUrls/URLContentType. The value must start with the string "URLContentType: " in order for CMR to properly identify the URL Content Type. The URL Content Type is required in UMM and is used to specify how the link will display in the Earthdata Search Client. The URL Content Type must be selected from the following controlled vocabulary options: CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL. Please see the best practices section (above) on guidance on choosing the correct URL Content Type. ISO 19115-2 SMAP | gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Type:" | Maps to the UMM element RelatedUrls/Type. The value must start with the string "Type: " in order for CMR to properly identify the URL Type.String Providing a URL Type is required in UMM. Failing to specify a Type in ISO metadata will result in the field being auto-populated by the CMR, which could result in the URL being mislabeled. URL Type 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 Type. ISO 19115-2 SMAP | gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Subtype: | String | Maps to the UMM element RelatedUrls/Subtype. The value must start with the string "Subtype: " in order for CMR to properly identify the URL 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.
N/A Example Mapping
|
UMM Migration
None
|
Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAPAn unlimited amount of Related URLs may be listed (Cardinality: 0..*) Note: These ISO paths only apply to CollectionURLs and PublicationURLs. Please see the RelatedURLs (GET DATA) wiki page for ISO guidance specific to data access URLs. Please see the RelatedURLs (USE SERVICE API) wiki page for ISO guidance specific to services. Please see the Data Center wiki page for ISO guidance specific to DataCenterURLs. Please see the Data Contact wiki page for ISO guidance specific to DataCenterURLs.
|
UMM Migration
None
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.17.1 | 8/10/2022 | No changes were made for RelatedUrls during the transition from version 1.17 to 1.17.1 |
1.17 | 5/11/2022 | No changes were made for RelatedUrls during the transition from version 1.16.7 to 1.17 |
1.16.7 | 3/2/2022 | No changes were made for RelatedUrls during the transition from version 1.16.6 to 1.16.7 |
1.16.6 | 12/1/2021 | No changes were made for RelatedUrls during the transition from version 1.16.5 to 1.16.6 |
1.16.5 | 7/13/2021 | Removed enumerations for RelatedUrls/URLContentType, RelatedUrls/Type, and RelatedUrls/Subtype values, and indicating that KMS should be the source of the values. |
1.16.4 | 6/30/2021 | Changed RelatedUrls that adds HITIDE , SOTO , Sub-Orbital Order Tool , and CERES Ordering Tool as new enumerations to the subtype field. |
1.16.3 | 5/19/2021 | Changed RelatedURL that adds GET CAPABILITIES as a new enumeration to the type field and adds GIBS as a new subtype, opensearch already exists as a valid subtype. |
1.16.2 | 4/7/2021 | No changes were made for RelatedUrls during the transition from version 1.16.1 to 1.16.2 |
1.16.1 | 4/7/2021 | No changes were made for RelatedUrls during the transition from version 1.16.0 to 1.16.1 |
1.16.0 | 3/24/2021 | No changes were made for RelatedUrls during the transition from version 1.15.5 to 1.16.0 |
1.15.5 | 12/3/2020 | No changes were made for RelatedUrls during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for RelatedUrls during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for RelatedUrls during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for RelatedUrls during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for RelatedUrls during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for RelatedUrls during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for RelatedUrls during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for RelatedUrls during the transition from version 1.12.0 to 1.13.0. |
1.12.0 | 01/22/2019 | During the transition from version 1.11.0 to 1.12.0, 4 new Related URL keywords were added. |
1.11.0 | 11/28/2018 | During the transition from version 1.10.0 to 1.11.0, the enumerations for sub elements 'Type' and 'Subtype' were changed to match the GCMD version of the keywords that was released on March 15, 2018. |
1.10.0 | 05/02/2018 | During the transition from version 1.9.0 to 1.10.0, the following sub elements were added: 'Mime Type' (Get Data) and 'Format' (Get Service). |
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
An unlimited amount of Related URLs may be listed (Cardinality: 0..*)
Note: These ISO paths only apply to CollectionURLs and PublicationURLs. Please see the RelatedURLs (GET DATA) wiki page for ISO guidance specific to data access URLs. Please see the RelatedURLs (GET SERVICE) wiki page for ISO guidance specific to services. Please see the Data Center wiki page for ISO guidance specific to DataCenterURLs. Please see the Data Contact wiki page for ISO guidance specific to DataCenterURLs.
Where the URL is provided.
Maps to the UMM element RelatedUrls/URL.
Note: This path only applies to CollectionURLs and PublicationURLs.
ISO 19115-1
Maps to the UMM element RelatedUrls/Description. It is highly recommended that a description be provided for each URL.
Provide a brief, unique description of the URL in this field. The value must start with the string "Description: " in order for CMR to properly identify the URL description.
ISO 19115-1
Maps to the UMM element RelatedUrls/URLContentType. The value must start with the string "URLContentType: " in order for CMR to properly identify the URL Content Type.
The URL Content Type is required in UMM and is used to specify how the link will display in the Earthdata Search Client. The URL Content Type must be selected from the following controlled vocabulary options: CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL. Please see the best practices section (above) on guidance on choosing the correct URL Content Type.
Maps to the UMM element RelatedUrls/Type. The value must start with the string "Type: " in order for CMR to properly identify the URL Type.
Providing a URL Type is required in UMM. Failing to specify a Type in ISO metadata will result in the field being auto-populated by the CMR, which could result in the URL being mislabeled. URL Type 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 Type.
Maps to the UMM element RelatedUrls/Subtype. The value must start with the string "Subtype: " in order for CMR to properly identify the URL 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.
N/A
Example Mapping
width | 50% |
---|
ISO 19115-1
Column | ||
---|---|---|
| ||
UMM
|
History
UMM Versioning
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 707/25/182018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |