Search

Dans le cadre du projet ANR COPiLOtE, nous parlerons des « Persistent IDentifiers (PID) » (Identifiants pérennes en français) dont le DOI est un exemple. Les PID sont déclinés en fonction du type d’objet numérique que nous désirons identifier de façon pérenne. Ce guide est destiné aux responsables des Centres de Données et Services (CDS) en charge de la création et de l’attribution de PID/DOI dans leur structure. Ce guide est constitué de six sections principales : une présentation générale des PID, la syntaxe et la structure des PID, le choix du PID en fonction de l’objet numérique, la granularité du DOI pour un jeu de données, le choix de l’entrepôt, et une brève introduction sur le concept des « PID graphs » (toiles d’information)., As part of the ANR COPiLOtE project, we will discuss Persistent IDentifiers (PIDs), of which the DOI is an example. The PIDs are tailored according to the type of digital object that we wish to identify in a persistent way. This guide is intended for the Data and Services Centre (DSC) managers in charge of creating and assigning PIDs/DOIs within their organisation. This guide is made up of six main sections: a general presentation of PIDs, the syntax and structure of PIDs, the choice of PID based on the digital object, the DOI granularity for a dataset, the choice of a repository, and a brief introduction to the concept of "PID graphs" ( information networks).

This deliverable D2.7 describes the Blue Cloud architecture as it is known at Month 20. It is the second release of the architecture and an update of the earlier 1st release of the Blue-Cloud architecture document D2.6. It is expected that there will be further developments and refinements to the Blue Cloud system. For that purpose, one more release of the architecture document is planned, namely report D2.8 in Month 27. In order to make it easier for readers and reviewers, a table is included as part of Chapter 1, which indicates the elements and sections of this Deliverable 2.7, which have been updated or added in comparison with the earlier Deliverable 2.6. The technical framework of the pilot Blue-Cloud features: the Blue Cloud Data Discovery and Access service component to serve federated discovery and access to blue data infrastructures the Blue Cloud Virtual Research Environment (VRE) component to provide a Blue Cloud VRE as a federation of computing platforms and analytical services. In this report, the current architecture and functionalities of each of these components are described in detail as well as the roles of partners that are developing and hosting modules. The Blue Cloud Data Discovery and Access service architecture is based upon a combination of the DAB metadata broker service of CNR-IIA, and the SeaDataNet CDI service modules as developed by MARIS, IFREMER, and EUDAT in the framework of the EU SeaDataCloud project. For the Blue-Cloud Data Discovery and Access service and its modules, additional developments were needed such as adapting and upgrading of existing services, adding new services, testing modules, integrating modules, and testing the integrated service, in order to achieve the planned functionality. The Blue Cloud VRE is largely based upon the existing D4Science e-infrastructure as developed and managed by CNR-ISTI. This e-infrastructure from the start hosted already multiple Virtual Labs and offered a variety of services. These services have been adopted and adapted for the Blue Cloud and new services have been added, while also new Virtual Labs have been constructed and deployed as part of the Blue-Cloud Demonstrators. The D4Science e-infrastructure also already had proven solutions for connecting to external computing platforms and means for orchestrating distributed services, which are instrumental for smart connections to the other e-infrastructures in the Blue-Cloud system. The Blue Cloud demonstrators are developed as Virtual Labs embedded in the D4Science VRE e-infrastructure and supported by data input from the Blue Cloud Data Discovery and Access service and other data resources, and additional computing services. The demonstrators are worked out in a cooperation between WP3 and WP4, analysing their scientific workflows and technical set-up, and considering the D4Science VRE infrastructure and services that provide the basis platform. As part of their development, the demonstrators have required upgrading of existing functionality and development of additional services. This is described, where relevant, in this document. In addition, consideration is given to integration aspects, such as two-way linking between the 2 Blue Cloud components, and expanding the VRE with additional platforms for computing and algorithms, and where needed for specific demonstrators, direct access to data infrastructures. Moreover, aspects of authentication and monitoring are considered on full Blue Cloud scale. The Blue Cloud architecture as described in this report, is designed to be scalable and sustainable for near-future expansions, such as connecting additional blue data infrastructures, implementing more and advanced blue analytical services, configuring more dedicated Virtual Labs, and targeting more (groups of) users.

