#  Executive Summary

This document contains the Data Management Plan (DMP) for GRECO project. It
describes the types of data that will be generated or gathered during the
project, the standards that will be used, the ways how the data will be
exploited and shared for verification or reuse, and how the data will be
preserved. In addition, our DMP explains how GRECO ensures its research data
are findable, accessible, interoperable and reusable (FAIR) regardless these
are or not open into a repository.

#  Glossary- Abbreviations

**FAIR:** FAIR data are data which meet standards of findability,
accessibility, interoperability, and reusability. For detailed explanation on
each of these terms visit: _https://www.go-fair.org/fair-principles/_

**PEDRC** : Plan of Exploitation and Dissemination of Results and
Communication. Deliverable 5.2 of GRECO.

**ORD:** Open Research Data.

**DMP:** Data Management Plan.

**TRL:** Technology Readiness Level.

**P1.UPM:** Partner nº1. Universidad Politécnica de Madrid.


#  Introduction

##  GRECO in a nutshell

The two main objectives of GRECO (H2020-787289) are to demonstrate that the
application of Open Science practices (and more broadly, Responsible Research
and Innovation methodologies “RRI”) are the basis for obtaining research
products aligned with current society challenges and; to become a fundamental
reference of how these materialize in all phases of an R&D project.

**GRECO faces the specific challenge of putting Open Science into action** in
a three years research project. To this end, GRECO has designed a model for
implementation that will be tested within a typical research project of
societal challenges pillar of H2020 Program. Thus, GRECO investigates on **six
innovative solutions that Photovoltaics (PV)** can offer to the society.
However, the key of the project is that the research process is being carried
out using the fresh and innovative approaches for science that researchers in
sociology and humanists have been developing during the last decade. The
project operationalizes tools that enable **public engagement mechanisms** for
different research lines (from high TRL to low TRL). In this way, processes
such as user-centered Open Innovation, Citizen Science or Mobilization and
Mutual Learning (MML) actions are especially relevant for the development of
our products. Also, through **Open Science tools** such as Open Access, Open
Data, Open Education, Open Notebooks, Open Software and Open Peer-Review GRECO
aims to generate a research process more accessible to the rest of world. And
of course, GRECO conscientiously implements the ethical, gender and governance
principles, to guide the execution of the project in its search for socially
responsible products.

The aims of GRECO project are:

  * To obtain an inclusive, validated, and understandable rationale pilot for Open Science ready to be applied to a wide spectrum of research projects. 

  

  * To evidence the impact of Open Science and RRI approaches 

  

  * To develop a model to come up with a Responsible Citizen Science Initiative exemplified for Photovoltaics 

  

  * To carry out a Mutual and Mobilization Learning Action Plan as a way for ensuring socially acceptable innovative solutions. 

  

  * To operationalize quadruple helix innovation collaborations in research projects. 

  

  * To empower citizens in the scientific endeavour. 

  

  * To provide high innovative research solutions using GRECO Open Science pilot. 

  

A Consortium formed by eleven partners aims at demonstrating to their
counterparts how any societal challenge project can be operated in a novel
way. That is, by using the mechanisms that Open Science and RRI offer to
generate socially acceptable innovative solutions. **GRECO aims at bridging
the gap between SWAFS and Societal Challenges pillars.**

##  Data Management context

The European Commission (EC) is running a flexible pilot under Horizon 2020
called the Open Research Data Pilot (ORD pilot). In the 2014-16 work
programmes, the ORD pilot was included only in a few selected areas of Horizon
2020. Under the revised version of the 2017 work programme, the Open Research
Data pilot has been extended to cover all the thematic areas of Horizon 2020
and GRECO takes part of it. This pilot is part of the Open Access to
Scientific Publications and Research Data Program in H2020  1  . Its core
objective is to improve and maximise access to and re-use of research data
generated by Horizon 2020 projects. However, it also considers **_the need to
balance_ ** openness and protection of scientific information,
commercialisation and Intellectual Property Rights (IPR), privacy concerns,
security as well as data management and preservation questions. For such
reason, the **ORD pilot applies primarily to the data needed to validate the
results presented in scientific publications** . Other data can also be
provided by the beneficiaries on a voluntary basis, as stated in their Data
Management Plans according to the content of the article 29.3 of the Grant
Agreement “Open Access to Research Data”:

_The Beneficiaries must deposit their data in a research data repository and
take measures to make it possible for third parties to access, mine, exploit,
reproduce and disseminate -free of charge for any user- the following:_

  * _**The data, including metadata, needed to validate the results presented in scientific publications as soon as possible** _

  

  * _**Other Data, including associated metadata, as specified and within the deadlines laid down in the data management plan** _

  

_The Beneficiaries must provide information-via the repository-about the tools
and instruments at the disposal of the beneficiaries and necessary for
validating the results (and- where possibleprovide the tools and instruments
themselves)._

_This does not change the obligation to protect results in Article 27, the
confidentiality obligations in Article 36, the security obligations in Article
37 or the obligations to protect personal data in Article 39, all of which
still apply._

_As an exception, the beneficiaries do not have to ensure open access to
specific parts of their research data if the achievement of the action's main
objective, as described in Annex I, would be_

_jeopardised by making those specific parts of the research data openly
accessible. In this case, the data management plan must contain the reasons
for not giving access_ .”

The EC provides a document with guidelines  2  for projects participating in
the ORD pilot. Guidelines explain that all H2020 Projects will be required to
develop a Data Management Plan (DMP). The DMP is the document that describes
the life cycle of data within a project, i.e. types of data that will be
generated or gathered during the project, the standards that will be used, the
ways how the data will be exploited and shared for verification or reuse, and
how the data will be preserved. The DMP is the document that describes how
Beneficiaries are going to ensure that those selected research data are
findable, accessible, interoperable and reusable (FAIR)  3  .

There are several helpful guidelines for preparing a DMP plan. The EC
Guideline in [2] Version 3.0 of 26 of July contains a DMP template for helping
researchers on its preparation. The Digital Curation Centre (DCC) offers an
online tool for preparing a DMP including an extended version  4  . And
through the DMP Tool the users can also create such Plan through an oriented
questionnaire depending on to the Funding Agencies  5  , although this feature
is oriented to the North-American Agencies. GRECO has decided to follow the
recommendations and template defined by the European Commission in [2].

#  DATA SUMMARY

Within the Plan of Dissemination, Exploitation of Results and Communication
described in deliverable D5.2. GRECO has a defined strategy on research
outputs management in order to reach its maximum impact and a basis for a
solid Open Science pilot. Every six months all Beneficiaries complete an Excel
file. In that sheet (included also in Annex I of this document), they report
all research outputs generated as a result of GRECO activity regardless its
classification as positive, negative or neutral. Once identified, they have to
classify the type of data, the potential users and uses as well as the impact
of such output and the proposed route for either exploitation or
dissemination. Moreover, in such sheet the relation of the data with the
Project is shown, defining both the workpackage and/or task and its
relationship with the expected impact of the call.

Within this Excel Sheet any reader can find practically implemented the
questions identified in the DMP template  2  :

**Table 1. Correlation between DMP requirements and GRECO implementation**  
  
<table>  
<tr>  
<th>

**DMP Template Section1 Questions**

</th>  
<th>

**GRECO compliance**

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

What is the purpose of the data collection/generation and its relation to the
objectives of the project?

</td>  
<td>

Purpose is related to the expected impacts of the call. Beneficiaries list
them in Colum H of the sheet.

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

What types and formats of data will the project generate/collect?

</td>  
<td>

Colum H (types of data).

The main format of electronic data in order to ensure the accessibility to
data will be any of the included in the IANA Myme Media Types  6  .

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

What is the origin of the data?

</td>  
<td>

Colum D (owner) and Colum 0 (WP/task)

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

What is the expected size of the data?

</td>  
<td>

We have not included this feature. GRECO is not going to deal with large data
files.

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

To whom might it be useful ('data utility')?

</td>  
<td>

Colum E (uses) and Colum F (Users)

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

In conclusion, **all characteristics that would define a data of GRECO have
been properly documented in section 2 of D5.2 PEDRC** . The real management of
research outputs (included data) is done through an updated EXCEL file in
charge of P1. UPM.

