#  EXECUTIVE SUMMARY

##  PRESENTATION OF THE DOCUMENT

This document presents the plan for the management of the generated and
collected data from the HOLA CLOUD project; the main purpose of the Data
Management Plan (DMP) is to support and monitor the data management life cycle
for all data that will be collected, processed or generated by the project. In
order to comply this purpose, the DMP has to provide an analysis of the main
elements of the data management policy used during the project.

One of the main objectives to achieve during the life of HOLA CLOUD project is
to increase the visibility of scientific outcomes from projects and
researchers and experts to other projects and people in the same area, as well
as to other stakeholders by continuing with the creation and implementation of
the on-line searchable joint knowledge repository. Therefore, data collection,
sharing and storing is crucial for its achievement. This document will enable
to identify and monitor the main aspects regarding the management of data.

This document is composed of a brief introduction of the deliverable,
reminding the main specific objectives. After that we will briefly introduce,
define and describe the main data sets collected and generated during the life
time of HOLA CLOUD, having identified the target audience to whom will be
useful. Later on, we will go in deep in the standards utilised for the key
aspect of the project, metadata. Then, we will carry on with the nature of the
data sharing and finally we will describe our strategy for data storing.

##  OBJECTIVES OF THE DELIVERABLE

A short description of the D5.5 (DMP), as stated in the Guidelines on Data
Management:

_“A DMP describes the data management life cycle for all data sets that will
be collected, processed or generated by the research project. It is a document
outlining how research data will be handled during a research project, and
even after the project is completed, describing what data will be collected,
processed or generated and following what methodology and standards, whether
and how this data will be shared and/or made open, and how it will be curated
and preserved. The DMP is not a fixed document; it evolves and gains more
precision and substance during the lifespan of the project”._ The scope of
this document is to define and describe:

  * Data set that will be generated or collected, by identifying their origin, nature and scale, and its potential targets. 

  

  * Standards on which data are based. 

  

  * Data sharing, by identifying how data will be shared in order to outline technical mechanisms for dissemination and definite its access. 

  

  * Repository where data will be stored. 

  

  * Procedures that will be put in place for long-term preservation of the data, by indicating how long the data should be preserved. 

  

#  DATA SET DESCRIPTION

##  COLLECTED DATA SET

In continuation with our past efforts to create a sustainable knowledge
repository from R&D or Innovation projects in the area in order to radically
increase the searchability of documents generated by EU projects and expert
search experience, we will collect and index metadata mainly from

  * Scientific reports 

  

  * Conference proceedings 

  

  * Articles 

  

  * Newsletters 

  

  * Project deliverables 

  

Furthermore, in order to capture the entity recognition we need an accurate
affiliation parser (University, Department, Lab), contact information, name,
location. This is based on a proprietary algorithm, trained with thousands of
labelled datasets to achieve high precision for this task and domain.

The purpose is to build an interface that provides technology insights, and
show this R&D data in a visual and intuitive way, by generating expert
profiling, hot-spots profiling (companies and academic institutions) and
visual picture of the search (i.e. text clustering).

The collection and re-using of the metadata make us offer unique opportunities
in terms of searchability, to really help people find and understand each
others’ research, share their knowledge and create the needed ground for
effective collaboration. We have also designed the repository for the
permanent storage of a particular/most valuable knowledge source from
projects: their public deliverables.

###  Stakeholder Database

HOLA CLOUD partners have access to multiple distribution lists of relevant
organisations and stakeholders who will be involved in contributing to the
dissemination of the project. In addition, several consortium members have
developed in the past databases of key ICT related stakeholders, which will be
used to attract support and recruit target stakeholders in order to increase
this database.

##  GENERATED DATA SET

###  Co-authored Roadmap

One of the main focuses of the Scientific Conferences, especially for the
second edition (Cloud Forward 2016), will be to activate the process for a co-
production of a shared Roadmap, which should set mid/long terms R&D priorities
of the areas of software, services and cloud computing. This Roadmap will be
the result of the cooperation of the winners of the selection of papers for
each edition of the Conference to be run during project lifetime.

Therefore, this Roadmap that will include:

  * A vision document, depicting the scenarios of deployment and use of cloud infrastructures and services in the next years, with a vision towards 2030 

  

  * A position paper, expressing the opinion of the co-authors about the actual challenges that the technology providers have to face in the coming years, the support that the EC and other public bodies can provide to the growth of the sector, the obstacles that should be overcame, etc. 

  

Thus, this roadmap will thereby help guiding the industry in search for new
trends and products for the future that they can develop based on state of the
art European knowledge of today. This outcome will be a final result from the
second year’s conference, having the first edition for starting to compile the
baseline state-of-the-art and first identification of long-term technological
trends. In this context, contribution requests, contribution types, processes
and outcomes will be set in place and optimized for the second conference.

LKN focuses on "fresh" research data to provide technology insights, as
opposed to other tools like Google Scholar, Scopus (Elsevier),Thomson-Reuters
or Inno360 who focus on "old data": publications and patents. The purpose is
to bring the most value to user, for which LKN is building the biggest "fresh
research data" database, by focusing on conferences, grants (R&I projects in
software, services and Cloud computing) and related software, publications and
metadata

###  Data Journals Development

In order to increase the awareness on joint knowledge, we will generate data
journals development from metadata collected. The data journals annotation
will be based on models extending the Unidata’s Common Data Model (CDM) and
the Dryad Metadata Application Profile, including parameters such as topic,
area, dataset source type (real-world vs. synthetic), level of noise,
popularity (e.g., number of views, number of downloads), associated research
topics, citation source (i.e., which researchers have used this dataset),
among others. Based on this annotation, the data papers are semantically
linked with research papers and could potentially be searchable through a
variety of ways. Moreover, the research trends service feeds this one by
proposing candidate topics for the data journal.

###  Data target audience

Data from the HOLA CLOUD project will benefit the following stakeholders:

  * **Researchers** , interested in increasing the academic merits by participating in the Scientific Conference and publishing their work in high-quality proceedings with a renowned publisher 

  

  * **Industrial players,** in search for new trends and products for the future. Even though the roadmap resulting from International Conferences is generated based on research, experience shows that it will take three to five years to turn research prototypes into innovative products. Thus, this roadmap will thereby help guiding the industry in search for new trends and products for the future that they can develop with state of the art European knowledge of today. 

  

  * **Related EU funded projects** , interested in the discovery functionalities foreseen for the on-line platform and in contributing to the roadmapping also through joint-publications from different projects 

  

The data project are also useful for:

  * **Policy makers** , interested in the roadmapping co-authored exercise and its relation to public support to European R&D and Innovation in Cloud and services 

  

  * **Brokers** (intermediaries), interested in the discovery functionalities foreseen for HOLA CLOUD on-line plaform 

  

  * **Media, publication editors** , also interested in the proceedings from the Scientific Conference and the features from the advanced services within the on-line platform. 

  

#  STANDARDS USED

The key to success in providing the appropriate information to support the
objectives of HOLA

CLOUD is metadata. The project uses as its basis CERIF (Common European
Research Information Format which is an EU Recommendation to Member States).
The EC requested euroCRIS (www.eurocris.org) to maintain and develop CERIF
since 2002. Although originally designed as a data model for research
information – where it is used in 43 countries – CERIF has found wide usage in
many domains since it is rather general. It covers objects such as project,
organisation, person, publication, product (dataset or software), patent,
facility, equipment, event and many more - in fact the set of entities
required for managing research information whether for reporting, management
decision-making or inquiry and analysis. Instances of entities are related by
linking relations which have role (e.g. author) and start and end date/time.
From CERIF it is possible to generate many of the well-known metadata
standards such as DC (Dublin Core) or CKAN (Comprehensive Knowledge Archive
Network) and in a geospatial environment INSPIRE, yet also point to more
detailed, specific, domain level datasets that are of specialised usage. CERIF
forms the lowest common level across many kinds of data. In this sense it is
trans-disciplinary.

CERIF is widely used. It has entities and attributes appropriate for recording
information on legalistic and economic aspects of research entities
particularly datasets, publications, patents and products. As such it is
positioned to assist in interoperation and homogeneous access over
heterogeneous sources of information. CERIF has been adopted by the EC Project
OpenAIREPlus concerning research publications, datasets and their evaluation
and is used for interoperation in ENGAGE and EPOS-PP. In this context it is
also being considered within RDA (Research Data Alliance) especially through
the three groups working on metadata which all have euroCRIS representation as
co-chairs. The potential further standardisation of CERIF is also being
discussed with W3C.

