**Executive summary**

As part of the limited pilot action on open access to research data, Sci-GaIA
has implemented a limited pilot action on open access to research data based
on the “Guidelines on Data Management in Horizon 2020”. This document
specifies the Data Management Plan (DMP) for the project and has created a
detailed outline of our policy for data management.

#  1 INTRODUCTION

As part of the limited pilot action on open access to research data, Sci-GaIA
has implemented a limited pilot action on open access to research data based
on the “Guidelines on Data

Management in Horizon 2020”. As part of the overall project Management work
package (WP5), this has been captured in task T5.1 Data Management and
specifies the Data Management Plan (DMP) by creating a detailed outline of the
project policy for data management. As specified in the Guidelines, this will
consider the following:

  * Determine if the project will produce new data or combine existing data 

  

  * Identify the data sources used and produced during project and the related file formats 

  

  * Describe how you will implement a Quality Assurance procedure (QA) for data collection 

  

  * Explain your strategy for preventing data loss: files organization and indexing, data backups and storage 

  

  * Depending on the dissemination level of each dataset, explain how you will ensure (1) data confidentiality, (2) restricted access, or (3) data high visibility 

  

  * Explain how data management tasks and responsibilities are distributed among partners and how they cover the entire data life cycle of the project 

  

This document therefore outlines the first version of the project DMP. The
Sci-GaIA DMP primarily lists the different datasets that will be produced by
the project, the main exploitation perspectives for each of those datasets,
and the major management principles the project will implement to handle those
datasets. The purpose of the DMP is to provide an analysis of the main
elements of the data management policy that will be used by the consortium
with regard to all the datasets that will be generated by the project.

The DMP is not a fixed document. It will evolve during the lifespan of the
project. This first version of the DMP includes an overview of the datasets to
be produced by the project, and the specific conditions that are attached to
them. The next version of the DMP, to be published at M18, will detail and
describe the practical data management procedures implemented by the Sci-GaIA
project. The data management plan will cover all the data life cycle (figure
1).

_Figure 1: Steps in the data life cycle. Source: From University of Virginia
Library, Research Data Services_

#  2 DATASET LIST

All Sci-GaIA partners have identified the datasets that will be produced
during the different phases of the project. The list is provided below, while
the nature and details for each dataset are given in the subsequent sections.

This list is indicative and allows estimating the data that Sci-GaIA will
produce – it may be adapted (addition/removal of datasets) in the next
versions of the DMP to take into consideration the project developments.  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

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

**#**

</td>  
<td>

**Dataset (DS) name**

</td>  
<td>

**Responsible partner**

</td>  
<td>

**Related WP(s)**

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

1

</td>  
<td>

DS1_Newsletter-

Subscribers_SIGMA_V01_DATE

</td>  
<td>

SIGMA

</td>  
<td>

WP4

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

2

</td>  
<td>

DS2_e-Infrastructure-

Survey_WACREN_V01_DATE

</td>  
<td>

WACREN

</td>  
<td>

WP1

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

3

</td>  
<td>

DS3_User-Forum-Members_CSIR_V01_DATE

</td>  
<td>

CSIR

</td>  
<td>

WP2

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

4

</td>  
<td>

DS4_Open-Access-

Repositories&Services_UNICT_V01_DATE

</td>  
<td>

UNICT

</td>  
<td>

WP3

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

**5**

</td>  
<td>

DS5_Event-Membership_SIGMA_V01_DATE

</td>  
<td>

SIGMA

</td>  
<td>

WP4

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

**6**

</td>  
<td>

DS6_Educational-

Materials_BRUNEL_V01_DATE

</td>  
<td>

BRUNEL

</td>  
<td>

WP1

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

**7**

</td>  
<td>

DS7_Project-Deliverables_V01_DATE

</td>  
<td>

BRUNEL

</td>  
<td>

WP5

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

_Table 1: Dataset list_

#  3 GENERAL PRINCIPLES

##  3.1 PARTICIPATION IN THE PILOT ON OPEN RESEARCH DATA

The Sci-GaIA project participates in the Pilot on Open Research Data launched
by the European Commission along with the Horizon 2020 programme. The
consortium strongly believes in the concepts of open science, and in the
benefits that the European innovation ecosystem and economy can draw from
allowing reusing data at a larger scale. Therefore, all data produced by the
project can potentially be published with open access – though this objective
will obviously need to be balanced with the other principles described below.

