1. Status of advanced access and viewing services following SeaDataNet D5.6 and D8.7 By Dick M.A. Schaap – Technical Coordinator Barcelona – Spain, 19 – 20 March 2014, Combined EMODNet Chemistry 2 TWG and SeaDataNet TTG

2. Robot harvester is operational and has been applied for automatically harvesting ca 1.000.000 T&S data sets as part of the joint data climatology product development SeaDataNet – MyOcean Robot harvester can be configured for specific data buffer profiles and in agreement (SLA’s) with data providers AND specific data user communities (such as MyOcean, SeaDataNet regional dataproduct groups, EMODNet Chemistry regional product groups, WG DIKE) MARIS is making good progress with implementing a buffer CMS to set profiles, to oversee harvesting and maintenance of buffers the central buffer system with specific subsets will be maintained automatically by the buffer CMS in connection with RSM - robot user system, following new and updated CDI submissions Working with a central buffer to support products generation and additional visualisation

4. Robot CMS + CDI buffer User Interface CDI User Interfaces CDI Robot harvester Specific data buffers CDI User Interface + Shopper: Access regulated via AAA Agreed Settings Dynamic Maintenance Robot CMS to configure Robot harvesting profiles MARIS master

5. the central buffer system will contain ‘raw’ data sets for specific parameters and as harvested from the distributed data centres => further action needed for making the collection more homogeneous and validated => aggregated data sets this can be done by using ODV software and specific expertise per region and chemical substance use will also be made of the new P35 Vocabulary for aggregating P01 terms. The P35 population is making progress: http://seadatanet.maris2.nl/v_bodc_vocab_v2/welcome.asp The access to these buffers of aggregate data sets can also be virtual for specific Workflow Processes (WPS) in which case only results and graphics of analyses are made available, not the individual data Converting buffer data sets to validated aggregated data sets

6. EMODnet Chemistry extension Specific data buffers Oceanotron & OpenEarth services ODV QC + aggregation QCd data buffers Regional experts DIVA + OceanBrowser service CDI Robot Harvester

7. Next to already existing ODV -> Diva -> OceanBrowser service for interpolated maps Use the robot harvester to build a central buffer of data sets with regular updating intervals Extract relevant 'raw' data files for EMODNet Chemistry from the central buffer QA/QC and aggregate these into a homogeneous ODV collection which sits in ODV Evaluate the advances of Oceantron (within SeaDataNet) for having access to the ODV Collection, using the ODV API and appropriate Oceanotron plug-in, and making them available for OGC SWE and WMS services WPS processes will take the OGC compliant output (possibly from Oceantron) as their input and generate on the fly added value graphics such as station time series, concentration plots for a given time and space window, etc These new WPS products will be described in the SEXTANT Catalogue service The new WPS products will be served to users via the OceanBrowser viewing service EMODnet Chemistry planned output services

8. Implementing regulated access to the buffer with subsets for selecting and delivering specific collections to agreed groups By means of special version of regulated CDI User Interface and shopping mechanism Complexity of large volumes exploring options for hosting the buffer system in the cloud developing subsetting and visualisation services (presentations by IFREMER, GHER and DELTARES) Outstanding

9. Sufficient storage Pref. accessable as an external harddisk; otherwise minimally by FTP Machine to machine interfacing, such as automatic login etc. Reading of statistics Security Using SeaDataNet Caslogin must be possible Ip-number security desirable for setting up IP to IP connections Possible support for OpenID access How can we configure and control rights of the cloud towards accessing MARIS systems How safe is the system on which the cloud operates Possibility by MARIS to develop, include and run own software, such as SOAP (machine to machine) Support for platforms (windows en unix); for MARIS windows is 1st requirement Possible to develop and run Webservices (SOAP) (windows, php,..) Possible to make and operate service for preparing and downloading of zipfiles. Possible to make and operate internet interface. Making use of storage and of database, eg mysql Draft specifications for cloud hosting (prelimininary)

10. END