URL

Element Description

The specific URL to the back-end service. A back-end service refers to any of the following types of services: (1) a service that permits user selection of service options for data transformations which are provided by the service(s) for any given collection; (2) a web service that uses standards-based protocols i.e. Open-source Project for a Network Data Access Protocol (OPeNDAP), Web Coverage Services (WCS), and Web Mapping Services (WMS); or (3) a web service that performs data processing., e.g., spatial subsetting, reprojection, reformatting, etc. These back-end services are available programmatically through APIs and generally consumed by front-end clients. 

Best Practices

The URL should provide a direct link to the location on the web where the service may be accessed. While not required, it is highly recommended that a description be provided for the URL provided in the metadata. The description should be kept brief and explain to the user that the link goes directly to the back-end service. 

Examples:

• OPeNDAP example: 
  • Description: Access to OPeNDAP protocol for GLDAS datasets.
  • URL Value: https://hydro1.gesdisc.eosdis.nasa.gov/opendap/GLDAS/contents.html
• SEDAC Hazards mapper example:
  • Description: Access the SEDAC Hazards mapper
    URL Value: https://sedac.ciesin.columbia.edu/mapping/hazards/

Element Specification

Metadata Validation

All records undergo CMR schema and business rule validation before entering the system. 

• The 'URLValue' element is required.
  • Must contain at least 1 character and be no longer than 1024 characters in length.
• The 'Description' element must contain at least 1 character and be no longer than 4000 characters in length.

History

UMM Versioning