#  Introduction

1.1. Scope

This document contains the initial version of the Prêt-à-LLOD Data Management
Plan (DMP). The DMP is a living document and will be regularly updated.
Succesive stable versions of the DMP will be published in M24 and M36. This
document is complemented by “D5.2 Policy-based language Data Management” (due
in M24) and it is related to “D7.1 Ethics Requirements I” (delivered in M3).

The Data Management Plan adheres to and complies with the “H2020 Data
Management Plan – General Definition” given by the European Commission (EC)
online  1  , where the DMP is described as follows:

“​ _A DMP describes the data management life cycle for the data to be
collected, processed and/or generated by a Horizon 2020 project. As part of
making research data findable, accessible, interoperable and reusable (FAIR),
a DMP should include information on:_

  * _the handling of research data during and after the end of the project_

  

  * _what data will be collected, processed and/or generated_

  

  * _which methodology and standards will be applied_

  

  * _whether data will be shared/made open access and_

  

  * _how data will be curated and preserved (including after the end of the project)”_

  

Prêt-à-LLOD adopts policies compliant with the official FAIR guidelines [1]
(findable, accessible, interoperable and re-usable), as mandated by the EC.
Also, Prêt-à-LLOD participates in the Open Research Data Pilot (ORDP  2  ) and
is obliged to deposit the produced research data in a research data
repository, as per Art. 29.3 of the Grant Agreement.

This Section 1 concludes with the presentation of preliminary concepts;
Section 2 is the Data Management Plan itself and follows the template proposed
by the EC  3  .

1.2. Preliminary concepts

**Zenodo**

Zenodo  4  5  ​is a general-purpose open-access repository much used for
publishing5 deliverables and data of H2020 projects. Zenodo exposes the data
to OpenAIRE , a network of Open Access repositories to support the EC
publication policies.

Resources in Zenodo (consequently also in OpenAire) are identified with a
Document Object Identifier (DOI), they can be versioned, and there are good
chances that they will enjoy long term preservation. Moreover, common search
engines such as Google Scholar or Microsoft Research are aware of the assets
hosted at Zenodo and they enjoy high visibility.

A Prêt-à-LLOD community has been created in the Zenodo portal.

https://zenodo.org/communities/pret-a-llod/

Both deliverables and research data will be published in this Zenodo
community.

**Prêt-à-LLOD Data Portal**

The “ **Prêt-à-LLOD** ​ **Data Portal** ”​ will be the data portal of the
project and will host the description of relevant datasets (metadata). The
data portal will also be used to host newly created language resources as long
as their size is manageable. This data portal will be open to the general
public and users will be able to search for datasets, visualize their
description and eventually download the resource itself.

The Prêt-à-LLOD Data Portal will be built using the CKAN  6  technology (a
standard software package for data portals) and Linghub, a Linked Data based
portal already describing language resources [3]. Due to many internet users
being already familiar with CKAN, their visual appearence will be respected,
only being customized for the needs of this project and using the corporate
image of Prêt-à-LLOD. A CKAN data access API will be exposed to offer
infomation on the datasets metadata.

#  Data Management Plan

The sections of this document and the questions hereinafter are taken from the
_Horizon_ ​ _2020 FAIR Data Management Plan (DMP) template._ The use of the
template is recommended by the EU commission.

2.1 Data summary  
  
<table>  
<tr>  
<th>

**1\. Data summary**

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

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

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

</th>  
<th>

The declared objectives of this project are:

  * to support the exchange of multilingual cross-sectoral data 

  

  * to develop interoperable language technology services and language data 

  

  * to favour the sustainability of language technologies and language resources Consequently, the collection and generation of data are core activities for this project, and its purpose can be summarized as ‘prepare linguistic data so that it can power multilingual applications in a digital single market’. 

  

An initial list of 52 processing activities is documented in annex A of “D7.1.
Ethic Requirements I” [2].

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

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

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

</td>  
<td>

The vast number of formats that will be handled by this project does not allow
a preliminary enumeration. Data in different formats will be collected and
eventually transformed. The preferred type for the generated data is the one
which most favours interoperability ― this will be ​RDF (Resource Description
Framework  7  ) in its different serializations.

