DAAC Roles with Common Metadata Repository (CMR) ESDIS System Engineering Technical Interchange November 2014 Copyright © 2014 Raytheon Company. All Rights Reserved

What we’ve covered so far… /

Micro-service Based Architecture

Sub-second Search

Multiple Metadata Concepts Services Metadata Parameter Metadata Visualization Metadata Future Metadata Concepts Science Metadata Meta-Metadata (Collections and Granules)

Unified Metadata Model ECHO 10GCMD DIFEMS ISO Atom JSON … Ingest Adapter UMM-C … … UMM-G ECHO 10 UMM-S GCMD SERF UMM-V Visualization (GIBS) UMM-P Parameters/Variables (Giovanni AESIR) UMM-? Future Concepts

UMM-* Development Outline Stakeholder Interviews Surveying Existing Implementations Defining and Crosswalking Fields Defining Relationships Identifying Subsystem Interactions Tailoring Lifecycle ESDIS Standards Office (ESO) review

What’s ahead… ok … maybe a little more bumpy /

METADATA RECONCILIATION IS COMING

Collections (UMM-C) UMM-C GCMD DIF Model ECHO10 Collection Model ESDIS Metrics Model

Reconciliation What is it? When should I expect it? What do I need to do to prepare? What problems should I expect? How long will it take? ECHO + GCMD + EMS

What it is ECHO + GCMD + EMS One submission per product/collection – ECHO or GCMD DIF record CMR as the authoritative source Short Name + Version/Entry ID Unification UMM Compliant (Collections and Granules) – Provisional UMM-C May include products not in EMS/ECHO/GCMD BEDI/CDI Datasets are High Priority

What it is PlanMergeClean

When you should expect it “Soon” First 4 DAACs identified for reconciliation – NSIDC – LP DAAC / USGS EROS – LARC – PO.DAAC Preliminary data collection is well underway We are looking at your holdings and will help you make informed decisions

What you should do to prepare Know your data and empower your points of contact Identify POCs for current systems – DIF Authors – ECHO/EMS contacts – Other Stakeholders Are you still using FTP? Do ECHO/EMS/GCMD have all your data? Do you know what your ECHO additional attributes are? Know the list of required fields for UMM-C

What problems you could expect Controlled vocabulary mismatch, Entry ID issues … Do your Entry IDs and Short Names align? Are your Science Keywords correct/current? Do you have different teams preparing data for ECHO/EMS/GCMD? Are there UMM-C required fields you can’t provide for some collections? How are your granules referring back to parent collections?

The Process Initial Contact & Stakeholder Identification Tailored Reconciliation Package Package Review Period Facilitated Stakeholder Meeting Plan & Timeline

The Process Initial Contact & Stakeholder Identification Tailored Reconciliation Package Package Review Period Facilitated Stakeholder Meeting Plan & Timeline Reconciliation Package Contents: Metadata holdings report Submission process report Options for future submission Potential pain points identified Reconciliation Package Contents: Metadata holdings report Submission process report Options for future submission Potential pain points identified

The Process Initial Contact & Stakeholder Identification Tailored Reconciliation Package Package Review Period Facilitated Stakeholder Meeting Plan & Timeline Example activities might include: REST API migration Metadata merge working meetings Adapter development CMR Resources may be available if needed Example activities might include: REST API migration Metadata merge working meetings Adapter development CMR Resources may be available if needed

Each DAAC’s process will be unique. One size does not fit all. Each DAAC’s process will be unique. One size does not fit all.

Other DAAC Roles Participating in UMM review process Suggesting improvements and enhancements Requesting new concepts

Where can I get help? How can I help? Process Help & API Support – Katie Baynes Metadata Quality & Keyword Support – Scott Ritz ESO Review and Requests – General Questions –

Metadata Quality Assurance ©iStock.com/BrianAJackson

Made with wurdle.com Questions?

Earthdata Search Client