**1\. IMPAQT DATA PROCEDURES**

This deliverable report the Data Management Plan (DMP) that define the main
elements of the IMPAQT data management policy for the data collected or
generated. Details how the data will be treated during the IMPAQT project
regarding all the procedure for managing the IMPAQT data collection, analysing
& processing, preservation and sharing.

###  1.1. Data Purpose

The main purpose for data gathered intends to meet the objectives of the
IMPAQT project in order to develop and validate in-situ a multi-purpose
(inland, coastal and offshore productions), multi-sensing (heterogeneous
sensors and new/emerging technologies) and multi-functional (advanced
monitoring, modelling, data analytics and decision making) management platform
for sustainable IMTA production. The specific objectives of IMPAQT project
are:

  * Design and implement new/emerging efficient and cost-effective technologies to monitor and manage systems for IMTA production; 

  

  * Validate IMPAQT systems and IMTA model in-situ and the fish/seafood product in a laboratory; 

  

  * Demonstrate an optimal sustainable IMTA development from a holistic perspective based on ecosystem services and circular economy principles; 

  

  * Promote an effective transfer of knowledge consequent by IMPAQT activities to the EU aquaculture stakeholders. 

  

The IMPAQT project will generate and collect several kinds of data mostly
originated from environmental data to be observed such as:

  * Measurement data from diverse sources deployed in IMPAQT pilots; 

  

  * Full visualization of fish/shellfish and associated quality parameters at any given time; 

  

  * Water quality data needed for model development; 

  

  * Environmental, socioeconomic and cost-effectiveness analysis data (both qualitative and quantitative). 

  

###  1.2. Data Principles

Participants of the IMPAQT consortium must follow this DMP when describing the
types of data that will be produced or collected, how the data will be
exploited and shared, the standards that will be applied, how the data will be
preserved allowing their security and how will it be provided all the
information, procedures, tools and instruments required for access,
extraction, exploitation and reproduction IMPAQT data. The data management is
in accordance with European Commission (EC) guidelines  1  and also with the
following data principles:

  * Open Access; 

  

  * FAIR Data; 

  

  * IPR Management; 

  

  * Compliance with non-EU Partners. 

  

###  Open Access

The Open Access movement began in the 1990s when access to the internet became
available. Open Access means that scientific information must be publicly
available and free of charge so that everyone can read, download, copy,
distribute, print, search and consult without facing any financial, legal or
technical barriers. Making search results accessible to everyone provides
faster progress in innovation, improves the quality of results, inspires
partnerships involving and enhances society and the public and private
sectors.

This movement gained even more notoriety in a meeting in October 2003 that
brought together several international experts that aspired to develop a web-
based search environment using the Open Access paradigm. From this meeting
results the Berlin Declaration on Open Access to Knowledge in the Sciences and
Humanities  2  which is also based on the Budapest Open Access Initiative  3
and the subsequent annual conferences have increasingly sensitized other
entities to the accessibility of scientific information. This Declaration has
been signed by nearly 300 research institutions, libraries, archives, museums,
funding agencies, and governments from around the world.

In the research & development context, Open Access to Scientific Information
4  refers to two main categories:

####   Scientific Publications  Research Data

The following Figure 1 presents the context of dissemination and exploitation
of Open Access Policy to scientific publications and to research data.

Figure 1 - Open access to scientific publication and research data

_Scientific Publications_

Scientific Publication means to peer-reviewed scientific research articles
that are firstly published in academic journals. Open Access to scientific
publications means free access for everyone including the rights to read, make
download, print and also right to copy, distribute, search, link, trace and
extract. Open Access does not imply an obligation to publish results since
this decision is entirely the responsibility of the partners and does not also
affect the decision to commercially exploit the results. Open access can only
become a problem if the publication is chosen as the means of dissemination.
The decision to publish (or not) through open access should only come after a
more general decision on whether to publish directly or to first seek IP
protection.

According with the Grant Agreement (GA) each IMPAQT partner must ensure Open
Access to scientific publications regarding the results and need to make all
the efforts to ensure right to copy, distribute, search and link thought
involving two steps:

  * Deposit Publications 

  

  * Provide Open Access 

  

_Deposit Publications_

A digital copy of the accepted document for publication needs to be deposit in
a repository of a scientific publication that must be in an accessible,
standardized or publicly accessible text file format. The publication must be
deposited before the publication deadline and can be deposited before (for
example, at the moment that the article is accepted by the journal).

When deposit publications, the research data that is required to authenticate
the results presented in publication (underlying data) must also be deposited
in a data repository.

The chosen repository should be an online archive, preferably an institutional
and centralized repository, that do not claim rights over the deposited
publications or block their access. The OpenAIRE  5  (Open Access
Infrastructure for Research in Europe) is a suggested entry point to choose
and select a repository.

_Provide Open Access_

Once the publication has been deposited, free access through the repository
must be guaranteed and one of two main methods for the Open Access to
Publications must be provided:

  * **“Green” Open Access** – May deposit immediately the publication in a chosen repository, since that guarantees their Open Access during the embargo period as established in the Open Access Publishing Agreement  6  (usually between 6 and 12 months depending on the type of publication). 

  

  * **“Gold” Open Access** \- Can publish in open access journals, that sell signatures and offer the option of making individual articles openly accessible. These articles are eligible for reimbursement during the IMPAQT project and once the project is completed, they cannot be reimbursed by the IMPAQT project budget. 

  

_Research Data_

