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

Compare with Current View Page History

« Previous Version 5 Next »

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:



Element Specification

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

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonDataCenterString
n/aYes1..*
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 String
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 String
n/aNo0..*
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/RelatedURLsString
1 - 4000 charactersNo0..*
UMM-CommonDataCenters/ContactInformation/RelatedURLs/UrlContentType = DataCenterURLString

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


Yes1
DIF 10Organization/ Organization_Name/ Long_Name *


No0..1
DIF 10Organization/Organization_Name attribute uuid


No0..1
DIF 10Organization/ Hours_Of_Service


No0..1
DIF 10Organization/ Instructions


No0..1
DIF 10Organization/ Organization_URL


No0..1
DIF 10Organization/ Data_Set_ID


No0..*
DIF 10Organization/Personnel


Yes1..*
DIF 10Organization/ Personnel/ Role


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


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


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


Yes1
DIF 10Organization/Personnel/Contact_Person/uuid


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


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


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


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


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


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


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


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


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


Yes1
DIF 10Organization/ Personnel/ Contact_Person/ Phone/ TypeEnumerationTelephone
Yes1
DIF 10Organization/Personnel/Contact_Group


Choice of 11..*
DIF 10Organization/ Personnel/ Contact_Group/ Name


No0..1

Organization/Personnel/Contact_Group/Name attribute uuid


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


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


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


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


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


No0..1


Example Mapping

DIF 10

<Related_URL>
  <URL_Content_Type>
    <Type>DATA SET LANDING PAGE</Type>
  </URL_Content_Type>
  <URL>https://doi.org/10.3334/ORNLDAAC/1568</URL>
  <Description>Access the data set landing page for the collection.</Description>
</Related_URL>
<Related_URL>
  <URL_Content_Type>
    <Type>VIEW RELATED INFORMATION</Type>
    <Subtype>USER'S GUIDE</Subtype>
  </URL_Content_Type>
  <URL>https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html</URL>
  <Description>The guide document contains detailed information about the data set.</Description>
</Related_URL>

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 10/Collection/OnlineResources/OnlineResource/URLString


Yes1
ECHO 10/Collection/OnlineResources/OnlineResource/DescriptionString

No0..1
ECHO 10/Collection/OnlineResources/OnlineResource/TypeStringKMS controlled
Yes1ECHO 10 only has a single URL Type field (not a Type and Subtype field). Thus, a URL Type may be selected from either the URL Type or Subtype keywords.
ECHO 10/Collection/OnlineResources/OnlineResource/MimeTypeStringKMS controlled
No0..1It is recommended that a mime type always be provided for service URLs.
ECHO 10/Collection/AssociatedBrowseImageUrls/ProviderBrowseUrl/URLString


No0..1This element can be used to link to a browse image. Browse images may also be provided as an Online Resource URL. Use of the Associated Browse URL element is discouraged in favor of the Online Resource URL.
ECHO 10/Collection/AssociatedBrowseImageUrls/ProviderBrowseUrl/DescriptionString

No0..1A brief explanation/ description of the browse image.


Enumeration Mapping

N/A

Example Mapping

ECHO 10

<OnlineResources>
  <OnlineResource>
    <URL>https://doi.org/10.3334/ORNLDAAC/1568</URL>
    <Description>Access the data set landing page for the collection.</Description>
    <Type>DATA SET LANDING PAGE</Type>
  </OnlineResource>
  <OnlineResource>
    <URL>https://daac.ornl.gov/ACTAMERICA/guides/ACTAMERICA-PICARRO_Ground.html</URL>
    <Description>The guide document contains detailed information about the data set.</Description>
    <Type>USER'S GUIDE</Type>
  </OnlineResource>
  <OnlineResource>
    <URL>https://daac.ornl.gov/graphics/browse/project/act-america_logo.png</URL>
    <Description>Browse Image</Description>
    <Type>GET RELATED VISUALIZATION</Type>
    <MimeType>image/png</MimeType>
  </OnlineResource>
</OnlineResources>

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