H2020 ProjectProject Number: DASSH USECASE DAN LEAR, ABRAHAM NIEVA DE LA HIDALGA, ALEX HARDISTY 1

H2020 ProjectProject Number: DASSH USE CASE Description of the DASSH use case Description of DASSH using ENVRI-RM ( please comment as/if needed ) Lessons (we) Learned

H2020 ProjectProject Number: DASSH INTRODUCTION The DASSH system supports the publishing and discovery of data about marine species and habitats. DASSH shares data directly via the DASSH portal and indirectly via the MEDIN portal. The DASSH portal allows access to metadata and raw data, while MEDIN displays only aggregated metadata DASSH needs to be integrated with other European marine biological data (e.g. data curated by EMSO, SeaDataNet, JERICO and EMBRC)

H2020 ProjectProject Number: DASSH ACTIVITIES DASSH started conversation with CU about use case December 2015 DASSH produced use case overview January 2016 CU revised initial overview and recommended changes (January 2016) DASSH updated the use case overview (February 2016) Meeting at Plymouth to discuss use case (February 2016) Update from MBA about discuss advance (March 2016) Discussion with EGI about opportunities to support DASSH (April 2016)

H2020 ProjectProject Number:

H2020 ProjectProject Number: DASSH Data Types

H2020 ProjectProject Number: DASSH Processes

H2020 ProjectProject Number: Communities, Roles, Behaviours

H2020 ProjectProject Number: System and Subsystems

H2020 ProjectProject Number: Data Types Processes Communities

H2020 ProjectProject Number: WHAT ARE THE MAIN PROBLEMS IN THIS SCENARIO Service Provision: Allow access to external systems, automate data transfers and linking Semantic Harmonisation: Facilitate interpretation of data Data usage: Behaviour tracking, profile management, workgroup collaboration, workspaces definition

H2020 ProjectProject Number:

H2020 ProjectProject Number:

H2020 ProjectProject Number: THE EXISTING COMMUNITIES ON THE RM Data service provision community and data usage community

H2020 ProjectProject Number: ROLES OF TARGET COMMUNITIES

H2020 ProjectProject Number: BEHAVIOURS OF TARGET COMMUNITIES

H2020 ProjectProject Number: CONSTRAIN FOR DATA INTEGRATION

H2020 ProjectProject Number: DATA PROCESSING SUBSYSTEM

H2020 ProjectProject Number: COMMUNITY SUPPORT SUBSYSTEM

H2020 ProjectProject Number: BROKERED DATA QUERY Persistence Layer Access Layer Presentation Layer

H2020 ProjectProject Number: Describe Interactions (Data Search) DASSH Portal > DASSH > DASSH > DASSH > USER Query “Gobius Plymouth University” Translated Query and contact appropriate system Query DASSH metadata Query DASSH database Metadata of 14 Registers Display Metadata Metadata of 14 Registers

H2020 ProjectProject Number: BROKERED DATA EXPORT Persistence Layer Access Layer Presentation Layer

H2020 ProjectProject Number: Describe Interactions (Metadata Search) MEDIN Portal > DASSH > DASSH > DASSH > USER Query “English Channel Bathymetric Survey” Translated Query and contact appropriate system Query DASSH metadata Query DASSH database Metadata of 4 Surveys Display Metadata

H2020 ProjectProject Number: DASSH GENERALISATION AND APPLICABILITY Identify areas for improvement o Produce a Model of DASSH as it is to identify clearly integration points Model proposed solutions o New service layer (broker?): export data to integrate with other RIs o Improve portal (virtual laboratory?): query data in a controlled way (Secured and authenticated access) Using the RM to review possible solutions o Review engineering and technology possible solutions o Deploy a prototype of the service and portal solutions (Cloud?) o Evaluate engineering and technology options for the deployment of new functionalities (new equipment vs. cloud) Example of alignment and integration with other RIs (EMSO, SeaDataNet, JERICO and EMBRC) Example of use of Foundational RIs (EGI, EUDAT)