Research data refers to data from underlying publications (underlying data)
and/or other data collected such as statistics, experiment results,
measurements, observations, and others. Open Access to Research Data is the
right to access and re-use data under the conditions established in the GA.

The access and re-use of research data generated in H2020 projects such IMPAQT
is facilitated through the flexible Open Research Data (ORD) Pilot  7  . The
ORD Pilot aims to make the research data available with few restrictions as
possible and also to protect sensitive data from possible inappropriate
accesses. Research data need to be monitored with the objective to develop the
policy regarding open science.

However not all research data need to be open under the ORD Pilot and during
the project lifetime, different accesses policy’s (public, restricted, closed,
private) to the data can be chosen, where it needs to involve two steps:

  * **Deposit Research Data** \- Project research data (and underlying data) should be deposited whenever possible into an online data repository. It is advisable that the repository allows to deposit both publications and underlying data with tools to "link" them (such persistent identifiers and citations of data). OpenAIRE also provides supplementary information and support for linking publications with underlying research data. 

  

  * **Provide Access** –All the effort and procedures must be taken to enable third parties to access, exploit, reproduce and disseminate (for free) the data. To do so, it is necessary to attach licenses to the deposited research data. 

  

The requirements for open access do not imply an obligation to publish all the
project results because this decision is entirely the responsibility of IMPAQT
partners. In addition, open access also does not affect the decision to
commercially exploit the results.

IMPAQT consortium believes in the concepts of Open Research and development
and the benefits that can draw by allowing the re-use of research data. For
that, the data produced in IMPAQT will be published whenever possible under
Open Access procedures.

###  Explanatory note

The consortium is working on a list of all IMPAQT datasets, with detailed
information regarding its confidentiality, storage and availability
mechanisms. Each identified public IMPAQT dataset will have details on how it
can be accessed, and the restricted ones will have a clear explanation on why
they were considered restricted. This list is currently being updated and will
be made available online in 2 different versions: 1) IMPAQT Public datasets,
which will be publicly available online, and 2) IMPAQT All datasets, which
will be a confidential list, with all IMPAQT datasets, including public and
restricted ones. This 2  nd  list will only be available to the consortium
partners and EC services.

The consortium has been working on a 1  st  version of the IMPAQT deployments,
so information is currently being collected. The plan is that both versions of
the IMPAQT Datasets list are made available online during April 2020.

###  FAIR Data

IMPAQT consortium is conscious of the directives for Open Access of
Publications and Research Data in the H2020 projects and in the participation
on Open Research Data Pilot. Making research data findable, accessible,
interoperable and re-usable (FAIR  8  ) is an integral part of the process of
open science and research.

Making research data FAIR enable both scientific research and society to
leverage the benefits of such data and also make a significant contribution to
economic growth. The FAIR principles, presented in Figure 2, are particularly
helpful since allow:

  * support to knowledge discovery and innovation; 

  

  * data and knowledge integration support; 

  

  * allow sharing and data re-use; 

  

  * support data and metadata to be machine-readable; 

  

  * allow data discoveries through the harvest and analysis of multiple datasets. 

  

Figure 2 - FAIR Data principles  9

When managing research data, these principles should be heeded to ensure that
the IMPAQT research data will be shared in a way that enables and enhances re-
use, by humans and machines. Annex 1 provide a set of questions that should be
considered in order to make IMPAQT research data FAIR.

_Findable_

IMPAQT research data must be easily discovered and locatable in order to be
used and re-used. Both IMPAQT data and metadata should be easy to find for
humans and computers. The use of machine-readable metadata is essential for
datasets to be discovered automatically. To be findable:

  * IMPAQT research data and metadata must be given a unique, persistent, global identifier; 

  

  * IMPAQT research data should be described with well-founded metadata; 

  

  * IMPAQT research data and metadata must be registered/indexed in a searchable resource (repository); 

  

  * Metadata must specify the identifier for the IMPAQT research data. 

  

_Accessible_

Must be provided all the necessary information to access the IMPAQT research
data and, if existing, all authentication/authorization methods must also be
provided. Data do not need to be necessarily open if there are good reasons
such as privacy concerns or commercial interests and there must be
transparency in the conditions of access and reuse. To be accessible:

  * IMPAQT research data and metadata need to be recoverable through their identifier using a standardized communication protocol that needs to be open and free allowing, if required, authentication and authorization procedures; 

  

  * Metadata must be accessible, even when IMPAQT data is no longer available. 

  

_Interoperable_

Interoperability allows the exchange of data between several entities such as
researchers, institutions and organizations. To be interoperable, IMPAQT
research data and metadata need to use community agreed formats and should be
also interoperable with applications or workflows for analysis, storage, and
processing. In order to be interoperable:

  * IMPAQT research data and metadata must use a formal, accessible, shared, and widely applicable language for knowledge representation; 

  

  * IMPAQT research and metadata should have vocabularies that follow the FAIR principles; 

  

  * IMPAQT research data and metadata should include qualified references to other research data or metadata. 

  

_Re-usable_

Optimize data re-use is the basic purpose of the FAIR data principles. IMPAQT
research data should maintain its initial richness and must be clearly
described. In order to be reusable:

  * IMPAQT data and metadata must have a plurality of precise and relevant attributes; 

  

  * IMPAQT data and metadata must be released with a clear and accessible data usage license; 

  

  * IMPAQT data and metadata need to be associated with their origin; 

  

  * IMPAQT data and metadata must be aligned with the community standards and relevant to their domain. 

  

###  IPR Management

