#  FAIR data 2. 1. Making data findable, including provisions for metadata

FABLABIA participates in Open Research Data Pilot, which requires the policy
of FAIR data (findable, accessible, interoperable and re-usable research data)
Data collected and created during the project implementation are for internal
usage only. It is not research data, it is only data from survey to get the
information from FabLabs and innovation agencies users/clients. No metadata
included. Data will be use only for the project purposes (mainly for Design
option paper) and collected data itself are no valuable for other users from
outside.

Within the internal system of the coordinator and project partner the data
will be findable according the internal standards and regulations. For the
purposes of the project results the data will be anonymized.

##  Making data openly accessible

Fablabia will not be openly accessible. Data will be used for analysis to
recognize the recommendation and best practise that will be the part of the
project result (Design option paper). As the estimated interest to the survey
data outside FabLab community is very limited, these data will be available
for use outside FABLABIA consortium only upon request made to FABLABIA
coordinator.

##  Making data interoperable

Collected data are interoperable only for internal purposes, the vocabulary
used is standard in basic level. No research data are collected. The data will
be stored in a format readable by commonly used data management tools or
office software. The data sets are small and specified, so direct automatic
interoperability of the data with other external data sets is not sought for.

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

Data are planned to be used only for the purposes of this project and its
results. Data might be used internally by project partners for their further
development related to the project objectives and aims. No licences are needed
for re-use of the data, as long as the data source is acknowledged.

#  Allocation of resources

The amount of data produced by FABLABIA is rather small, and therefore there
are no resources specifically allocated for making the data FAIR. The
resources for data collection are allocated in the work packages and tasks
collecting the data. Responsible person for data management is Tomas Mejzlik
(project coordinator) and Eliska Matejova (administrative project manager),
both form JIC – project coordinator. No additional resources are predicted.

#  Data security

Data are saved in an internal storage of the project coordinator (with the
ability to set access restrictions). The storage is accessible only to the
coordinator's employees and access to the data collected during the project
implementation can only be granted to selected employees. The storage is
backed up so that the data can be recovery if necessary.

In case of data breaches, the person responsible for the breached data shall
notify coordinator of FABLABIA project as soon as possible, but at maximum
during 72 hours. The individuals whose personal data were breached shall also
be notified without undue delay. It is worth noting, that due to the nature of
personal data collected during FABLABIA project the damage that can be caused
by a data breach is expected to be limited.

##  Right to erasure

If a person wishes his/her personal data to be erased, that can and shall be
done. It is easy to do from the contact lists controlled by FABLABIA
coordinator or WP leaders conducting surveys. If a person wants his/her
personal data to be removed from a survey, the non-personal data shall remain
in the analysis of the survey.

##  Privacy by design and by default

Personal data collected during FABLABIA will be used only by project partners,
including beneficiaries and only for purposes needed for the implementation of
FABLABIA. Even within the project, if someone of the project consortium asks
for personal data, the person holding the data should consider whether that
data is needed for the implementation of the project. If personal data is
provided, the data shall not be distributed further within or outside the
project.

2

#  Ethical aspects

Collected data will be processed and store according the applicable
legislation and the deliverable D.1.1 – Data protection policy and compliance
with GDPR.

#  Other issues

No other special procedures for data management are used.

.

3

**SUMMARY TABLE 1**

**FAIR Data Management at a glance: issues to cover in your Horizon 2020 DMP**

This table provides a summary of the Data Management Plan (DMP) issues to be
addressed, as outlined above.  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

</th>  
<th>

**Issues to be addressed**

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

**1\. Data summary**

</td>  
<td>



</td>  
<td>

**The purpose of the data collection/generation:** Survey, benchmarking

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

</td>  
<td>



</td>  
<td>

**Relation to the objectives of the project:** Mapping good practices and
success stories of FabLab supporting SMEs around Europe and worldwide, Various
business models of FabLab will be developed

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

</td>  
<td>



</td>  
<td>

**Types and formats of data generated/collected:** Documents, project
deliverables, contracts, raw and processed data collected through surveys,
others

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

</td>  
<td>



</td>  
<td>

**The origin of the data:** On-line survey and semi-structured interview, data
from project partners

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

</td>  
<td>



</td>  
<td>

**Data utility (to whom will it be useful):** Project partners, FabLabs and
innovation agencies

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

  2. **FAIR Data**

  

  

2.1. Making data findable, including provisions for metadata

</td>  
<td>







</td>  
<td>

Data collected and created during the project implementation are **for
internal usage only.**

**No metadata included.**

Data will be findable according to the internal standards and regulations.

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

</td>  
<td>



</td>  
<td>

Data will be anonymized.

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

4  
  
<table>  
<tr>  
<th>

2.2 Making data openly accessible

</th>  
<th>



</th>  
<th>

**No openly accessible data.**

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

</td>  
<td>



</td>  
<td>

Data will be used for the project results (Design option paper).

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

2.3. Making data interoperable

</td>  
<td>



</td>  
<td>

Only for internal purposes.

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

</td>  
<td>



</td>  
<td>

The vocabulary is standard in basic level.

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

</td>  
<td>



</td>  
<td>

Data will be stored by commonly used data management tools or office software.

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

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

</td>  
<td>



</td>  
<td>

Data are planned to be used only for the purposes of this project and its
results.

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

**3\. Allocation of resources**

</td>  
<td>



</td>  
<td>

No additional resources are allocated.

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

</td>  
<td>



</td>  
<td>

Responsible persons are Tomas Mejzlik, Eliska Matejova (both from JIC –
project coordinator), as part of their workload for the project

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

**4\. Data security**

</td>  
<td>



</td>  
<td>

Data are saved in an internal storage of the project coordinator (with the
ability to set access restrictions).

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

</td>  
<td>



</td>  
<td>

The storage is regularly backed up.

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

**5\. Ethical aspects**

</td>  
<td>



</td>  
<td>

Applicable legislation

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

</td>  
<td>



</td>  
<td>

Deliverable D.1.1 Data protection policy and compliance with GDPR

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

**6\. Other**

</td>  
<td>



</td>  
<td>

No other special procedures for data management are used.

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

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

**HISTORY OF CHANGES**

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

**Version**

</td>  
<td>

**Publication date**

</td>  
<td>

</td>  
<td>

</td>  
<td>

**Change**

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

1.0

</td>  
<td>

30.9.2019

</td>  
<td>

▪

</td>  
<td>

Initial version

</td>  
<td>

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

5