This guide of the Ocean Data Cluster - ODATIS (IR Data Terra) is produced in the framework of the ANR project COPiLOtE. It takes up and refines: - The general recommendations specified in the CDS specifications ; - The detailed recommendations established during the ODATIS Technical Workshops and outlined in the minutes. These recommendations concern - On the one hand, the vocabularies and metadata, whether they are those for data discovery or in the data; - Formats, attributes and conventions for data files., Le présent guide du pôle de données Océan – ODATIS (IR Data Terra) est produit dans le cadre du projet ANR COPiLOtE, reprend et affine: - Les recommandations générales spécifiées dans le cahier des charges des CDS ; - Les recommandations détaillées établies lors des Ateliers Techniques du pôle ODATIS et tracées - dans les compte-rendu. Ces recommandations concernent - D’une part les vocabulaires et métadonnées, qu’elles soient celles de découverte des données ou - dans les données ; - Les formats, attributs et conventions pour les fichiers de données.

This guide is intended to support the CoreTrustSeal self-assessment of the various Data Centres of the (French) Ocean Data Cluster - ODATIS. It is a reading guide to the different CoreTrustSeal requirements with additional explanations., Ce guide est là en appui pour l’autoévaluation CoreTrustSeal des différents Centres de Données du pôle de données océan - ODATIS. Il s'agit d'une lecture guidée des différents critères ("Requirements") CoreTrustSeal avec des explications complémentaires.

