IOOS Data Management The Plan

1
IOOS Data Management The Plan

• Sixty-six expert team members
• 6 Federal agencies
• 12 Universities
• 4 Not-for-Profit Corporations
• 2 State agencies
• 1 International Research Consortium
• 1 For-Profit Corporation
• Six sub-teams
• Data Archive Access
• Data Discovery Metadata
• Data Transport
• Applications Products
• User Outreach
• 18 months in preparation
• 3 months community review
• Published May 2004

2
IOOS Data Management - DMAC

• 30-day public comment period began Nov 10, 2004
  with Federal Register Notice
• Final Plan goes to NORLC as representing
  consensus (Dec)

3
Key Findings

• A coherent strategy is needed to integrate marine
  data streams across disciplines, time scales,
  geographic regions, and institutional sources
• Technology is not an insurmountable barrier
• Principal challenge best characterized as one of
  coordination and cooperation among participants
• Standards will vary - One size wont fit all

4
Differing User Needs Add Dimensions to Standards
Development, and Not All Users Are Created Equal

• Marine buoys
• Water level
• Water flow currents
• Wave gauges
• Bathymetry
• Satellite imagery
• Habitat surveys
• LMR surveys

5
Example SEACOOS ApproachProvide observations
(data) and GIS maps (information) from
distributed sources

• OpenDAP
• netCDF
• Climate Common Data Language (CDL) extended
  marine data
• Internet GIS map services

6
Two-Tiered IOOS DMAC Approach Taken

• Establish sustainable, community-based IOOS
  standards evolution process
• Hit must do standards areas first
• Metadata and discovery
• Machine-to-machine data exchange with meaning
  (data selection, extraction and transport)
• Cooperative data archival framework

7
Process Overview

• Ocean.US DMAC Steering Team now underway
  (Community based)
• Standards-specific technical working groups to be
  formed (e.g., metadata)
• Federal inter-agency IOOS Implementation
  Oversight Working Group (influencing current
  programs, budget development, coordination)

8
Must Do Near-term Concrete Standards Actions

• Providers of certain types of data should for
  time being partner for management of data
• Mooring buoy data ? National Data Buoy Center
• Model output ? U.S. GODAE Server Center
• Must leverage (influence?) current activities
  (e.g., COTS, ONR, NSF, NASA, etc.) to address
  pressing needs
• Metadata
• Data discovery
• Data transport
• Data archival
• Online exploration and browsing

9
Pressing Needs

• Consistent, IOOS-wide descriptions of data
  (metadata)
• Vocabulary
• Content
• Ability to search and find data/information of
  interest
• FGDC Clearing House (at a minimum)
• Other ?
• Ability to access/retrieve data and information -
  parsing if user needs to - via Internet using
  common browsers
• Ability for users to evaluate character of data
  using common browsers
• Secure, responsive long-term data storage
  (archival)

10
Leave Behind Thoughts

• Each observing activity should publish its data
  in a consistent manner so that it can be
  discovered, retrieved or extracted, and
  transported by/to the user on a
  machine-to-machine interoperable basis
• This will require common approaches for
  publishing data and associated metadata
• Tasks to achieve this will have to be taken on by
  funded activities