The types of data in Table 1 have been identified, with respect to their
meaning:  
  
<table>  
<tr>  
<th>

**Name**

</th>  
<th>

**Description**

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

**Catalogue metadata**

</td>  
<td>

Description of existing data resources

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

**Open linguistic data**

</td>  
<td>

Existing open linguistic data already available prior to Prêt-à-LLOD.

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

**New linguistic data**

</td>  
<td>

Transformation of existing resources or creation of new resources in the LLOD
(Linguistic Linked Open Data cloud [8]) by the Prêt-à-LLOD project. These
assets are considered results of this project.

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

**Experiment-related data**

</td>  
<td>

Data produced in the course of reports generations, execution of experiments
(e.g. experiments for automated linking), etc., often related to research
publications.

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

_Table 1. Types of data generated or collected by Prêt-à-LLOD according to
their meaning_ The following types of data have been identified, according to
their openness.  
  
<table>  
<tr>  
<th>

**Name**

</th>  
<th>

**Description**

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

Private to partners

</td>  
<td>

Available to the partner who owns it

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

Available to partners

</td>  
<td>

Not public, only available to the partners. No

Non-Disclosure Agreements (NDAs) are not necessary and the Consortium
Agreement suffices.

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

Published as Open Data

</td>  
<td>

Both public and available with an open license.

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

_Table 2. Types of data in Prêt-à-LLOD, according to their openness._

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

c) Will you re-use any existing data and how?

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

</td>  
<td>

This project will extensively reuse linguistic resources, eventually
republishing them possibly after a transformation.

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

d) What is the origin of the data?

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

</th>  
<th>

Datasets available in the LLOD cloud and resources available in other data
catalogues (OLAC  8  , LRE Map  9  , META-SHARE  10  , Clarin  11  , Retele
12  ), and private data resources that will not be exposed.

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

e) What is the expected size of the data?

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

</td>  
<td>

The size of the data is broken down per data type:

Catalogue metadata: ~1Gb

Open linguistic data: not to be stored by Prêt-à-LLOD

New linguistic data: ~100Gb

Experiment-related data: ~10Gb

These figures have been estimated considering the experience of some of the
Prêt-à-LLOD partners in the past FP7-funded LIDER project  13  .

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

f) To whom might the data be useful ('data utility')?

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

</td>  
<td>

Two large communities are identified: (i) the community of researchers and
practitioners of linguistics and social sciences and (ii) the community of
computer scientists and developers with interests in natural language
processing.

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

2.2. FAIR data  
  
<table>  
<tr>  
<th>

**2\. FAIR data**

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

**2.1 Making data findable, including provisions for metadata**

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

a) Are the data produced and / or used in the project discoverable and
identifiable?

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

</td>  
<td>

**Catalogue metadata** will be available at the Prêt-à-LLOD Data Portal **.**
​ Data will be discoverable because each dataset will have a description using
the standard DCAT vocabulary  14  (see Figure 1) --in particular, DCAT-AP: the
"DCAT application profile for European data portals", developed in the
framework of the EU ISA Programme  15  , which has become a de-facto standard.

**New linguistic data** produced by this project will also be offered through
the Prêt-à-LLOD Data Portal. Identifiability will be supported because each
data in all datasets will have a unique identifier (IRI  16  ) accessible
through the Web.

**Experiment-related data** will be published in Zenodo, in turn connected
with OpenAIRE and every major indexer of scientific documents. Eventually,
small pieces of data will also be available from source code repositories
(e.g. a Gitlab instance hosted in the premises of the coordinating institution
in Ireland).

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

</th>  
<th>

_Figure 1. Metadata elements in the DCAT specification_

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

b) What naming conventions do you follow?

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

</td>  
<td>

We defined the following two policies:

  1. Identification of datasets. Datasets are identified by an slug (a user friendly and URL valid name of a resource). 

  

  2. URI minting policy, to be decided at a later stage of the project. 

  

  

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

c) Will search keywords be provided that optimize possibilities for re-use?

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

</td>  
<td>

The use of keywords is natural in the Prêt-à-LLOD Data Portal and in Zenodo.
Zenodo’s commitment with FAIR policies is made explicit  17  .

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

d) Do you provide clear version numbers?

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

