Photo credit left to right:  Dr. John Payne, Pacific Ocean Shelf Tracking Project, Rutgers University, CeNCOOS, PacIOOS, SECOORA

Photo credit left to right: Dr. John Payne, Pacific Ocean Shelf Tracking Project, Rutgers University, CeNCOOS, PacIOOS, SECOORA

Welcome data contributors!

Below are the data management and communications requirements for IOOS Regional Associations and other IOOS grant recipients who are providing data to IOOS.

 

  1. Open Data Sharing

    IOOS, being a part of the Global Earth Observing System of Systems (GEOSS), ascribes to the GEOSS data sharing principles.
  2. Data management planning and coordination

    Data management is an increasingly important aspect of IOOS activities. Data management plans and the coordination of activities between Regions and the IOOS Program Office ensure that data are maintained in easily accessible formats that are archived for long-term storage.
  3. Provision of data to the Global Telecommunication System (GTS)

    U.S. IOOS is committed to ensuring that all relevant U.S. coastal ocean observations will be contributed in near real time to the global GTS network.
  4. Data access services

    All IOOS Data Providers must serve all data and products through these DMAC recommended services.
  5. Catalog registration

    The IOOS Catalog is the master inventory of IOOS DMAC datasets and data access services.
  6. Common data formats

    U.S. IOOS® data providers are expected to offer data in one or more approved U.S. IOOS® formats .
  7. Metadata standards

    All IOOS data providers are expected to ensure relevant metadata is produced, accessible and compliant with IOOS conventions, and to participate as appropriate in the development of such conventions. Descriptive information about datasets, sensors, platforms, models, analysis methods, quality-control procedures is essential for the long-term usability and reuse of information.
  8. Storage and archiving

    Data providers are expected to provide for storage of data, metadata and other supporting documentation and algorithm descriptions, to establish data recovery mechanisms, and to perform off-site storage of backups until the data and metadata are submitted to NCEI for archiving.
  9. Ontologies, vocabularies, common identifiers

    IOOS is presently developing and adopting shared vocabularies for terminology such as names of observed properties, units of measure, coordinate reference systems, animal species, etc.
  10. Consideration for Long-term Operations

    The IOOS observing, data management, and modeling capacities being developed will, ideally, persist as the overall enterprise matures. In data managements plans, IOOS partners should include a discussion of potential plans for maintaining such persistence as part of normal IOOS operations (e.g., by automating as many activities as possible, implementing operational procedures).

 

The U.S. IOOS Program Office is happy to answer any questions you have. Please feel free to contact the IOOS Program Operations Division (data.ioos@noaa.gov)