ESO and the CMR Life Cycle Process Winter ESIP, Jan 2015 ESDIS Standards Office (ESO) Yonsook Enloe Allan Doyle Helen Conover

ESDIS Standards Office (ESO) Background The ESDIS Standards Office (ESO) assists the ESDIS Project in formulating standards policy for NASA Earth Science Data Systems (ESDS), coordinates standards activities within ESDIS. Funded mission data systems can use the ESO recommended standards with high confidence that the specification is accurate and works with NASA data in NASA environments. ESO reviews an existing convention or standard to evaluate the technical value of the specification, determine its fitness for purpose, confirm that working implementations exist. ESO supports developing standards via feedback to the authors of new specifications in order to help improve the quality of the developing standard. ESO also can help evaluate developing standards by evaluating a prototype of its capabilities. The ESO supports the CMR Systems Engineering Team (SET) by managing and conducting a series of internal and public reviews of the developing specifications for the Common Metadata Repository (CMR), including the underlying Unified Metadata Model (UMM) 2

Stakeholder Input on CMR 3 To maintain the quality and usefulness of EOSDIS metadata for users (discoverability, usability, etc.), CMR relies on stakeholder input into all aspects of CMR including UMM concepts, GCMD Keywords, and documents that describe CMR processes. The ESO review process for the CMR developing standards and best practices will be a regular part of the CMR development. ESO reviews will be a routine and regular part of the CMR life cycle for metadata moving forward. These reviews need stakeholder participation. Reviews will be conducted via Jama, an easy-to-use, online tool. We have Jama guides and a 4 minute training video for ESO reviewers to make it as easy as possible. ESO and SET are building and maintaining lists of stakeholder subject matter experts who can be called upon for reviews. Please contact ESO or Yonsook Enloe to have your name added to the list of

How to Request a Change to CMR 4 All requests for changes or additions to CMR use the existing support already used for reporting issues and bugs across ESDIS supported systems: This includes change requests for: All CMR system components: CMR/ECHO APIs, CMR/ECHO tools and their interfaces, GCMD-related tools such as docBuilder, GCMD Portals and their configurations, Keyword Management System, and any other related tool or service All CMR metadata components: UMM-*, GCMD DIFs/SERFs, GCMD Keywords, other controlled vocabularies, schema constraints, ingest/output formats/standards, etc. This also includes routine requests for new keywords to support new platforms, instruments, organizations, science disciplines, etc.

CMR Life Cycle Overview 5 The CMR life cycle defines the process by which requirements for all CMR elements are managed, updated, modified, reviewed, and approved for implementation through open and transparent processes involving all stakeholders. 1.Change request received from stakeholder 2.After initial vetting, CMR Systems Engineering Team (SET) assembles a team to do cost-benefit analysis of change and presents recommendation to SET Lead. 3.If approved, requirements undergo internal review (in Jama) 4.Changes that impact external stakeholders (e.g. DAACs, users) undergo ESO review Analysis team prepares formal package for ESO. ESO assembles Technical Working Group (including DAAC representatives) to conduct review, collect comments, and make a recommendation on the proposed change. Some reviews will be internal and/or for comment only Analysis team dispositions any comments 5.Final requirements package goes to CMR Project Manager for approval. 6.If approved, changed requirements get scheduled for implementation 7.New release is publicly announced.

Major CMR Current Activities 6 Defining and documenting processes: CMR Life Cycle Document – Describes process for assessing, reviewing, and approving requirements for CMR including UMM concepts, GCMD Keywords, and other controlled vocabularies CMR Metadata Quality Assurance Life Cycle Document - Describes the process for reviewing all CMR metadata content to maximize data discoverability and usability; includes periodic reviews of all metadata and methods for assessing quality GCMD Keywords Community Guide – Targeted for the community, contains information on GCMD keywords, keyword structure and rules, and an overview of how GCMD engages with the community to keep the keywords relevant and useful Implementing these processes for: UMM-C (Collections) - Metadata model for collections that harmonizes the GCMD DIF and ECHO10 models, including mappings to ISO UMM-G (Granules) - Metadata model for granules, largely based on ECHO10 UMM-S (Services) – Metadata model for services, initially based on GCMD SERFs UMM-P (Parameters/Variables) – Metadata model for parameters/variables (e.g., AESIR) UMM-V (Visualization) – Metadata model to support visualization tools, initially GIBS

Next Steps 7 ESO will seek reviewers drawing upon the lists of participants being provided by the DAACs and also add subject matter experts ESO Reviews of CMR UMM-C, UMM-GDec 2014 UMM-S, UMM-VFeb/March 2015

Related Resources 8 ESO Main Page ESO Standards and References references references ESO Standards Process references/standards-process-overview references/standards-process-overview ESO CMR Review Page