As part of the EU H2020 Blue-Cloud project activities are undertaken for developing and deploying a Blue-Cloud cyber infrastructure with smart federation of multidisciplinary data repositories, analytical tools, and computing facilities. This infrastructure will facilitate exploration and demonstration of the potential of cloud based open science, supporting research for understanding and better managing the many aspects of ocean sustainability, ranging from sustainable fisheries to ecosystem health to pollution, in support of the EU Green Deal and also in connection with UN Decade of the Oceans and G7 Future of the Oceans initiatives. This document provides an initial version and guidance towards the delivery of a final Blue-Cloud Service Exploitation and Sustainability Plan for the Blue-Cloud assets. While these Blue-Cloud assets are still under development, the process of defining the way forward for their future exploitation after Project end (2022) will benefit from an early consideration and discussion, engaging all Project Partners. Also, additional input from external stakeholder dialogue and consultations as being undertaken in the framework of the Blue-Cloud Roadmap to 2030 development needs to be taken into account. The Roadmap analyses will provide recommendations for the future capitalization and further development of the results of the Blue-Cloud Project in the medium (2025) and long-term (2030). This document is the first release of the Blue-Cloud Service Exploitation and Sustainability Plan and it gives present understanding as well as will serve as guiding framework for further analyses, discussion, and identifying the key elements that will need to be addressed during the remainder of the Project with input and feedback from all Partners. This process should deliver the 2nd and final release of the Blue-Cloud Service Exploitation and Sustainability Plan by July 2022. The goal of the final Blue-Cloud Service Exploitation and Sustainability Plan is at one hand, to define an exploitation model and to secure with partners the operation and exploitation of the Blue-Cloud results in the 3 years following the project end, and on the other hand, to explore and pave the way to longer sustainability, supported by major stakeholders. For the latter there is clear synergy and interaction with the Blue-Cloud Roadmap 2030 development. Moreover, sustainability perspectives will motivate partners to ensure and commit to the planned short-term operation and exploitation. The path to definition of the Blue-Cloud sustainability model is a process founded on 3 main pillars, supported by the project outcomes and research results and obtained with a consortium-wide commitment: Pillar 1: problem/solution fit and vision/solution fit of the Blue-Cloud framework – demonstrating ability to solve needs of target end-users, moving up the MRL (Market Readiness Level) scale to show proof of traction. This pillar is equivalent to MRL 5 and 6 ("open beta with pipeline customers" and "market traction"). Pillar 2: demonstrating customer understanding of Blue-Cloud, gathering evidence of satisfaction through validation scoring and marketing evidence of concrete benefits gained (e.g. testimonials from pilots and their users; subsequently through the open pilot stream). Equivalent to MRL 7 ("proof of satisfaction: both for customers and within the team"). Pillar 3: Proof of scalability with evidence of satisfied market needs and evidence of willingness to cover resources needed for a post-project continuation of services. Equivalent to MRL8 ("proof of scalability") demonstrated through the Blue-Cloud joint exploitation plan. Throughout its duration, Blue-Cloud will seek for demonstration of early market traction, which it will subsequently transform into a business plan. For this purpose, the current workplan of the Blue-Cloud project includes not only scientific and technical developments on the planned Blue-Cloud services, but also extensive activities for marketing and promotion of the Blue-Cloud assets to all major stakeholders, from project partners, targeted users, and potential funders. This includes activities for evaluating the defined MRL through KPIs (Key Performance Indicators) on the market penetration and the fitness of the market model for establishing a stable position, demonstrating incremental growth and anticipated added-values and impacts. Therefore, this initial Blue-Cloud Service Exploitation and Sustainability Plan identifies and describes all elements which are considered relevant. Also, it identifies where further activities are needed to provide firm answers and decisions. The document starts with describing the overall methodology and process that have been followed to prepare this plan, making optimal use of the Horizon Result Booster (HRB) instrument of the EU and provided business consultancy services, while engaging all Blue-Cloud beneficiaries in the process. It continues with sketching the European marine data landscape and the foreseen position of the Blue-Cloud platform and its services. The overall aims and concept are formulated, and a description is given of the planned Blue-Cloud services, the so-called Key Exploitable Results (KER). Next, an initial market analysis is worked out, reporting on the results of a Joint Workshop with Blue-Cloud beneficiaries to draft a Lean Canvas Business Model, and identifying different Blue-Cloud stakeholders and their interest and potential benefits. This is followed by giving an overview of the Marketing Media Mix (MMM), an extensive portfolio of marketing and promotion activities, which is applied in the Blue-Cloud project, since its start, to reach out to potential stakeholders and to make them aware and informed about the Blue-Cloud developments and resulting services and to collect KPIs relevant for the three pillars (see above). The next chapter looks into the organization of management and operation of each of the planned Blue-Cloud services and the associated roles and Intellectual Property Rights (IPR) of beneficiaries. Although this is still premature, since the majority of Blue-Cloud services are under development, whereby the organisation of their exploitation is still to be determined. Next, categories of costs for the exploitation phase are explored, followed by assessing the expected added-values and impacts of the Blue-Cloud services for different stakeholders and considering ways for measuring these as KPIs. Overall, the Blue-Cloud philosophy is not to aim for commercial services, but for public services, which are valued and appreciated by authorities, such as EU and Member States as major stakeholders, in a positive balance. This requires achieving success towards potential users and collecting convincing evidence of usage and impacts (see three pillars above). Aligned with this, another interactive Joint Workshop with all Blue-Cloud beneficiaries was held to brainstorm about these added-values and impacts and ways for monitoring. Finally, a draft is given of the initial exploitation and sustainability strategy and a summary of actions, which need to be deployed in the remaining project period in order to provide further answers and insights. This initial Services Exploitation and Sustainability Plan makes use of a number of already available Blue-Cloud deliverables [1], [2], [3], and [4], and the insights that these provide. Also use is made of the discussions between Blue-Cloud WP6 core partners in their regular WP6 meetings. And a lot of synergy is found in the activities and discussions for formulating a Blue-Cloud Roadmap 2030 with ambitions for the medium and long term, and organising input and engagement from major stakeholders for a future upscaling and funding of the Blue-Cloud services, aiming for a long-term sustainability and expansion of the Blue-Cloud initiative, e.g. by means of a portfolio of EU funded projects and synergies with other projects and initiatives. Complementary, the Blue-Cloud exploitation and sustainability plan is aiming for making arrangements for securing the short term (3 years after the project) with an outlook to the medium term. For that reason, the Blue-Cloud Service Exploitation and Sustainability Plan aims for developing a set of agreements between the respective Blue Cloud operators, in which they will guarantee that each of the Blue-Cloud services will be kept operational and available for use by researchers for at least 3 years after the Blue-Cloud project end, under prevailing conditions. However, currently there are still a number of questions which need to be answered as part of planned project activities. These should give sufficient input for completing the exploitation and sustainability insights and upgrading this initial plan into a final plan, Deliverable D6.5, as planned later near the end of the Blue-Cloud project.

