You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

Element Description

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 being described in the metadata.  

Contact information about an individual or a group affiliated with the data center will also be provided. Information about an individual should be provided in the DataCenter/ContactPerson sub-fields. Information about a group should be provided in the DataCenter/ContactGroup sub-fields.

There are 5 options for providing contact information in the UMM:

  1. Data Center
  2. Data Center/Contact Person
  3. Data Center/Contact Group
  4. Contact Person
  5. Contact Group

Details for each of these options is 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:

  1. 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).   
  2. 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. 
  3. ORIGINATOR: the organization responsible for producing the data.
  4. 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://gcmdservices.gsfc.nasa.gov/static/kms/providers/providers.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://gcmdservices.gsfc.nasa.gov/static/kms/providers/providers.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

An unlimited amount of Data Centers may be listed (Cardinality: 1..*)

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonDataCenters/Roles Enumeration

DISTRIBUTOR

ORIGINATOR

ARCHIVER

PROCESSOR

n/aYes1..*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
UMM-CommonDataCenter/ShortName StringData Center Short Name KeywordsKMS controlledYes1
UMM-CommonDataCenter/LongName StringData Center Long Name KeywordsKMS controlledNo0..1It is highly recommended that a Data Center Long Name be provided if one exists in the keyword list.
UMM-CommonDataCenter/Uuid NumberData Center UUIDKMS controlledNo0..1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/UrlStringn/an/aYes, if applicable1..*

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-CommonDataCenters/ContactInformation/RelatedURLs/UrlContentTypeEnumerationDataCenterURLn/aYes, if applicable1

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-CommonDataCenters/ContactInformation/RelatedURLs/TypeStringHOME PAGEKMS controlledYes, if applicable1

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-CommonDataCenters/ContactInformation/RelatedURLs/DescriptionStringn/a1 - 1024 charactersNo0..1It is strongly recommended that a description be provided for each URL.
UMM-CommonDataCenters/ContactInformation/ServiceHours Stringn/a1 - 1024 charactersNo0..1The time zone should be specified.
UMM-CommonDataCenters/ContactInformation/ContactInstructionsStringn/a1 - 2048 charactersNo0..1Supplemental/ special instructions on how or when to contact the data center.
UMM-CommonDataCenters/ContactInformation/ContactMechanism/Type Enumeration

Direct Line

Email

Facebook

Fax

Mobile

Modem

Primary

TDD/TTY Phone

Telephone

Twitter

U.S. toll free

Other

n/aYes, if applicable1

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-CommonDataCenters/ContactInformation/ContactMechanism/Value Stringn/a1 - 1024 charactersYes, if applicable1

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-CommonDataCenters/ContactInformation/Address/StreetAddresses Stringn/a1 - 1024 charactersNo0..*Multiple Street Addresses may be provided to indicate multiple lines in a street address
UMM-CommonDataCenters/ContactInformation/Address/City Stringn/a1 - 100 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/StateProvince Stringn/a1 - 100 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/PostalCode Stringn/a1 - 20 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/Country Stringn/a1 - 100 charactersNo0..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).

Please see the expandable sections below for flowchart details.


  • Manual Review
    • Identify errors, discrepancies or omissions.
    • Confirm that the URL link to the appropriate web page.
  • Automated Review
    • Check that the field length is not greater than 160 characters (Dataset_ID).
    • Check that the field length is not greater than 1,024 characters (Hours_of_Service).
    • Check that the field length is not greater than 2,048 characters (Instructions).
    • Check that the field length is not greater than 2,048 characters (Organization_URL).
    • Check that the field has been populated.
    • Check that the field value is not a duplicate.
    • Check that the field value (Role) matches the enumeration value (DISTRIBUTOR, ORIGINATOR, ARCHIVER, PROCESSOR).
    • Check for potential broken links.
    • Check that the URL is formatted correctly.

