Page History

Element Description

Note: This wiki page is a draft/ still in progress

This wiki page is for Data Center elements only

Create a separate page for DataCenter/ContactPerson elements & DataCenter/ContactGroup elements 

Best Practices

Examples:

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

Contact information 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. 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 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:

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://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

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.

ARC Priority Matrix

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:

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

DIF 10

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

Organization/ Organization_Type

Enumeration

PROCESSOR

ORIGINATOR

ARCHIVER

DISTRIBUTOR

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.

Dialect Mappings

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

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "SEDAC",
    "LongName": "Socioeconomic Data and Applications Center"
    "ContactInformation": {
      "RelatedUrls": [
        {
          "URLContentType": "DataCenterURL",

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

 <Personnel>

 <Role>DATA CENTER CONTACT</Role>

 <Contact_Group>

 <Name>SEDAC USER SERVICES</Name>

 <Address>

 <Street_Address>61 Route 9W, P.O. Box 1000</Street_Address>

 <City>Palisades</City>

 <State_Province>NY</State_Province>

 <Postal_Code>10964</Postal_Code>

 <Country>USA</Country>

 </Address>

 <Phone>

 <Number>+1 845-365-8920</Number>

 <Type>Telephone</Type>

 </Phone>

 <Phone>

 <Number>+1 845-365-8922</Number>

 <Type>Fax</Type>

 </Phone>

 <Email>ciesin.info@ciesin.columbia.edu</Email>

 </Contact_Group>

 </Personnel>

</Organization>

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"
  }
]

ECHO 10

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

N/A

Example Mapping

<Contact>
  <Role> ARCHIVER> </Role>
  <OrganizationName> ORNL_DAAC </OrganizationName>
  <OrganizationAddresses>
    <Address>
      <StreetAddress> ORNL DAAC User Services Office, P.O. Box 2008, MS 6407, Oak Ridge National Laboratory </StreetAddress>
      <City> Oak Ridge </City>
      <StateProvince> Tennessee </StateProvice>
      <Country> USA </Country>
    </Address>
  </OrganizationAddresses>
  <OrganizationPhone>
    <Phone>
      <Number> (865)241-3952 </Number>
      <Type> Direct Line </Type>
    </Phone>
  </OrganizationPhone>
  <OrganizationEmails>
     <Email> uso@daac.ornl.gov </Email>
  <OrganizationEmails>
</Contact>

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"
  },
  {
    Description: "Browse Image",
    URLContentType: "VisualizationURL",
    Type: "GET RELATED VISUALIZATION",
    URL: "https://daac.ornl.gov/graphics/browse/project/act-america_logo.png"
  }
]

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

<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>
          "Type":    <gmd:CI_OnlineResource>"HOME PAGE",
          "URL":      <gmd:linkage>
"http://sedac.ciesin.columbia.edu"
        }
      ]
      <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>       

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"
  }
]

}
  ],

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