This deliverable, D3.3 "Blue Cloud Demonstrator Users Handbook V1" is a first version of the handbook and guidelines on how to use the Virtual Research Environments (VREs) of the five demonstrators. For each demonstrator, the following information will be described: the objective, the targeted users, a summary of their provided services and the guidelines of how to use their respective VREs. As this version of the Handbook describes the β-version of the VREs, it is not fully complete and final, as the VREs are not fully finalised yet. It must be considered as an intermediate version to be used internally for integration and testing. This Handbook V1 is an ongoing and living document. It will be updated following advances of the demonstrators and their VREs. The final version V2 of this handbook will be published in M27 of the Blue-Cloud project (December 2021) and will be open to users. Intermediate versions in between now and then will be written and possibly made accessible online, following progress of demonstrators and their VREs, deploying functionalities, achieving results, etc.

The Blue-Cloud innovation potential will be explored and unlocked by developing five dedicated Demonstrators as Virtual Labs together with excellent marine researchers. For that purpose, Blue-Cloud selected five varied and domain-coverage rich scientific demonstrators. The objective is to develop and deploy a Virtual Lab for each demonstrator, which will become part of the Blue-Cloud Virtual Research Environment (VRE) and as such will be made accessible for users. The D4Science e- infrastructure will be the core platform for the VRE. This e-infrastructure already holds a generic VRE with many core services for building and running multiple Virtual Labs, dedicated to specific research targets. The D4Science e-infrastructure also has proven solutions for connecting to external computing platforms and means for orchestrating distributed services, which will be instrumental for smart connections to the other e-infrastructures in Blue-Cloud, namely EUDAT and DIAS (WekEO). This deliverable D3.1 describes and summarizes the technical requirements towards the development and implementation of the Blue-Cloud demonstrators as Virtual Labs. These technical requirements have been derived from communications with the partners who are in charge of the Blue-Cloud Demonstrators. This implicates that the technical requirements are assessed and formulated from their perspective concerning the input, output, and workflow processes that are envisioned for the Demonstrators. These requirements will be used in the further development of the Virtual Labs, which will take place in a close cooperation between WP3 and WP4, whereby WP4 will focus on the activities for making the existing VRE at D4Science more fit for purpose of the Blue-Cloud Demonstrators, which might involve expanding and/or upgrading functionalities. The technical requirements as summarized in this deliverable D3.1 will also contribute to the identification of the key challenges to address with the design of the overall technical architecture for the Blue-Cloud project. As a next step in the cooperation and exchanges between WP3 and WP4, the Demonstrator groups will explore the existing VRE at D4Science, which will be supported by Webinars introducing and explaining VRE services. Moreover, the deliverable D3.2 'Demonstrator Implementation guidelines' will be drafted in cooperation with WP4 and from the perspective of the existing D4Science e-infrastructure.