##  3.2 IPR MANAGEMENT AND SECURITY

Project partners obviously have Intellectual Property Rights (IPR) on their
technologies and data, on which their economic sustainability relies. As a
legitimate result, the Sci-GaIA consortium will have to protect these data and
consult the concerned partner(s) before publishing data.

Another effect of IPR management is that – with the data collected through
Sci-GaIA being of high value – all measures should be taken to prevent them to
leak or being hacked. This is another key aspect of Sci-GaIA data management.
Hence, all data repositories used by the project will include a secure
protection of sensitive data.

An holistic security approach will be undertaken to protect the 3 mains
pillars of information security: confidentiality, integrity, and availability.
The security approach will consist of a methodical assessment of security
risks followed by an impact analysis. This analysis will be performed on the
personal information and data processed by the proposed system, their flows
and any risk associated to their processing.

Security measures will include the implementation of PAKE protocols – such as
the SRP protocol – and protection against bots such as CAPTCHA technologies.
Moreover, the WP/Task leaders identified in Table 1 will implement monitored
and controlled procedures related to data collection, integrity and
protection. Additionally, the protection and privacy of personal information
will include protective measures against infiltration as well as physical
protection of core parts of the systems and access control measures.

##  3.3 PERSONAL DATA PROTECTION

For some of the activities to be carried out by the project, it may be
necessary to collect basic personal data (e.g. full name, contact details,
background), even though the project will avoid collecting such data unless
deemed necessary.

Such data will be protected in compliance with the EU's _Data Protection
Directive 95/46/EC_ 1  aiming at protecting personal data. National
legislations applicable to the project will also be strictly followed, such as
the < _Italian Personal Data Protection Code_ 2  _ > _ .

All data collected by the project will be done after giving data subjects full
details on the analysis to be conducted, and after obtaining signed informed
consent forms.

2  http://www.privacy.it/privacycode-en.html

#  4 DATA MANAGEMENT PLAN

##  4.1 DATASET 1: NEWSLETTER SUBSCRIBERS  
  
<table>  
<tr>  
<th>

**DS1_Newsletter-Subscribers_ SIGMA_V01_DATE**

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

**Data Identification**

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

Dataset description

</td>  
<td>

Mailing list containing email addresses and names of all subscribers to the
Sci-GaIA’s newsletter

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

This dataset is automatically generated in

<Mailchimp/Mailjet/…> by visitors signing up to the newsletter form available
on the project website. Additional subscribers can be manually added to the
mailing list by the partner in charge of the project communication after
receiving informed consent from the data subjects

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

SIGMA

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

Partner in charge of the data collection

</td>  
<td>

SIGMA

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

Partner in charge of the data analysis

</td>  
<td>

SIGMA

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

Partner in charge of the data storage

</td>  
<td>

SIGMA

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

Related WP(s) and task(s)

</td>  
<td>

WP4, T4.1

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

This dataset can be imported from, and exported to a CSV, TXT or Excel file.
Currently, at the time of this deliverable, the list is containing contact
information of around 7000 people, and is smaller than 1 Mb

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The mailing list will be used for disseminating the project newsletter to a
targeted audience. An analysis of newsletter subscribers may be performed in
order to assess and improve the overall visibility of the project

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

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

This dataset does not contain confidential information. However, the
information is sensitive because it implies managing personal data. Therefore,
access to the dataset is restricted to the project dissemination and
communication leader

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

None

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

The mailing list contains personal data (names and email addresses of
newsletter subscribers). People interested in the project voluntarily
register, through the project website, to receive the project newsletter. They
can unsubscribe at any time.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

The mailing list will be regularly backed up in Excel file format all along
the project. Back-ups are safely stored in SIGMA’s server.

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

##  4.2 DATASET 2: E-INFRASTRUCTURE SURVEY

**DS2_e-Infrastructure-Survey_WACREN_V01_DATE**  
  
<table>  
<tr>  
<th>

**Data Identification**

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

Dataset description

</td>  
<td>

Dataset containing details of people who have participated in the Sci-GaIA
e-Infrastructure Survey

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

This dataset is

in the survey. The

gaia.eu/index.php/531683

</td>  
<td>

captured using Limesurvey as people take part link

</td>  
<td>

is

</td>  
<td>

http://surveys.sci-

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

**Partners activities and responsibilities**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

WACREN

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Partner in charge of the data collection

</td>  
<td>

WACREN

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Partner in charge of the data analysis