<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • No Data Center information is provided.
    • No Data Center Short Name is provided.
    • No Data Center Role.
    • No Data Center URL is provided.
  • The Data Center URL provided is broken.
  • The Data Center URL provided is incorrect/unrelated to the data center.
  • The URL Content Type does not match the enumeration value "DataCenterURL."
  • The URL Type provided does not match the keyword value "HOME PAGE."
  • The Data Center Short Name and/or Long Name does not align with the KMS.
    • The Short Name and/or Long Name does not exist in the KMS.
    • The Short Name and/or Long Name is placed in the incorrect position of the hierarchy (e.g. DOC/NOAA/OOE should not be provided in the Long Name field, because it is categorized as a Short Name in the KMS).
    • There is an invalid Short Name/ Long Name relationship (e.g. Short Name: DOC/NOAA/OOE, Long Name: Energy Team, U.S. Geological Survey, U.S. Department of the Interior, is not a valid combination in the KMS).
  • The UUID provided is incorrect for the Data Center.
  • The Data Center provided is incorrect for the data set.
  • The Data Center Role provided does not align with the UMM-Common enumeration values (DISTRIBUTOR, ORIGINATOR, ARCHIVER, PROCESSOR).
  • The Contact Mechanism Type does not align with the UMM-Common enumeration values (Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other).
  • The Contact Information provided is incorrect.

This element is categorized as medium priority when:

  • The Data Center Related URL 'Description' element is left blank. It is highly recommended that a description be provided for each URL.
  • The Data Center Related URL provided in the metadata redirects - it is recommended that the most current link always be provided.
  • A recommendation is made to change a valid Data Center keyword for purposes of consistency with other similar metadata records.
  • No Data Center Long Name is provided when a long name exists in the KMS.
  • The information provided in the Data Center elements is better suited for the DataCenter/ContactGroup or DataCenter/ContactPerson metadata elements.

This element is categorized as low priority when:

  • The Data Center Related URL is provided via http when https is available.

The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules


Dialect Mappings

DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018)

DIF 10

An unlimited amount of Related_URLs may be listed (Cardinality: 0..*)

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
DIF 10

Organization/Organization_Type

Enumeration

PROCESSOR

ORIGINATOR

ARCHIVER

DISTRIBUTOR


Yes1..*
DIF 10Organization/Organization_Name/Short_Name String

Yes1
DIF 10Organization/Organization_Name/Long_Name String

No0..1
DIF 10Organization/Organization_Name attribute uuidString

No0..1
DIF 10Organization/Hours_Of_ServiceString

No0..1
DIF 10Organization/InstructionsString

No0..1
DIF 10Organization/Organization_URLString

No0..1
DIF 10Organization/Data_Set_IDString

No0..*This field does not map to UMM


Example Mapping

DIF 10

<Organization>
  <Organization_Type>ARCHIVER</Organization_Type>
  <Organization_Type>DISTRIBUTOR</Organization_Type>
  <Organization_Name>
    <Short_Name>SEDAC</Short_Name>
    <Long_Name>Socioeconomic Data and Applications Center</Long_Name>
  </Organization_Name>
  <Organization_URL>http://sedac.ciesin.columbia.edu</Organization_URL>
  <Dataset_ID>CIESIN_SEDAC_ESI_2000</Dataset_ID>
</Organization>

UMM

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "SEDAC",
    "LongName": "Socioeconomic Data and Applications Center"
    "ContactInformation": {
      "RelatedUrls": [
        {
          "URLContentType": "DataCenterURL",
          "Type": "HOME PAGE",
          "URL": "http://sedac.ciesin.columbia.edu"
        }
      ]
    }
  ]

ECHO 10

An unlimited amount of OnlineResources and/or AssociatedBrowseImageUrls may be listed (Cardinality: 0..*)

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10ProcessingCenter




The ECHO 10 field 'ProcessingCenter' maps to the UMM field DataCenter/ShortName and the associated DataCenter/Role will automatically be set to "PROCESSOR"

Values provided in the 'ProcessingCenter' field should be selected from the Data Center keywords list: https://gcmdservices.gsfc.nasa.gov/static/kms/providers/providers.csv? 

Note that the Short Name should be selected from the "Short_Name" column in the keyword list.

ECHO 10ArchiveCenter




