Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColor#accdef
bgColor#ededed
titleBGColor#ebebeb
borderWidth1
titleIntroduction
borderStylesolid

The Common Metadata Repository (CMR) catalogues all data and service metadata records for the EOSDIS system.  These metadata records are registered, modified, discovered, and accessed through programmatic interfaces leveraging standard protocols and APIs.

  • CMR will be the authoritative management system for all EOSDIS metadata for all EOSDIS data holdings.
  • CMR is a common middleware replacement for for the ECHO backend and GCMD’s backend. The GCMD frontend, however, will not change and users of GCMD should see no impact.
  • CMR is designed to handle metadata at the Concept level beyond just Collections and Granules to Visualizations, Parameters, Documentation, Services, and more.
  • CMR is designed around an evolvable Unified Metadata Model (UMM).
  • CMR is designed to handle hundreds of millions of metadata records; making them available through high performance, standards compliant, temporal, spatial, and faceted search.
  • CMR incorporates both human and machine metadata assessment features that work to ensure the highest quality metadata possible
Panel
borderColor#accdef
borderWidth1
titleUnified Metadata Model (UMM)
borderStylesolid

The Unified Metadata Model is a model that encompasses various metadata profiles maintained and archived by EOSDIS. The UMM will be used by the Common Metadata Repository and will drive search and retrieval of metadata cataloged within that system.

The UMM is managed as a series of documents, each covering a subset of the entire UMM. The UMM documents are listed on the UMM Documents page. An overview of the UMM can be seen by clicking on the box below

UI Expand
titleUMM Overview

Quick overview:

  • UMM stands for Unified Metadata Model
  • UMM profiles are not metadata standards
  • UMM-C represents Collection Metadata
  • UMM-G represents Granule Metadata
  • UMM-S represents Service Metadata (TBD)
  • UMM-V represents Visualization Metadata (TBD)
  • UMM-P represents Parameter Metadata (TBD)
  • New UMM profiles will be added in the future.


More details:

First a link to a presentation: AGU Fall 2014 - Streamlining Metadata in NASA EOSDIS CMR 

To increase the level of quality and consistency among its metadata holdings, EOSDIS has developed (and continues to develop and expand) a model for various metadata profiles that it archives and maintains. This model aims to document vital elements that may be represented across various metadata formats and standards and unify them through core fields useful for data discovery and service invocations. This unified model, aptly named the Unified Metadata Model (UMM), has been developed as part of the EOSDIS Metadata Architecture Studies (MAS I and II) conducted between 2012 and 2013.

 

The UMM will be used by the Common Metadata Repository (CMR) and will drive search and retrieval of metadata cataloged within that system.

 

All UMM profiles will be mapped to the ISO 19115 metadata model as shown in the diagram below.

 

 

 

 

 

 


Left-over - needs a home...

 

 

UI Expand
titleCMR Metadata Reconciliation

Data Provider Metadata Reconciliation

...