PROJECT SUMMARY

#  IV. PROJECT SUMMARY

The LOFAR4SW design study addresses all conceptual and technical aspects
required to upgrade the LOFAR radio telescope, system-wide, to take on a
parallel role as a highly innovative new facility that enables large-scale
monitoring projects generating unique data for the European (and worldwide)
space weather research community, with great downstream potential for improved
precision and advance warning of space weather events affecting crucial
infrastructures on earth. The LOFAR4SW facility will be a powerful research
infrastructure that will allow scientists to answer many important questions
with regard to the solar corona, the heliosphere, and Earth’s ionosphere. The
term “space weather” covers the effects that the Sun has on the Earth,
including: direct powerful electromagnetic emission as a result of, for
example, solar flares; the continuous, but highly variable, outflow of hot
plasma known as the solar wind, carrying with it the interplanetary magnetic
field through the heliosphere; and large ejections of solar material known as
Coronal Mass Ejections (CMEs). These conditions drive processes in the Earth’s
magnetosphere and ionosphere which can strongly affect many technologies upon
which we now rely, including satellite operations, telecommunications,
navigation systems and power grids. Reliable prediction of space weather,
necessary to provide sufficient warning for effective counter-measures against
its effects on human technology, requires a full understanding of the physical
principles driving material from the Sun out through interplanetary space, and
the resulting dynamical impact on the magnetosphere and ionosphere. Ground-
based remote-sensing observations, coupled with sophisticated analysis and
modelling techniques for further physical understanding, are of critical
importance to space weather science and forecasting capabilities.

The overarching objective of the LOFAR4SW design project is to prepare fully
for subsequent implementation of a timely and efficient upgrade, and an
expedient start of operations.

#  V. EXECUTIVE SUMMARY

This deliverable is related to the Task 8.4 Project Data Management, which
comprise of the following subtasks:

  * T8.4.1. Data Management Plan: creation of this document along the lines of the “Guidelines on FAIR Data Management in Horizon2020” provided by EC (20 July 2016). 

  

  * T8.4.2 Manage data according to the DMP: management and activation of project participants to populate and update the repositories. 

  

The primary goal of this document is to present how the data will be handled
during the course of the project and after the project completion.

#  1\. Introduction

The LOFAR4SW is the part of the Open Research Data Pilot, which means that
data produced in the frame of this project will be generally available with as
few restrictions as possible, if any. This document describes how the data
will be handled during the project and after the project is completed. Figure
1.1 below presents the Data Management Plan scheme.

Figure 1.1 Data Management Plan Scheme.

Following the ORDP requirements, this document comprises the following
aspects:

  1. The data set: defines and describes the data collected/generated in the project, as well as to whom the data might be useful. 

  

  2. Standards and metadata: describes the data content, applied types, formats and standards. It is desired that the scientific data (if any will be produced) are interoperable and can be accessed via queries from other platforms (e.g. VO). 

  

  

Data types, formats, standards

  3. Data sharing: describes the licenses and policies under which the data are accessible, although desired policy is an Open Access. It also defines the user, to whom the data will be available. 

  

  4. Archiving and preservation: describes long-term storage and data management, including data curation. It ensures that data are FAIR. 

  

  5. Budget: this point will be especially important to ensure that the data are available, reusable and accessible not only within the project time frame, but also after the project is completed. 

  

  

#  2\. Data types, formats, standards

##  2.1 Scientific datasets

A basic requirement of the LOFAR4SW facility will be to provide easily
accessible, open-access space weather science data products to the community.
This functionality will require designing an update of the Data Distribution
Module of the LOFAR system software. The design for the curation and
dissemination of LOFAR4SW observatory data products through the Science Data
Centre will largely build on existing and freely available concepts such as
the Virtual Observatory. This issue will be described in more detail in the
deliverable D6.8 - Final Science DMP.

##  2.2 Documentation