The ECHO 10 field 'ArchiveCenter' maps to the UMM field DataCenter/ShortName and the associated DataCenter/Role will automatically be set to "ARCHIVER"

Values provided in the 'ArchiveCenter' field should be selected from the Data Center keywords list: https://gcmdservices.gsfc.nasa.gov/static/kms/providers/providers.csv? 

Note that the Short Name should be selected from the "Short_Name" column in the keyword list.

ECHO 10Contacts/Contact/RoleString
1 - 80 charactersYes1

While this field is not controlled in ECHO 10, it is highly recommended that the Role be selected from the UMM-Common enumeration values for role: DISTRIBUTOR, ORIGINATOR, ARCHIVER, PROCESSOR

The CMR will attempt to map any value provided in this field to one of the 4 roles above when displaying metadata in the Earthdata Search client. Providing one of the UMM-Common enumeration values will help prevent translation errors from occurring.

ECHO 10Contacts/Contact/OrganizationNameString
1 - 200 charactersNo0..1

Values provided in the 'OrganizationName' field should be selected from the Data Center keywords list: https://gcmdservices.gsfc.nasa.gov/static/kms/providers/providers.csv? 

Note that the Organization Name should be selected from the "Short_Name" column in the keyword list.

ECHO 10Contacts/Contact/Hours of ServiceString
1 - 1024 charactersNo0..1
ECHO 10Contacts/Contact/InstructionsString
1 - 2048 charactersNo0..1
ECHO 10Contacts/Contact/OrganizationAddresses/Address/StreetAddressString
1 - 1024 charactersYes1
ECHO 10Contacts/Contact/OrganizationAddresses/Address/CityString
1 - 80 charactersYes1
ECHO 10Contacts/Contact/OrganizationAddresses/OrganizationAddress/StateProvinceString
1 - 30 charactersYes1
ECHO 10Contacts/Contact/OrganizationAddresses/Address/PostalCodeString
1 - 20 charactersYes1
ECHO 10Contacts/Contact/OrganizationAddresses/Address/CountryString
1 - 10 charactersYes1Use "Unknown" if no value exists
ECHO 10Contacts/Contact/OrganizationPhones/Phone/NumberNumber
1 - 23 charactersYes1
ECHO 10Contacts/Contact/OrganizationPhones/Phone/TypeString
1 - 30 charactersYes1
ECHO 10Contacts/Contact/OrganizationEmails/Email String
1 - 1024 charactersNo0..*


Enumeration Mapping

N/A

Example Mapping

ECHO 10

<Contacts>
  <Contact>
    <Role>ARCHIVER</Role>
    <OrganizationName>SEDAC</OrganizationName>
  </Contact>
  <Contact>
    <Role>DISTRIBUTOR</Role>
    <OrganizationName>SEDAC</OrganizationName>
  </COntact>

UMM

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "SEDAC",
    "LongName": "Socioeconomic Data and Applications Center"
    "ContactInformation": {
      "RelatedUrls": [
        {
          "URLContentType": "DataCenterURL",
          "Type": "HOME PAGE",
          "URL": "http://sedac.ciesin.columbia.edu"
        }
      ]
    }
  ]



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.

SpecificationPathTypeNotes
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

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>https://doi.org/10.3334/ORNLDAAC/1568</gmd:URL>
                </gmd:linkage>
                <gmd:description>
                  <gco:CharacterString>Description: Access the data set landing page for the collection., URLContentType: CollectionURL, URLType: DATA SET LANDING PAGE</gco:CharacterString>
                </gmd:description>
                <gmd:linkage>
                  <gmd:URL>https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html</gmd:URL>
                </gmd:linkage>
                <gmd:description>
                  <gco:CharacterString>Description: The guide document contains detailed information about the data set., URLContentType: PublicationURL, URLType: VIEW RELATED INFORMATION, URLSubtype: USER'S GUIDE</gco:CharacterString>
                </gmd:description>
              </gmd:CI_OnlineResource>
              </gmd:onlineResource>
            </gmd:contactInfo>
          </gmd:CI_ResponsibleParty>
          </gmd:citedResponsibleParty>
        </gmd:CI_Citation>
      </gmd:aggregateDataSetName>
    </gmd:MD_AggregateInformation>
    </gmd:aggregationInfo>
  </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