</td>  
<td>

The use of a semantic versioning is inherent to Zenodo. The Prêt-à-LLOD Data
Portal will also provide versioning and provenance mechanisms.

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

e) What metadata will be created?

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

</td>  
<td>

The stored data are described by using the standard metadata schema Qualified
Dublin Core and DCAT.

Zenodo's metadata is compliant with DataCite's Metadata Schema minimum and
recommended terms, with a few additional enrichments  18  .

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

**2.2 Making data openly accessible**

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

a) Which data produced and / or used in the project will be made openly
available as the default?

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

</th>  
<th>

By default, all metadata in Zenodo and Prêt-à-LLOD Data Portal are openly
available as soon as the record is published.

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

b)

</td>  
<td>

How will the data be made accessible (e.g. by deposition in a repository)?

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

</td>  
<td>

All data are stored in Zenodo and the Prêt-à-LLOD Data Portal. All metadata in
Zenodo and the Prêt-à-LLOD Data Portal are publicly available in an Open
Access modality. Eventually, language resources created by Prêt-à-LLOD will be
introduced in the well-known language resources catalogues (OLAC, LRE Map,
META-SHARE, Clarin, Retele).

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

c)

</td>  
<td>

What methods or software tools are needed to access the data?

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

</td>  
<td>

The extensive use of open specifications and consolidated standards grants
that there is no need for special software tools to access the data.

Eventually, experiment-related data may require of additional software (e.g.
GATE  19  ).

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

d)

</td>  
<td>

Is documentation about the software needed to access the data included?

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

</td>  
<td>

Not necessary for the time being.

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

e)

</td>  
<td>

Is it possible to include the relevant software (e.g. in open source code)?

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

</td>  
<td>

Not necessary for the time being.

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

f)

</td>  
<td>

Where will the data and associated metadata, documentation and code be
deposited?

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

</td>  
<td>

The following data stores are foreseen:

― The Prêt-à-LLOD Data Portal store defined in Section 1.1, hosted in Ireland,
for catalogue data and some newly generated resources.

― A Gitlab instance, hosted in Ireland, for small datasets.

― Zenodo for research-related data.

Data will also be mirrored, whenever possible, in projects with whom liaisons
will be established. In particular, relevant data will be also passed to the
ELG (European Language Grid  20  ) project, “Towards the Primary Platform for
Language Technologies in

Europe”.

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

g)

</td>  
<td>

Have you explored appropriate arrangements with the identified repository?

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

</td>  
<td>

The aforementioned repositories are either self-managed by Prêt-à-LLOD
partners, or they are already deemed for these purposes.

Formal arrangements with ELG are pending to be done.

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

h)

</td>  
<td>

If there are restrictions on use, how will access be provided?

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

</td>  
<td>

No restrictions have been identified at this stage, but the commercial
interest of the partners may lead to the creation of private data.

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

i) Is there a need for a data access committee?

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

</td>  
<td>

No. Rules that concern governing of data access of the partner institutions
will be followed and implemented, together with the FAIR principles followed
by this Plan.

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

j) Are there well described conditions for access (i.e. a machine readable
license)?

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

</td>  
<td>

Licenses in Prêt-à-LLOD Data Portal are represented in a machine readable
form, using the most common metadata descriptor (dct:license, see Figure 1)
pointing to standard URL licenses’.

Whenever linked data is published, standard practices will be followed to
publish the rights information [5].

Moreover, in some cases, a fully machine readable representation of the
licenses is given using the Open Digital Rights Management Language (ODRL)  21
. Licenses from the RDFLicense dataset are also used [4].

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

k) How will the identity of the person accessing the data be ascertained?

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

</td>  
<td>

Not necessary for the time being.

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

**2.3 Making data interoperable**

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

a) Are the data produced in the project interoperable?

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

</td>  
<td>

Both Zenodo and the Prêt-á-LLOD Data Portal use standard interfaces, protocols
and metadata, etc. Using standard metadata schemas in Zenodo, metadata can
easily be converted into other metadata schemas.

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

b) What data and metadata vocabularies, standards or methodologies will you
follow to make your data interoperable?

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

</td>  
<td>

