Implementation plan for common development goals

Revision as of 08:50, 18 June 2021 by M.brus (talk | contribs) (Created page with "=Abstract= {{Infobox | project = ENVRI-FAIR | image = ENVRI-FAIR_logo.jpg | deliverable-nr = D5.2 | submission-date = 2020-09-30 | type = Strategy | url = https://mediawiki.en...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


D5.2 Implementation plan for common development goals
ENVRI-FAIR logo.jpg
Deliverable nr D5.2
Submission date 2020-09-30
Type Strategy

PDF | Zenodo

Document metadata

During the first year of the project the cluster worked on the data service requirement tracking and a technology landscape and gap analysis on the RI FAIR data/services level, to provide an up-to-date investigation of the most common gaps the ENVRIs need to bridge with respect to the FAIR principles and the EOSC requirements. The FAIRness analysis (D5.1) established that the participating RIs display a wide range of states of readiness. The present document uses this analysis to explain the actions that have been taken by the ENVRI-FAIR partners during the second year of the project, and to define the common development goals and prepare an implementation plan at cluster level. During the WP5 Review Workshop in M10 of the project, a decision was made to form (six) cross-cutting Task Forces, which involve representatives from all subdomains, bringing together technical, scientific and managerial staff in order to coordinate the work on a common platform. The development of the ENVRI catalogue of services and other relevant technical issues, e.g. the authentication and authorisation of the cluster end-users, the role of persistent identifiers, triple stores and the best practices, the benefits of certifying data repositories and the available options, the technical approach of machine-readable licenses and their use for citation and usage tracking, and the design of interoperable demonstrators and crossdomain service prototypes, are introduced and discussed in the text.

Document metadata

Document amendment procedure

Amendments, comments and suggestions should be sent to the Project Manager at