During the course of the project it is envisaged to deliver detailed and
extensive documentation related to the software and hardware development,
completed milestones, produced deliverables, reports and others. Documentation
will be internally reviewed by all project partners.

It is expected that LOFAR4SW documentation will consist of various types of
documents as listed below:

  * public/confidential reports 

  

  * technical/scientific publications 

  

  * project presentations and posters 

  

  * user guide 

  

  * training materials ● data policy. 

  

The list is not closed and will be modified during the course of the project.

All released documents that have public access rights will be available in one
of the recommended formats (preferably in PDF format) on the main project
website Metadata

( _http://lofar4sw.eu_ ). The documentation with confidential access rights
will be available to the project partners via Redmine. Documentation before
final release are also treated as restricted to the project partners.

The documentation under preparation may be distributed among project partners
via selected sharing platform (see Annex B) in order to allow efficient joined
edition.

An additional type of the project documentation will be entries in social
media. The community will be informed about important updates and events
related to the project also via the project Twitter account (
_https://twitter.com/lofar4sw/_ ). This will be used to provide in an
accessible way project progress to wide community using popular social media.
The selected person from the project will be responsible for maintaining and
updating content published on the platform.

##  2.3 Software

LOFAR4SW project will design software dedicated to support/handling new
functions of the upgraded LOFAR stations and new data processing pipelines to
produce high-quality space weather science data products. Part of the software
and software documentation related to the key technical-level functionality of
the LOFAR infrastructure is expected to be confidential. However documentation
and materials related to the data processing pipelines software prototypes
accessible to users, will remain publicly available at the end of the project
via the project website (or other sharing platform).

#  3\. Metadata

##  3.1 Standards and formats

Metadata is a set of a data that describes and gives information on the data.
The queries submitted by the user can be against metadata not against data
itself. Since metadata are smaller in size then the data it describes, using
metadata helps to resolve the queries more effectively and more efficiently.

This part is mainly related to scientific data and will be described in more
detail in deliverable D6.8 - Final Science DMP

##  3.2 Data description

Data description should contain information the user will likely search for,
by submitting a query. Regarding the data type the information stored in
metadata will be as follows:

  1. Scientific datasets (if any produced during design study) are expected to be compliant with: 

    1. Dublin Core standards 

  

    2. SPASE data model 

  

    3. ISTP 

  

    4. IVOA 

  
  

  

  2. Documentation: 

    1. Dublin Core standards 3) Software: 

  
  

    1. name 

  

    2. purpose (what it can do?) 

  

    3. input (what has to be added, submitted to use the software?) 

  

    4. output (ex. output format(s)) 

  

    5. authors 

  

    6. copyrights, policies of using the software 

  

    7. version 

  

    8. software inline documentation (comments): e.g. Sphinx for python code. i) etc. 

  
  

  

  

#  4\. Data exploitation, sharing and accessibility

##  4.1 Licenses and access rights

We distinguish two types of access rights that can be applied to the data
derived in the LOFAR4SW project. These are:

  * public: 

  

○ are available with no restrictions;

○ public data can be obtained via project website or other sharing platform
(see annex B); ● confidential:

○ confidential data are available only for the limited group of users, in this
project mainly it means the data restricted to the project participants or
selected persons cooperating within the LOFAR4SW project.

LOFAR4SW project will use for produced results and documentation licences
including:

  * Documentation is by default licensed under CC-BY-NC-SA (this should be specified in each document). 

  

  * Codes developed in the project are recommended to be licensed under GPLv3 license. 

  

Documents written on the basis of the selected CC license may be made
available to third parties under other selected licenses after agreement.

All other changes and additions to licensing rules will be updated during the
project.  
  
<table>  
<tr>  
<th>

DATA TYPE

</th>  
<th>

FORMAT

</th>  
<th>

ACCESS RIGHTS

</th>  
<th>

LICENSE

</th>  
<th>

USER

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

DOC

</td>  
<td>

\- PDF,

-any other readonly formats 

</td>  
<td>

public

