Page tree
Skip to end of metadata
Go to start of metadata

This is a working document open for discussion. Please comment, according the local Confluence Editing Guidelines

Proposed guidelines

EPN-2020-RI proposed to be one of the H2020 pilot projects for setting a DMP. The EPN-2020-RI VESPA-DMP was created in this frame. It is necessary to review and adjust the structure the document for EPN-2024-RI, following the EC guidelines.

Data Management Plans (DMPs) are a key element of good data management. A DMP describes the data management life cycle for the data to be collected, processed and/or generated by a Horizon 2020 project. As part of making research data findable, accessible, interoperable and re-usable (FAIR), a DMP should include informationon:

  • the handling of research data during & after the end of the project
  • what data will be collected, processed and/or generated
  • which methodology & standards will be applied
  • whether data will be shared/made open access and
  • how data will be curated & preserved (including after the end of the project).

A DMP is required for all projects participating in the extended ORD pilot, unless they opt out of the ORD pilot. However, projects that opt out are still encouraged to submit a DMP on a voluntary basis.

(Extracted from

The generic DMP guidelines imply that we describe in the document all datasets that we plan to produce. On the other hand, the DMP is a living document, so we add or adjust the content throughout the project. Since we are many teams, with possibly many dataset output, it is proposed to split the DMP document into individual page sections.

Since we agreed to use VESPA as a common interoperability interface for searching and retrieve data, a VESPA Data Management Guidelines section will be kept at the beginning of the document. The VESPA DOI guidelines also apply.

In this DMP, we use the term science data collections for the datasets (actual collection of data files, either measurements, simulation runs or derived products), metadata tables (the EPNcore tables), softwares (code, libraries or tools produced or revised during the project) and documents (any documentation, tutorial or report produced during the project and related to the science data collections). We do not include une this DMP, the non scientific project-related datasets (user database, access logs, meeting notes, internal reports to the coordination...).  

Since VESPA and the other VAs form a distributed infrastructure, we need to describe several items (such as the long term preservation, or the persistent identifier naming authorities) per institutions. 


ActionDue dateNotes
Review DMP guideline pages and agree on DMP outline


Inputs from VA teams


First (initial) issue of DMP (v1.0)


Second (mi-term) issue of DMP (v2.0)


Third (final) issue of DMP (v3.0)



  • No labels