Ce rapport s’insère dans l’activité 1 du projet GIFS « Gouvernance des zones côtières et des pêches maritimes » ayant pour objectifs : * De comprendre les différents modes de gouvernance côtière de la zone d’étude et identifier les pratiques de gestion. * D’inventorier et comprendre les approches et les cadres de gestion existants dans l’ensemble de la zone d’étude et identifier la place de la pêche maritime dans ces derniers.

This report is part of the GIFS Project Activity 1 "Governance of coastal zones and maritime fisheries", the objectives of which are: *To understand the different modes of coastal governance of the study area and identify management practices. *To inventory and understand the approaches and existing management frameworks throughout the study area, as well as to identify the place held by maritime fishing in the latter.

This guide of the Ocean Data Cluster - ODATIS (IR Data Terra) is produced in the framework of the ANR project COPiLOtE. It takes up and refines: - The general recommendations specified in the CDS specifications ; - The detailed recommendations established during the ODATIS Technical Workshops and outlined in the minutes. These recommendations concern - On the one hand, the vocabularies and metadata, whether they are those for data discovery or in the data; - Formats, attributes and conventions for data files., Le présent guide du pôle de données Océan – ODATIS (IR Data Terra) est produit dans le cadre du projet ANR COPiLOtE, reprend et affine: - Les recommandations générales spécifiées dans le cahier des charges des CDS ; - Les recommandations détaillées établies lors des Ateliers Techniques du pôle ODATIS et tracées - dans les compte-rendu. Ces recommandations concernent - D’une part les vocabulaires et métadonnées, qu’elles soient celles de découverte des données ou - dans les données ; - Les formats, attributs et conventions pour les fichiers de données.

This guide is intended to support the CoreTrustSeal self-assessment of the various Data Centres of the (French) Ocean Data Cluster - ODATIS. It is a reading guide to the different CoreTrustSeal requirements with additional explanations., Ce guide est là en appui pour l’autoévaluation CoreTrustSeal des différents Centres de Données du pôle de données océan - ODATIS. Il s'agit d'une lecture guidée des différents critères ("Requirements") CoreTrustSeal avec des explications complémentaires.

The main goal of Blue-Cloud WP5 is to deliver and maintain a Communication, Marketing & Dissemination Plan and Strategy for the pan-European rollout of the Blue-Cloud services. As part of this strategy, the project is identifying the Blue-Cloud Key Exploitable Results (KERs) to be disseminated towards key stakeholders. This is done through consistent and content-rich communication activities, by using multiple integrated communication tools. The success of this mission is highly dependent on a continuous interaction with all WPs. The Blue-Cloud "D5.2 Communication, Dissemination & Stakeholders Engagement Interim Report" is an updated version of "D5.1 Communication, Dissemination & Stakeholder Engagement Strategy" released in April 2020 (M7). This report documents the results and impact of communication efforts undertaken from October 2019 (M1) to March 2021 (M18), which focused on creating awareness about the Blue-Cloud project, its goals, its ambition and the expected Key Exploitable Results (KERs). This report also defines the communication strategy roadmap for M19-M36 (April 2021 - September 2022). The focus from M19 (April 2021) onwards will be to consolidate the active stakeholder engagement approach for each target group by disseminating the project's KERs, which are being made accessible to target stakeholders during the next months. A massive promotion of the project results to potential user communities will be implemented through the activities described in this report. This period will also be dedicated to further promoting dialogue and engagement with key stakeholder communities towards the Blue-Cloud Roadmap to 2030, which aims to become a policy tool for the capitalization and evolution of Blue-Cloud's efforts into the future. All Blue-Cloud communication and dissemination activities performed aimed to maximise the outreach, dissemination and exploitation impacts of the project during the first period, with the intent to have the same effect during the whole project lifetime and after its conclusion.

