#  1\. Introduction

1.1. Scope

This document is the deliverable “D7.1 Data Management Plan v1” for the EU

H2020 (COMPET-5-2015 – Space) project “A Gaia and Herschel Study of the

Density Distribution and Evolution of Young Massive Star Clusters” (Grant

Agreement Number: 687528), with abbreviated code name StarFormMapper (SFM)
project. The structure and content is based on [AD1].

1.2. Applicable documents

The following documents contain requirements and references, which are
applicable to the work:

\- [AD1] SFM proposal: A Gaia and Herschel Study of the Density Distribution
and Evolution of Young Massive Star Clusters. Reference 687528\. Reference:
Space2015- StarFormMapper-Parts1-3, Issue: 1.1, Date:

04/08/2015.

#  2\. Data Summary

The project relies on the analysis of images and catalogued properties of
objects related to star formation regions. The catalogues are in standard
database format for astronomy (VO compatible

XML or FITS tables), the images will be FITS files. This allows for long term
curation of the data. Any simulations present will either be stored in
appropriate generic form (we are considering how to provide these as HDF5
files) or suitable s/w to read them provided through our own dedicated
servers. The exact solution here is still to be determined. There are no
restrictions on the use of these data which are all public. Any other data
acquired for the project (e.g. from ground based telescopes) will have their
final products made available after the nominal telescope proprietary period
ends (usually 12 months).

The GAIA and Herschel data will be taken from the ESA Science Archive
(eventually may be fed directly from there into the project server). Any other
observational data will be taken from other relevant science archives but will
require local hosting as those archives do not have the same feed in
capability. The original metadata will be added to as appropriate for the
project.

We estimate the final data size for the project that will be stored locally to
be modest (since we are only interested in relatively small areas of the sky).
Our initial DMP is scoped on a final dataset of up to 8TB.

The project has allowed for separate servers at the Leeds and Madrid nodes,
which are now fully installed and functional. These will provide backup to
each other. In addition, off-server local backups (to local NAS) will also be
made up to the 8TB limit noted above. These facilities are allowed for within
the cost of the project. The initial project datasets will be limited to
simulation data which are estimated to require ~300MB each.

#  3\. Fair Data

3.1. Making data findable, including provisions for metadata:

Both FITS and the IVOA formats are standard, and the metadata requirements are
established.

The Madrid node will be responsible for creating and documenting all data
standards required for the project. They have prior experience with large ESA
archives which will be adopted by this project.

3.2. Making data openly accessible

Data will be open access, and made available through the dual public access
servers at Leeds and Madrid. The exact format of the interface has not yet
been decided, but will be addressed in a series of documents to be prepared by
Quasar.

3.3. Making data interoperable:

We will use standard IVOA metadata and file types.

3.4. Increase data re-use (through clarifying licenses):

  * Quasar Science Resources will gather from public archives the data you will need to run your algorithms and the derived products will be accessible from the consortium. At the end of the H2020 project, the consortium will decide what to do with these data. 

  

  * The idea is to have the data available as soon as possible, but keeping in mind the release of the premature data could be unproductive. According to this, the consortium will decide when to make data public. 

  

  * There are no thoughts to restrict any kind of data. It should be all available at the end of the project. 

  

  * QSR will provide the interface to run the scientific validations. As the project progresses, the data quality test, a kind of scientific validation, will be developed by scientific teams. 

  

  * There are no restrictions about this point. As long as there are resources the data will remain re-usable. In particular, the University of Leeds will commit to hosting the server mentioned in Section 2 for a period of at least 10 years. 

  

#  4\. Allocation of Resources

We have adopted open standards from the outset, so there are limited
additional costs in ensuring fair access to all data gathered.

The scientific validation of simulations and data products will be developed
by the scientific teams and therefore will be their responsibility. Data
products, meta-accessibility of data and SW interfaces to scientific
algorithms will be the responsibility of QSR.

Overall data management is the responsibility of the management group, with
day-to-day leadership of the DM being led by Leeds.

#  5\. Data Security

There are no sensitive data held by this project.

Immediate storage will be provided on the servers at Leeds and Madrid paid for
by the project. Off-line backup in Madrid will be provided by local NAS also
paid for by the project. Off-line backup in Leeds will be provided within
space already purchased by the Astrophysics Group for general data curation.
Medium term storage of key products is envisaged to continue through these two
routes. Longer term storage may evolve, particularly in line with the
University of Leeds data storage policies.

6\. Ethical Aspects

There are no ethical implications for this project.

#  7\. Other

All of our policies at Leeds are also consistent with the DMP requirements of
STFC, which the IT support team are already familiar with, and which is
aligned with the EU's policy on open access. The local IT team at Leeds will
at all times also follow institutional guidance. Quasar will adopt similar
policies.