17
Streamlining Metadata in NASA's EOSDIS Common Metadata Repository (CMR) Kathleen Baynes Raytheon Company Andrew Mitchell NASA GSFC Kevin Murphy NASA GSFC Dan Pilone Element 84 This work was supported by NASA/GSFC under Raytheon Co. contract number NNG10HP02C. ESIP Winter Meeting 2015

Streamlining Metadata in NASA's EOSDIS Common Metadata Repository

Embed Size (px)

Citation preview

Streamlining Metadata in

NASA's EOSDIS Common

Metadata Repository (CMR)

Kathleen Baynes – Raytheon Company

Andrew Mitchell – NASA GSFC

Kevin Murphy – NASA GSFC

Dan Pilone – Element 84

This work was supported by NASA/GSFC under Raytheon Co. contract number NNG10HP02C.

ESIP Winter Meeting 2015

Some Background

• NASA’s EOSDIS System has two

metadata catalogs.

– GCMD: Global Change Master Directory

– ECHO: EOS Clearinghouse

• These systems are being combined into

the Common Metadata Repository (CMR)

So What’s the Problem?

“Metadata serves as the foundation for

data discovery for all of EOSDIS. ”

To be most effective, metadata must to be:

• Simple to generate, submit, and

maintain

• Consistent and informative

When we have high-quality, reliable, and consistent

metadata, we can begin building truly insightful systems

for scientific problem solving.

Just looking at Collections…

• Many metadata dialects CMR must handle

– ISO 19115

– DIF

– ECHO10

– More? Gosh I hope not.

• Several core concepts

– Data Identification

– Descriptive Keywords

– Extent Information

– Acquisition Information

Streamlining Via The UMM

• UMM: Unified Metadata Model (Mapping)

– Several Profiles

• Collections

• Granules (File)

• Services

• Visualizations

– Crosswalk across many core elements and

formats

Multiple Metadata Profiles

Services Metadata

Parameter Metadata

Visualization Metadata

Future Metadata Concepts

Science Metadata

Meta

-Me

tadata

(Collections and Granules)

Why Not Just Stick to ISO 19115?

We sort of are.

Sample UMM-C Crosswalk

Why Not Just Stick to ISO 19115?

Part 2

• We want minimal impact on existing

metadata in the catalog

• The UMM is being built with ISO 19115 in

mind as its backbone.

• ISO 19115 is where we want to be

– Modular and flexible

– Internationally Accepted

– Allows for extension and revision

Unified Metadata Model

ECHO 10

GCMD DIF

EMS

ISO 19115

Atom

JSON

LOD

Ingest

AdapterUMM-C

UMM-G ECHO 10

UMM-S GCMD SERF

UMM-VVisualization (GIBS)

UMM-PParameters/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

Current Work and Future Plans

• Collections and Granules just completed ESO review

• CMR is using provisional versions of these models for its search

• Services and Visualizations are under development

• Metadata Reconciliation between ECHO and GCMD is underway

• Next Steps: Parameters, Documentation and Meta-Metadata

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

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

Each DAAC’s process will be

unique.

One size does not fit all.http://upload.wikimedia.org/wikipedia/commons/4/49/PSM_V53_D092_Various_snow_crystal_forms.pn

g

Made with wurdle.com

Questions?