DCAT (described above) and the CKAN schema  22  based on it. Linghub currently
makes use of the META-SHARE OWL ontology [6].

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

c) Will you be using standard vocabularies for all data types present in your
data set, to allow inter-disciplinary interoperability?

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

</td>  
<td>

Yes, see above (2.3.b).

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

d) In case it is unavoidable that you use uncommon or generate project
specific ontologies or vocabularies, will you provide mappings to more
commonly used ontologies?

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

</td>  
<td>

The use of RDF as the meta-format grants the easy definition of links between
equivalent metadata elements.

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

**2.4 Increase data re-use (through clarifying licences)**

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

a) How will the data be licensed to permit the widest re-use possible?

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

</td>  
<td>

​Open by 23default, using the CC-BY license (Creative Commons 4.0 Attribution
International ) unless this hampers the business model of our partners.

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

b) When will the data be made available for re-use?

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

</td>  
<td>

​Data will be made available as soon as it is created and no data embargoes
are foreseen.

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

c) Are the data produced and / or used in the project useable by third
parties, in particular after the end of the project?

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

</td>  
<td>

Making data ready to use is the motto of this project, and every possible
measure will be taken to maximize its usability.

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

d) How long is it intended that the data remains re-usable?

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

</td>  
<td>

Data in the Prêt-à-LLOD Data Portal may not be supported after the end of the
project, but because it will be mirrored in the ELG, long time preservation
will be possible.

Research data will enjoy long term preservation as it will be uploaded to
Zenodo.

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

e) Are data quality assurance processes described?

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

</td>  
<td>

No. Future versions of this DMP may include a definition of such process.

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

​

2.3. Allocation of resources  
  
<table>  
<tr>  
<th>

**3 Allocation of resources**

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

a) What are the costs for making data FAIR in your project?

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

</td>  
<td>

None that is not foreseen in the Grant Agreement: making data FAIR is an
explicit objective of this project.

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

b) How will these be covered?

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

</td>  
<td>

Not applicable.

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

c) Who will be responsible for data management in your project?

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

</td>  
<td>

Víctor Rodríguez Doncel (UPM) will be the responsible for the management of
open data in this project. The management of private data will be
responsibility of the partners having produced it.

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

d) Are the resources for long term preservation discussed?

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

</td>  
<td>

​The cooperation agreements with the ELG project are headed towards long term
preservation.

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

2.4. Data security  
  
<table>  
<tr>  
<th>

**4 Data security**

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

a) Is the data safely stored in certified repositories for long term
preservation and curation?

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

</td>  
<td>

Most data (catalogue data, newly created resources) will contain data to be
published under an open license. This data does not need any security measure
whatsoever. For the case partners generate privative data with personal
information, security measures

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

</td>  
<td>

will have to be adopted to comply with the General Data Protection Regulation
(GDPR, Regulation (EU) 2016/679).

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

b) What provisions are in place for data security?

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

</td>  
<td>

Not yet described.

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

2.5. Ethical aspects  
  
<table>  
<tr>  
<th>

**5 Ethical aspects**

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

a) Are there any ethical or legal issues that can have an impact on data
sharing?

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

</td>  
<td>

Ethical aspects have been extensively documented in Prêt-à-LLOD deliverables
“D7.1 Ethics Requirements I” and in “D7.4 Ethics Requirements 4”.

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

b) Is informed consent for data sharing and long term preservation included in
questionnaires dealing with personal data?

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

</td>  
<td>

See Prêt-à-LLOD deliverable “D7.1. Ethics Requirements I”.

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

​

2.6. Other issues  
  
<table>  
<tr>  
<th>

**6 Other issues**

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

a) Do you make use of other national / funder / sectorial / departmental
procedures for data management?

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

</td>  
<td>

― National University of Ireland Galway (NUIG) is subject to a​ _“Insight Open
Source Release Process”_ ​procedure.

_―_ Universidad Politécnica de Madrid (UPM) is subject to “​ _Normativa sobre
protección de resultados de investigación de la Universidad Politécnica de_

_Madrid_ ​” and “​ _Reglamento del comité de ética de actividades i+d+i de la
Universidad Politécnica de Madri_ ​d”

These procedures are compatible with the provisions made in this data
management plan.

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