When the dissemination is the way for reaching the final users, then GRECO
requests that all contributions are made open through ZENODO Community (
_https://zenodo.org/communities/greco-787289/_ ), and therefore all research
data that support the dissemination are also requested to be archived in
ZENODO.

Conversely, when the exploitation route has been chosen we must analyse what
type of exploitation is suggested. For those outputs reporting other benefits
that are not economic, (i.e.: social, environmental, regulatory, educational,
etc…) and exploited in further research activities (for education, for
improving policies, for setting standards, etc., but not in commercial
activities), the exploitation is going to be made through Open Mechanisms.

Then, such Research Outputs will be also published in ZENODO to enhance their
exploitation. On the other hand, in those cases of legitimate interests for
exploiting commercially a research output, there will not be any archive of
these results in ZENODO.

Why have we decided to use ZENODO as main repository? Motivations to use this
repository are:

  * Allows researchers to deposit both publications and data, while providing tools to link them. 

  

  * In order to increase visibility and impact of the project the Community GRECO has been created in ZENODO, so all beneficiaries of the project can link the uploaded research outputs to the Community. 

  

  * The repository has backup and archiving capabilities. 

  

  * ZENODO assigns all publicly available uploads a Digital Object Identifier (DOI) to make the upload easily and uniquely citable. 

  

  * The repository allows different access rights. 

  

  * The repository is in a common language for all partners of the project. 

  

All the above makes ZENODO a good candidate as a unified repository for all
foreseen project data (presentations, publications, images, videos and
measurement data) from GRECO.

Even when due to the policy of Journals against archiving out of the
Institutional Repository, or when using specialized repositories such as
GitHub for software; a proper input describing the research output will be
included into ZENODO with a link to the repository where the data can be
found.

#  FAIR DATA

##  Making data findable, including provisions for metadata

###  Discoverability: Metadata Provision

Metadata are created to describe the data and aid discovery. According to
ZENODO repository all metadata is stored internally in JSON-format according
to a defined JSON schema. Metadata is exported in several standard formats
such as MARCXML, Dublin Core, and DataCite Metadata Schema (according to the
OpenAIRE Guidelines).

Beneficiaries will complete all mandatory metadata required by the repository
and metadata recommended by the repository but mandatory for GRECO Consortium,
and may provide additional metadata if appropriated. In the Table 2 a general
overview of metadata is outlined.

**Table 2. Information on metadata generated at ZENODO.**  
  
<table>  
<tr>  
<th>

**Metadata**

</th>  
<th>

**Category**

</th>  
<th>

**Additional Comments**

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

Type of data

</td>  
<td>

Mandatory

</td>  
<td>

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

DOI

</td>  
<td>

Mandatory

</td>  
<td>

If not filled, ZENODO will assigned an automatic DOI. Please keep the same DOI
if the document is already identified with a DOI.

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

Publication Date

</td>  
<td>

Mandatory

</td>  
<td>

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

Title

</td>  
<td>

Mandatory

</td>  
<td>

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

Authors

</td>  
<td>

Mandatory

</td>  
<td>

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

Description

</td>  
<td>

Mandatory

</td>  
<td>

A description of the dataset including the procedures followed to obtain those
results (e.g., software used for simulations, experimental setups, equipment
used, etc.)

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

Keywords

</td>  
<td>

Mandatory

</td>  
<td>

Frequently used keywords, plus GRECO

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

Access rights

</td>  
<td>

Mandatory

</td>  
<td>

Open Access. Other permissions can be considered when appropriated.

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

Terms for Access Rights

</td>  
<td>

Mandatory

</td>  
<td>

Licenses Creative Common will be detailed here. GRECO will open the data under
Attribution, ShareAlike, Non

Commercial and No Derivatives Licences.

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

Communities

</td>  
<td>

Mandatory

</td>  
<td>

Fostering a Next Generation of European

Photovoltaic Society through Open Science

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

Funding

</td>  
<td>

Mandatory

</td>  
<td>

European Union (EU), Horizon 2020, Grant Nº 787289, GRECO

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

Version

</td>  
<td>

Mandatory

</td>  
<td>

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

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

###  Identifiability of data

Beneficiaries will maintain the Digital Object Identifier (DOI) when the
publication/data has already been identified by a third party with this
number. Otherwise ZENODO will provide each dataset with a DOI.

###  Naming convention

**GRECO does not establish a naming convention for uploading data to the
repository** . Since mandatory metadata in ZENODO repository include a
description of the dataset, we ensure third parties will access data easily by
describing properly the dataset. Likewise, our policy of not changing data
names will allow data to be consistent and traceable in each author’s local
back-up devices.

###  Approach towards search keyword

ZENODO allows for introducing keywords for each dataset. Each author will
introduce relevant keywords and **all dataset generated by the Consortium will
be also identified with the keyword GRECO** .

##  Making data openly accessible

###  Types of data made openly available

**GRECO establishes that is mandatory to make publicly available, by means of
ZENODO, the underlying data related to the scientific publications and any
other dissemination activity.** This will allow that other researchers can
make use of that information to validate the results, thus being a starting
point for their research, as expected by the EC through its open access
policy.

In addition, we will make public any type of data or research output that,
having not been disseminated, have the purpose of being non-commercially
exploited: i.e. presentations in events for trainings, videos used for
educational purposes, etc. Their identification within the EXCEL file will
facilitate the archive of these type of data. Therefore, **the Innovation
Manager in charge of data management will recommend partners, what other data
they should make available in open access mode** , **additionally to the data
underlying publications or dissemination,**

###  Methods or software tools needed to access the data

All our data are openly accessible since we work with standard formats
according to IANA Myme Media Types. If any software is needed for opening a
non-conventional file, we will inform on that through the repository. As far
as possible, we will try to convert our files into the most frequent software
programmes, even when possible in Open Software such as i.e. Julia vs.
Mathematica.

###  Deposition of data and associated metadata,

#  documentation and code

As explained, we will use ZENODO repository for the purpose of data, metadata
and documentation deposition. General policy of this repository is accessible
here: _http://about.zenodo.org/policies/_

Other repositories that could be used for some specific data are

  * GitHub **(** _https://github.com/collections/policies_ **)** for some Open Software developed in the project; 

  

  * Institutional Repositories, for archiving post-prints if the Journal policy does not allow to archive the paper out of the institutional repository. 

  

o _http://oa.upm.es/eprints/_ ; o _https://repositori.upf.edu_ o
_https://dspace.uevora.pt/ri/_ o
_https://www.helmholtzberlin.de/zentrum/locations/bibliothek/literatur/publikationsserver_de.ht
ml_

##  Making data interoperable

Interoperability means allowing data exchange and re-use between researchers,
institutions, organisations, countries, etc. (i.e. adhering to standards for
formats, as much as possible compliant with available (open) software
applications, and in particular facilitating re-combinations with different
datasets from different origins.

GRECO Consortium ensures the interoperability of the data by using data in
standard formats according to IANA Myme Media Types and using ZENODO
repository with a standardization JSON scheme for metadata.

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

Data (with accompanying metadata) will be shared no later than publication of
the main findings. The maximum time allowed to share underlying data is the
maximum embargo period established by the EC, six months.

GRECO will include a licence for increasing the re-use of data. Licenses based
on the Creative Commons scheme will be attributed by the owner of the data.
GRECO researchers have received due training on licenses on the 20  th  of
November 2018 and are aware about the options they have. We encourage at CC0
Licenses, but it is not mandatory.

Data will be accessible for re-use without limitation during and after the
execution of GRECO project. After the end of the project, data will remain in
the repository. Publications and/or other data related with the project but
generated after its deadline will be also uploaded.

##  “Open” Notebook and FAIR data.

As a part of the Open Science Pilot we will also explore the policy of FAIR
data INSIDE organizations for non-open data. What we have defined as Open
Notebooks in our proposal (T1.4) will be a pilot for carrying out a FAIR
management of research outputs at P1.UPM, although other partners such as
P9.HZB are also interested in exploring the alternative. We intent to generate
a routine on FAIR data along our daily research activity regardless these data
are going to be published or not. We believe that FAIR data inside
Organizations will allow them, firstly to manage better their resources and
not losing valuable information along the time and; secondly, to realize about
the importance of FAIR data as a tool for a more responsible science rather
than just to meet Funding Agencies mandates. So far, we have identified three
alternatives for implementing this internal system, but we are in an early
stage.

#  Allocation of resources

GRECO will use ZENODO (GitHub or Institutional Repositories) to make data
openly available so there is no cost for the infrastructure. The cost of
personnel devoted to the management of the data is considered to be charged
under the Program.

Each beneficiary will devote its own personnel resources to upload data to
ZENODO and follow the instructions contained in this document. The Coordinator
has named two Innovation Managers within the project, and one of them (Prof.
Antonio Martí) will be responsible to verify and control data opened by
partners ensuring that the policy described in this document is fulfilled.

#  Data Security

ZENODO counts with a technical infrastructure that ensures data security and
long-

term preservation. The interested reader can check the terms at:
_http://about.zenodo.org/infrastructure/_

GitHub data security is described at _https://help.github.com/articles/github-
security/_ Data stored in institutional repositories follow the policy of each
Institution.

#  Ethical Aspects

In order to guarantee that no sensitive data are archived without the consent
of the Consortium, partners will apply the good practice of communicating any
kind of disclosure 30 days beforehand.

Plan of Exploitation, Dissemination and Communication 14