Author(s): user-73cc8

 

Description of Problem

  • For some URLs, specifically those associated with Citations, OnlineResource class provides an alternate to RelatedURL and helps to bring the CMR towards interoperability with other systems.

JIRA Linkage

ECSE-88 - Revise Related URL content and usage in UMM, MMT, and CMR COMPLETED

 

Background

Related URLs - this element describes any data/service related URLs that include project home pages, services, related data archives / servers, metadata extensions, direct links to online software packages, web mapping services, links to images, or other data.  

Currently ECHO10 metadata which use /Collection/OnlineResource or /Collection/OnlineResources/OnlineResourceURL can be mapped to UMM-C OnlineResource class. DIF9 metadata which use /DIF/Reference/Online_Resource can be mapped to UMM-C OnlineResource class.

 

 

Approach

For UMM and CMR, we propose the following fundamental tenents to guide the resolution of issues related to additional attributes and acquisition information:

  • Focus on the CMR community and their metadata uses.   Metadata standards, recommendations, and guidance only make sense in the context of a community and their use cases for the metadata.  When deciding between options for a UMM metadata structure, we choose the one that makes sense for the CMR community.  We learn from other communities, such as the ISO community, but our focus is on the metadata needs of the CMR community.

  • Learn from ISO, but don’t blindly reuse ISO metadata structures.  Whenever possible,  have a single UMM metadata structure that might map to multiple locations in ISO.   We don’t need the flexibility and complexity of ISO to support the rich metadata needs of the CMR.   

  • Whenever possible,  specific typed metadata structures should be created from the  classification  of additional attributes.   For example,  in UMM-C-136 our approach would move information from additional attributes to enhance the structure of Platform/Instrument characteristics  instead of moving the characteristics into new additional attributes.   Over time, this tenent will produce a richer UMM structure that evolves as our understanding of metadata, applications, and missions evolves.

Analysis/Recommendations

 

  • Recommend incorporating the OnlineResource class to the UMM as an alternate to RelatedURL for such cases. Useful for Web pages which contain resources, e.g. downloadable files (e.g. CSV, PDF, DOC files
  • Use ISO CI_OnlineResource attributes: Linkage, Name, Description, Function at a minimum. See UMM-Common model diagram for class specification.

Changes to UMM-Common fields 

Publication

 

Currently:                                                               Change To:

 

Publication
 
Publication
 
/ResourceCitationType/ResourceCitationType
/ResourceCitationType/Version/ResourceCitationType/Version
/ResourceCitationType/RelatedUrl/ResourceCitationType/OnlineResources
/ResourceCitationType/Title/ResourceCitationType/Title
/ResourceCitationType/Creator/ResourceCitationType/Creator
/ResourceCitationType/Editor/ResourceCitationType/Editor
/ResourceCitationType/SeriesName/ResourceCitationType/SeriesName
/ResourceCitationType/ReleaseDate/ResourceCitationType/ReleaseDate
/ResourceCitationType/ReleasePlace/ResourceCitationType/ReleasePlace
/ResourceCitationType/Publisher/ResourceCitationType/Publisher
/ResourceCitationType/IssueIdentification/ResourceCitationType/IssueIdentification
/ResourceCitationType/DataPresentationForm/ResourceCitationType/DataPresentationForm
/ResourceCitationType/OtherCitationDetails/ResourceCitationType/OtherCitationDetails
/ResourceCitationType/DOI/ResourceCitationType/DOI