Page History

Table of Contents

style	circle

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:

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.

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.

Contact Information: Any relevant contact information for the data center can be provided in the Contact Information fields. Providing contact information is optional, but it is recommended that some minimal contact information such as a link, email or phone number be provided in case the user has questions about the data set. Some examples of contact information that can be provided include: phone number, email, fax, related links, service hours, contact instructions. See the element specification table below for full details.

Examples:

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/RelatedURL/URL: https://ghrc.nsstc.nasa.gov/home/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..*)

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
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???	1..*	This URL should be a link to the home page of the Data Center's website.
UMM-Common	DataCenters/ContactInformation/RelatedURLs/UrlContentType	Enumeration	DataCenterURL	n/a	Yes???	1	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??	1	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 recommended that a description be provided for each URL.
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 Email Facebook Fax Mobile Modem Primary TDD/TTY Phone Telephone Twitter 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	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

title	GCMD Metadata QA/QC

Expand

title	CMR Validation

<>

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: No Data Center information is provided 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 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 The URL provided is incorrect/ unrelated to the associated data setcenter The URL Content Type or Subtype provided does not accurately describe the link (i.e. the link is mislabeled)match the enumeration value "DataCenterURL" The URL Type or Subtype 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 align with the KMS The Type or Subtype does not exist in the KMS The Type or Subtype Short Name and/or Long Name is placed in the incorrect position of the hierarchy (e.g. GET DATA DOC/NOAA/OOE should not be provided in the Subtype Long Name field, because it is categorized as a Type keyword Short Name in the KMS) There is an invalid TypeShort Name/ Subtype Long Name relationship (e.g. Type: GET DATA, Subtype: USER'S GUIDEShort 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 URL links to an FTP server (this only applies to NASA EOSDIS metadata)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 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.A recommendation is made to change a valid URL Type or Subtype keyword for purposes of consistency with other similar metadata records The Data Center 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 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 Data Center Related 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

Expand

title	DIF 9

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

Expand

title	DIF 10

DIF 10

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

Specification	Path	Type	Usable Valid Values	Required in DIF 10?	Cardinality
DIF 10	Organization/ Organization_Type	Enumeration	PROCESSOR ORIGINATOR ARCHIVER DISTRIBUTOR	Yes	1..*
DIF 10	Organization/ Organization_Name/ Short_Name *	String		Yes	1
DIF 10	Organization/ Organization_Name/ Long_Name *	String		No	0..1
DIF 10	Organization/Organization_Name attribute uuid	String		No	0..1
DIF 10	Organization/ Hours_Of_Service	String		No	0..1
DIF 10	Organization/ Instructions	String		No	0..1
DIF 10	Organization/ Organization_URL	String		No	0..1
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

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>

Column

width	50%

UMM

No Format

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

Expand

title	ECHO 10

ECHO 10

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

Specification	Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10	Contacts/ Contact/ Role	String	1 - 80 characters	Yes	1
ECHO 10	Contacts/ Contact/ Hours of Service	String	1 - 1024 characters	No	0..1
ECHO 10	Contacts/ Contact/ Instructions	String	1 - 2048 characters	No	0..1
ECHO 10	Contacts/ Contact/ Organization Name	String	1 - 200 characters	No	0..1
ECHO 10	Contacts/ Contact/ Organization Addresses/ Address/ Street Address	String	1 - 1024 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Addresses/ Address/ City	String	1 - 80 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Addresses/ Organization Address/ State Province	String	1 - 30 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Addresses/ Address/ Postal Code	String	1 - 20 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Addresses/ Address/ Country	String	1 - 10 characters	Yes	1	Use "Unknown" if no value exists
ECHO 10	Contacts/ Contact/ Organization Phones/ Phone/ Number	Number	1 - 23 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Phones/ Phone/ Type	String	1 - 30 characters	Yes	1
ECHO 10	Contacts/ Contact/ Organization Emails/ Email	String	1 - 1024 characters	No	0..*

Enumeration Mapping

N/A

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

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

Column

width	50%

UMM

No Format

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

Expand

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.

Specification	Path	Type	Notes
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL	String	Where the URL is provided. Maps to the UMM element RelatedUrls/URL. Note: This path only applies to CollectionURLs and PublicationURLs.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Description: "	String	Maps to the UMM element RelatedUrls/Description. A brief, unique description of the URL should be provided in this field. It is highly recommended that a description be provided for each URL. * The character string should always start with the prefix "Description: " in order for CMR to properly parse out the URL description.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType: "	String	Maps to the UMM element RelatedUrls/URLContentType. The URL Content Type is required in UMM and is used to specify how the link will display in the Earthdata Search Client. The URL Content Type must be selected from the following controlled vocabulary options: CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL. Please see the best practices section (above) on guidance on choosing the correct URL Content Type. * The character string should always start with the prefix "URLContentType: " in order for CMR to properly parse out the URL Content Type.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Type: "	String	Maps to the UMM element RelatedUrls/Type. Providing a URL Type is required in UMM. Failing to specify a Type in ISO metadata will result in the field being auto-populated by the CMR, which could result in the URL being mislabeled. URL Type is a GCMD controlled vocabulary field and must be selected from keywords in the KMS. Please see the best practices section (above) on guidance on choosing the correct URL Type. * The character string should always start with the prefix "Type: " in order for CMR to properly parse out the URL Type.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/ gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Subtype: "	String	Maps to the UMM element RelatedUrls/Subtype. Providing a URL Subtype is optional, but is encouraged if an appropriate URL Subtype exists. URL Subtype is a GCMD controlled vocabulary field and must be selected from keywords in the KMS. Please see the best practices section (above) on guidance on choosing the correct URL Subtype. * The character string should always start with with the prefix "Subtype: " in order for CMR to properly parse out the URL Subtype.

Enumeration/Code List Mapping

N/A

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

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

Column

width	50%

UMM

No Format

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

Expand

title	ISO 19115-2 SMAP

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
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 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	gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="URLContentType:"	String	Maps to the UMM element RelatedUrls/URLContentType. The value must start with the string "URLContentType: " in order for CMR to properly identify the URL Content Type. The URL Content Type is required in UMM and is used to specify how the link will display in the Earthdata Search Client. The URL Content Type must be selected from the following controlled vocabulary options: CollectionURL, PublicationURL, DataCenterURL, DistributionURL, DataContactURL, VisualizationURL. Please see the best practices section (above) on guidance on choosing the correct URL Content Type.
ISO 19115-2 SMAP	gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Type:"	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 SMAP	gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/ gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty/ gmd:contactInfo/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description/gco:CharacterString="Subtype:	String	Maps to the UMM element RelatedUrls/Subtype. The value must start with the string "Subtype: " in order for CMR to properly identify the URL Subtype. Providing a URL Subtype is optional, but is encouraged if an appropriate URL Subtype exists. URL Subtype is a GCMD controlled vocabulary field and must be selected from keywords in the KMS. Please see the best practices section (above) on guidance on choosing the correct URL Subtype.

Enumeration/Code List Mapping

N/A

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format

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

Column

width	50%

UMM

No Format

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

Expand

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.

Specification	Type	Notes
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

Section

Column

width	50%

ISO 19115-1

No Format

Column

width	50%

UMM

No Format

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

Version	Date	What Changed
1.10.0	5/2/2018	<>
1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.0	7/25/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux

Page tree

Versions Compared

Old Version 23

New Version 24

Key

Element Description

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

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation