#  Executive Summary

This deliverable aims to present a plan for the data management, collection,
generation, storage and preservation related to CITADEL activities. In this
action, we envision five different types of data: data related to the use
cases, data related to the meta-analysis to be done in the social-sciences
tasks, data coming from publications, public deliverables and open source
software.

The document presents, following the EC template [1], how these different
types of data will be collected, who the main beneficiaries are, and how
CITADEL will store them, manage them, and make them accessible, findable and
re-usable. The text continues with the foreseen resources needed for the
openness and data to finalize with security and ethical aspects that will be
taken into consideration in the context of CITADEL.

This plan is the first version of the data management plan, which will be
updated in subsequent versions (M12, M24 and M36) as part of the Technical
Reports, having as input the work carried out in the use cases (WP5), the
social and technical work packages (WP2 – WP4) and the dissemination
activities (WP6).

#  Introduction

##  About this deliverable

This deliverable focuses on the management of the data in CITADEL. In CITADEL
there will be two different data, the first strand related to the publications
generated as part of the research activities, and the second strand related to
the data collected from citizens, users and non-users of digital public
services, as well as from civil servants, that will be used as part of the
implementation of the different key results established in the project.

##  Document structure

The document follows the established H2020 template for a Data Management Plan
(DMP) [1]. Section 2 presents a summary of what the purpose of the data
collection and generation is in the case of CITADEL. Section 3 explains how
the data and metadata will be made fair, and thus accessible, findable and
reusable. Section 4 briefly explains how the financial resources for this
openness are envisioned at this stage to be allocated. Section 5 and 6 focus
on the security and ethical aspects respectively. Section 7 presents the
conclusions and future work.

#  Data Summary

The purpose of the data to be collected in CITADEL is twofold. On one hand, to
understand why citizens are not currently using a certain digital public
service, even if they do have the skills for it. On the other hand to
understand what the opinion is of citizens that are using a digital public
service and how this digital service can be improved or created from scratch
with the participation of the citizens.

To realize this, CITADEL will develop the following Key Results (KR) [2]:

  * **KR1: CITADEL Recommendations and guidelines to transform PA** . A set of guidelines derived from the use cases and surveys will focus on the re-definition of the public policies, processes and services to be adapted to citizens´ and organizations’ (users and non-users) expectations. The use of these CITADEL recommendations will allow PAs save significant money in the re-design of their processes. 

  

  * **KR2: CITADEL Information monitoring service:** This service monitors and analyses available citizens´ (user and non-users) data (e.g. feedback, open data, demographic statistics, preferences and so on). The objective is to extract, using big data, semantics and privacy preserving technologies, relevant information required for the formulation of the recommendations (KR1). This service is composed of two important assets: 

    * Monitoring services asset: Based on semantics, this asset will select the relevant information in each moment and in each situation. o Analysis services asset: Based on the relevant information provided by the monitoring asset, this asset will provide KPI (Key performance Indicators) or if possible recommendations. 

  

  

  * **KR3: CITADEL tool supported methodology for services co-creating.** This methodology will guide and support PAs in the co-creation process and will be customized for taking into account the characteristics of each PA. The adaptation could be done based on different aspects like, legal systems, scope and audience or the target group. 

  

  * **KR4: CITADEL Co-creation collaborative tool** that allows the PA, the Private Sector and citizens to co-create new public services at a conceptual level. 

  

  * **KR5: CITADEL Discovery service,** that allows discovering digital public services based on the citizen’s profile and the result of semantic analysis of the data such as preferences, utilization, opinions and so on. 

  

  * **KR6: CITADEL Assessment services** that are responsible for allowing those citizens that use digital public services to evaluate them providing useful information for improving them. 

  

  * **KR7: CITADEL Security toolkit:** A set of assets integrated in CITADEL: 

    * Dedicated asset for the integration of privacy regulations 

  

    * Implementation of cloud- and device-based personal data privacy features o Privacy-by-Default features 

  

  

  * **KR8: CITADEL Ecosystem** is the main result of the project and aggregates both the social and technical aspects. CITADEL Ecosystem will include not only the services provided by the other objectives of CITADEL (KR2: Information monitoring service; KR3: Co-creation collaborative tool; KR4: Discovery service; CITADEL DISCOVERY SERVICE (KR2): Assessment services and KR6: Security toolkit) but also those outcomes focused on the transformation of the CITADEL Recommendations for the re-definition of the public processes (KR1: Recommendations to transform PA). 

  

All the CITADEL services to enable both the pillars of ‘Understand to
transform’ and ‘Co-create to transform’ will be integrated as part of the
CITADEL ICT Enablers. The high level architecture of the different components
and their link to the CITADEL KR’s are shown in the next figure.

**Figure 1.** CITADEL High level architecture and the link to CITADEL’s
envisioned Key Results

Out of all the Key Results envisioned for CITADEL, the ones that are more
data-oriented, either by using, generating or analyzing data are KR2 - CITADEL
Information monitoring service, CITADEL DISCOVERY SERVICE (KR2) - CITADEL
Discovery service, KR6 - CITADEL Assessment services and KR7- Security
toolkit, which aims to apply privacy by design and security by design
principles as well as anonymization and pseudo-anonymization techniques.

In CITADEL three distinct environments are envisioned, namely, a development
environment, an integration environment and dedicated environments for each of
the use cases.. The development environment will be deployed in the
corresponding sites of the technological partners (imec, FINCONS and
TECNALIA). The integration environment will be deployed at TECNALIA’s DevOps
infrastructure and will include the different components developed by the
technological partners. For testing purposes, these partners will use
synthetic, fake, data or ‘persona’ data, but never real data, anonymized or
not, coming from the use cases. The third environment is the customized
environment for the four distinct CITADEL use cases. The CITADEL platform and
the already existing IT systems of the four different use cases will be
integrated by means of REST APIs, and will be deployed on the PAs own sites.
The data that will be collected from these will follow the principles
underlined along this deliverable, fulfilling always the GDPR requirements.

**Figure 2.** CITADEL Envisioned environments

Different types of data will be collected and generated in the context of the
project. These can be summarized as follows:

  1. Data related to the execution of the use cases, testing KR1 –KR8. 

  

  2. Data related to the results of the analysis and metadata analysis of the social-related work packages (WP2 and WP3), which will be embedded (partially or wholly) in KR1 – KR8. 

  

  3. Data related to scientific publications. 

  

  4. CITADEL public deliverables. 

  

  5. CITADEL Open Source Software 

  

  

##  Data related to the use cases

The aim of this section is to establish what the purpose is of the collection
and generation of data within CITADEL, which the sources of this data are and
how this is important to realize the Key Results of CITADEL. Furthermore, we
also determine the baseline for the formats for the data both collected and
generated and the main beneficent of the collection and generation of such
data.

Use cases are a key pillar of CITADEL as they will validate the work (in WP5)
to be performed in the social and technological work packages (WP2-WP4).

In principle, for the real execution of the use cases, CITADEL trials will
involve real end users (i.e. data subjects) using a test bed designed to
emulate operational services they are using or intend to use. Wherever
possible, use cases will use synthetic (i.e. fictional but representative)
data, avoiding the use of personal data from operational systems at the PAs.
However, this does not mean that no personal data will be collected from
participating citizens. In such cases, anonymized data from users of digital
public services will be collected. These data can originate either from the
databases already in production at the Public Administrations where citizens’
data are stored, which in the event they are not anonymized, they will be
anonymized or de-anonymized through a dedicated anonymization component of
CITADEL, as part of the module ‘Security Management’ of Figure 1. In the event
surveys are to be launched, as for instance in the case of the VARAM’s use
case, in order to capture and understand why digitally skilled citizens are
not using the offered online governmental services, or to understand the civil
servants’ willingness to change, the users will be required to provide some
personal data (such as age group, education level), but this will be stored in
a confidential manner. Data will be anonymised once data collection has been
completed. This is especially relevant for CITADEL Information monitoring
service (KR2) and CITADEL Evaluation Service (KR6).

For the CITADEL Discovery service (KR2), in which citizens are recommended
digital public services, based on their profile, this will be pseudo-
anonymized, taking into consideration generic characteristics such as services
already being used by that specific citizen as well as age, for instance in
the cases of ICTU. This data will be used following the European GDPR
legislation for personal data.

The generic sources of data for CITADEL Information monitoring service (KR2),
CITADEL Discovery Service (KR5) and CITADEL Evaluation Service (KR6) are
envisioned as follows:

  * **Open Data** coming in a first phase, from EU-wide open data portals such as, the 

  

European Data portal  1  , and the EU open data portal  2  . In a second
stage, it might be

needed to consider other open data portals at EU, national, regional or local
level. This will be updated in subsequent technical reports due M12, M24 and
M36. The format of such data is preferably JSON, CSV, TSV (Tab separated
values), or when relevant, SDMX for statistical data. The exact data sets to
be used are part of the study to be performed in D2.1.

  * **Synthetic data** , generated for testing purposes. This data will be preferably in JSON. 

  

  * **Citizens’ data** stored in the governments participating in CITADEL, namely, Antwerp, Regione Puglia, the Netherlands and Latvia. As stated before, not be shared with the technological partners. Furthermore, for the CITADEL Information monitoring service (KR2) and CITADEL Evaluation Service (KR6) data will be (pseudo-)anonymized. The preferred formats are JSON or CSV. 

  

The collected data will be curated and processed as part of CITADEL
Information monitoring service (KR2), CITADEL Discovery Service (KR5) and
CITADEL Evaluation Service (KR6), with the main aim to provide recommendations
(KR1) to the Public Administrations, which will be shown, mostly, in the form
of KPI reports. The format for the generated metadata will be preferably JSON,
RDF and XML. The size of the expected datasets is unknown at this stage of the
project.

Furthermore, each use case will need certain specific data for the execution
of their own characteristics. This data will be useful only for each of the PA
that owns / collect the data. Next, we proceed to describe, by use case, the
data available at this stage of the project.

###  Stad Antwerpen

For Stad Antwerp, this is the current data available:

  * **Back-end data of** the Antwerp citizen platform (antwerpen.be): 

    * These data are not anonymized, neither is Stad Antwerpen authorized to use the data for other purposes than the stated objective (i.e. delivery of the requested service). This is part of the citizen platform’s general conditions and is confirmed by legal partner, Time.Lex. 

  

    * In January 2017, a censored back-end data sample has been delivered to Tecnalia to give insight in the data structure. Conducting trials on the data thus is possible. Hence, back-end data will always be stored on local servers and managed by Digipolis (the externalised IT-department from Stad Antwerpen). This policy applies to the use case within CITADEL as well. 

  

  

  * **Front-end data** Google analytics data of the platform o These data are anonymised and aggregated and can be used within the CITADEL project. 

  

  * **Marketing research data,** such as: Antwerp Monitor, Panel surveys, and Surveys that are conducted in the local city desk, which are anonymised and aggregated and can be used within the CITADEL project. A specific survey to measure usability within the use case can be conducted on Stad Antwerpen’s own panel 

  

###  VARAM

Current available data in the use case of VARAM include:

  1. Latvia's e-index results raw data; 

  

  2. National Citizens' portal www.latvija.lv, Google Analytics Data; 

  

  3. Service catalogue and service descriptions of more than 2000 public services; 

  

  4. Public opinion evaluation on public sector services; 

  

  5. Regional development data. 

  

  6. HotJar (Analytics and Feedback application) installation in portal 

  

  

All existing data are anonymous. There might be personalised data when CITADEL
co-creation tools are used. However, as expressed before, the intention is to
use fictional but representative data in order to evaluate the adequateness of
CITADEL ICT Enablers for cocreation.

###  ICTU

ICTU does not collect any data such as names or addresses but the current
system does collect IP addresses or other information by means of ‘cookies’.

ICTU, however, will generate data during the co-creation activities. These
data will be gathered will through focus group of youngsters turning 18 or
parents/caretakers for, with a need analyses; prototyping testing, etc., users
for prototyping, customer satisfaction surveys and qualitative research
(interviews, workshops) on target audience and needs analysis (and
validation). For such data, inform of consents will be collected and signed.

###  Reglione Puglia

In the case of Regione Puglia, existing data includes tourist flow, prices and
services, personal data of business players, promotion data (photo,
description, and activities), special offers, leisure activities and events,
pathways, attractors, social data, google analytics. These data are anonymized
or (pseudo-) anonymized. In the case this is not feasible, making participant
subjects easily recognisable, fictional data will be sought to be used
instead.

##  Data related to the analysis and metadata analysis of socialrelated work
packages

In the context of the activities related to ‘Understand to transform’,
vignette studies will be carried out to understand the willingness of civil
servants to changes. Vignette studies are mostly used for qualitative research
studies and they can be defined as “short stories about hypothetical
characters in specified circumstances, to whose situation the interviewee is
invited to respond” [3]. In the context of CITADEL, these studies will be used
as a complementary technique to other data collection methods. Before the
vignette studies are carried out, civil servants participating in them will be
required to sign informed consent forms. Their answers will be used, processed
and stored in an anonymously manner.

Moreover, in those activities for Understanding the citizens, surveys and
questionnaires will be launched to understand why citizens are or are not
using digital public services. This is especially relevant in the case of
VARAM. The data provided by the participants to these questionnaires will be
treated in an anonymous way. Data allowing to identify participants will be
deleted prior to data analysis.

In the context of the activities related to ‘Co-create to transform’, a
metadata analysis of existing co-creation, co-production and co-design
approaches will be performed. The origin of the data is theoretical and
empirical studies, papers and projects’ deliverables (e.g. from FP7 or H2020),
from which the CITADEL partners own the rights, either because they are the
authors, for the access fees paid to editorial companies, they are published
following an open access policy or are publicly available. For this metadata
analysis, no standard format will be used, but rather an ad-hoc one, created
for the purpose of CITADEL needs. The results will be exposed mainly in the
form of a deliverable, a study, which will be published on the CITADEL website
and as part of the rules that will be used to customize the co-creation
methodology.

The data created as part of the previously explained (meta-)data analysis in
the context of both ‘Understand’ and ‘Co-create’ will serve as input data for
the implementation of the ICT enablers to be developed in the project. The
exact format is at this stage still to be decided, but it will be customized
for the needs of the CITADEL ICT Enablers. The transmission of this data will
be done programmatically.

##  Data related to scientific publications

As part of the dissemination activities, CITADEL will publish scientific
publications in conferences and journals. Following the EC Mandate on Open
Access [4], CITADEL adheres to the Open Access policy choosing the most
appropriate route for each case. CITADEL favours whenever possible, the
‘green’ open access, in which the published article or the final peerreviewed
manuscript will be deposited in an online repository, before, at the same time
as, or after publication, ensuring that the embargo period requested by
certain publishers has elapsed.

The format in which the data related to the scientific publications will be
accessible pdf files. The metadata to be used will be compliant with that of
the repository where the paper is to be deposited and will be compliant with
the format requested by Open Aire, as to ease the index.

The data related to the scientific publications will be relevant to scientists
in the field of innovation in the public sector as well as developers and
technical-oriented communities.

##  CITADEL public deliverables

All information and material related to the public such as public
deliverables, brochures, posters and so, on will be freely available on the
project website in the form of accessible pdf files. When IPR of foreground
knowledge needs to be protected, the corresponding disclosures will be
published.

All deliverables include a set of keywords and a brief description that are
aimed to facilitate the indexing and search of the deliverables in search
engines. The keywords in each deliverable aim to stress the main topics
addressed in the document, be it a report or a software – related document.

The audience of the public deliverables of CITADEL range from general
audiences, interested in the activities performed in the project, to more
specialized audiences, interested in social sciences, innovation in the public
sector, ICT enablers for the Public Sector, or experiences gathered through
the pilots.

##  CITADEL Open Source Software

CITADEL will develop ICT Enablers as means to help Public Administrations to
aid in their transformation. The source code will be released, whenever IPR of
the partners is not breached, under a friendly open source licensing schema.

CITADEL ICT Enablers will be developed in a variety of programming languages
but deployed using a container-based approach following a micro-services [5]
architecture. The size of the source code, the readme files, the user manual
and technical specifications as well as the docker scripts cannot be known at
the moment.

The open source software is aimed at developers of ICT providers of the PAs
and PA providers’ IT departments.

#  Fair Data

This section focuses on the following aspects, namely, on the feasibility and
appropriateness of making data findable, openly accessible, interoperable and
reusable in the context of CITADEL.

##  Data related to the use cases

At this stage, for all use cases, both the collected and generated data,
anonymized or fictional, are not envisioned to be made openly accessible. In
principle, all data collected, stored and processed will be treated as
strictly confidential, and kept for a specific period of time as stated on the
consent form. This time period shall be no longer than necessary to achieve
the aims of the scenario and to validate the project objectives, and after
this point, the data will be destroyed as required.

The openness of the fictional data for testing purposes is, however, an option
that will be evaluated as part of the exploitation and sustainability strategy
and the final decision will be provided in subsequent updates of the Data
Management Plan. In the event they are finally released, they will follow
machine – readable formats such as CSV, RDF/XML or RDF/JSON, and when
appropriate, the DCAP-AP format [7]. Following that structure, it will
immediately make the use cases’ data immediately identifiable, openly
accessible, semantically interoperable and re-usable. Each metadata set will
be accompanied by its licensing schema.

###  Stad Antwerpen

As stated in Section 2.1.1, the back-end data from this scenario will always
be stored on local servers and managed by the externalized IT-department from
Stad Antwerpen, Digipolis. The other data, anonymized or pseudo-anonymized, as
well as the synthetic data that will be used when needed, will also be stored
in the instance of CITADEL that will be created for the Stad Antwerp scenario
(see Figure 2. CITADEL Envisioned environments). Access to the data will be
restricted to citizens under their pseudonyms as well as authorized members of
the CITADEL implementation team who might require access to the data. VARAM

In the case of VARAM, and as represented in Figure 2. CITADEL Envisioned
environments, the data related to this use case will also be stored in VARAM’s
premises, following the Latvian legislation procedures on data protection. The
data gathered through the surveys as well as the citizens’ data will be
anonymized or when not possible, it will be pseudo-anonymized.

For the activities in which citizens’ participation will be required in a
proactive way, such as for the co-creation phase, the approach to be followed
will be under a pseudo-anonym procedure. That is, real data of users will not
be used or disclosed, but rather fictional although representative data will
be favored.

Access to the data will be restricted to citizens under their pseudonyms as
well as authorized members of the CITADEL implementation team who require
access to the data.

###  ICTU

As in the previous cases, in ICTU the same approach for the usage of the data
of the citizens participating in the co-creation activities will be sought,
that is, carry out these activities under a pseudo – anonym. Access to the
data will be restricted to citizens under their pseudonyms as well as
authorized members of the CITADEL implementation team who require access to
the data.

ICTU will also store its own data in its own CITADEL customized environment.

###  Regione Puglia

Regione Puglia will also host a customized CITADEL environment in its own
premises, following the Italian legislation on data protection. As in the
previous use cases, access to the data will be restricted to citizens under
their pseudonyms as well as authorized members of the CITADEL implementation
team who require access to the data.

##  Data related to the analysis and metadata analysis of social – related
workpackages

Data related to the metadata analysis to be performed in the social sciences
work packages will be released mainly as statistical data, following when
feasible, standardized formats (e.g. SPSS).

In the context of the work to be done in the strand of ‘Understand to
transform’, the software AutoMap  3  is envisioned to be used to analyse the
willingness of civil servants to change processes, policies or services,
either in conjunction with citizens (co-design, co-create) or individually.
AutoMap delivers as output a specific format DyNetML as well as standard
formats such as CSV or XML. The personal data of the civil servants
participating in the questionnaires and vignette studies will not be
disclosed, being therefore, anonymized.

The licensing schema for these data is currently under evaluation but the
project will favour its openness as much as possible. However, depending on
the licensing schema selected, the reusability may be limited.

The collected and generated data will be stored as part of the results of
CITADEL on the project’s website and it will be available 3 years beyond the
time frame of the project. In addition, where relevant for secondary research,
data will be deposited in open access social data archives such as DANS or
Gesis.

##  Data related to scientific publications

The project will favour, whenever possible, the ‘green’ open access, in which
the published article or the final peer-reviewed manuscript will be deposited
in an online repository, before, at the same time as, or after publication,
ensuring that the embargo period requested by certain publishers has elapsed.
The Consortium will ensure open access to the publication within a maximum of
six months. CITADEL partners have the liberty to choose the repository where
they will deposit their publications, although Open Aire – compliant and Open
Aire - indexed repositories such as Zenodo [5] will be favoured. The partner
TECNALIA will use its own repository, already indexed by Open Aire.

For the case of the scientific publications, a persistent identification
number will be provided when uploading the publications to the selected
repository / repositories.

##  Data related to deliverables

For the project’s publications on the website, the naming convention to be
used will be <<Dx.y Deliverable name _ date in which the deliverable was
submitted.pdf>>. All deliverables include a set of keywords and a brief
description that are aimed to facilitate the indexing and search of the
deliverables in search engines.

The deliverables will be stored at TECNALIA’s hosting provider, and for three
years beyond the duration time frame of the project

##  Open Source Software