</td>  
<td>

WACREN

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

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

Partner in charge of the data storage

</td>  
<td>

WACREN

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

Related WP(s) and task(s)

</td>  
<td>

WP1, T1.3

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

This dataset can be imported from, and exported to a CSV, TXT or Excel file.
Currently, at the time of this deliverable, the list contains 0 people and
their responses, and is smaller than 1 Mb

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The data will be analysed to give indications of the impact of
eInfrastructures in Africa. This will appear in D1.3.

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

This dataset does not contain confidential information. However, the
information is sensitive because it implies managing personal data. Therefore,
access to the dataset is initially restricted to the task leader. However, if
the participant has indicated that they are happy to have their personal
details shared then this will be made available to the project team and within
D1.3 (i.e. participants wish to have their e-Infrastructure project efforts
shared with the international community).

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

See above.

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

The survey specifically asks if the participants are happy to share their
details. If so, they indicate this in the survey document and add their
details.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

The list will be stored within the Limesurvey tool or exported to Excel and
stored in the WACREN beneficiary’s computer. These will be held at WACREN. The
list will be deleted six months after the end of the project. Participants who
are happy to share their details will have their data stored within D3.1 (see
project deliverables dataset).

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

##  4.3 DATASET 3: USER FORUM MEMBERS  
  
<table>  
<tr>  
<th>

**DS3_User-Forum-Members_CSIR_V01_DATE**

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

**Data Identification**

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

Dataset description

</td>  
<td>

Forum list containing email addresses and names of all subscribers to the Sci-
GaIA User Forum. Dataset also contains all Forum posts.

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

This dataset is automatically generated by visitors signing up to the User
Forum at discourse.sci-gaia.eu.

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

CSIR

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

Partner in charge of the data collection

</td>  
<td>

CSIR

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

Partner in charge of the data analysis

</td>  
<td>

CSIR

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

Partner in charge of the data storage

</td>  
<td>

CSIR

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

Related WP(s) and task(s)

</td>  
<td>

WP2, T2.1

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

This dataset can be imported from, and exported to a CSV, TXT or Excel file.
Currently, at the time of this deliverable, the list is containing contact
information of around 20 people, and is smaller than 1 Mb

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The dataset is the Forum discussions that support the project’s activities.
This is “self-exploiting” in the sense of continued discussion. The Forum’s
themes and content will be analysed without reference to specific users in
D2.1 Outcomes of the Web-based Forum.

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

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

This dataset does have some personal data. Users have control over the
visibility of this and the degree to which this is shared with other Forum
users. Access to personal data is otherwise restricted to the task leader.
Posts in the Forum are visible to all users.

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

As noted above.

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

This dataset does have some personal data. Users have control over the
visibility of this and the degree to which this is shared with other Forum
users. People interested in the Forum voluntarily register and can deregister
at any time.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

The forum is held on the discourse server in their own file format. The
location of the server is being investigated.

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

##  4.4 DATASET 4: OPEN ACCESS REPOSITORIES & SERVICES  
  
<table>  
<tr>  
<th>

**DS4_Open-Access-Repositories &Services_V01_DATE **

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

**Data Identification**

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

Dataset description

</td>  
<td>

This is the list of open access data repositories and services supported by
Sci-GaIA’s infrastructure services. Where appropriate it will list the data
management policy for a particular service.

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

This is a simple list that is added to when new data repositories and services
are added to our infrastructure services.

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

UNICT

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

Partner in charge of the data collection

</td>  
<td>

UNICT

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

Partner in charge of the data analysis

</td>  
<td>

UNICT

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

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

Partner in charge of the data storage

</td>  
<td>

UNICT

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

Related WP(s) and task(s)

</td>  
<td>

WP3, T3.2

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

Under development

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

Standards, format, estimated volume of data

</td>  
<td>

Under development

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

Various and will reflect the services. Each will be captured along with the
service description.

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

Through IdP, i.e. only those will appropriate security credentials can access
the service. This will be detailed against each service.

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

This will vary from service to service and will be captured with a service
description.

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

Embargo periods (if any)

</td>  
<td>

None.

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

The policy for each service will be captured.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

As above.

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

##  4.5 DATASET 5: EVENT MEMBERSHIP  
  
<table>  
<tr>  
<th>

**DS5_Event-Membership_ SIGMA_V01_DATE**

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

**Data Identification**

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

Dataset description

</td>  
<td>