In a project like IMPAQT, it is fundamental to carry out property rights of
the data used and generated during the project. Since IMPAQT consortium will
produce research data, publications and underlying-data, all the Intellectual
Property Rights (IPR) must be safeguarded using explicit licenses to make them
openly accessible  10  :

  * **Publications** – The copyrights must be safeguarded and appropriate licenses to publications should be granted. Creative Commons  11  licenses are recommended since offer useful licensing solutions in order to provide Open Access to third parties; 

  

  * **Research data** \- To make research data more openly accessible  12  , explicit licenses such as Creative Commons Attribution 4.0 (CC BY) or Creative Commons CCZero (CC0) should be attached to the deposited research data in the repository. In order to help the selection of the license for the research data, it is recommended to be used the EUDAT B2SHARE tool  13  that includes an integrated license wizard to facilitates the selection. 

  

Must be taken all necessary steps to prevent both publications and research
data from being leaked or hacked in order to not damage the IMPAQT project
plan as well as the opportunities and individual IMPAQT partner plan.

###  Compliance with non-EU Partners

Since there are two non-EU countries involved in IMPAQT project (China and
Turkey), all the IMPAQT consortium need to make sure that meet all the ethical
requirements and that EU and national standards for research data obtain the
approval of the local/national data protection  14  authority.

The EU standard to the transfer of data needs to follow the rules of the
General Data Protection Regulation (GDPR). In the People's Republic of China
these rules are included on the Cybersecurity Law of China (CLS) and in Turkey
in their Data Protection Law (DPL).

IMPAQT consortium must pay attention to some guidelines when transferring data
between countries:

  * All the EU partners need to follow the GDPR guidelines; 

  

  * GDPR makes clear that non-EU partners must follow and comply with GDPR; 

  

  * CLS required that to transfer data generated in China to a foreign party, need to be stored within China territory and is firstly necessary to conduct a security assessment covered by a separate regulation; 

  

  * DPL allow transfer of data generated in Turkey to a foreign party, it has provided explicit consent or if the destination country has an adequate level of protection where both sides make a writing statement to provide data protection. 

  

If there is an additional need to transfer data, can be established an
agreement through the EC standard contractual clauses  15  for data transfers
between EU and non-EU countries. In the case of multinational companies, if
necessary, can be also established binding corporate rules  16  .

####  1.3. Data Lifecycle

IMPAQT DMP covers all the data lifecycle steps of the research data generated
or collected in the project and is an important aspect to provide the project
sustainability and also produced opportunities for new emerging applications
and services. The IMPAQT research data can be preserved in different ways and
may also have different data access or use policies.

In a typical project data lifecycle there are some key steps that must to be
considered and the following Figure 3 provides an overview of the IMPAQT Data
Lifecycle that will be applied for each research data.

Figure 3 - IMPAQT Data Lifecycle

  * **Data Collection** – The first step is data collection/creation. Data needs to be collected from his origin and kept in a workspace (it is always recommended to make backup); 

  

  * **Data Processing** – At this stage, the data must be identified, analysed and processed as well as ensure their quality. It is also advisable to always make a copy of the raw data before start working with them. The analysis of the research data may also require the collection of new data for the same or for other project purposes; 

  

  * **Data Storage** – The data need to be organized by specifying and choosing the file formats, their access policy, their metadata and also must be deposited in an online (and also local) repository. When the data is on a repository all the efforts need to be made to allow their long-term preservation; 

  

  * **Data Share** – After depositing the data in an online repository, they are available to be accessed and discovered by third parties, and then can be used for other purposes (re-use). 

  

The following section provides the IMPAQT Data Management Plan with detailed
guidelines that must be applied in each stage of the IMPAQT data lifecycle.

**2\. DATA MANAGEMENT PLAN**

###  2.1. Data Collection

When collecting/creating IMPAQT research data, it is recommended to follow
good practices since they may come from different origins and can have many
forms. The most common are text, numeric, audio, code, pictures and videos. It
is recommended to keep the collected data in a workspace and to make backups.

###  Data Type

The research data can be classified as qualitative data, when refers to text,
pictures, video, observations, or quantitative data, when refers to numerical
data. Also, data can be categorized as:

  * **Observed Data** – Unique data that is collected in real time and cannot be reproduced (such input data from sensors); 

  

  * **Experimental Data** – Data derived from laboratory equipment that is subject to controlled conditions (such as gene sequences); 

  

  * **Simulated Data** – Data generated from the simulations of test models that study real or theoretical systems (such climate modes); 

  

  * **Derived Data** – Data that is a result of the analysis of data or aggregates from various sources. 

  

###  Origin of Data

In the scope of IMPAQT, the research data will originate mostly from
measurement data of diverse sources deployed in pilots, from monitoring of
fish and associated quality parameters, from environmental, socioeconomic and
cost-effectiveness analysis data, among others.

During the evolution of the IMPAQT project, the nature of the data may change,
and it is also necessary to specify in the data collection the origin of the
data.

**2.2.** **Data Processing**

###  Choose File Format

Once collected/generated and identified, IMPAQT research data should be
analysed and processed. During processing and analysis, may be require the
collection of new data for the same or for other project purposes.

IMPAQT research data must be recorded using digital and user-friendly format.
The choice of an accessible format allows their preservation, access and share
with third parties.

It is recommended to make backup of the raw data in the original format
without being changed or edited and to use open standards formats. In case
IMPAQT research data comes from sources with restrict and own formats, all the
efforts should be made to convert the data to a common standard, preferably an
open access format. In this case must be provided documentation of the
necessary resources such as tools, instruments or software used to access,
visualize and work with the data.

When choosing a file format, it needs to be non-proprietary, have no
encryption, are uncompressed, use an open and documented format that is used
by the community, has common character encodings (e.g., ASCII, UTF-8) and be
adapted for the data type.

Some of the most used formats, according to the European Data Portal  17  ,
are CSV, TXT, HTML, JSON, PDF, XLS and XML. The following Table 1 provides a
set of recommended digital formats to be used based in the respective data
type.

Table 1 - Recommended Digital Formats  
  
<table>  
<tr>  
<th>

**Type**

</th>  
<th>

**Recommended Formats**

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

**Audio**

</td>  
<td>

WAV, AIFF, MP3, MP4, FLAC

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

**Video**

</td>  
<td>

MOV, MPEG-4, AVI, MP4

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

**Pictures**

</td>  
<td>

TIFF, JPEG, JPG, PNG, BMP

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

**Text/Documentation**

</td>  
<td>

DOC, TXT, PDF

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

**Scripts/Code**

</td>  
<td>

XML, HTML, JSON

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

**Database**

</td>  
<td>

XLS, CSV, XML

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

###  File identification

It is important from the beginning of IMPAQT project to provide a correct
identification of files where must be used the same structure in both the
active data and the backup data.

Regarding IMPAQT document files (such deliverables) the identification should
follow the guidelines presented in D7.1 Project Quality Plan.

For the identification of IMPAQT research data files it is recommended to use
a descriptive name since its name will reflect the contents of the file and
not use an exaggerated number of characters or special characters, and spaces.
Use only numbers, letters and underscores and if is necessary to use the date
to specify them in a standard format (e.g. “DDMMYYYY”) and for ease
understanding. The attributes to include in the file naming convention for
IMPAQT research data are presented in the following example:

_**“IMPAQT_ LCA_Inventory_Data_v0.1.xls”** _

  1. A prefix to specify that is an IMPAQT data (e.g. “IMPAQT”); 

  

  2. An intuitive title to the data (e.g. “Dataset Example”); 

  

  3. For each new version of the data, specify the respective number (e.g. “v0.1”); 

  

  4. The file respective format (e.g.”xls”). 

  

  

###  Provide metadata

Metadata is data that provides information describing other data and the
context in which they were established. Should be sufficient to enable the
data to be discovered, understood, re-used and enable organization and data
sharing/preservation facilitating the use of the data by others and the
combination of information from different origins allowing transparency.

There are many different schemas of metadata that use a Standard Generalized
Markup Language (SGML) or Extensible Markup Language (XML). Metadata schemes
may be developed and maintained by standard organizations that have standards
and schemas designed specifically for their types of data. There are several
services that list metadata standards by subject areas such as the Digital
Curation Centre  18  (DCC) and the Research Data Alliance (RDA)  19  . Dublin
Core metadata standard is a good candidate that cover the basics attributes,
can be used for any type of data and provide an online tool  20  to generate a
fully-formed Dublin Core metadata code.

All metadata needed to identify IMPAQT data must be provided. Regarding
publications, it should be ensured that EU funding is recognized. Information
on EU funding should be included to monitor the H2020 program, the statistics
produced, and the impact of the program evaluated. The publication date and
embargo period must be provided as well as assigned a permanent and unique
identifier, a Digital Object Identifier (DOI), action name, acronym, and Grant
Number.

Regarding research data the following Table 2 provides a set of metadata
attributes that need to be provided to each IMPAQT research data.

Table 2 - IMPAQT research data metadata  
  
<table>  
<tr>  
<th>

**Metadata**

</th>  
<th>

**Description**

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

**Research Data**

**Name**

</td>  
<td>

Title of the IMPAQT research data. Should be a name easily for search

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

**Category Type**

</td>  
<td>

Need to be provided the IMPAQT research data category

(e.g. Production Data)

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

**Responsible Partner**

</td>  
<td>

The IMPAQT partner that is responsible for his creation/generation

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

**Description & **

**Purpose**

</td>  
<td>

Should be provided a description, including the procedures followed to obtain
those results and also his purpose and what will be their benefits

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

**Format**

</td>  
<td>

Specify the respective format (e.g. CSV, XLS, DOC…)

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

**Expected Size**

</td>  
<td>

What is/will be the IMPAQT research data approximated size (e.g. <100 MB, 3GB)

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

**Origin**

</td>  
<td>

How and where the IMPAQT research data was generated

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

**Repository**

</td>  
<td>

The repository where will be submitted

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

**DOI**

</td>  
<td>

Can be specified once the IMPAQT research data has been deposited in the
repository

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

**Version**

</td>  
<td>

Specify his version number to keep track all their changes

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

**Keywords**

</td>  
<td>

Provide keywords to be associated (e.g. IMPAQT)

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

**Access**

</td>  
<td>

Specify the rights to access the IMPAQT research data

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

####  2.3. Data Storage

Making IMPAQT research data easily findable and identifiable is fundamental.
For that is required active backups and deposit the research data and in a
data repository. It is advisable to make frequent backups and kept source data
(raw data) separate from the ongoing work or final data.

Attention must be taken to its protection (confidential or restricted data),
ease of access and collaboration (internal or external). Choosing a data
repository ensure maximum visibility, serves as backups in case of failures
and guarantee the data availability after the end of the IMPAQT project.

To preserve the data can be used a repository already established for your
research domain but use an external and on-line repository is also required.
Searching for a data repository can be done using the Registry Of Research
Data Repositories Portal  21  that in addition to specific searches, permit to
search repositories by filtering access categories, data usage licenses,
trusted data repositories and whether a repository provides the data with a
persistent identifier.

Some aspects to be considered when choosing a repository are:

  * A repository that is trustworthy and keeps the IMPAQT research data available in long-term; 

  

  * Provides all the means to match the IMPAQT project requirements (e.g. formats; access, back-up and recovery); 

  

  * Allows a unique identifier to be assigned to IMPAQT research data to ensure that different search results are linked to specific searchers and grants; 

  

  * Provides a landing page for each IMPAQT research data, with metadata that enables their search visible and stimulating their data re-use; 

  

  * Offers clear terms and conditions (e.g. for data protection) and allows for re-use;  Offers statistics that allow tracking how the IMPAQT research data was used. 

  

Data stored in the repository must have the highest quality and provide
documentation to be accessed. The data need to be updated to ensure that the
latest version is available. All methods to provide security measures and
backup policies to ensure the maintenance of IMPAQT research data must be
taken.

It is advisable to use in IMPAQT the Zenodo  22  that is a cost-free
repository developed by CERN  23  through OpenAIRE  24  project that allows
the deposit of both publications and research data and facilitates link
publications and underlying data through persistent identifiers and data
citations.

Zenodo also follows the minimum metadata standards, stored them internally in
JSONformat, according to a defined JSON schema and can be exported in several
standard formats such as MARCXML, Dublin Core, and DataCite Metadata Schema.
Also provide a technical infrastructure that allows data security and long-
term preservation. The data files can be deposited in closed access, open or
restricted. Data files deposited under close access are protected from
unauthorized access at all levels. Data files deposited as restricted may be
shared with others if certain requirements are confirmed. These files will not
be made publicly available and the share will only be possible with the
approval.

The IMPAQT research data need to be stored during the period of the project
and must be preserved for at least 5 years after the end of the IMPAQT
project. Any unexpected costs related to open access to research data are
authorized for compensation during the duration of the project under the
conditions defined in the GA.

####  2.4. Data Share

According to the IMPAQT GA, research data should be owned by who generated
them, and IMPAQT consortium intends to provide early as possible publicly
available, easily discovered and re-used unless there is legitimate interest
to protect them. This approach aims to maximize the IMPAQT visibility, the
exploration of its results, the long-term impact and allow that other
researchers make use of them to validate the IMPAQT results, as a starting
point for their investigations.

Interoperability and data re-use must be provided following the FAIR
principles. The research data should be shared in an easy and transparent way
to ensure that can be understood and accessed by other researchers,
institutions, and organizations, along with all the metadata and documentation
available.

Since a huge amount of research data is generated in a project such as IMPAQT,
must be selected which research data can be shared and as well as specified
their access type (public, restricted, private, other).

Several publications will be carried out during the IMPAQT project and should
be explored “Gold” and “Green” Open Access practices. Highly impacting and
cited publications need to be provided through "Gold" Open Access to ensure
maximum visibility and immediate availability. The research data required to
validate the results of scientific publications (underlying data) should be
deposited in the chosen repository at the same time and as soon as possible,
unless a decision has been made to protect them.

If it is necessary to assign restricted access to the data, all the efforts
must be made to make data available to other researchers under controlled
conditions, and all methods and software tools to access the data must be also
provided.

To increase data re-use, is required to make all the efforts to use standards
and formats that are compatible with common (and preferably free) software
applications. The IMPAQT research data need to be available through the
repository and need to be accessible for reuse without limitations during and
after the end of the IMPAQT project.

**3\. IMPAQT DATASET**

IMPAQT will generate several research data during the project life cycle that
are represented as datasets. These datasets can be conserved in different
ways, where can be imposed some data access or use policies as mentioned in
the previous sections. They can also be analysed through a wide range of
perspectives for the project development as well as for other scientific
purposes.

The following subsections identifies the available IMPAQT datasets at M6 of
the project where for each one was collected relevant information regarding
the topics of the IMPAQT Dataset Template presented in “ANNEX B: IMPAQT
Dataset template”.

###  3.1. MI Pilot Site  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

MI Pilot Site

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

**Responsible & **

**Collector**

</td>  
<td>

MI (in cooperation with the second pilot site owners Keywater Ltd)

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Environmental monitoring data collected from the sensors deployed on the pilot
site and that will be used to inform management decisions.

It will be used to inform the IMPAQT platform.

These data are currently stored in various formats on MI servers and are kept
for historical record and to inform research work

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

**Formats**

</td>  
<td>

.XLS files, ERDAP

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

**Expected Size**

</td>  
<td>

The volume size will depend on the data. It is expected to be < 1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Non-strategic and environmental data will be shared openly where there is no
commercially sensitive restrictions. Currently elements of the environmental
data is shared on ERDAP

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

</td>  
<td>

( _https://erddap.marine.ie/erddap/index.html_ )  and it is expected to add
new IMPAQT data to this (or other open access locations as suggested by WP
leaders) as the project progresses. Data will be shared openly between the
partners.

Relevant data will be included in any publications or made available as a
supplementary to publications.

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data will be validated when
downloading

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be stored on MI
servers for an indefinite period of time with no associated costs, as well as
being available on ERDAP.

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

###  3.2. NSF Data 1  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

NSF Data 1

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

**Responsible & **

**Collector**

</td>  
<td>

NSF

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Environmental monitoring data (biotic, abiotic and metocean) collected from
the sensors deployed on the pilot site and that will be used to inform
management decisions. It will be used to inform the IMPAQT platform.

These data are currently stored in various formats on NSF servers and are kept
for historical record and to inform research work

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

**Formats**

</td>  
<td>

.XLS files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be 500 MB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Publicly available upon request - We will communicate clearly that the
information is available for use. Upon contacting we will distribute the data
with the proper guidance for the intended use by the requestee

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data will be validated when
downloading

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be stored on NSF
servers until 5 years from the end of the project with none practical costs
associated

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

###  3.3. NSF Data 2  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

NSF Data 2

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

**Responsible & **

**Collector**

</td>  
<td>

NSF

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

**Category Type**

</td>  
<td>

Hydrodynamic Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Hydrodynamic monitoring data (forces on the system) collected from the sensors
deployed on the pilot site and that will be used to inform management
decisions. It will be used to inform the IMPAQT platform. These data are
currently stored in various formats on NSF servers and are kept for historical
record and to inform research work

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

**Formats**

</td>  
<td>

.XLS files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be 500 MB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Publicly available upon request - We will communicate clearly that the
information is available for use. Upon contacting we will distribute the data
with the proper guidance for the intended use by the requestee

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data will be validated when
downloading

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be stored on NSF
servers until 5 years from the end of the project with none practical costs
associated

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

###  3.4. LCA Inventory Data  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

LCA Inventory Data

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

**Responsible & **

**Collector**

</td>  
<td>

LEITAT (also in cooperation with each pilot site owners)

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

The LCA Inventory Data provide inputs and outputs data collected from the
pilots that is related to the process to allow quantifying of the
environmental impacts

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

**Formats**

</td>  
<td>

.XLS files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be 500 KB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected. Nevertheless, the data collected from the pilots will be
aligned with ISO 14044 (LCA)

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy to the LCA Inventory Data should be restricted since it will
have sensible information related to resources consumption.

The results reported by the LCA software will be in .XLS format but will be
also integrated in a .PDF document

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data come from direct measured based
on standards, expert judgement and data published in scientific papers

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the dataset edition will be
limited. The data will be stored for an indefinite period of time with none
associated costs

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

###  3.5. Envi-Vars  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

Envi-Vars

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

**Responsible & **

**Collector**

</td>  
<td>

CAMLI and DEU

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Environmental variables that will be used to represent and detect any changes
in the biogeochemical status of the monitoring pilot site. Mostly collected
automatically in situ by sensors and/or manually for post-processing procedure
at labs.

All data will be stored digitally in hard drives with an appropriate database
format

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

**Formats**

</td>  
<td>

.XLS files and will be also used high resolution microscopic images

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be several GBs

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected. Nevertheless, the data collected from the pilots will be
aligned with ISO 14044 (LCA)

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted until the publication are submitted. It can be
accessed thought .XLS files

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained for the data measured by sensors, the
calibration parameters of sensors have to be archived for each calibration
performed (including dates).

For the data measured in lab, the necessary methodological coefficients (facts
and absorbance values of standards, etc.) have to be archived

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be backing up on
CDs, hard drives and clouds until 5 years from the end of the project with
none practical costs associated

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

###  3.6. Data of Production Operations  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

Data of Production Operations

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

**Responsible & **

**Collector**

</td>  
<td>

CAMLI and DEU

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

**Category Type**

</td>  
<td>

Production Data

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

**Description & **

**Purpose**

</td>  
<td>

Data representing the production operations at the pilot sites that have to be
coupled with the environmental data for analysing and establishing of an
integrated management model.

Some of these data are: feeding (amount/frequency), mortality (collection of
death fish/mussel), net/rope changes (frequency), size grading (fish), medical
treatment (drug/vaccine uses) in terms of dosages and duration, and others.

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

**Formats**

</td>  
<td>

.XLS files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be several GBs

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

**Metadata & **

**Standards**

</td>  
<td>

TBD

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

**Data Sharing**

** & Access **

</td>  
<td>

Access policy has to restricted with the partners of the tasks in which the
data is going to be used. To be accessed it is also a confidentiality
agreement among users

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data will be alignment with the
planned production plan

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

**Preservation**

** & Archiving **

</td>  
<td>

Each pilot will be responsible to ensure archiving, preservation and security
of the data through baking up on hard drives and cloud until 5 years from the
end of the project (with an associated cost of 1 PM per year for each pilot
site)

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

##  3.7. Environmental Dataset  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

Environmental Dataset

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

**Partner**

**Responsible**

</td>  
<td>

CAMLI

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Measuring of environmental parameters in order to understand the functioning
of IMTA and environmental impact assessment of fish production.

Some environmental parameters collected are temperature, oxygen level, water
currency direction and speed, ammonia, phosphorus, light intensity, turbidity,
meteorological conditions (wind, wave strength, direction), and others

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

**Formats**

</td>  
<td>

.XLS files

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

**Sizes**

</td>  
<td>

The dataset volume size will depend on the data. It is expected to be

< 1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected. Nevertheless, the data collected from the pilots will be
aligned with ISO 14044 (LCA)

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted. The Data also need to be harmonised before
opened to public for 3 years and will be available thought .XLS files

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

**Quality**

**Assurance**

</td>  
<td>

Data will be archived in IMST and CAMLI's own cloud and data system. To ensure
that quality is maintained for the data measured by sensors, the calibration
parameters of sensors have to be archived for each calibration performed
(including dates).

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

**Preservation**

** & Archiving **

</td>  
<td>

Each pilot and DEU-IMST will be responsible to ensure archiving, preservation
and security of the data through baking up on hard drives and cloud until 5
years from the end of the project with none practical costs associated

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

##  3.8. IMTA Species Dataset  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

IMTA Species Dataset

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

**Responsible & **

**Collector**

</td>  
<td>

CAMLI

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

**Category Type**

</td>  
<td>

Production Data

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

**Description & **

**Purpose**

</td>  
<td>

Data of species cited in a culture system that need to be followed. This
dataset regard data such growth condition of the species, welfare conditions
and stress conditions

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

**Formats**

</td>  
<td>

.XLS files

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

**Expected Size**

</td>  
<td>

The volume size will depend on the data. It is expected to be < 1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted. The Data also need to be harmonised before
opened to public for 3 years and will be available thought .XLS files

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

**Quality**

**Assurance**

</td>  
<td>

Data will be archived in IMST and CAMLI's own cloud and data system. To ensure
that quality is maintained for the data measured by sensors, the calibration
parameters of sensors have to be archived for each calibration performed
(including dates).

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

**Preservation**

** & Archiving **

</td>  
<td>

Each pilot site will be responsible to ensure archiving, preservation and
security of the data through baking up on hard drives and cloud until 5 years
from the end of the project with none practical costs associated

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

##  3.9. Food Safety Dataset  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

Food Safety Dataset

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

**Responsible & **

**Collector**

</td>  
<td>

CAMLI

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

**Category Type**

</td>  
<td>

Food Safety Tests

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

**Description & **

**Purpose**

</td>  
<td>

Since the species produced in IMTA will be used for human consumption, the
Food Safety Dataset will be used to perform food safety analysis, such as
heavy metals, as well as to help monitor food safety

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

**Formats**

</td>  
<td>

.XLS and .PDF files

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

**Expected Size**

</td>  
<td>

The volume size will depend on the data. It is expected to be < 1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted. The Data also need to be harmonised before
opened to public for 3 years and will be available thought .XLS and .PDF files

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

**Quality**

**Assurance**

</td>  
<td>

Data will be archived in IMST and CAMLI's own cloud and data system. To ensure
that quality is maintained for the data measured by sensors, the calibration
parameters of sensors have to be archived for each calibration performed
(including dates). Analyses and methods performed in accredited labs are will
be archived in the same system.

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

**Preservation**

** & Archiving **

</td>  
<td>

Each pilot site will be responsible to ensure archiving, preservation and
security of the data through baking up on hard drives and cloud until 5 years
from the end of the project with none practical costs associated

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

##  3.10. OptData  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

OptData

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

**Responsible & **

**Collector**

</td>  
<td>

IOPAN

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Measurements of several water parameters, mainly these that are optically
significant, collected during field campaigns on the pilot sites. Data will be
used for development and validation of the satellite algorithms and products

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

**Formats**

</td>  
<td>

.CSV files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be to be < 1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted until the publication are submitted. It can be
accessed thought .CSV files

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained for the collected data measured by
various instruments, the calibration parameters of sensors have to be archived
for each calibration performed, and the measurements have to be carried out
with the state of the art and well-documented procedures and standards

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be stored on
IOPAN servers until 5 years from the end of the project with none associated
costs

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

##  3.11. SatData  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

SatData

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

**Responsible & **

**Collector**

</td>  
<td>

IOPAN

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Satellite products, based on locally developed algorithms, presenting temporal
and spatial variability of selected environmental parameters, supporting the
monitoring of the pilot sites

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

**Formats**

</td>  
<td>

netCDF files

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

**Expected Size**

</td>  
<td>

The dataset volume size is expected to be several GBs

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

The access policy is restricted. The Data also need to be harmonised before
opened to public and will be available thought netCDF and

GeoTIFF files

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the presented satellite products have to
be calculated with locally developed algorithms and validated with high-
quality measurements on the pilot sites. The atmospheric corrections of ocean
colour data should also be validated, possibly at each pilot site

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

**Preservation**

** & Archiving **

</td>  
<td>

To ensure archiving, preservation and security the data will be stored on
IOPAN servers until 5 years from the end of the project with none associated
costs

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

##  3.12. Daily Meteo harvestering MIC  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

Daily Meteo harvestering MIC

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

**Responsible & **

**Collector**

</td>  
<td>

Unparallel Innovation

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Gathering real deployment data about Meteorological conditions per day at
specific location (MIC pilot) to correlate / validate with theoretical data
(e.g. EU tool). To assist in the choice and specifications of the energy
harvesting system due to the demand of energy requirements and weather
conditions.

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

**Formats**

</td>  
<td>

.CSV files

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

**Expected Size**

</td>  
<td>

aprox. 1 MB per day

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Public

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

**Quality**

**Assurance**

</td>  
<td>

To ensure the quality: Validation / correlation with theoretical sources (e.g.
EU tool and wunderground site).

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

**Preservation**

** & Archiving **

</td>  
<td>

Data stored on Unparallel Innovation servers

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

##  3.13. SGB dataset  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

SGB dataset

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

**Responsible & **

**Collector**

</td>  
<td>

YSFRI

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Environmental monitoring data collected from the platform deployed on the
Sanggou Bay site and that will be used to inform management decisions. The
data are currently stored in various formats on the servers maintained by
RobotFish and YSFRI. The new data since

IMPAQT project is not integrated yet

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

**Formats**

</td>  
<td>

.xls & netCDF

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

**Expected Size**

</td>  
<td>

depend on the data. Expected to be <1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Restricted until publications are submitted and permitted by I.T department of
local government

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

**Quality**

**Assurance**

</td>  
<td>

Quality Assurance Procedures

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

**Preservation**

** & Archiving **

</td>  
<td>

Data stored on RobotFish/YSFRI severs

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

##  3.14. SAMS pilot site  
  
<table>  
<tr>  
<th>

**Dataset Name**

</th>  
<th>

SAMS pilot site

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

**Responsible & **

**Collector**

</td>  
<td>

SAMS

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

**Category Type**

</td>  
<td>

Environmental Monitoring

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

**Description & **

**Purpose**

</td>  
<td>

Environmental monitoring data collected from the sensors deployed on the pilot
site and that will be used to inform management decisions. It will be used to
inform the IMPAQT platform. Restricted access data kept on SAMS in-house
servers (accounting for full permissions, security) following defined internal
data preservation. Controlled access

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

**Formats**

</td>  
<td>

.xls

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

**Expected Size**

</td>  
<td>

approx >1GB

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

**Metadata & **

**Standards**

</td>  
<td>

None are expected

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

**Data Sharing**

** & Access **

</td>  
<td>

Restricted and not in publicly accessible format. This is because the data is
being kept on SAMS secure serve only accessible to SAMS staff but upon request
we are happy to share the data

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

**Quality**

**Assurance**

</td>  
<td>

To ensure that quality is maintained the data will be validated when
downloading

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

**Preservation**

** & Archiving **

</td>  
<td>

Data stored on SAMS servers

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

The identified IMPAQT Datasets are mostly originated from diverse sources
deployed in the IMPAQT pilots. These datasets include a wide range of
significant information such as quality parameters, hydrodynamic monitoring
data, environmental monitoring data, production data, food safety tests data
and others.

During the development of the IMPAQT project new purposes and objectives can
arise and it may be necessary generate and/or collect new IMPAQT datasets that
will be identified by the consortium. IMPAQT consortium will also ensure a
database always updated with all the identified IMPAQT datasets.

#  CONCLUSION

IMPAQT Data Management Plan result from the work developed in WP6 within the
first 6 months of the IMPAQT project that is funded from the EU H2020 research
and innovation programme under Grant Agreement No 774109\.

This Data Management Plan is in accordance with the European Commission
guidelines an also with the data principles of the section 1.2. In the scope
of Open Access, all the efforts will be made to ensure the right to copy,
distribute and easily search both scientific publication and research data.
IMPAQT consortium is conscious of the directives for Open Access of
Publications and Research Data in H2020 projects. IMPAQT will published
whenever possible under Open Access procedures since believes that make the
research data FAIR (findable, accessible, interoperable re-usable) and
available with few restrictions as possible can make a significant
contribution to economic growth.

As stated in the document, the aim of the consortium is to have non-strategic
datasets as publicly available datasets by the end of the project. The
consortium is working on an online list with IMPAQT datasets identified,
detailing the publicly available and restricted ones (including the details on
why these are restricted). A version of this list (with the public IMPAQT
datasets) will be made publicly available, while the complete version will
only be available to the consortium and EC. Both versions of this list will be
online during April 2020.

Section 2 cover all the data lifecycle steps of the DMP that will be applied
in order to describe each research data that will be generated or gathered
during the IMPAQT project and that will help to provide the sustainability of
the project. These steps are Data Collection (regarding how to collect and
generate IMPAQT data), Data Processing (methods to identify, analyse and
process data), Data Storage (how to deposit research data in an online
repository) and Data Share (the steps to ensure that data can be accessed,
discovered and re-used by third parties).

This deliverable also includes in section 3 the identification of the
available IMPAQT Datasets, mostly originated from diverse sources deployed in
the IMPAQT pilots and that includes several relevant information as quality
parameters, hydrodynamic monitoring data, environmental monitoring data,
production data, food safety tests data and others. During the development of
the project, IMPAQT consortium will ensure a database always updated with all
the identified IMPAQT datasets.

#  FAIR DATA MANAGEMENT

The research data should be 'FAIR': findable, accessible, interoperable and
re-usable. The following questions were extracted from the "Guidelines on FAIR
Data Management in Horizon 2020  25  " document in order to assist IMPAQT
consortium to make the project research data FAIR.

**FAIR Data**

###  1- Make data Findable (including provisions for metadata)

  * Are the data produced and/or used in the project discoverable with metadata, identifiable and locatable by means of a standard identification mechanism (e.g. 

  

persistent and unique identifiers such as Digital Object Identifiers)?

  * What naming conventions do you follow? 

  

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

  

  * Do you provide clear version numbers? 

  

  * What metadata will be created? In case metadata standards do not exist in your discipline, please outline what type of metadata will be created and how. 

  

###  2- Make data Openly Accessible

  * Which data produced and/or used in the project will be made openly available as the default? If certain datasets cannot be shared (or need to be shared under restrictions), explain why, clearly separating legal and contractual reasons from voluntary restrictions. 

  

  * Note that in multi-beneficiary projects it is also possible for specific beneficiaries to keep their data closed if relevant provisions are made in the consortium agreement and are in line with the reasons for opting out. 

  

  * How will the data be made accessible (e.g. by deposition in a repository)? 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)? 

  

  * Where will the data and associated metadata, documentation and code be deposited? Preference should be given to certified repositories which support open access where possible. 

  

  * Have you explored appropriate arrangements with the identified repository? 

  

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

  

  * Is there a need for a data access committee? 

  

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

  

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

###  3- Make data Interoperable

  * 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? 

  

  * 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? 

  

###  4- Increase data Re-use (through clarifying licences)

  * 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?