CITADEL has envisioned following a freemium business model for the ICT
enablers and the CITADEL ecosystem which implies a free version of the
software as well as a premium one. The free versions of the open source
components of the CITADEL ICT Enablers will be released as open source in a
source code repository, namely GitHub, which will be stored at TECNALIA’s
premises.

The free versions of these components will be accessible, findable and
reusable by any developer that is interested in the CITADEL ICT Enablers.
Furthermore, CITADEL will explore the possibility of developers outside of the
consortium to experience with such components, which will ensure the uptake
and sustainability of the software results of the project.

Alongside every software component, a readme file as well as technical
specifications document will be released and made available, and in addition
the docker script so as to be able to deploy the container in any desired
infrastructure.

#  Allocation of resources

CITADEL does not envision an additional need for beyond the duration of the
project to handle data or making the data fair. As expressed before, open
access repositories will be favoured.

In the case of open source software, the partner TECNALIA will ensure that the
github repository is available after the project duration, either by keeping
it in its own premises or by transferring it to existing open source projects
and communities, such as JoinUp [7].

#  Data Security

CITADEL will develop the ICT enablers adhering to the security – by – design
and privacy – by design principles that allow the security and audit standards
to remain consistent across multiple environments.

Furthermore, as part of the CITADEL Security toolkit (KR7) and the overall
CITADEL ecosystem (KR8), the following components are at this stage foreseen
in the architecture (see next figure):

  * 1) Access Management, which grant authorized users the right to use a service, while preventing access to non-authorized users of CITADEL; 

  

  * 2) Credentials Management to manage credential information such as user names and passwords, and 

  

  * 3) Anonymization, which is responsible for removing personally identifiable information from user data or pseudonymizing the personally identifiable information. 

  

**Figure 3.** Security components envisioned in the CITADEL ecosystem as part
of the ICT Enablers

Moreover, CITADEL will ensure that the General Data Protection Regulation
(GDPR), which will enter into force in May 2018, is ensured, especially in
regards to protection of private data. The security components shown above
will be implemented with that principle in mind.

#  Ethical Aspects

The basis of ethical research is the principle of informed consent. All
participants in CITADEL use cases will be informed of all aspects of the
research that might reasonably be expected to influence willingness to
participate. Moreover, project researchers will discuss before and after each
practical exercise (e.g. interview, co-creation session, etc.) to maintain on-
going consent. Participants will be recruited by each organization leading the
use cases (VARAM, ICTU, Stad Antwerp, and Regione Puglia) and other supporting
organizations (e.g. InnovaPuglia, FINCONS) and will cover more than one type
of citizens. If participants wish to withdraw from the participation in the
use cases at any time, they will be able to do it, and their data, even the
pseudo-anonymized data, will be destroyed.

A specific task has been included in CITADEL to ensure that ethical principles
are used throughout the use cases, which are clustered together for management
purposes in the work package related to the use cases (WP5). This task
involves the performance of a privacy impact assessment per use case.

CITADEL also has a task dedicated to analyse technical and operational issues
related to privacy, and identify suitable solutions to be included in the
CITADEL framework. Furthermore, CITADEL has as one of the key results to be
delivered a Security Toolkit, which looks for the application of security-by-
design and privacy-by-design principles

#  Conclusions

This deliverable has presented the plan for the management of data in the
CITADEL project. In this action, several types of data will be collected and
generated. Specifically, we envision that there will be five different types
of data, namely data coming from the use cases, from the metadata analysis to
be performed in the social sciences work packages, from publications,
deliverables and open source software. This data will be anonymized or pseudo-
anonymized using, when relevant, an anonymization engine as part of the ICT
enablers to be developed. In the event this engine cannot be used, such as in
surveys to civil servants or directly to the citizens, manual anonymization
techniques will be used. A combination of real data coming from the different
Public Administrations with fictional but relevant data will be sought. GDPR
compliance will be ensured.

All data and metadata generated will follow machine readable formats, such as
CSV, RDF or JSON.

Data from the use cases will be stored in the use cases’ premises fulfilling
the relevant legislations. Data from publications will be stored in Open Aire
indexed repositories favouring the green model whenever possible. Other
publications such as deliverables will be stored at TECNALIA’s hosting
services.

This deliverable will be updated in subsequent releases, namely in M12, M24
and M36 as part of the technical reports. It is envisioned that in those
versions the aspects that at this stage are not fully clear (e.g. naming
conventions, versioning, dataset size) will be clarified as work progresses in
all the work packages.