Task 5.3

Task 5.1: Data policy and distribution
Task 5.2: Integration of biological data
Task 5.3: Platform registration and metadata management system
Task 5.4: Interoperable data flow from in situ measurements to archiving in data centers
Task 5.5: Enhancement of Quality Control procedures for sensor based biochemical data
Task 5.6: Definition of Quality Control procedures for HF Radar data
Task 5.7: Scientific calibration procedures on gliders data collection
Task 5.8: Linking JERICO-NEXT activities to a Virtual Access infrastructure 

Platform registration and metadata management system

Lead: IFREMER (Thomas Loubrieu)

Email address: Please login or register to view contact information.

There is a strong necessity to improve the management process of the metadata of the deployed observatories. This weakness has been highlighted during the SeaDatanet and MyOcean projects. We propose to give a major role to the observatory operators in managing the metadata. Dedicated interfaces will be implemented in order to allow operators to describe their instrument, to monitor them in real-time, to publish and to advertise the work of data acquisition. Providing these metadata publishing tools will also greatly facilitate discovery, visualisation and downloading fully INSPIRE compatible services. We will take into account and will be consistent with other experiment for industry sensors such as http://www.sensorcloud.com. The standards (Sensor Web Enablement –SWE) already implemented in other projects (SeaDataNet, ODIP & JERICO) will be used.

We will focus on few observatory networks on which we propose to implement observatory operator advanced services: FerryBox, fixed moorings and non permanent operational costal observation networks. The developments will be coordinated with related tasks in marine data management infrastructure projects (ODIP, SeaDataNet) or others European project managing observatories (Eurofleet, EuroARGO, future AtlantOS).

The steps to achieve our goals are to:

  • Define core services to be provided to observatory operators and identify which will be the data ingestion systems  involved for such an experiment (ROOSes for MyOCean, in datasets indexes-CDI- and EDIOS for SeaDataNet).

  • Define and prioritize with the targeted observatory network operators the services to be developed: data ingestion mode, specific events editions (deployments, calibrations, …), alerts on data availability and thresholds, monitoring dashboards, other publication facilities such as DOI registration.

  • Adapt the existing templates (SeaDatanet, ODIP, JERICO) to ingest SWE information from the targeted observatory networks.

  • Design and implement the data ingestion modules for targeted observatory networks

  • Design and implement the services to observatory operators

  • Design and implement the interface with data managements systems SeaDataNet and MyOcean ROOSes.

Provide automated quality control module through the web console applicable on standardized datasets (e.g. in ODV or NetCDF format) and implemented them through a Pilot-test Web Service, following the Web Processing Service (WPS) OGC standard. This service could be triggered on real-time and near real-time data flows.


D5.6 Requirements specifications for the observatory operator console (M16)

D5.7 Definition of SWE templates (sensorML and O&M) for the targeted observatory networks. Mapping for ingestion in data management systems (SeaDataNet: CDI, EDIOS, EuroGOOS ROOSes) (M24)

D5.8 Assessment of the reached/missed target requirements (M44)