</td>  
<td>

CC BY-NC-SA

</td>  
<td>

regular user, anonymous user

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

DOC

</td>  
<td>

-any editable formats, -any read-only formats 

</td>  
<td>

confidential

</td>  
<td>

CC BY-NC-SA

</td>  
<td>

PP

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

STW

</td>  
<td>

executable version

</td>  
<td>

public

</td>  
<td>

GPLv3

</td>  
<td>

regular user

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

STW

</td>  
<td>

-any editable formats, source codes, -executable formats 

</td>  
<td>

confidential

</td>  
<td>

GPLv3

</td>  
<td>

PP

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

Table 4.1. Overview of the data types produced during the LOFAR4SW project
with their access rights and licences.

##  4.2 User definition and privileges

The user privileges will be fit into sharing data platform capabilities, like
www, ftp network services, other. By the default we can recognize the standard
structure of users:

  1. administrators 

    1. system administrator 

  

    2. system operator 

  

    3. data administrator 

  
  

  

  2. users 

    1. registered user (mainly Project participant) 

  

    2. registered anonymous user 

  

    3. anonymous user (read only access) 

  
  

  

  

At the beginning of the project, only the persons invited by the project
consortium will be able to receive the registered user or registered anonymous
user privileges.

In order to meet the requirements introduced by The General Data Protection
Regulation (GDPR), LOFAR4SW will be using platforms where appropriate
procedures are provided on the protection of natural persons with regard to
the processing of personal data (see annex B). In the case of accessing
confidential data via the project website, solution of single anonymous user
with password was chosen (registered anonymous user). Username and password
will be distributed to all those involved via the email.

The standard user privileges are presented in table below:  
  
<table>  
<tr>  
<th>

privileges/ roles

</th>  
<th>

administrators

</th>  
<th>

</th>  
<th>

users

</th>  
<th>

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

system

administrator

</th>  
<th>

system

operator

</th>  
<th>

data

administrator

</th>  
<th>

registered user

(Project participant

)

</th>  
<th>

registered

anonymou s user

</th>  
<th>

anonymo us user

(read only access)

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

maintenance

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

system software installation

</td>  
<td>

yes

</td>  
<td>

only plugins

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

system software update

</td>  
<td>

yes

</td>  
<td>

only plugins

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

system software remove

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

system software configuration

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

system backup

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

user/group add/remove/edit

</td>  
<td>

only system

operators

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

user/group permissions to data

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

data metadata editing

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

yes

(limited)

</td>  
<td>

yes

(limited)

</td>  
<td>

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

data upload

</td>  
<td>

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

(limited)

</td>  
<td>

</td>  
<td>

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

data download/view

</td>  
<td>

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

yes

(limited)

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

data remove

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

yes

(limited)

</td>  
<td>

</td>  
<td>

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

feedback

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

yes

</td>  
<td>

yes

</td>  
<td>

yes

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

##  4.3 Sharing platform

This section presents how the data will be handled, how it will be shared with
the user and what tools will be used in the sharing process. The section
describes the communication ways and tools between the project and the user.
LOFAR4SW project will use different sharing platforms, depending on the type
of data being shared.

Project website

The main platform that is already in use is the project website. It is
designed to be used by all users under Open Access license, although some
website content, that are sensitive information, may be accessible for the
limited group of users under certain conditions. It allows (or will allow as
the project evolves) for the following actions:

  * learn about the project, products and updates, 

  

  * forward to the project Redmine platform, 

  

  * search a content, 

  

  * download the documentation (not yet available), 

  

  * log in/register (not yet available), 

  

  * access to the software facility (not yet available), ● submit a query (not yet available). 

  

Redmine platform

Redmine is dedicated for the project participants at the current stage, since
it contains sensitive information. Its purposes is to make the project
management more efficient and effective as well as to boost communication and
exchanging information within the project. It allows for the following
actions:

  * creation and assignment of the tasks, 

  

  * controlling the time schedule for milestones and deliverables, 

  

  * time schedule for teleconferences and meetings, 

  

  * storing/uploading/downloading important documentation. 

  

