#  Introduction

The purpose of this document is to provide a data management plan (DMP) for
ReachOut. According to the guidelines of the European Commission [EC13a], “the
purpose of the DMP is to support the data management life cycle for all data
that will be collected, processed or generated by the project.”

The ReachOut project is a Coordination and Support Action that aims to help
H2020 projects in the area of software technologies to establish their
software ecosystems by providing them all necessary resources to conduct beta-
testing campaigns: a technical infrastructure for the publication of beta
releases, questionnaires and collaterals, a comprehensive framework for the
development of beta testing campaigns and outreach activities to promote the
platform for the collective benefit of the projects.

Hence, the data management plan relates to data provided by the projects for
their beta-testing campaigns and the software evaluation results.

#  Data Management Objectives

The guideline [EC13a] provides a check list of objectives to be taken into
account when defining data management principles. In the following, we are
going to relate out approach to these:  
  
<table>  
<tr>  
<th>

Objective

</th>  
<th>

Description

</th>  
<th>

ReachOut actions

</th> </tr>  
<tr>  
<td>

Discoverable

</td>  
<td>

Are the data and associated software produced and/or used in the project
discoverable (and readily located), identifiable by means of a standard
identification mechanism (e.g. Digital Object Identifier)?

</td>  
<td>

The ReachOut platform provides a list of the beta-testing campaigns including
their name, description, the organiser and technical details.

</td> </tr>  
<tr>  
<td>

Accessible

</td>  
<td>

Are the data and associated software produced and/or used in the project
accessible and in what modalities, scope, licenses (e.g. licencing framework
for research and education, embargo periods, commercial exploitation, etc.)?

</td>  
<td>

The tested in the campaigns software and its documentation is provided under
the license selected by the research project organising the campaign. The
software evaluation results will remain private and accessible only by the
campaign organisers.

</td> </tr>  
<tr>  
<td>

Assessable and

intelligible

</td>  
<td>

Are the data and associated software produced and/or used in the project
assessable for and intelligible to third parties in contexts such as
scientific scrutiny and peer review (e.g. are the minimal datasets handled
together with scientific papers for the purpose of peer review, are data is
provided in a way that judgements can be made about

their reliability and the competence of those who created them)?

</td>  
<td>

The software and documentation for beta-testing campaigns are provided by the
projects. It will be publicly accessible at the ReachOut platform.

</td> </tr>  
<tr>  
<td>

Useable beyond the original purpose for which it was collected

</td>  
<td>

Are the data and associated software produced and/or used in the project
useable by third parties even long time after the collection of the data (e.g.
is the data safely stored in certified repositories for long term preservation
and

</td>  
<td>

The ReachOut project will not use repositories certificated for long term
storage. The project aims to help other H2020 to improve the quality of the
produced by them software. The results of beta-testing will remain
confidential and accessible only for

</td> </tr> </table>  
<table>  
<tr>  
<th>

</th>  
<th>

curation; is it stored together with the minimum software, metadata and
documentation to make it useful; is the data useful for the wider public needs
and usable for the likely purposes of nonspecialists)?

</th>  
<th>

the project, which organised the testing campaign. The tested software and its
documentation belongs the projects as well. They will follow the own data
management plans.

</th> </tr>  
<tr>  
<td>

Interoperable to

specific quality standards

</td>  
<td>

Are the data and associated software produced and/or used in the project
interoperable allowing

data exchange between researchers, institutions, organisations, countries, etc
(e.g. adhering to standards for data annotation, data exchange, compliant with
available software applications, and allowing recombinations with different
datasets from different origins)?

</td>  
<td>

The ReachOut will not produce any new data, which would be publicly avaialble
to other researchers or institutions apart from the deliverables about project
activities, which will be published on the project web site.

</td> </tr> </table>

#  Data Collection and Quality

The ReachOut project will help H2020 projects to organise their beta-testing
campaigns. It will provide a technical platform, in which the projects will be
able to publish their testing campaign information and provide links to the
software to be tested and its documentation. The feedback of beta-testers will
be collected with help of project/software specific surveys. The ReachOut
project team will actively support the testing campaign organisers and the
beta-testers in producing the data needed for the success of the campaign.

Hence, data quality is achieved by a continuous dialogue between the projects
and beta-testers, and the ReachOut consortium.

#  Data Sharing

The software to be tested and its documentation will be shared through the
ReachOut platform , but only for the period of the beta-testing campaign. The
users will get access to the software to be tested, its documentation and the
instructions regarding the testing procedure.

#  Publications and Deliverables

Publications produces in the ReachOut project and deliverables (with
dissemination level “public”) after the approval by the European Commission
will be published on the ReachOUt web site as fast as possible. Hence,
ReachOut will provide (gold) open access publishing whenever this is possible
[EC13b].