#  Executive Summary

This document is the first version of the Data Management Plan (DMP) for data
collected and created by DESIR. It describes the datasets generated during the
course of the project, how the data will be produced and analysed. It details
also how the data generated will be shared, disseminated and preserved.  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

Nature of the deliverable

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

</td>  
<td>

R

</td>  
<td>

Document, report

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

</td>  
<td>

DEM

</td>  
<td>

Demonstrator, pilot, prototype

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

</td>  
<td>

DEC OTHER

</td>  
<td>

Websites, patent fillings, videos, etc.

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

✓

</td>  
<td>

ORDP

</td>  
<td>

Open Research Data Pilot

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

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

Dissemination level

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

✓

</td>  
<td>

P

</td>  
<td>

Public

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

</td>  
<td>

CO

</td>  
<td>

Confidential only for members of the consortium (including the Commission

Services)

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

</td>  
<td>

EU-RES

</td>  
<td>

Classified Information: RESTREINT UE (Commission Decision 2005/444/EC)

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

</td>  
<td>

EU-CON

</td>  
<td>

Classified Information: CONFIDENTIEL UE (Commission Decision 2005/444/EC)

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

</td>  
<td>

EU-SEC

</td>  
<td>

Classified Information: SECRET UE (Commission Decision 2005/444/EC)

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

Disclaimer

DESIR has received funding from the European Union’s Horizon 2020 research and
innovation programme under grant agreement No 731081. This publication
reflects the views only of the author, and the Commission cannot be held
responsible for any use which may be made of the information contained
therein.

#  Introduction

The DESIR project sets out to strengthen the sustainability of DARIAH and
firmly establish it as a long-term leader and partner within arts and
humanities communities. By DESIR’s definition, sustainability is an evolving
6-dimensional process, divided into the following challenges:

  1. Dissemination: DESIR will organise a series dissemination events, including workshops in the US and Australia, to promote DARIAH tools and services and initiative collaborations. 

  

  2. Growth: DESIR sets out to prepare the ground for establishing DARIAH membership in six new countries: the UK, Finland, Spain, Switzerland, Czech Republic and Israel. 

  

  3. Technology: DESIR will widen the DARIAH research infrastructure in three areas, vital for DARIAH’s long-term sustainability: entity-based search, scholarly content management, visualization and text analytic services. 

  

  4. Robustness: DESIR will make DARIAH’s organizational structure and governance fit for the future and develop a detailed business plan and marketing strategy. 

  

  5. Trust: DESIR will measure the acceptance of DARIAH, especially in new communities, and define mechanisms to support trust and confidence in DARIAH. 

  

  6. Education: Through training and teaching DESIR will promote the use of DARIAH tools and services. 

  

  

Funded under the Work Programme part European Research infrastructures
(including eInfrastructures), DESIR participates to the Open Research Data
Pilot (ORDP). As such, this document introduces the first version of the
project Data Management Plan (DMP). The DMP describes the data management life
cycle for the data to be collected, processed and/or generated by the DESIR
Consortium. It includes information on how the research data will be handled
during and after the end of the project, what data will be collected or
generated, which methodology and standards will be applied, how the data will
be disseminated and shared, how the data will be curated and shared during and
after the end of the project.

The DMP is to be considered as a living document: the information contained
therein will be updated following the implementation of the project and when
significant changes occur. Moreover, in a second phase, the Consortium intends
to deliver a version which will contain recommendations to the community and
specifically tailored to Digital Humanities. Research data generated and
processed in DESIR will be FAIR (findable, accessible, interoperable and
reusable).

#  What kind of data is considered in the DMP

According to the _Guidelines to the Rules on Open Access to Scientific
Publications and Open Access to Research Data in Horizon 2020_ (Version 3.0,
26 July 2016), research data “ _refers to information, in particular facts or
numbers, collected to be examined and considered as a basis for reasoning,
discussion, or calculation._ _In a research context, examples of data include
statistics, results of experiments, measurements, observations resulting from
fieldwork, survey results, interview recordings and images. The focus is on
research data that is available in digital form._ ”

DESIR focuses on the sustainability of the DARIAH ERIC and will develop
Actions consisting primarily of accompanying measures such as standardisation,
dissemination, awarenessraising and communication, networking, coordination,
support services, policy dialogues and mutual learning exercises. As such, we
expect that limited research data will be generated during the course of the
project.

#  Structure of the template

Each dataset will cover issues identified in the template below. The data will
follow best practises defined in the _Guidelines on FAIR Data Management in
Horizon 2020_ to make the DESIR research data findable, accessible,
interoperable and re-usable  1  .  
  
<table>  
<tr>  
<th>

Data Summary

</th>  
<th>

•

</th>  
<th>

State the purpose of the data collection/generation

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

</td>  
<td>

•

</td>  
<td>

Explain the relation to the objectives of the project

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

</td>  
<td>

•

</td>  
<td>

Specify the types and formats of data generated/collected

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

</td>  
<td>

•

</td>  
<td>

Specify if existing data is being re-used (if any)

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

</td>  
<td>

•

</td>  
<td>

Specify the origin of the data

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

</td>  
<td>

•

</td>  
<td>

State the expected size of the data (if known)

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

</td>  
<td>

•

</td>  
<td>

Outline the data utility: to whom will it be useful

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

  2. FAIR Data 

  

  

2.1. Making data findable, including

provisions for

metadata

</td>  
<td>

• •

•

</td>  
<td>

Outline the discoverability of data (metadata provision)

Outline the identifiability of data and refer to standard identification
mechanism.

Do you make use of persistent and unique identifiers such as Digital Object
Identifiers?

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

</td>  
<td>

•

</td>  
<td>

Outline naming conventions used

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

</td>  
<td>

•

</td>  
<td>

Outline the approach towards search keyword

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

</td>  
<td>

•

</td>  
<td>

Outline the approach for clear versioning

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

</td>  
<td>

•

</td>  
<td>

Specify standards for metadata creation (if any). If there are no standards in
your discipline describe what type of metadata will be created and how

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

2.2 Making data

openly accessible

</td>  
<td>

•

</td>  
<td>

Specify which data will be made openly available? If some data is kept closed
provide rationale for doing so

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

</td>  
<td>

•

</td>  
<td>

Specify how the data will be made available

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

</td>  
<td>

•

</td>  
<td>

Specify what methods or software tools are needed to access the data? Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?

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

</td>  
<td>

•

</td>  
<td>

Specify where the data and associated metadata, documentation and code are
deposited

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

</td>  
<td>

•

</td>  
<td>

Specify how access will be provided in case there are any restrictions

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

2.3. Making data interoperable

</td>  
<td>

  * Assess the interoperability of your data. Specify what data and metadata vocabularies, standards or methodologies you will follow to facilitate interoperability. 

  

  * Specify whether you will be using standard vocabulary for all data types present in your dataset, to allow inter-disciplinary interoperability? If not, will you provide mapping to more commonly used ontologies? 

  

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

2.4. Increase data re-use (through

clarifying licences)

</td>  
<td>

  * Specify how the data will be licenced to permit the widest reuse possible 

  

  * Specify when the data will be made available for re-use. If applicable, specify why and for what period a data embargo is needed 

  

  * Specify whether the data produced and/or used in the project is useable by third parties, in particular after the end of the project? If the re-use of some data is restricted, explain why 

  

  * Describe data quality assurance processes 

  

  * Specify the length of time for which the data will remain reusable 

  

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

3\. Allocation of resources

</td>  
<td>

  * Estimate the costs for making your data FAIR. Describe how you intend to cover these costs 

  

  * Clearly identify responsibilities for data management in your project 

  

  * Describe costs and potential value of long term preservation 

  

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

4\. Data security

</td>  
<td>

• Address data recovery as well as secure storage and transfer of sensitive
data

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

5\. Ethical aspects

</td>  
<td>

• To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former

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

6\. Other

</td>  
<td>

• Refer to other national/funder/sectorial/departmental procedures for data
management that you are using (if any)

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

#  Datasets description

The DESIR Consortium identified the datasets that will be produced during the
different phases of the project. The list is, however, to be considered
indicative and datasets may be adapted, added or removed following the
evolution of the project.

##  Datasets

  1. Source code of software developed in WP4 

  

  2. Survey conducted in WP6 

  

  
  
<table>  
<tr>  
<th>

Dataset 1: Source code of software developed in WP4

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

Data Summary

</td>  
<td>

Computer source code generated as part of the programming activities in WP4,
through development activities by the project partners contributing to WP4 and
through the Code Sprint planned for Summer 2018\.

The efforts will follow the recommendations to encourage best practices in
research software: _https://softdev4research.github.io/recommendations/_

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

2\. FAIR Data 2.1. Making data findable, including provisions for metadata

</td>  
<td>

The code will be licenced under OSI approved licenses. When no other choice is
preferred (e.g. when contributing to an existing ecosystem), the default
license will be Apache-2.0 or EUPL-1.2 (In each case the decision for or
against Copyleft and other implications can be readdressed.).

The source code will be designed, formatted and commented according to the
established standards and practices of the corresponding programming
languages. Additional documentation will be provided in text-based form along
with the code.

The identifiers, versions, licenses and contributors will be collected
according to existing open source standards. The code repositories will be
registered via DataCite or Zenodo.

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

2.2 Making data openly accessible

</td>  
<td>

The source code will be made publicly available.

The code will be licenced under OSI approved licenses. When no other choice is
preferred (e.g. when contributing to an existing ecosystem), the default
license will be Apache-2.0 or EUPL-1.2 (In each case the decision for or
against Copyleft and other implications can be readdressed.).

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

2.3. Making data interoperable

</td>  
<td>

By using the established Github platform and adhering to each programming
language’s individual software design standard, interoperability with third-
party development will be ensured.

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

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

</td>  
<td>

Code specifically developed within DESIR will be published on GitHub using the
responsible partner's or the DARIAH ERIC's organisational account, using
appropriate OSI approved licenses, see 2.2. Where existing solutions are
extended, applicable platforms will be chosen on a per-case basis, and efforts
will be undertaken to merge

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

</td>  
<td>

improvements back upstream. This will allow re-use and discoverability and
constitutes the publication.

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

3\. Allocation of resources

</td>  
<td>

Publication of source code on GitHub is part of the development process and
free of charge. Archiving of code repositories will be done by consortium
members.

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

4\. Data security

</td>  
<td>

Source code will be archived in institutional repositories at the end of the
project, on Zenodo and/or the DARIAH repository.

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

5\. Ethical aspects

</td>  
<td>

n/a

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

6\. Other

</td>  
<td>

n/a

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

Dataset 2: Survey conducted in WP6

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

Data Summary

</td>  
<td>

This survey aims to identify cross-disciplinary DARIAH communities and new
core groups, considering gender and diversity as main variables. It also aims
to explore to what extent is DARIAH is reaching such research communities in
terms of use and access. It is expected to analyse to what extent these
communities perceive DARIAH as a reliable, trustworthy and sustained
infrastructure.

Generated data will be the source to the empirical study of DARIAH’s usage in
new communities, and define new strategies and the data will be exported in
xsl format.

Original data will be collected from researchers defined within target groups
(three cross-disciplinary communities and core groups: i) early career
researchers, including MA and PhD students; ii) academics without permanent
institutional affiliations (no reliable access to RIs); iii) academics with
cross-disciplinary backgrounds and research interests (not clearly associated
merely with one academic discipline).

Data size cannot be specified yet and no specific data re-use is expected
within this data collection.

The collected data will be mostly useful for WP6 study. The analysed data will
be, nonetheless, useful for future comparative studies.

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

2\. FAIR Data 2.1. Making data findable, including provisions for metadata

</td>  
<td>

Files will have common identifiers (respondents’ identification number and
country codes) and identification numbers will be consistent across all data
files.

Users will be given access to contextual, multilevel and thematic data.

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

2.2 Making data openly accessible

</td>  
<td>

In accordance with data protection, only anonymous data will be available to
users.

No specific methods or software tools are needed to access the data to be made
available.

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

2.3. Making data interoperable

</td>  
<td>

n/a

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

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

</td>  
<td>

Analysed data and final report will be published under Creative Commons
Attribution 4.0 License, allowing data re-use by third parties after the end
of the project

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

</td>  
<td>

Data quality will be assured through quality assessment, including the quality
and comparability of measurement instruments, the assessment of target-groups
sample composition and the output quality of the survey.

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

3\. Allocation of resources

</td>  
<td>

The data collection and analysis is part of WP6 tasks within the project and
no additional costs are expected.

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

4\. Data security

</td>  
<td>

Data will be archived in institutional repositories at the end of the project
and/or the DARIAH repository.

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

5\. Ethical aspects

</td>  
<td>

Research data will be generated from the participation of humans through a
survey. Respondent, which will be anonymous and will participate on a
volunteer basis, will be fully aware of the nature and purpose of the
research, what their role in it will be, and how the data they provide will be
subsequently used. The template of the survey will has been included in D6.1
and will be provided on request.

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

6\. Other

</td>  
<td>

n/a

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