ftp/torrent

This two platform are proposed as an alternative for the project website for
sharing large volume data or handling more complex user queries. It allows for
the following actions:

  * query submission, ● data upload/download. 

  

other

The list of recommended platforms is presented in Annex B and may change
during the implementation of the project.

##  4.4 Data Workflow Scheme

This section presents the relation between different components: between the
data, software, repository and the user.

In the current phase of the project only an overview of the data flow is
presented and to whom the data will be available. More detailed scheme will be
delivered at the final project Data Management Plan, when data provided by the
project will be well defined.

Figure 4.1 An overview of Data Workflow Scheme.

##  4.5 Publication Policy

Dissemination of the findings/upgrades/progress of LOFAR4SW project may go by
a different channels including:

  * Journal articles 

  

  * Conference proceedings articles 

  

  * Books or book chapters 

  

  * Technical reports 

  

  * Published patents 

  

  * Published abstracts 

  

  * Invited or contributed talks 

  

  * Popular articles 

  

  * Press reports 

  

In all publications, policy is that the list of authors include all persons
who contributed significantly to the result under discussion. It is not
expected that all project partners, who

Archiving and preservation

had minor participation in, will be included as authors. However, it is
required that one representative of each project partner will be acknowledged
in the general ‘publications’ describing the main goals and concepts of the
LOFAR4SW project. It is also required that all public written materials
include an acknowledgement statement about project funding source; see below.

The research leading to these results has received funding from the European
Community’s Horizon 2020 Programme H2020-INFRADEV-2017-1under grant agreement
777442.

In the Horizon 2020 program, open access is an obligation for scientific peer-
reviewed publications.

The 2 main routes to open access are:

  * Self-archiving / 'green' open access – the author, or a representative, archives (deposits) the published article or the final peer-reviewed manuscript in an online repository before, at the same time as, or after publication. Some publishers request that open access be granted only after an embargo period has elapsed. 

  

  * Open access publishing / 'gold' open access - an article is immediately published in open access mode. In this model, the payment of publication costs is shifted away from subscribing readers. The most common business model is based on one-off payments by authors. These costs, often referred to as Article Processing Charges (APCs) are usually borne by the researcher's university or research institute or the agency funding the research. In other cases, the costs of open access publishing are covered by subsidies or other funding models. For more information please visit: 

  

_http://ec.europa.eu/research/participants/docs/h2020-funding-guide/cross-
cuttingissues/open-access-data-management/open-access_en.htm_

#  5\. Archiving and preservation

Archiving and preservation aspects are summarised in the Table 4.1 below.  
  
<table>  
<tr>  
<th>

ASPECT

</th>  
<th>

DESCRIPTION

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

Curation

</td>  
<td>

Adding value through the data life cycle to ensure:

  * interoperability, 

  

  * necessary upgrades, 

  

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

Preservation

</td>  
<td>

Ensures:

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

Budget  
  
<table>  
<tr>  
<th>

</th>  
<th>

  * the data can be used/reused in the future, 

  

  * data can be easily interpreted in the future, ● data sharing, 

  

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

Archiving

</td>  
<td>

Ensures:

  * the data are secured and well protected, 

  

  * sharing policy and licenses are followed, 

  

  * the appropriate references are preserved, 

  

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

Storage

</td>  
<td>

All hardware and software needed to ensure:

● restoring the data, ● sharing the data, ● data backup.

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

Table 4.1 Archiving and preservation aspects.

#  6\. Budget

To guarantee the data availability, reusability and accessibility not only
within the project time frame, but also after the project is completed,
LOFAR4SW will be looking for solutions that are either external, open access
and ensure long term accessibility, or platforms developed and applied within
the framework of LOFAR and ILT activities with assured budget.

In Annex B a list of platforms, in line with EC policy, recommended for
sharing data is presented.