In the domain of HOLA CLOUD it is notable that key sources of information use
CERIF namely OpenAIREplus (providing information on H2020 projects, and their
outputs using OpenAIRE and DRIVER, the ERC management system and many systems
of funding agencies or universities and research institutes throughout Europe
(and wider). The advanced metadata is thus based on an existing standard.

HOLA CLOUD utilises a more advanced version of CERIF than that used by
OpenAIRE thus permitting more complex analysis. Unlike OpenAIRE which harvests
metadata from open access repositories (almost all with scholarly
publications; OpenAIREplus will also harvest datasets), HOLA CLOUD will
interoperate with a wider range of sources and wider range of metadata
standards. Thus HOLA CLOUD will have as its central information base a richer
metadata description of more sources.

However, depending on the requirements of HOLA CLOUD extensions to CERIF may
be proposed to accommodate those requirements. In particular one would expect
extensions in domain-specific vocabularies (CERIF manages its own ontology)
and additional entities and attributes may be required. CERIF provides a well-
defined extension mechanism.

Thus we take advantage of solid previous work and use it for this novel
purpose, but also allow for and expect further advances which will benefit not
only the particular objectives of the project but also more widely. euroCRIS
provides the expertise on the CERIF model and its usage including changes and
developments and the provision of any necessary convertors between metadata
formats.

CERIF has some novel concepts. In particular it distinguishes base entities –
such as person or project – from linking entities which relate instances of
base entities together. An example would be Person X is author of Publication
P or Person X collaborates with Person Y. Moreover these linking entities also
cover the role (e.g. is author of) and temporal validity. This provides a very
rich semantics for managing research information. Furthermore, CERIF separates
the syntax (structure) of the data used as metadata from the semantics
(meaning) by having a semantic layer. This functions as an ontology and is
interconvertible with OWL and SKOS (W3C recommendations). However, having the
ontology integral with the data and using relational or other database
technology provides advantages in performance over traditional ontologies.

CERIF is natively multilingual with all text attributes being repeatable in
different languages.

#  DATA SHARING

This project aims at introducing and piloting a holistic approach to the
publication, sharing, linking, review and evaluation of research results,
based on the open access to scientific information. Towards this direction, it
pilots a range of novel services that could alleviate the lack of structured
data journals and associated data models, the weaknesses of the review
process, the poor linking of scientific information, as well as the
limitations of current research evaluation metrics and indicators.

In order to improve the searchability of documents generated by EU projects
and expert search experience in general, and to enable an efficient data
sharing, we will focus on overcome the major barrier for researchers: entering
data, particularly metadata. To achieve this purpose, HOLA CLOUD will automate
as much as possible of the processes and procedures.

  * By harvesting from pre-existing systems (that are already integrated into the workflow of users) one major obstacle is overcome. 

  

  * By using a canonical metadata format (CEIF) that is a superset of the other commonly-used formats ingestion is automatic and, if required, we can generate those other formats for interoperation. 

  

  * CERIF is designed to be extensible and if HOLA CLOUD requirements indicate further entities or attributes are needed it can be extended transparently while preserving backward compatibility. 

  

HOLA CLOUD will generate profiles for the researchers (and institutions:
research groups, labs and companies) so that they will only have to "claim"
them, not create them.

HOLA CLOUD will implement a periodical update of the experts’ profiles with
the "fresh" metadata that they generate from new reports, project results and
deliverables, conferences proceedings, etc. This up-to-date data is the most
important for other researchers and especially for SMEs and companies.

##  SEARCH ENGINE

Because of the physical level, and given the constraints imposed by the
agreement objectives (an scalable and distributable architecture to leverage
search with high performance) we will not use a traditional DataBase. As
specified on the proposal we will use fault tolerant high efficient search
architecture in top of ElasticSearch, a distributed, open source search and
analytics engine, designed for horizontal scalability, reliability, and easy
management.

##  CONFERENCE PROCEEDINGS

The contents of CF2015 proceedings (i.e. list of accepted papers) are shown in
deliverable D3.3. All accepted papers, including the preface and the
consolidated paper (expressing the positions of authors of accepted papers)
are online as open access, these are available on the corresponding Elsevier
repository. For CF2016 proceedings and the co-authored Roadmap publishing, we
will follow the same open access strategy, although we are currently exploring
other publisher alternatives.

Page  
  
<table>  
<tr>  
<th>

**PRESERVATION**

</th>  
<th>

[DR1]

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

#  DATA ARCHIVING AND

One of HOLA CLOUD value propositions is the storage of H2020 project reports,
deliverables and R&D results, as opposed to the fragmentation that exists
today (each project has its own website) and temporarily. HOLA! Digital
Library started storing and tagging public deliverables from around 40 FP7
projects in the area (even some FP6), which proves the need for a permanent
repository for these documents, since some of the websites for those projects
are not alive any longer (data is lost after 2-4 years since those webs stop
maintenance), and Hola Portal is now the place to find them. In continuation
with this effort, the searchable knowledge repository and all its services
will be integrated into HOLA CLOUD on-line platform.

Storing documents requires computing power, cleaning data and structure it,
and therefore, resources. And storing documents to be able to access them for
a search engine fashion is even more demanding since information retrieval
needs to be very fast-, e.g. servers with high RAM requirements are needed and
the database structure needs to be optimized among other parameters. It could
happen that requirements go beyond available resources for the project.

In order to have this under control, Linknovate will monitor while
implementing, by reassessing every month. Linknovate has previous experience
at building a very similar metadata database for their search engine (
_www.linknovate.com_ )  .

One of the most successful technologies uses nowadays for indexing, search and
store is Lucene. Lucene enables fast indexing and searching using inverted and
direct files, and makes transparent to the user the management of the document
fields. However, our search engine needs some features such as scalability,
distributivity, entity-relationships that are not possible with Lucene.

For these reasons, we decided to work with ElasticSearch. ElasticSearch is a
distributed, open source search and analytics engine, designed for horizontal
scalability, reliability, and easy management. ElasticSearch relies on Lucene
as final storage solution but enables a much larger range of possibilities.
Moreover, the use of this technology will allow the dynamic adding of entity
types and entity attributes to our models, enabling the future use of a more
ample set of the CERIF standard when new kind of information arrives to the
system.

During HOLA CLOUD project Linknovate will be in charge of the preservation and
storing of metadata. In order to achieve it, 50.000 € of the budget will be
allocated in concept of hosting costs for HOLA Cloud on-line platform,
estimated considered standard rates for platforms functioning as a search
engine and storing an important volume of files and metadata.

Page