#  1\. Introduction

We report on the deliverable 8.2 in Work Package 8 “Data Management Plan”. The
deliverable is to set up the EWC Data Management Plan (DMP) as required by the
EU Open Research Data Pilot of which EWC is a member.

The DMP was written by PI Kitching with advice from the Project Manager and
the Management Committee (MC). The primary source of information required was
from the Open Research Data Pilot (ORDP) website
_https://www.openaire.eu/what-is-theopen-research-data-pilot_ and the template
document titled “h2020-tpl-oa-data-mgtplan_en” was used. The source of the
content of the DMP was from the WPs that were derived from the GA.

#  2\. Data Management Plan

##  a) Data Summary

In EWC we will collect raw astronomical imaging and spectroscopic data from
three primary sources: the Hubble Space Telescope Archive (
_https://archive.stsci.edu/hst/),_ the ESO public archive (
_http://archive.eso.org/cms.html_ ), and from the PauCAM Survey (PAUS,
_https://www.pausurvey.org_ )  .

The HST data is pre-existing and public data. EWC will download this raw
public data and re-analyse it to meet the EWC objectives. In the process
secondary data products will be produced that include ‘reduced’ (science
ready) images, and catalogues of galaxy and star properties; as well as
scientific papers submitted to journals. These outputs are described in the
deliverables.

The ESO data is also pre-existing and public data. EWC will download this raw
public data and re-analyse it to meet the EWC objectives. In the process
secondary data products will be produced that include ‘reduced’ (science
ready) images, and catalogues of galaxy and star properties; as well as
scientific papers submitted to journals. These outputs are described in the
deliverables.

The PAUS data is private and data access is granted to members of the PAUS
consortium. In this case all leads and developers in WPs that require PAUS
data access are PAUS consortium members; the relation between PAUS and EWC is
controlled by the EWC-PAUS MOU. EWC will re-analyse this to meet the EWC
objectives. In the process secondary data products will be produced that
include catalogues of galaxy and star properties; as well as scientific papers
submitted to journals. These outputs are described in the deliverables.

The project will collect astronomical imaging data and spectroscopic data. The
data that will be generated will be processed imaging data, and catalogues.
The format

used in astronomy for all these projects is the FITS format

_(https://fits.gsfc.nasa.gov/fits_ _documentation.html)._

We expect the data that we generate to be useful for the general astronomical
community, and in particular the Euclid Consortium who is will be the primary
user of the EWC data – the EWC objectives are to the provide calibration
products for the weak lensing method used on the Euclid data.

Secondary products include code in Python and C++ format, and scientific
papers in Latex and PDF format.

**b) FAIR data**

##  Making data findable, including provisions for metadata

As recommended by the Open Research Data Pilot we will use Zenodo to publish
data that satisfies the FAIR requirements  _https://www.zenodo.org_ .

The naming conventions for the imaging and spectroscopic data are to be
determined by the Management Committee. It is expected that standard astronomy
naming conventions will be used. For images the position of the sky in RA and
dec coordinates is used as a standard naming convention coupled with the name
of the survey and/or team. Data will be published on fully searchable public
archives. Version numbers are agreed and listed in the deliverables where
multiple versions of the same underlying product will be issue d. The FITS
format allows for searchable metadata to be included in the primary data in
the form of a “header”. Zenodo also provides meta data searching and a unique
object ID.

##  Making data openly accessible

All data will be fully public (see below for license). For re-processed
imaging and spectroscopic data we will use the Euclid Consortium and PAUS
public archives. The use of these archives is agreed in the Euclid and PAUS
MOUs.

For the case of code publication we will use Github public repositories than
enable searches to be performed on data and metadata associated with any code.

##  Making data interoperable

The data formats we use for imaging, spectroscopy and catalogue data (the FITS
format), has a vast amount of existing infrastructure publically available for
use, manipulation and transformation into different formats. For example all
main coding languages have standard libraries (e.g. CFITSIO, AstroPy, Matlab)
for the manipulation of these formats.

##  Increase data re-use (through clarifying licences)

All data will be published using a license that enables reuse of the data for
any purposes, with appropriate citation (such as the CC BY 4.0 license or
similar; to be determined by the management committee).

##  c) Allocation of resources

There are no additional costs incurred to making the EWC data FAIR. Convention
within the astronomical community is to publish all papers on the arXiv at
submission to the journal. We will use existing infrastructure in the Euclid
and PAU consortia, agreed in the MOUs, to host the data as well as on Zenodo.
Human resources required to make the data in the format required for
publication are covered by the FTE stated in GA.

The WP leaders associated with each deliverable will be responsible for the
data management of those products from their WPs.

##  d) Data security

By using Zenod our research output will be stored safely for the future in the
same cloud infrastructure as CERN's own LHC research data.

**e) Ethical aspects**

There are no ethical aspects associated with the data products from the EWC.

#  3\. Conclusions and future steps

As stated by the ORDP, the DMP is a living document that should be updated
regularly. The MC will review the DMP on an annual basis and issue a new
version if any changes need to be made. Furthermore WP leaders are responsible
for informing the MC immediately if any differences are required as a result
of the research carried out, in particular at the time that data products are
delivered.