documenting data to support discovery and use dave neufeld ted habermann john kozimor

Post on 27-Mar-2015

217 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Documenting Data to Support Discovery and Use

Dave Neufeld

Ted Habermann

John Kozimor

Where does it go?

Station Histories

Quality Measurements

Data Processing

Sensors

Extents

ParametersPeople

Levels of Documentation for OceanSITES

Content Distribution

Usage

Discovery

Program

(OceanSITES)

Network

(ESTOC, LINE, MBARI, TAU)

Platform

(M0, M1, M2,)

Deployment

(MO-04 M-05, MO-06, MO-07)

Sensor

(Current Profiler, CTD, CO2 Analyzer, Flurometer, Spectroradiometer )

ISO Content

ncISO: Generating ISO metadata from NetCDF and THREDDS

ISO Integration with Geoportal

Improving Discovery Documentation

Work with Data Managers• Improve Content• Expand Content• Review guidance on the wiki and the role of

Unidata’s Data Discovery Convention• Harmonize UDDC and OceanSITES User

manual

Improving Content

Depth of Content: Is information missing from existing metadata?– Are all PI’s included in the program level record?– Are all network contacts included in network level record?

Breadth of Content: Is the standard utilized to the fullest?– Is the data processing workflow described?– Are quality reports included?– Is the instrumentation described?– Is platform/instrument maintenance documented?

Organization of Content: Is information documented at the correct level?

Remapping OceanSITES to UDDC Examples

• http://www.ngdc.noaa.gov/thredds/ncisoExamplesCatalog.html

Expanding Content

NetCDF Conventions• UDDC• CF• Importance of Titles, Keywords, Abstract

• Lineage• Quality• Instrumentation

• WHOTS as a starting point for discussion on evolving conventions to include sensor level info: WHOTS Example link

Next Steps: Supporting Use Documentation

• Extending Existing Conventions – Deployment / Sensor / Lineage

• Incorporate into ISO• Incorporate OSMC ingest

Documentation Hierarchies

• Enable objects to be grouped by scope (level)

• Enable levels to be related or connected by hierarchy order

• Produce a comprehensive documentation structure

• Produce a complete archive information object

ISO Examples

Complete Hierarchyhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/iso_series/xml/oceansites_seriesV2.xml

Program Levelhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/network/xml/antares.xml

Network Levelhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/network/xml/antares.xml

Platform Levelhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/platform/xml/antares-1.xml

Deployment Levelhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/deployment/xml/antares-1_200509.xml

Sensor Levelhttp://www.ngdc.noaa.gov/metadata/published/NOAA/OAR/OCO/oceansites/sensor/xml/antares-1_200509.barometer.xml

Questions?

david.neufeld@noaa.gov

ted.habermann@noaa.gov

top related