#  Executive Summary

Data management is a crucial issue for research and innovation projects and
many mistakes were made in the past, when no one was actually thinking about
what to do with the data and how to preserve them or make them available for
other researchers too. This first Data Management Plan (DMP) shows that there
are mainly eight data sets that will be produced as part of the project
activities and that are relevant to be included in the DMP. These data sets
cover the collected stakeholder contacts, public security services and digital
security solutions. Furthermore, the empirical research will generate data
from the quantitative survey, expert interviews, focus groups and workshops.
Additionally, also the validation of the TAKEDOWN solutions will generate
data.

Due to privacy and security concerns related with the sample size, the
qualitative research data will not be made openly accessible as primary data
but in a processed form. Due to the scope of the research and the intended
sample size, it is planned to make the data from the quantitative survey
openly accessible on the data repository Zenodo. Furthermore, reports working
with the qualitative data will also be accessible. The consortium will also
aim at open access when publishing papers and articles. However, these steps
will be done in accordance with the ethical guidelines elaborated in this
report as well as in D2.2.

The DMP is a living document and hence several issues will be updated and
further questions will be answered in the second version, which will be
finalized in month 18.

#  1\. Introduction

Research and innovation projects such as TAKEDOWN usually produce large sets
of data. Depending on the discipline, the data could come for example from
social science research, laboratory testing, field studies or observations.
However, it often remains unclear and uncertain, what will happen with the
data after they were analysed and the project was finished. Furthermore, a lot
of data sets are potentially interesting also for other researchers, but due
to the fact that they are either stored on a local serves or miss crucial
meta-data (or both), their potential value cannot be exploited. Hence,
researcher need to think about the data that they will produce at the
beginning of the research – and this is exactly the purpose of the Data
Management Plan (DMP).

The purpose of the Data Management Plan (DMP) is to provide an analysis of the
main elements of the data management policy that will be used in the TAKEDOWN
project and by the consortium with regard to the project research data. The
DMP covers the complete research data life cycle. It describes the types of
research data that will be generated or collected during the project, the
standards that will be used, how the research data will be preserved and what
parts of the datasets will be shared for verification or reuse.

The DMP is a living document, which will evolve during the lifespan of the
project, particularly whenever significant changes arise such as dataset
updates or changes in Consortium policies. This document is the first version
of the DMP, delivered in Month 6 of the project. It includes an overview of
the datasets to be produced by the project, and the specific conditions that
are attached to them. Although this report already covers a broad range of
aspects related to the TAKEDOWN data management, the upcoming versions will
get into more detail on particular issues such as data interoperability and
practical data management procedures implemented by the TAKEDOWN project
consortium.

The following section of the DMP provides an overview of the data sets, which
will be produced in the TAKEDOWN project. It describes the origins of the data
as well as the formats the allocation the particular WPs. Furthermore, it
highlights the purpose of the collection as well as information on the
utility. Section 3 clearly points out, which data will be made openly
accessible and which won’t – including detailed justifications for the
reasons. This is especially relevant for the primary data that will be
collected as part of the empirical research. Furthermore, the section also
provides details on the data repositories or other locations, where the data
will be stored. Section 4 highlights main aspects related to the costs of the
accessibility, whereas Section 5 discusses the main ethical issues. The final
section provides an outlook on the open issues and questions to be addressed
in the next DMP report.

#  2\. Data summary

In order to provide an overview of the different data sets that are currently
and will be produced in the TAKEDOWN project, the following table shows the
data type, the origin of the data, the related WP number and the format, in
which the data will be presumably stored.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data type**

</th>  
<th>

**Origin**

</th>  
<th>

**WP#**

</th>  
<th>

**Format**

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

1

</td>  
<td>

Stakeholder contacts collection

</td>  
<td>

Publicly available data

</td>  
<td>

2

</td>  
<td>

.xls

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

2

</td>  
<td>

Public security services collection

</td>  
<td>

Publicly available data

</td>  
<td>

2

</td>  
<td>

.xls

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

3

</td>  
<td>

Digital security solutions collection

</td>  
<td>

Publicly available data

</td>  
<td>

2

</td>  
<td>

.xls

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

4

</td>  
<td>

Quantitative survey data

</td>  
<td>

Primary data

</td>  
<td>

3

</td>  
<td>

.xls +.csv

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

5

</td>  
<td>

Expert interview data

</td>  
<td>

Primary data

</td>  
<td>

3

</td>  
<td>

.mp3 + .docx + .txt

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

6

</td>  
<td>

Focus groups data

</td>  
<td>

Primary data

</td>  
<td>

3

</td>  
<td>

.docx + .txt

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

7

</td>  
<td>

Workshops data

</td>  
<td>

Primary data

</td>  
<td>

3

</td>  
<td>

.docx + .txt

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

8

</td>  
<td>

Validation cycles data

</td>  
<td>

Primary data

</td>  
<td>

7

</td>  
<td>

xls + .csv

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

##  Table 1: Data sets overview

Table 2 describes the data set and the purpose of the data collection of data
generation in relation with the objectives of the project. Additionally, it
shows the data utility for clarifying to whom the data might be useful.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data type**

</th>  
<th>

**Description & Purpose **

</th>  
<th>

**Utility**

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

1

</td>  
<td>

Stakeholder contacts collection

</td>  
<td>

**Description** The data contain information on the main stakeholders of
TAKEDOWN along the major stakeholder groups. They include researchers,
practitioners, policy makers, law enforcement agencies, NGOs and other
initiatives as well as security solutions providers. The contact information
that is collected includes the name, institutional affiliation, position,
email address, phone number and office address.

**Purpose** The collection will be used for contacting the respondents of the
empirical research as well as the validation of the project outcomes. It also
provides the basis for the dissemination of the project and for promoting the
TAKEDOWN solutions.

</td>  
<td>

The data could be on the one hand useful for research, as they comprise a
large part of the ecosystem. Furthermore, the data might also be interesting
for the private sector as target groups of their products.

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

2

</td>  
<td>

Public security services collection

</td>  
<td>

**Description** The data set is a collection of public security services such
as helplines, online reporting platforms or information sites. It covers most
of the European countries and the entries are providing information on the
name, the purpose or focus (OC or TN of both), the institution

</td>  
<td>

These data are on the one hand useful for initiatives working in the field of
counter violent extremism (CVE) and against organized crime, because it allows
them to get an overview on

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

</th>  
<th>

</th>  
<th>

that is providing the service and the link or phone number etc.

**Purpose** The collection is on the one hand crucial to get an overview of
already existing public service. On the other hand, the collection will be
made accessible on the TAKEDOWN open information hub.

</th>  
<th>

the available resources. On the other hand, also public authorities can make
use of the data in order to see which countries have implemented which
services.

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

3

</td>  
<td>

Digital security

solutions collection

</td>  
<td>

**Description** The data set structures and clusters digital security software
and hardware from European companies along several main categories. They
include the name of the solution, the field where it can be applied, the
geographical scope and the status (laboratory, market-ready etc.).
Additionally it includes a brief description of the solution, the operational
language, the target group, the vendor, the country of the company and the
link to the solution.

**Purpose** The collection is used for getting an overview of existing
software and hardware tools, which aim at fighting organized crime and
terrorist networks. Additionally, it will be accessible for LEAs and
professionals on the TAKEDOWN

Solutions Platform.

</td>  
<td>

These data can be useful on the one hand for LEAs, which are looking for
specific software or hardware

against particular phenomena related to OC or TN. Furthermore, they can also
be useful for private security companies working in one of these fields. The
data might also be useful for solution developer in order to get a market
overview as well as for investors, who are looking for future products to
invest in.

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

4

</td>  
<td>

Quantitative survey data

</td>  
<td>

**Description** This data set contains the data from the quantitative survey,
which is conducted in the TAKEDOWN project. The target group of the survey is
first-line practitioners (such as teachers, social workers, street workers,
community police officers etc., who are working with people at risk of
becoming involved in OC or TN. In addition to getting information on how they
are dealing with these issues in their daily practice, the survey strongly
aims at getting an understanding what they actually need in order to make
their work easier and how toolkits need to be shaped in order to be a real
support for them. The quantitative survey will be implemented as an online
survey and aims at a minimum of 1.000 recipients.

**Purpose** The outcomes of the survey will be used to develop the
practitioner toolkits, the policy recommendations and the digital Open
Information Hub.

</td>  
<td>

The large-scale survey, which will be implemented in TAKEDOWN, is the first
one of this kind and of this scope.

On the one hand, the outcomes will be crucial for understanding the needs and
requirements of the first-line practitioners and for developing the toolkits
etc. On the other hand, the data will be interesting for other researchers
working in this field – either for (full or partial) secondary analysis, for a
comparative analysis with other data or for a panel (longitudinal) survey.

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

5

</td>  
<td>

Expert interview data

</td>  
<td>

**Description** The data contain of recordings, transcriptions and notes from
about 40 qualitative expert interviews with

</td>  
<td>

The information provided in the data is not only crucial for TAKEDOWN, but it
can

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

</td>  
<td>

</td>  
<td>

researchers and policy makers. The interviews will be either conducted
personally, on the phone (or skype) or they can also be conducted in written
form.

**Purpose** The aim of the qualitative interview is to get further insights on
the obstacles related to current policies that are in place. They will
therefore support the development of recommendations for future policies
related to both OC and TN.

</td>  
<td>

also be useful for research as well as for policy making. Also practitioners
and LEAs might benefit from it.

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

6

</td>  
<td>

Focus groups

data

</td>  
<td>

**Description** The dataset contains of protocols, written notes and summaries
from the five focus groups that are held in different countries and attended
by practitioner organizations and LEA representatives.

**Purpose** The focus groups aim at getting in-depth insights on the
challenges and obstacles that these stakeholders are facing related to OC and
TN. The acquired knowledge will help the consortium to shape the toolkits, the
open information hub and the digital solutions platform.

</td>  
<td>

The data are not only crucial for TAKEDOWN, but they are also useful for OC or
TN research and policy making. Also practitioners and LEAs might benefit from
it.

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

7

</td>  
<td>

Workshops data

</td>  
<td>

**Description** The data contain protocols, written notes and summaries that
were done at the three workshops, which are organized in different countries.
The workshops aim at developers and providers of technical solutions.

**Purpose** The information gathered at the workshops will support the
development of the TAKEDOWN Solutions Platform by being able to take into
account the requirements of the security industry.

</td>  
<td>

The information provided in the data is not only important for TAKEDOWN, but
it can also be useful for research as well as for policy making. Also
practitioners and LEAs might benefit from it.

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

8

</td>  
<td>

Validation cycles data

</td>  
<td>

**Description** The data from the evaluation of the non-digital and the
digital solutions shows how major stakeholder groups experience their
usability and relevance.

**Purpose** The validation provides the basis for improving and releasing the
final solutions.

</td>  
<td>

The data from the validation of the non-digital and the digital solutions do
mainly have an internal use for improving the solutions and for the lessons-
learned.

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

**Table 2: Data sets description and utility**

#  3\. FAIR data

##  Making data openly accessible

The following table is highlighting A) which data that are produced and used
in the project and B) will be made openly available. It also explains why
several datasets cannot be shared because of particular reasons. For these
cases, an alternative solution is provided.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data type**

</th>  
<th>

**Data openly available**

**(y/n)**

</th>  
<th>

**Justification**

</th>  
<th>

**Alternative solution**

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

1

</td>  
<td>

Stakeholder contacts collection

</td>  
<td>

No

</td>  
<td>

Although the contacts of the collection are professionals’ contacts that are
available, the consortium can’t publish them due to potential misuse caused by
automated Spam programs.

</td>  
<td>

publicly

</td>  
<td>

The statistical information on the stakeholder data (such as how many, from
which countries, which professions etc.) will be integrated in the public
report D2.6. In case an external institution is looking for contacts in a
specific and the coordinator doesn’t see any privacy concerns, relevant
contacts might be forwarded.

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

2

</td>  
<td>

Public security services collection

</td>  
<td>

Yes

</td>  
<td>

(not relevant)

</td>  
<td>

</td>  
<td>

(not relevant)

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

3

</td>  
<td>

Digital security solutions collection

</td>  
<td>

Yes

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

4

</td>  
<td>

Quantitative survey data

</td>  
<td>

Yes

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

5

</td>  
<td>

Expert interview data

</td>  
<td>

No

</td>  
<td>

The data from the

interviews (recordings, protocols

</td>  
<td>

expert

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

and transcriptions) will not be published as primary data due to privacy and
security concerns.

Anonymization is not considered as an alternative, because the sample size
allows drawing conclusions on the respondents.

</td>  
<td>

The categorization, analysis and interpretation of the primary data will be
accessible in the public report D3.6 (and others) that can be accessed on the
TAKEDOWN project website. Furthermore, the

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

6

</td>  
<td>

Focus groups data

</td>  
<td>

No

</td>  
<td>

The data from the focus groups (recordings, protocols and transcriptions) will
not be published as primary data due to privacy and security concerns.
Anonymization is not considered

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

as an alternative, because the sample size allows drawing conclusions on the
respondents.

</td>  
<td>

outcomes will also be disseminated in scientific publications.

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

7

</td>  
<td>

Workshops data

</td>  
<td>

No

</td>  
<td>

The data from the workshops (recordings, protocols and transcriptions) will
not be published as primary data due to privacy and security concerns.

Anonymization is not considered as an alternative, because the sample size
allows drawing conclusions on the respondents.

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

8

</td>  
<td>

Validation cycles data

</td>  
<td>

No

</td>  
<td>

The data from evaluation survey will not be published due to privacy and
security concerns.

Anonymization is not considered as an alternative, because the sample size
allows drawing conclusions on the respondents.

</td>  
<td>

The deliverable D7.3 will report on the validation and the development of the
final non-digital and digital solutions based on the validation.

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

###  Table 3: Data sets accessibility

As it was indicated above, the following data sets will be made openly
accessible: Data type **#2** (Public security services collection), **#3**
(Digital security solutions collection) and **#4** (Quantitative survey data).
The following table describes the accessibility details of these particular
datasets.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data type**

</th>  
<th>

**Location**

</th>  
<th>

**Level of acessibility**

</th>  
<th>

**Type of availability and required software tools**

</th>  
<th>

**Information on metadata and additional data information**

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

2

</td>  
<td>

Public

Security

Services

</td>  
<td>

TD Solutions Platform

</td>  
<td>

Public

</td>  
<td>

Filterable and searchable database; can be accessed with a state-ofthe-art

webbrowser

</td>  
<td>

No metadata needed; additional information will be provided on the platform

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

3

</td>  
<td>

Digital security solutions collection

</td>  
<td>

TD Solutions Platform

</td>  
<td>

Validated professionals

</td>  
<td>

Filterable and searchable database; can be accessed with a state-ofthe-art

webbrowser

</td>  
<td>

No metadata needed; additional information will be provided on the platform

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

4

</td>  
<td>

Quantitative survey data

</td>  
<td>

https://zenodo.org/

</td>  
<td>

Registered ZENODO

users

</td>  
<td>

Cleaned primary data; can be accessed with SPSS, Excel or open source

</td>  
<td>

Metadata as well as a codebook will be deposited in the data repository Zenodo

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

data analysis

software (such

as

PSPP

etc.)

###  Table 4: Details on accessible data sets

As it is indicated in the table, especially dataset #4 (Quantitative survey
data) can be accessed with commercial statistical programs such as SPSS or
with open source programs such as PSPP. An account at the Zenodo repository
was created by the TAKEDOWN coordinator and a TAKEDOWN community, where the
dataset as well as papers, reports and presentations will be published, was
installed. The consortium will follow the conditions, rules and regulations
from the Zenodo repository – including the settings for accessing the dataset.

#  4\. Allocation of resources and data security

The consortium will use the free-of-charge Zenodo repository for making the
dataset #4 (Primary data from the qualitative survey) accessible.
Additionally, also the reports D2.6 and D3.6, which includes the analysis of
the expert interview, the workshops and the focus groups, will be published
there. This will ensure that the data are safely stored in this certified
repository for long term preservation and curation.

The handling of the Zenodo repository on behalf of TAKEDOWN as well as all
data management issues related to the project fall in the responsibility of
the coordinator.

As for the publications, where the analyses of the empirical research data
will be presented, the consortium will publish them in scientific journals
that allow open access the costs related to open access will be claimed as
part of the Horizon 2020 grant.

#  5\. Ethical aspects

In order to ensure that all ethical aspects are considered and that the
TAKEDOWN project is compliant with all legal requirements and ethical issues,
a general strategy has been designed by the Ethics leader (IDT-UAB). This
strategy involves an ad hoc monitoring process of the project development by
applying the privacy-by-design approach trough a methodological design based
on a “Socio-legal Approach.” This is a risk approach to privacy and data
protection issues in line with the new General Regulation for Data Protection.
The complete strategy is included in Deliverable 2.2.

This general strategy for the monitoring of the ethical and privacy
implications of the TAKEDOWN project consists of the following four steps.

  * **Knowledge acquisition:** This task will include the study of the needs of the empirical research of the project. It will also include the study of all the stakeholders involved in the project and all their potential interactions with the Open Information Hub and the Solutions platform. 

  

  * _**Privacy-impact-assessment (PIA):** _ a PIA (Wright & de Hert 2012) will be conducted to study of all the scenarios in which, during the project lifecycle, personal data rights can be at stake. Special attention will be paid to activities involving data collection from external participants. 

  

  * _**Risk mitigation strategy** _ : Initial, mid-term and final recommendations, prepared by the Ethics leader (IDT-UAB), regarding compliance with the relevant ethical and legal provisions. 

  

  * _**Ongoing Monitoring** _ : In order to ensure that all data collection, storage, protection, retention and destruction during the project are developed in full compliance with EU legislation and relevant national provisions, an Ethics Board has been included in the management structure. 

  

At this stage, a set of initial recommendations have been generated by the
Ethics leader (IDT-UAB) for the three main domains of the project: (i)
empirical research, (ii) Open Information Hub and, (iii) Solutions Platform.

##  Initial Recommendations in relation to the empirical research task within
the TAKEDOWN project

The set of recommendations presented here suggest procedures, measures or
strategies for conducting a proper and responsible empirical research
according to the ethical and legal requirements previously identified. These
recommendations are the results of the potential risks detected through: i)
the EUROPRISE criteria, and ii) the application of the Privacy Impact
Assessment methodology. The structure of these recommendations represents the
different domains of the TAKEDOWN research that are relevant for the ethical
and legal requirements and potential risks detected trough the previously
stated methodologies.  
  
<table>  
<tr>  
<th>

</th>  
<th>

**Data formats and software**

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

**1.R1**

</td>  
<td>

**Online Survey** : Detailed information on open source software tool for
programming the European-wide online survey will be provided (SocialSci,
ScoGosurvey, LimeSurvey or Survey Monkey).

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

**1.R2**

</td>  
<td>

**Expert interviews:** Specific guidance to researchers will be provided about
techniques and procedures to conduct expert interviews. Data formats and
software to manage the information gathered through the interviews will be
specified, specially taking into account the potential variety of research
material that can be generated (interviews transcriptions, audio recordings,
images, ethnographic diaries, written texts).

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

**1.R3**

</th>  
<th>

**Focus groups:** Specific guidelines on procedures and content of the focus
groups will be provided. Clear protocols on how to collect and store
information during the development of the focus groups will be specified.
Formats regarding the data gathered and different software to manage this
information will be provided too.

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

</td>  
<td>

**Processing quantitative data files**

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

**2A.R1**

</td>  
<td>

Questions regarding the recording of data matrix, variable names and labels,
values and labels, recording variables, missing data, and weighting will be
specified in a codebook.

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

</td>  
<td>

**Processing qualitative data files**

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

**2B.R1**

</td>  
<td>

Provide guidance and methods for transcribing interviews

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

**2B.R2**

</td>  
<td>

Provide guidance and specification on procedures to organize files

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

**2B.R3**

</td>  
<td>

Provide guidance and specification on naming data files

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

</td>  
<td>

**Physical data storage**

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

**3.R1**

</td>  
<td>

The Consortium will evaluate a secure storage system in addition to the
repository.

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

**3.R2**

</td>  
<td>

Primary and secondary research data will be stored in a secure and accessible
form.

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

**3.R3**

</td>  
<td>

It is necessary to define who, when and under which conditions data can be
accessed (raw data/analyzed data). Definition of access rights for: folders
and files, particularly when they are stored on a server instead of a single
computer.

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

**3.R4**

</td>  
<td>

Define procedures for backup and recovery of data (frequency and reliability).

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

**3.R5**

</td>  
<td>

Specification of data security measures (physical security, software updates,
virus protection).

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

**3.R6**

</td>  
<td>

Data disposal (erasure of data).

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

**3.R7**

</td>  
<td>

Specification of procedures for keeping data accessible in terms of migration
(conversion of data files from older formats to newer ones) and refreshing
(transfer of data from one storage tool to another).

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

</td>  
<td>

**Anonymisation, confidentiality and personal data**

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

**4.R1**

</td>  
<td>

**Online** **survey** : Ensuring anonymity and confidentiality.

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

**4.R2**

</td>  
<td>

**Interviews** : Anonymity and use of coded data - replacing personal names
with pseudonyms or categories. (example: replace Maria by female subject or
woman)- change or remove sensitive information (example: “I studied in Oxford”
by “I studied in University”).

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

**4.R3**

</td>  
<td>

**Interviews:** Each researcher is responsible for guaranteeing the
confidentiality of the information gathered from the data subject.

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

**4.R4**

</td>  
<td>

**Focus groups and Workshops:** Specific information must be provided to the
participants in relation to the type of information to be collected: video,
audio, transcripts.

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

**4.R5**

</td>  
<td>

**Storage of data collected:** Data collected will be stored by each partner
in local and protected with password or equivalent measures. Each partner will
ensure that only authorized researchers and for the purpose of the TAKEDOWN
research have access to the data. As this data is stored in local, each
partner can be considered liable for the misuse of such data.

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

**4.R6**

</td>  
<td>

**Stakeholder’s database:** Information collected will be restricted to
professional information gathered from open sources. In case a researcher has
private or private obtained information he/she should introduce only the
“available upon request” phrase. Prior to the transmission of this private
obtained information, as a result of a request by other researcher from the
Consortium, consent must be obtained from the data subject.

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

**4.R7**

</td>  
<td>

**Stakeholder’s database:** Professional information gathered from open
sources can be considered covered by the exemption to the obligation to inform
the data subject contained in article 14.5 (b) of the General Regulation.
However, the safeguards referred to in article 89.1, in relation to the data
minimization principle (as defined in article 5.1 (c), will be respected.

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

**4.R7**

</td>  
<td>

**Summary of empirical research:** No personal data or sensitive information
will be included in the summary. In order to ensure this, the summaries will
be sent to the EAB leader for checking before sharing with the rest of the
Consortium.

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

</td>  
<td>

**Informing Research Participants**

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

**5.R1**

</td>  
<td>

The **participation information sheet** provided will include: contact
information, subject and objectives of the research, data collection methods,
voluntary nature of participation, confidentiality, and information about the
potential reuse of data.

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

**5.R2**

</td>  
<td>

The participant information sheet will be specific for each research activity:
online survey, interviews, focus groups and workshops.

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

**5.R3**

</td>  
<td>

The **informed consent form** has to include the information sheet and a
certificate of consent. A model is provided by the Ethics Board.

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

**5.R4**

</td>  
<td>

The informed consent form must specific for each type of data that will be
collected, especially regarding video and audio recording.

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

**5.R5**

</td>  
<td>

Research participants must be informed that they may **withdraw** from the
project at any moment, without having to explain the reasons, and without any
repercussion.

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

**Table 5: Initial informations for the Empirical Research**

##  Initial Recommendations in relation to the Open Information Hub within the
TAKEDOWN project

The set of Recommendations presented here suggest procedures, measures or
strategies to be included in the design of the Open Information Hub. The
structure of these recommendations represents the different domains of the
Open Information Hub that are relevant for the ethical and legal requirements
and potential risks detected trough the previously stated methodologies.  
  
<table>  
<tr>  
<th>

**Scope of information collected and purposes of collection**

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

** 1  .R1 ** Data subjects will be informed according to articles 12 to 14 of
the General Data Protection Regulation.

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

**Notice and rights of the individual**

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

**2.R1**

</td>  
<td>

When the information is obtained from the data subject the Open Information
Hub will provide information according to article 13 and gather the subject
consent.

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

**2.R2**

</td>  
<td>

Regarding personal data in the Open Information Hub, only data obtained from
the data subject will be processed.

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

**2.R3**

</td>  
<td>

In case that the Open Information Hub provides the users with the possibility
to include data, a disclaimer should be included stating that the user
acknowledges that the inclusion of personal data from other subjects is not
allowed.  1  
</td> </tr>  
<tr>  
<td>

**2.R4**

</td>  
<td>

Any natural person whose data is available in the Open Information Hub will
have the right to access, modify and erase such data.

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

**Uses of the Open Information Hub and information collected**

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

**3.R1**

</td>  
<td>

More information is needed related to the digital reporting functionality.

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

**3.R2**

</td>  
<td>

In case the information is used for the reporting of malicious/suspicious
activities the exceptions concerning the use of personal data by competent
authorities for the purposes of the prevention, investigation, detection or
prosecution of criminal offences or the execution of criminal penalties will
be taken into account.  2  
</td> </tr>  
<tr>  
<td>

**3.R3**

</td>  
<td>

In case that the digital reporting tool allows for personal data to be
uploaded only relevant competent authorities, according to national
legislation, will have access to this data.

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

**3.R4**

</td>  
<td>

Access roles and permissions will be defined in the first steps of the
designing and development process.

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

</td>  
<td>

**Retention**

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

**4.R1**

</td>  
<td>

The Consortium will take into account that for the purposes of the TAKEDOWN
project the retention period is the one used in the relevant field, by analogy
to the administrative and financial issues this should be 5 years. (Grant
agreement article 18)

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

**4.R2**

</td>  
<td>

The Consortium will take into account that in case of a future exploitation of
the Open Information Hub, different retention periods may apply, depending on
the national legislations.

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

</td>  
<td>

**Technical aspects and security**

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

**5.R1**

</td>  
<td>

When defining roles and permissions special attention will be paid to the
possibility to track any interaction with the platform that entails access,
modification and deletion of personal data.

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

**Table 6: Initial Recommendations for the Open Information Hub**

##  Initial Recommendations in relation to the Solutions Platform within the
TAKEDOWN project

The set of recommendations presented here suggest procedures, measures or
strategies to be included in the design of the Solutions Platform. The
structure of these recommendations represents the different domains of the
Solution Platform that are relevant for the ethical and legal requirements and
potential risks detected trough the previously stated methodologies.  
  
<table>  
<tr>  
<th>

**Scope of information collected and purposes of collection**

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

** 1  .R1 ** Data subjects will be informed according to articles 12 to 14 of
the General Data Protection Regulation.

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

**Notice and rights of the individual**

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

**2.R1**

</td>  
<td>

During the registration process, in case personal data is collected, the
Solutions platform will provide the information listed in articles 13 and 14
of the General data protection regulation and collect the consent of the data
subjects.

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

**2.R2**

</td>  
<td>

Regarding personal data in the Solutions Platform, only data obtained from the
data subject will be processed.

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

**2.R3**

</td>  
<td>

In case that the Solutions Platform provides the users with the possibility to
include data from other subjects, a disclaimer will be included stating that
the user acknowledges that the inclusion is only allowed with the consent of
that subject.  3

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

**2.R4**

</td>  
<td>

Any natural person whose data is available in the Open Information Hub must
have the right to access, modify and erase such data.

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

</td>  
<td>

**Retention**

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

**3.R1**

</td>  
<td>

The Consortium will take into account that for the purposes of the TAKEDOWN
project the retention period is the one used in the relevant field, by analogy
to the administrative and financial issues this will be 5 years. (Grant
agreement article 18)

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

**3.R2**

</td>  
<td>

The Consortium will take into account that in case of a future exploitation of
the Solution platform, different retention periods may apply, depending on the
national legislations.

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

</td>  
<td>

**Technical aspects and security**

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

**4.R1**

</td>  
<td>

More information will be provided concerning the auditing mechanisms foreseen
for the platform.

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

###  Table 7: Initial Recommendations for the Solutions Platform

Related with the generation of primary empirical data, it needs to be
highlighted that, at this stage of the project, and realizing the importance
of the empirical research being conducted, a specific and comprehensive set of
guidelines have been provided to all partners in the Consortium by the Ethics
leader (IDT-UAB): the _Ethical Guidelines for the processing of data in the
context of the Empirical research for the TAKEDOWN project_ (see Annex). This
document aims at offering specific guidance to all the partners of the
Consortium for the performance of the different tasks and activities foreseen
in WP3, concerning empirical research. In order to ensure that all partners
are compliant with the requirements related to Research Ethics and
particularly, Informed consent procedures, the Guidelines include:

  * a general introduction containing an explanation on the concept and meaning of Informed consent, in the context of research ethics and empirical research. 

  

  * a set of guidelines for quantitative research (online survey) 

  

  * a set of guidelines for qualitative research (interviews, focus groups, workshops) 

  

  * legal notice to be included in the online survey 

  

  * written informed consent form 

  

  * oral consent script 

  

#  6\. Outlook towards next DMP

The next DMP will be prepared in for month 18, which is after the finalization
of WP3 (Empirical research). As it was emphasized in the introduction, the DMP
is a living document and several questions can only be answered at a later
stage of the project. Hence, the upcoming DMP will provide updates on the
issues raised above and more information on the following questions:  
  
<table>  
<tr>  
<th>

**Category**

</th>  
<th>

**Underlying questions**

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

Making data interoperable

</td>  
<td>

  * Are the data produced in the project interoperable, that is 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)? 

  

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

  

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

  

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

Increase data re-use (through clarifying licences)

</td>  
<td>

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

  

  * When will the data be made available for re-use? If an embargo is sought to give time to publish or seek patents, specify why and how long this will apply, bearing in mind that research data should be made available as soon as possible. 

  

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

  

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

  

  * Are data quality assurance processes described? 

  

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

Allocation of resources

</td>  
<td>

  * Are the resources for long term preservation discussed (costs and potential value, who decides and how what data will be kept and for how long)? 

  

  * Do you make use of other national/ funder/ sectorial/ departmental procedures for data management? If yes, which ones? 

  

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

Data security

</td>  
<td>

\- What provisions are in place for data security (including data recovery as
well as secure storage and transfer of sensitive data)?

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

Other aspects

</td>  
<td>

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

  

  * If yes, which ones? 

  

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

**Table 8: Issues to be addressed in the next DMPs**