A list of participants at the Sci-GaIA workshops and training events.

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

The dataset is generated from attendees joining the Sci-GaIA events.

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

SIGMA

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

Partner in charge of the data collection

</td>  
<td>

SIGMA

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

Partner in charge of the data analysis

</td>  
<td>

SIGMA

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

Partner in charge of the data storage

</td>  
<td>

SIGMA

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

Related WP(s) and task(s)

</td>  
<td>

WP4, T4.2 & T4.3

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

This dataset can be imported from, and exported to a CSV, TXT or Excel file.
Currently, at the time of this deliverable, the list is containing contact
information of 0 people as the events are yet to take place.

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

An analysis of event attendees may be performed in order to assess and improve
the overall visibility of the project

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

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

This dataset does not contain confidential information. However, the
information is sensitive because it implies managing personal data. Therefore,
access to the dataset is restricted to the project dissemination and
communication leader.

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

None

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

The list contains personal data (names and email addresses of newsletter
subscribers). People interested in the events voluntarily register, through
the project website.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

The mailing list will be regularly backed up in Excel file format all along
the project. Back-ups are safely stored in SIGMA’s server.

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

##  4.6 DATASET 6: EDUCATIONAL MATERIALS  
  
<table>  
<tr>  
<th>

**DS6_Educational-Materials_ BRUNEL_V01_DATE**

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

**Data Identification**

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

Dataset description

</td>  
<td>

Educational materials created for the training workshops.

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

This has been developed by UNICT and Brunel to support the training events and
subsequent educational modules.

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

UNICT, BRUNEL

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

Partner in charge of the data collection

</td>  
<td>

BRUNEL, UNICT

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

Partner in charge of the data analysis

</td>  
<td>

NA

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

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

Partner in charge of the data storage

</td>  
<td>

UNICT

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

Related WP(s) and task(s)

</td>  
<td>

WP1, T1.1

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

There are many types of data involved in this ranging from word documents to
videos. The estimated size as deployed in OPENEDX will be determined at the
time of the associated deliverable.

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

This will be published under an open commons licence for anyone to exploit.

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

Open access according to the open commons licence.

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

This will be available to all.

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

No personal data.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

The data will be held and backed up at UNICT servers.

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

##  4.7 DATASET 7: PROJECT DELIVERABLES  
  
<table>  
<tr>  
<th>

**DS7_Project-Deliverables_ BRUNEL_V01_DATE**

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

**Data Identification**

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

Dataset description

</td>  
<td>

The deliverables of the project.

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

Source (How have the data been collected? From which tool/survey does the data
come from?)

</td>  
<td>

Generated by WP leaders.

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

**Partners activities and responsibilities**

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

Partner owner of the data; copyright holder (if applicable).

</td>  
<td>

BRUNEL

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

Partner in charge of the data collection

</td>  
<td>

BRUNEL (and WP leaders)

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

Partner in charge of the data analysis

</td>  
<td>

BRUNEL (and WP leaders)

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

Partner in charge of the data storage

</td>  
<td>

SIGMA/EC

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

Related WP(s) and task(s)

</td>  
<td>

WP5 and all WPs

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

**Standards**

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

Info about metadata (production and storage dates, places) and documentation?

</td>  
<td>

N/A

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

Standards, format, estimated volume of data

</td>  
<td>

This will be determined by the end of the document. It will be a combination
of WORD/PDF documents and supporting information.

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

**Data exploitation and sharing**

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

Data exploitation (purpose/use of the data analysis)

</td>  
<td>

The deliverables present the outcomes of the project for public use.

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

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

Data access policy / Dissemination level : confidential (only for members of
the Consortium and the Commission Services) or Public

</td>  
<td>

Open access for all deliverables apart from financial information. This is
restricted to the consortium and Commission Services.

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

Data sharing, re-use, distribution, publication (How?)

</td>  
<td>

Open expect noted above.

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

Embargo periods (if any)

</td>  
<td>

None

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

Personal data protection: are they personal data? If so, have you gained
(written) consent from data subjects to collect this information?

</td>  
<td>

Any personal data will be handled according to the datasets appear in any
deliverable as noted above.

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

**Archiving and preservation (including storage and backup)**

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

Data storage (including backup): where? For how long?

</td>  
<td>

SIGMA and EC – indefinitely.

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

#  5 CONCLUSION

This document contains the data management policy for Sci-GaIA. The policy
will be periodically revised at Project Management Board meetings.