Page History
Table of Contents | ||
---|---|---|
|
Element Description
Note: This wiki page is a draft/ still in progress
The Data Center metadata element is used to identify and provide contact information for the organization responsible for originating, processing, archiving, and/or distributing the data set dataset being described in the metadata.
Contact information about for an individual or a group affiliated with the data center can also be provided. Information about an individual should be provided in the DataCenter/ContactPerson sub-fields. Please see the DataCenter/ContactPerson wiki page for details on the Contact Person sub-elements. Information about a group should be provided in the DataCenter/ContactGroup sub-elements. Please see the DataCenter/ContactGroup wiki page for details on the Contact Group sub-elements. Note that each contact person or group must be affiliated with a Data Center.
Best Practices
Examples:
Element Specification
An unlimited amount of Data Centers may be listed (Cardinality: 1..*)
DISTRIBUTOR
ORIGINATOR
ARCHIVER
PHONE
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).
fields.
There are 5 options for providing contact information in the UMM:
Details for each of these options are provided on a separate wiki page. This wiki page describes details for option 1 (Data Center).
Best Practices
Each Data Center listed in the metadata must be affiliated with a Role. Providing a Role for the Data Center is required and must be selected from a controlled vocabulary list. There are four options for Role:
- ARCHIVER: the organization responsible for storing the data. This role should be selected when listing the name of a NASA Distributed Active Archive Center (DAAC).
- DISTRIBUTOR: the organization responsible for distributing the data. The archiver and distributor will often be the same organization. In this case, both 'ARCHIVER' and 'DISTRIBUTOR' can be specified for the same data center.
- ORIGINATOR: the organization responsible for producing the data.
- PROCESSOR: the organization responsible for processing the data. Not all data is necessarily processed. Examples of processing include: converting raw data into level 1 data; re-gridding or re-projecting data to make a higher level product; combining multiple data products to derive a model output.
The same data center may be responsible for multiple roles. In this case, multiple roles may be assigned to the same data center.
Other Data Center metadata fields include:
Short Name: The name of the Data Center (abbreviated version). Providing a Data Center Short Name is required. The Data Center Short Name must be selected from a controlled vocabulary maintained in the Keyword Management System (KMS). A list of valid Data Center keywords can be found here: https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/providers?format=csv Note that the Short Name should be selected from the "Short_Name" column in the keyword list.
Long Name: The name of the Data Center. Providing a Data Center Long Name is optional, however, it is recommended that a long name be provided if one exists in the keyword list since short names are often comprised of acronyms. A list of valid Data Center keywords can be found here: https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/providers?format=csv Note that the Long Name should be selected from the "Long_Name" column in the keyword list.
Uuid: The uuid is the unique identifier associated with the Data Center name in the controlled vocabulary keyword list. Providing the uuid is completely optional. The uuid can be found in the Data Centers keyword list in the "UUID" column.
Contact Information: Any relevant contact information for the data center can be provided in the Contact Information fields. Providing contact information is optional, however, it is recommended that at least one piece of contact information (such as a link, email or phone number) be provided. Some examples of contact information include: phone number, email, fax, related links, service hours, and contact instructions. See the element specification table below for full details.
Example:
Role: ARCHIVER, DISTRIBUTOR
ShortName: NASA/MSFC/GHRC
LongName: Global Hydrology Resource Center, Marshall Space Flight Center, NASA
ContactInformation/RelatedURL/Url: https://ghrc.nsstc.nasa.gov/home/
ContactInformation/RelatedURLs/UrlContentType: DataCenterURL
ContactInformation/RelatedURLs/Type: HOME PAGE
ContactInformation/RelatedURLs/Description: The Global Hydrology Resource Center (GHRC) website's home page
ContactInformation/ServiceHours: 8 AM to 5 PM Central Time
ContactInformation/ContactMechanism/Type: Email
ContactInformation/ContactMechanism/Value: support-ghrc@earthdata.nasa.gov
ContactInformation/ContactMechanism/Type: Phone
ContactInformation/ContactMechanism/Value: 256-961-7932
Element Specification
Data Centers is a required element. At least 1 Data Center must be provided. Multiple Data Centers may also be provided, if necessary (Cardinality: 1..*).
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | DataCenters/Roles | Enumeration | DISTRIBUTOR ORIGINATOR ARCHIVER PROCESSOR | n/a | Yes | 1..* | Location of the enumeration list in the UMM-Common schema: https://git.earthdata.nasa.gov/projects/EMFD/repos/unified-metadata-model/browse/collection/v1.10/umm-cmn-json-schema.json#1435 Note: enumerations are case sensitive. This means that the Role must be provided in all caps to pass validation. |
UMM-Common | DataCenter/ShortName | String | Data Center Short Name Keywords | KMS controlled | Yes | 1 | |
UMM-Common | DataCenter/LongName | String | Data Center Long Name Keywords | KMS controlled | No | 0..1 | It is highly recommended that a Data Center Long Name be provided if one exists in the keyword list. |
UMM-Common | DataCenter/Uuid | Number | Data Center UUID | KMS controlled | No | 0..1 | |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Url | String | n/a | n/a | Yes, if applicable | 1..* | Providing a URL is optional. If information is provided in any of the 'RelatedURLs' metadata fields, then the URL must be provided. This URL should link to the home page of the Data Center's website. |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/UrlContentType | Enumeration | DataCenterURL | n/a | Yes, if applicable | 1 | This field is only required if a URL is provided. URL Content Types are controlled as an enumeration list in the UMM-Common schema. The only valid option for Data Center Related URLs is "DataCenterURL". |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Type | String | HOME PAGE | KMS controlled | Yes, if applicable | 1 | This field is only required if a URL is provided. Related URL Types are controlled by GCMD vocabulary (URL Content Types). The only valid keyword option for a Data Center Related URL is "HOME PAGE". |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Description | String | n/a | 1 - 1024 characters | No | 0..1 | It is strongly |
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:
- 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 (USE SERVICE API) 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 (i.e. the link is mislabeled)
- 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 highlyrecommended that a description be provided for each URL. |
- A noted exception to this is DOI URLs (e.g. https://doi.org/10.3334/ORNLDAAC/1416) since these will always re-direct
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
ARC Automated Rules
- If no value is provided, return is: "Recommend providing a Related URL. This is a required field."
- If a value is provided, the URL is put through a URL checker:
- Checks if the link starts with 'https'
- Checks for https return status codes (200, 302, 400, 403, 404, 500, 502, 503, 504)
- If all checks are passed, return is: "OK"
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
UMM-Common | DataCenters/ContactInformation/ServiceHours | String | n/a | 1 - 1024 characters | No | 0..1 | The time zone should be specified. |
UMM-Common | DataCenters/ContactInformation/ContactInstructions | String | n/a | 1 - 2048 characters | No | 0..1 | Supplemental/ special instructions on how or when to contact the data center. |
UMM-Common | DataCenters/ContactInformation/ContactMechanism/Type | Enumeration | Direct Line Fax Mobile Modem Primary TDD/TTY Phone Telephone U.S. toll free Other | n/a | Yes, if applicable | 1 | Providing a contact mechanism is optional. If provided, the Type is required and must be selected from the ContactMechanismType enumeration list found in the UMM-Common schema. The actual value (e.g. the phone number or email) should be provided in the Value field (see below). Multiple contact mechanisms can be provided for each data center (Cardinality 0..*). |
UMM-Common | DataCenters/ContactInformation/ContactMechanism/Value | String | n/a | 1 - 1024 characters | Yes, if applicable | 1 | Providing a contact mechanism is optional. If provided, a Value is required (e.g. if the contact mechanism type is 'Email' then the actual email would go in this field). Multiple contact mechanisms can be provided for each data center (Cardinality 0..*). |
UMM-Common | DataCenters/ContactInformation/Address/StreetAddresses | String | n/a | 1 - 1024 characters | No | 0..* | Multiple Street Addresses may be provided to indicate multiple lines in a street address. |
UMM-Common | DataCenters/ContactInformation/Address/City | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | DataCenter/ContactInformation/Address/StateProvince | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | DataCenter/ContactInformation/Address/PostalCode | String | n/a | 1 - 20 characters |
title | DIF 10 |
---|
DIF 10
An unlimited amount of Related_URLs may be listed (Cardinality: 0..*)
Organization/ Organization_Type
Enumeration
PROCESSOR
ORIGINATOR
ARCHIVER
DISTRIBUTOR
No | 0..1 |
UMM-Common | DataCenter/ContactInformation/Address/Country | String |
n/a | 1 - 100 characters | No | 0..1 |
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 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 10Data Centers is a required element. At least 1 Data Center must be provided. Multiple Data Centers may also be provided, if necessary (Cardinality: 1..*).
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10In ECHO 10, it is required that either Processing Center OR Archive Center be provided. It is not necessary to provide both. If a data center name is provided in the 'Contacts' section (with an appropriate GCMD Data Center Short Name and 'Type' value) then it will be mapped to the UMM 'Data Centers' element.
The ECHO10 "Contacts/Contact/Role" field is not enumeration controlled, however, the equivalent field in the UMM is enumeration controlled. The below table summarizes how values provided in the ECHO10 field "Contacts/Contact/Role" are converted to the UMM field "DataCenters/Roles". Note that the value provided in the ECHO10 field "Contacts/Contact/Role" will automatically be converted to all lower case and then mapped accordingly. If the ECHO10 value does not match any of the options provided below, then it will automatically be mapped to "ARCHIVER" by the UMM.
| DIF 10 | Organization/ Data_Set_ID | String | No | 0..* | DIF 10 | Organization/ Personnel/ Role | String | Yes | 1..* | DIF 10 | Organization/ Personnel/ Contact_Person/ First_Name | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Middle_Name | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Last_Name | String | Yes | 1 | DIF 10 | Organization/Personnel/Contact_Person/uuid | String | No | 0,.1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Address/ Street_Address | String | No | 0..* | DIF 10 | Organization/ Personnel/ Contact_Person/ Address/ City | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Address/ State_Province | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Address/ Postal_Code | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Address/ Country | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Email | String | Yes | 0..* | DIF 10 | Organization/Personnel/Contact_Person/Phone | String | No | 0..* | DIF 10 | Organization/ Personnel/ Contact_Person/ Phone/ Number | Number | Yes | 1 | DIF 10 | Organization/ Personnel/ Contact_Person/ Phone/ Type | Enumeration | Telephone Direct Line | Yes | 1 | DIF 10 | Organization/ Personnel/ Contact_Group/ Name | String | No | 0..1 | DIF 10 | Organization/Personnel/Contact_Group/Name attribute uuid | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Group/ Address/ Street_Address | String | No | 0..* | DIF 10 | Organization/ Personnel/ Contact_Group/ Address/ City | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Group/ Address/ State_Province | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Group/ Address/ Postal_Code | String | No | 0..1 | DIF 10 | Organization/ Personnel/ Contact_Group/ Address/ Country | String | No | 0..1 | Example Mapping|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Section |
Column | ||
---|---|---|
| ||
UMM
|
title | ECHO 10 |
---|
ECHO 10
An unlimited amount of OnlineResources and/or AssociatedBrowseImageUrls may be listed (Cardinality: 0..*)
N/A
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
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 (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.
/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.
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.
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.
/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.
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
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSData Centers is a not a required element in ISO 19115-2 MENDS. Multiple Data Centers may also be provided, if necessary.
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 (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. Specification | Path | Type | Notes | 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
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 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="Description:" | String | 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-2 SMAP |
N/A Example Mapping
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAPData Centers is a not a required element in ISO 19115-2 SMAP. Multiple Data Centers may also be provided, if necessary.
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 |
| 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 |
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
N/A Example Mapping
|
UMM Migration
None
Excerpt | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Data Centers during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Data Centers during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Data Centers during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Data Centers during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Data Centers during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Data Centers during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Data Centers during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Data Centers during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 01/22/2019 | No changes were made for Data Centers during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Data Centers during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | No changes were made for Data Centers during the transition from version 1.9.0 to 1.10.0. |
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 (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.
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
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | <> |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 709/2507/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |