#  Introduction

Over the course of a research project, substantial amounts of data are either
generated within the project, or collected from existing sources and collated.
Often, this data is not made available for researchers in related areas;
meaning considerable time and effort are spent gathering similar data. There
is thus a need to promote reuse of data, through making it accessible to a
wider audience. As a participant in the Horizon 2020 Open Research Data Pilot
(ORD Pilot), ClimeFish will take measures to ensure that collected research
data is made accessible and to enable future sharing, thereby promoting reuse
of data and transparency.

ClimeFish follows the FAIR Data principles (DG RTD 2016a; Wilkinson et.al.
2016), which entails making data:

  * Findable 

  

  * Accessible 

  

  * Interoperable 

  

  * Reusable 

  

The ORD initiative towards making research data openly accessible is based on
the principle of " _as open as possible, as closed as necessary_ " (DG RTD
2016b). This means that while all data is initially suitable for being made
public, exceptions are made for data that contains sensitive or otherwise
proprietary information. While the initiative applies primarily to data
underpinning scientific results and publications, all other data used within
the project is also applicable.

As part of this initiative, one of the objectives of Work Package 2 is " _to
connect ClimeFish to relevant data repositories where the generated data can
be made available after the project end_ ". In order to achieve this, plans
for archiving and sharing data must be made. This is handled as part of task
2.5, and involves " _updating the data management plan, providing accurate
metadata descriptions, and uploading relevant data to the Climate-ADATP_
_platform and to the H2020 Research Data Pilot_ ".

This deliverable specifies how and where data should be uploaded, what
provisions must be made to ensure access, etc. No actual data will be uploaded
at this point. The data upload itself will not take place until nearer the
project end, and will be documented in deliverable 2.4 " _Final list of data
collected and collated, with archiving and sharing in effect_ ", planned for
M45.

#  Data collected

As part of the H2020 ORDP, a data management plan (DMP) has been developed.
The DMP details what data the project generates, how that data will be
archived, barriers to making data publicly available, etc. It contains one
form per dataset. The DMP was written as part of Deliverable 2.1, and is
updated once within each 18-month reporting period, ensuring an up-to-date
overview of the data used in ClimeFish.

Version 2 of the DMP (written in October 2017) contains 39 forms covering all
16 ClimeFish case studies. Table 1 below shows the full list of datasets for
the four main case study areas: "Marine fisheries", "Lake and pond
production", "Marine aquaculture", and "European waters overall". A
standardized naming convention has been used for all datasets, based on the
following structure: < _Case study code_ > – < _Species_ > – < _Geographic
area_ > – < _Dataset description_ >. Where applicable, the time period covered
by the dataset is included. If the data covers three species or more, the
collective term" Several species" has been used.

_Table 1 ClimeFish datasets as of October 2017_  
  
<table>  
<tr>  
<th>

**Marine fisheries**

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

C1F – Several species – Northeast Atlantic – Catch statistics, 2005-2015

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

C1F – Several species – Northeast Atlantic – Stock size and recruitment,
2005-2015

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

C1F – Several species – Iceland – Fishing vessels, production, exports and
catch values, 2005-2015

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

C1F – Several species – Northeast Atlantic – Biological and physical data,
2005-2015

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

C1F – Mackerel – Northeast Atlantic – Trawl survey data, 2007-2017

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

C1F – Several species – Northeast Atlantic – Stock assessment

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

C2F – Herring, sprat – Baltic Sea – Environmental, biological and fishery data

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

C3F – Cod – Baltic Sea – Environmental, biological and fishery data

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

C4F – Cod, haddock – Barents Sea – Environmental data

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

C5F – Hake, cod – West of Scotland – Trawl survey data

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

C5F – Hake, cod – West of Scotland – Economic data

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

C5F – Hake, cod – West of Scotland – Oceanographic data

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

C5F – Hake, cod – West of Scotland – Simulation data

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

C6F – Demersal fishery – Adriatic Sea – Demersal fishery landings data

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

**Lake and pond production**

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

C7F – Several species – Norway – Freshwater fish survey data

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

C7F – Several species – Norway – Limnological data

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

C7F – Several species – Norway – IBM modeling output

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

C8F – Whitefish, arctic char – Lake Garda – Fishery data

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

C9F – Several species – Czech Republic, The Netherlands – Gillnet catch data

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

C9F – Several species – Czech Republic – Angling data

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

C9F – Several species – Czech Republic – Limnological data

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

C10A – Carp, catfish – Hungary – Industry data, 2000-to date

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

C10A – Carp, catfish – Hungary – Farm production and input data

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

C10A – Carp, catfish – Hungary – Simulation data

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

**Marine aquaculture**

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

C11A – Salmon – Chile – Environmental and production data

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

C11A – Salmon - Norway – Environmental and production data

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

C11A – Salmon – Scotland – Environmental and production data

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

C12A – Seabass, meagre – Greece – Growth, consumption and temperature data

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

C12A – Seabass, meagre – Greece –Simulation data

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

C13A – Blue mussel, carpet shell – Spain – Meteorological data

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

C13A – Blue mussel, carpet shell – Spain – Environmental data

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

C13A – Blue mussel, carpet shell – Spain – Harmful algal blooms data

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

C13A – Blue mussel, carpet shell – Spain – Mussel larvae settlement and
recruitment data

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

C13A – Blue mussel, carpet shell – Spain – Weight ratio

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

C13A – Blue mussel, carpet shell – Spain – Simulation data

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

C14A – Shellfish – Scotland – Environmental and production data

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

C15A – Blue mussel, carpet shell – Northern Adriatic Sea – Environmental and
production data

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

**European waters overall**

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

C16AF – Several species – European waters – Production by production source,
1950-2014

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

C16AF – Several species – European waters – Life history traits matrix

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

While the majority of data is not proprietary and can be shared freely,
certain datasets containing commercially sensitive information such as
production figures and socio-economic data collected in agreement with
industry actors are subject to restrictions.

#  Data archiving and sharing

As noted in the DMP, the majority of data is currently stored in in-house
repositories belonging to the different ClimeFish partners. However, in order
to be made available to both the research community and the wider public,
data, publications  1  and similar resources must be deposited in an open
access data repository. The OpenAIRE guidelines recommends four ways for
selecting a suitable data repository, in order of preference (OPENAIRE 2016):

  1. Use an external data archive or repository already established for your research domain to preserve the data according to recognised standards in your discipline. 

  

  2. If available, use an institutional research data repository, or your research group’s established data management facilities. 

  

  3. Use a cost-free data repository such as Zenodo. 

  

  4. Search for other data repositories here: re3data.org. On top of specific research disciplines you can filter on access categories, data usage licenses, trustworthy data repositories (with a certificate or explicitly adhering to archival standards) and whether a repository gives the data a persistent identifier. 

  

  

As noted in the DMP, some of the data used consists of data gathered from
public databases, either in the form of premade datasets downloaded from a
website, or datasets generated through the database in question. In general,
for data already openly accessible on the web, only a link to the original
source along with necessary metadata is needed, rather than copies of the
original datasets themselves. Original data generated by the project, however,
must be uploaded in full to a repository.

As specified in the Description of Action, applicable data from the ClimeFish
project will be shared on the Climate-ADAPT platform. Climate-ADAPT  2  is a
joint initiative between several DGs within the European Commission and the
European Environment Agency, allowing for sharing research data, case studies,
map data, publications, or other resources pertaining to climate change. More
specifically, Climate-ADAPT contains information pertaining to the following
categories:

  * Publications and reports 

  

  * Information portals 

  

  * Guidance documents 

  

  * Tools 

  

  * Research and knowledge projects 

  

  * Adaptation options 

  

  * Case studies 

  

  * Organisations 

  

  * Indicators 

  

In order to submit content to the platform, users must request an EIONET
account. Access can be requested by emailing the EIONET helpdesk (
_helpdesk@eionet.europa.eu_ ) and providing your name, email address and
organisation. When submitted, metadata will be evaluated by the EEA/ETC-CCA
team before being accepted for publishing.

Specific details on the necessary information and metadata for each of the
nine information categories can be found through:

  * _http://climate-adapt.eea.europa.eu/help/share-your-info_

  

Data uploaded to the Climate-ADAPT platform must be related to " _climate
change impacts, vulnerability and adaptation in Europe"_ . Therefore, data not
pertaining to " _impacts, vulnerability, and adaptation_ ", such as data
focusing solely on climate change mitigation, or data not related to Europe,
is outside of the scope of the platform.

Data not within the scope of the Climate-ADAPT platform will be uploaded to
Zenodo  3  if no other suitable repository within the given scientific domain
exists, or if the institution in question does not have a suitable open access
data repository of their own. Zenodo is a "catch-all" repository, hosted by
CERN and part of the OpenAIRE project. All data uploaded to Zenodo is given a
DOI (digital object identifier). A DOI is a persistent identifier that is
linked to- and uniquely identifies objects such as reports, datasets, etc.
Zenodo supports DOI versioning, meaning that if data is updated, each version
is given its own unique DOI. In order to upload content to Zenodo, users must
register an account. Registration is open to all parties.

Figure 1 illustrates the proposed timeline for archiving and sharing data
towards the project end. As per the ORDP, the DMP must be updated within each
18-month reporting period. The deadline for the next update is planned for
M43. Participants will be asked to update their respective forms, with special
attention being paid to whether the data contains sensitive information and if
it can be shared, and if so, suitable open access repositories in instances
where Climate-ADAPT is not appropriate.

Project participants will be asked to upload either full copies of the
datasets or simply associated metadata to applicable open access data
repositories themselves. If needed, Nofima staff involved in WP2 can assist in
making data available. All applicable data will be uploaded to a repository by
M45. This will be documented as part of Deliverable 4.5 "Final list of data
collected, with archiving and sharing in effect".  
  
<table>  
<tr>  
<th>

Project partners requested to update

datasets, metadata, etc. (M42)

</th>  
<th>

D2.4 Final list of data collected, with

archving and sharing in effect (M45)

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

Final version of data Project end (M48) management plan

(M43)

_Figure 1 Timeline for archiving and sharing of ClimeFish project data_