This report D2.6 describes the Blue Cloud architecture as it is known at Month 9. It is the first release of the architecture as it is expected that the actual development and implementation of the Blue Cloud system will provide further challenges and elaborated details. For that purpose, two more releases of the architecture document are planned, namely report D2.7 in Month 15 and report D2.8 in Month 27. The technical framework of the pilot Blue-Cloud will feature: the Blue Cloud Data Discovery and Access service component to serve federated discovery and access to blue data infrastructures the Blue Cloud Virtual Research Environment (VRE) component to provide a Blue Cloud VRE as a federation of computing platforms and analytical services. In this report, the architecture and functionalities of each of these components are described in detail as well as the roles of partners that will develop and host modules. The Blue Cloud Data Discovery and Access service architecture is based upon a combination of the GeoDab metadata broker service of CNR-IIA, and the SeaDataNet CDI service modules as developed by MARIS, IFREMER, and EUDAT in the framework of the EU SeaDataCloud project. For the Blue-Cloud Discovery and Access service and its modules, additional developments will be needed such as adapting and upgrading of existing services, adding new services, testing modules, integrating modules, and testing the integrated service, in order to achieve the planned functionality. The Blue Cloud VRE will be based upon the existing D4Science e-infrastructure as developed and managed by CNR-ISTI. This e-infrastructure already hosts multiple Virtual Labs and offers a variety of services, which can be adopted for the Blue Cloud. The D4Science e-infrastructure also has proven solutions for connecting to external computing platforms and means for orchestrating distributed services, which will be instrumental for smart connections to the other e-infrastructures in the Blue-Cloud system. The Blue Cloud demonstrators will be developed as Virtual Labs embedded in the D4Science VRE e-infrastructure and supported by data input from the Blue Cloud Data Discovery and Access service and other data resources, and possible additional computing services. The demonstrators are being worked out in a cooperation between WP3 and WP4, analysing their scientific workflows and technical set-up, and considering the present D4Science VRE infrastructure and services that will provide the basis platform. However, at this time of development, there is no insight yet whether the demonstrators will require upgrading of existing functionality or development of additional services. Therefore, the described architecture of the VRE concerns the current D4Science e-infrastructure. In addition, consideration is given to integration aspects, such as two-way linking between the 2 Blue Cloud components, and expanding the VRE with additional platforms for computing and D2.6Blue Cloud Architecture (Release 1) algorithms, and where needed for specific demonstrators, direct access to data infrastructures. Moreover, aspects of authentication and monitoring are considered on full Blue Cloud scale. The initial Blue Cloud architecture as described in this report, is designed to be scalable and sustainable for near-future expansions, such as connecting additional blue data infrastructures, implementing more and advanced blue analytical services, configuring more dedicated Virtual Labs, and targeting more (groups of) users.

The Blue Cloud data discovery and access service will be one of the components of the Blue-Cloud technical framework. It will serve federated discovery and access to blue data infrastructures and interact with the Blue-Cloud Virtual Research Environment(the component federating computing platforms and analytical services). The pilot Blue-Cloud project aims at federating initially in total 10blue data infrastructures. Each of these existing infrastructures have been described in this deliverable D2.1, in particular with a focus on their current data discovery and access mechanisms. From the descriptions and discussions, among others at the first TCom meeting in January 2020, it appears that a number of blue data infrastructures do not have to be federated with direct interfacing to the Blue-Cloud data discovery and access service, but indirectly as some are or will be coupled to another of the blue data infrastructures and that way it will be arranged that their contents will also be present in the Blue-Cloud data discovery and access service. In addition, activities are needed in several cases for providing API's which are suited for serving the planned Blue-Cloud data discovery and access service. In the following months a deeper analysis will be carried out, in order to detail technical specifications of the Blue-Cloud data discovery and access service, and developments required at and by each of the blue data infrastructures. This analysis, technical specification and workplan for the implementation and deployment of the Blue Cloud data discovery and access service will be documented in Deliverable D2.2 at M8. Thereafter, in the months till M17, the actual developments and deployment will take place for establishing an operational Blue-Cloud data discovery and access service by M17.