...
</gmi:MI_Metadata>

UMM

RelatedUrls: [
  {
    Description: "Access the data set landing page for the collection.",
    URLContentType: "CollectionURL",
    Type: "DATA SET LANDING PAGE",
    URL:  "https://doi.org/10.3334/ORNLDAAC/1568",
  },
  {
    Description: "The guide document contains detailed information about the data set.",
    URLContentType: "PublicationURL",
    Type: "VIEW RELATED INFORMATION",
    Subtype: "USER'S GUIDE",
    URL:  "https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html"
  }
]



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.

SpecificationPathTypeNotes
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: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 SMAPgmd: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 SMAPgmd: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 SMAPgmd: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:"

String

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.

ISO 19115-2 SMAPgmd: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.


Enumeration/Code List Mapping

N/A

Example Mapping

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:linkage>
                  <gmd:URL>https://doi.org/10.3334/ORNLDAAC/1568</gmd:URL>
                </gmd:linkage>
                <gmd:description>
                  <gco:CharacterString>Description: Access the data set landing page for the collection., URLContentType: CollectionURL, URLType: DATA SET LANDING PAGE</gco:CharacterString>
                </gmd:description>
                <gmd:linkage>
                  <gmd:URL>https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html</gmd:URL>
                </gmd:linkage>
                <gmd:description>
                  <gco:CharacterString>Description: The guide document contains detailed information about the data set., URLContentType: PublicationURL, URLType: VIEW RELATED INFORMATION, URLSubtype: USER'S GUIDE</gco:CharacterString>
                </gmd:description>
              </gmd:CI_OnlineResource>
              </gmd:onlineResource>
            </gmd:contactInfo>
          </gmd:CI_ResponsibleParty>
          </gmd:citedResponsibleParty>
        </gmd:CI_Citation>
      </gmd:aggregateDataSetName>
    </gmd:MD_AggregateInformation>
    </gmd:aggregationInfo>
  </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
...
</gmi:MI_Metadata> 
</gmd:seriesMetadata>  
</gmd:DS_Series>

UMM

RelatedUrls: [
  {
    Description: "Access the data set landing page for the collection.",
    URLContentType: "CollectionURL",
    Type: "DATA SET LANDING PAGE",
    URL:  "https://doi.org/10.3334/ORNLDAAC/1568",
  },
  {
    Description: "The guide document contains detailed information about the data set.",
    URLContentType: "PublicationURL",
    Type: "VIEW RELATED INFORMATION",
    Subtype: "USER'S GUIDE",
    URL:  "https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html"
  }
]



UMM Migration

None

Future Mappings

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.

SpecificationPathTypeNotes
ISO 19115-1


String

Where the URL is provided.

Maps to the UMM element RelatedUrls/URL.

Note: This path only applies to CollectionURLs and PublicationURLs.

ISO 19115-1


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-1


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-1


String

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.

ISO 19115-1
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.


Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-1

UMM

RelatedUrls: [
  {
    Description: "Access the data set landing page for the collection.",
    URLContentType: "CollectionURL",
    Type: "DATA SET LANDING PAGE",
    URL:  "https://doi.org/10.3334/ORNLDAAC/1568",
  },
  {
    Description: "The guide document contains detailed information about the data set.",
    URLContentType: "PublicationURL",
    Type: "VIEW RELATED INFORMATION",
    Subtype: "USER'S GUIDE",
    URL:  "https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html"
  }
]

History

UMM Versioning

VersionDateWhat Changed
1.12.001/22/2019 No changes were made for Data Centers during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Data Centers during the transition from version 1.10.0 to 1.11.0.
1.10.005/02/2018No changes were made for Data Centers during the transition from version 1.9.0 to 1.10.0.
1.9.0

ARC Documentation

VersionDateWhat ChangedAuthor
1.09/7/18Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux
  • No labels