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

Compare with Current View Page History

« Previous Version 19 Next »

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

Contact information about an individual or a group affiliated with the data 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 metadata elements. Information about a group should be provided in the DataCenter/ContactGroup sub-fields. Please see the DataCenter/ContactGroup wiki page for details on the Contact Group metadata elements. Note that each contact person or group must be affiliated with a 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.

Shoule we keep this example? The following is a (completely theoretical) example where a different Data Center is responsible for each role: A team from the University of Maryland is responsible for collecting raw data from an airborne sensor (ORIGINATOR). The raw data is sent to colleagues at Goddard Space Flight Center to be processed to level 1 data (PROCESSOR). It is ultimately decided that the NSIDC DAAC is the best place to archive the data (ARCHIVER). The USGS decides to harvest the data from the NSIDC DAAC and distribute it through their own data portal (DISTRIBUTOR).   

The following elements are also associated with Data Center:

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 chosen from a controlled vocabulary maintained in the Keyword Managenemt 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 (full version). 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. 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.


Examples:



Element Specification

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

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonDataCenter/Roles Enumeration

DISTRIBUTOR

ORIGINATOR

ARCHIVER


Yes1..*
UMM-CommonDataCenter/ShortName String
n/aYes1
UMM-CommonDataCenter/LongName String
n/aNo0..1
UMM-CommonDataCenter/Uuid Number
n/aNo0..1
UMM-CommonDataCenter/ContactInformation/RelatedURL String
n/aNo0..1
UMM-CommonDataCenter/ContactInformation/ServiceHours String
1 - 1024 charactersNo0..1
UMM-CommonDataCenters/ContactInformation/ContactInstructionsString
1 - 2048 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/ContactMechanism String
n/aNo0..*
UMM-CommonDataCenter/ContactInformation/ContactMechanism/Type Enumeration

PHONE

EMAIL

FACEBOOK

TWITTER

n/aYes1
UMM-CommonDataCenter/ContactInformation/ContactMechanism/Value String
1 - 1024 charactersYes1
UMM-CommonDataCenter/ContactInformation/Address/StreetAddresses String
1 - 1024 charactersNo0..*
UMM-CommonDataCenter/ContactInformation/Address/City String
1 - 100 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/StateProvince String
1 - 100 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/PostalCode String
1 - 20 charactersNo0..1
UMM-CommonDataCenter/ContactInformation/Address/Country String
1 - 100 charactersNo0..1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/UrlContentType = DataCenterURLString
1 - 4000 charactersYes1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/Type = HOME PAGEStringURL Content TypesKMS controlledYes1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/SubTypeStringURL Content TypesKMS controlledNo0..1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/DescriptionString
1 - 1024 charactersNo0..1
UMM-CommonDataCenters/ContactInformation/RelatedURLs/UrlString
n/aYes1..*




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

Priority CategorizationJustification

This element is categorized as highest priority when:

  • No Related URLs are provided
  • 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 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
  • The URL provided in the metadata redirects - it is recommended that the most current link always be provided

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 element is provided, and follows all applicable criteria specified in the best practices section above.

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 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..*
DIF 10Organization/ Personnel/ RoleString

Yes1..*
DIF 10Organization/ Personnel/ Contact_Person/ First_NameString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ Middle_NameString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ Last_NameString

Yes1
DIF 10Organization/Personnel/Contact_Person/uuidString

No0,.1
DIF 10Organization/ Personnel/ Contact_Person/ Address/ Street_AddressString

No0..*
DIF 10Organization/ Personnel/ Contact_Person/ Address/ CityString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ Address/ State_ProvinceString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ Address/ Postal_CodeString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ Address/ CountryString

No0..1
DIF 10Organization/ Personnel/ Contact_Person/ EmailString

Yes0..*
DIF 10Organization/Personnel/Contact_Person/PhoneString

No0..*
DIF 10Organization/ Personnel/ Contact_Person/ Phone/ NumberNumber

Yes1
DIF 10Organization/ Personnel/ Contact_Person/ Phone/ TypeEnumeration

Telephone

Direct Line


Yes1
DIF 10Organization/ Personnel/ Contact_Group/ NameString

No0..1
DIF 10Organization/Personnel/Contact_Group/Name attribute uuidString

No0..1
DIF 10Organization/ Personnel/ Contact_Group/ Address/ Street_AddressString

No0..*
DIF 10Organization/ Personnel/ Contact_Group/ Address/ CityString

No0..1
DIF 10Organization/ Personnel/ Contact_Group/ Address/ State_ProvinceString

No0..1
DIF 10Organization/ Personnel/ Contact_Group/ Address/ Postal_CodeString

No0..1
DIF 10Organization/ Personnel/ Contact_Group/ Address/ CountryString

No0..1


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>
  </Organization_Name> CIESIN_SEDAC_ESI_2000 </Dataset_ID>
 <Personnel>
 <Role> DATA CENTER CONTACT </Role>
 <Contact_Group>
 <Name> SEDAC USER SERVICES </Name>
 <Adress>
 <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>

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

ECHO 10

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

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10Contacts/ Contact/ RoleString
1 - 80 charactersYes1
ECHO 10Contacts/ Contact/ Hours of ServiceString
1 - 1024 charactersNo0..1
ECHO 10Contacts/ Contact/ InstructionsString
1 - 2048 charactersNo0..1
ECHO 10Contacts/ Contact/ Organization NameString
1 - 200 charactersNo0..1
ECHO 10Contacts/ Contact/ Organization Addresses/ Address/ Street AddressString
1 - 1024 charactersYes1
ECHO 10Contacts/ Contact/ Organization Addresses/ Address/ CityString
1 - 80 charactersYes1
ECHO 10Contacts/ Contact/ Organization Addresses/ Organization Address/ State ProvinceString
1 - 30 charactersYes1
ECHO 10Contacts/ Contact/ Organization Addresses/ Address/ Postal CodeString
1 - 20 charactersYes1
ECHO 10Contacts/ Contact/ Organization Addresses/ Address/ CountryString
1 - 10 charactersYes1Use "Unknown" if no value exists
ECHO 10Contacts/ Contact/ Organization Phones/ Phone/ NumberNumber
1 - 23 charactersYes1
ECHO 10Contacts/ Contact/ Organization Phones/ Phone/ TypeString
1 - 30 charactersYes1
ECHO 10Contacts/ Contact/ Organization Emails/ Email String
1 - 1024 charactersNo0..*


Enumeration Mapping

N/A

Example Mapping

ECHO 10

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

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"
  },
  {
    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.

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.10.05/2/2018<>
1.9.0

ARC Documentation

VersionDateWhat ChangedAuthor
1.07/25/18Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux



  • No labels