**_a) What types of data will the project generate/collect?_ **

The project generates different forms of data, which can be separated in the
following sections:

#  Generic research data (process description and communication data)

  * **Sources and resources** : collection of external references, studies, papers and openaccess material from other research projects, individuals, as well as related contexts 

  

  * **Articles and commentary** on related topics, research and overview of the larger field of research, such as open source cinema, open hardware 

  

#  Specific research data (outcomes)

  * **Code** (software) in various formats 

  

  * **Technical and functional plans, drawings & 3D-Models ** (CAD) 

  

#  Documentation

  * **Texts and articles:** documentation of processes and products of the main research 

  

  * **Photography** of processes, dissemination events, status 

  

  * **Video Communication** : updates for the (scientific) community, other developers as well as the interested public (title: apertus° Team Talks). 

  

#  Demonstrations

\- Demonstration footage from the camera prototypes - Tutorials

#  Research Papers and articles

\- Academic papers and articles about research outcomes and other aspects (not
pure technical benefits) of Open Hardware  
  
<table>  
<tr>  
<th>

**Title**

</th>  
<th>

**Types of data**

</th>  
<th>

**Dissemination**

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

Generic research data

</td>  
<td>

various

</td>  
<td>

Blog, Social Media, Wiki, Mailing List

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

Specific research data

</td>  
<td>

source code, technical plans and technical drawings

</td>  
<td>

Phabricator, Wiki, Github

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

Documentation

</td>  
<td>

text, photo, video

</td>  
<td>

Blog, Wiki, Social Media

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

Demonstrations

</td>  
<td>

video footage

</td>  
<td>

Repository

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

Research papers and articles

</td>  
<td>

text and pdf

</td>  
<td>

Blog, academic repositories

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

_b) Which standards will be used?_

The project focusses mainly on open standards, since this an integral part of
the nature of the project. All outcomes, including documentation and research
data produced will be released under open licenses. Public release of all
AXIOM project research data and results are published under a free licence
(GNU GPLV3, CERN Open Hardware Licence 1.2, GNU Free Documentation License

1.3).

AXIOM will open everything from the beginning. All of the hardware (including
optical and mechanical parts) and software produced in the course of the
project (including all knowledge/ know-how generated during our research and
development stage) will be made public and available on the Internet. It will
be open for anyone to access without registration ('gold' open access).

Output data is separated into Open Formats and Public Formats: _Open Formats_
are used for internal (archival) storage, while _Public Formats_ are used for
dissemination and circulation. Public Formats are often not open (and mostly
not _Free Formats_ ), but are necessary to publish research data on popular
different channels on the Internet.  
  
<table>  
<tr>  
<th>

**Data**

</th>  
<th>

**Format/** **Container**

</th>  
<th>

**Description**

</th>  
<th>

**Approx.**

**size after finished EU project**

</th>  
<th>

**Open Formats**

</th>  
<th>

**Public formats**

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

Photo documentati on

</td>  
<td>

CR, ARW, CR2,

DNG, NEF

</td>  
<td>

Photographic images and documentation throughout the whole project.

</td>  
<td>

400 GB

</td>  
<td>

DNG

</td>  
<td>

JPG,

PNG

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

Video Footage

</td>  
<td>

MOV, AVI, MXF, DNG

</td>  
<td>

demo footage from AXIOM camera, documentation, guides, introduction videos,
communication, events

</td>  
<td>

24 TB

</td>  
<td>

DNG,

Cinema

DNG

</td>  
<td>

MOV,

AVI,

MFX

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

Technical Drawings

</td>  
<td>

DWG, IPT, IAM, STP, STL, etc.

</td>  
<td>

mechanical components and assemblies as 3D CAD models created in various
software tools

</td>  
<td>

5GB

</td>  
<td>

STP,

STL,

AMF

</td>  
<td>

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

Finished Videos

</td>  
<td>

MP4, MOV

</td>  
<td>

finished edited documentation and demonstration videos for publication/
distribution

</td>  
<td>

5 TB

</td>  
<td>

DNG,

Cinema

DNG

</td>  
<td>

h.264/

h.265

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

Illustrations,

Graphic

Designs

</td>  
<td>

PSD, AI, EPS, PDF,

</td>  
<td>

drawings, illustrations for website and publications

</td>  
<td>

10GB

</td>  
<td>

SVG

</td>  
<td>

PDF

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

Animation Source Files

</td>  
<td>

AEP

</td>  
<td>

illustration animations and motion graphics

</td>  
<td>

1TB

</td>  
<td>

\-

</td>  
<td>

\-

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

Texts and

Source

Code

</td>  
<td>

Various

</td>  
<td>

documentation, articles, publications, software source code

</td>  
<td>

1GB

</td>  
<td>

ODF, ASCII

</td>  
<td>

PDF

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

#  Open Standards

The project AXIOM focusses on the use of _Open Standards_ defined as technical
(file) formats which are extensively documented and standardized. As the
general term is used very differently throughout disciplines and contexts, the
project AXIOM relates to the following definitions of _Open Standards_

  * Definition of the Free Software Foundation Europe 

  

  * The definition by OpenStand (joint IEEE, ISOC, W3C, IETF and IAB definition) 

  

While a lot of these formats are under different licenses, the main aspects
describing _Open Standards_ are:

  * freely available specification 

  

  * format based on open specifications and/or standards 

  

  * freely available source-code 

  

  * documented to have no known intellectual property encumbrances or license requirements 

  

Data in the project will be stored in at least one archival format (Open
Format) as well as in at least one _Public Format_ (accessible and popular,
compressed format) for dissemination.

_c) How will the data management be implemented?_

The data management in the project AXIOM consists of a 6-tier system:  
  
<table>  
<tr>  
<th>

#

</th>  
<th>

**Tier**

</th>  
<th>

**Implementation**

</th>  
<th>

**Application**

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

1

</td>  
<td>

Pre-Ingest

</td>  
<td>

gathered data from various sources

</td>  
<td>

data gathering, data validation and selection

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

2

</td>  
<td>

Intranet Raid

</td>  
<td>

ingest to backup: metadata and

classification of data, immediate archival of high-priority data

</td>  
<td>

Classification and description of data, adding of metadata, duplication on
local storage.

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

3

</td>  
<td>

Archival

</td>  
<td>

Long-term archival on LTO-6 tapes (incremental as well as immediate)

</td>  
<td>

Separation of data according to high-priority: instant archival of highly
important data (data which is not redundantly stored yet).

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

4

</td>  
<td>

Storage Cluster

</td>  
<td>

offsite server/storage cluster: preparation of

data for internal project use

</td>  
<td>

Transfer of relevant data to offsite storage cluster for availability to the
whole

consortium. Collection of external sources at the storage cluster. Backup of
storage cluster through regular scheduled backups.

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

5

</td>  
<td>

Cloud collaboration

</td>  
<td>

Project management and collaboration systems

</td>  
<td>

Internal data stored in Google Drive, consortium documents and EU-relevant
information in Phabricator, information for general public and larger team in
apertus wiki.

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

6

</td>  
<td>

Dissemination

</td>  
<td>

publication of data and outcomes

</td>  
<td>

external repositories (github, video hosting, social media, exernal photo
storage, apertus blog and wiki). See details in section b.

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

#  Used hardware for the implementation of the DMP

  * Intranet RAID (local RAID-6 with 24TB storage) 

  

  * Archival computer with LTO-6 tape drive (long-term archival) 

  

  * Storage Cluster with fileserver (research data sharing throughout the team, public availability of research data) 

  

#  Targeting Data Degradation (data decay/ data rot)

As “data degradation” is a key topic of the current discourse in long-term
archival, we decided to use up-to-date filesystems to secure our data. In the
case of file-level-corruption, we decided to work with ZFS and Btrfs file-
systems, which implement integrity-checking and self-repair algorithms to
prevent data rot.

_d) How will this data be exploited and/or shared/made accessible for
verification and re- use?_

According to the 6-Tier system, data will be made accessible according to the
scope of the tier:  
  
<table>  
<tr>  
<th>

1

</th>  
<th>

Pre-Ingest

</th>  
<th>

availability only to responsible team members

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

2

</td>  
<td>

Intranet Raid

</td>  
<td>

local availability at University of Applied Arts

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

3

</td>  
<td>

Archival

</td>  
<td>

local availability at University of Applied Arts

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

4

</td>  
<td>

Storage Cluster

</td>  
<td>

Availability to whole consortium through fileserver (ftp/http). Selected parts
will be made accssesible to the larger audience via a public repository
software.

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

5

</td>  
<td>

Cloud collaboration

</td>  
<td>

Internal data stored in Google Drive, consortium documents and EUrelevant
information in Phabricator, information for general public and larger team in
apertus wiki.

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

6

</td>  
<td>

Disseminatio n

</td>  
<td>

general availability according to the external context.

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

**Backup strategy for external sources**  
  
<table>  
<tr>  
<th>

**External source**

</th>  
<th>

**Max. size**

</th>  
<th>

**Backup to**

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

Github

</td>  
<td>

30GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Additional
redundancy through the nature of git-system; Additional daily pull on Storage
Cluster.

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

Developer FTP

</td>  
<td>

10GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Mirror on Storage
Cluster.

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

Google Drive

</td>  
<td>

20GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Mirror on Storage
Cluster.

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

Apertus° Wiki

</td>  
<td>

15GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Mirror on Storage
Cluster.

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

Apertus° Blog

</td>  
<td>

2GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Mirror on Storage
Cluster.

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

Phabricator

</td>  
<td>

2GB

</td>  
<td>

Incremental pull-backup from archival computer to LTO tape. Mirror on Storage
Cluster.

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

_Public Repository for research data_

A public and self-hosted repository for all the research data will be made
available during the project timeframe and is guaranteed to be hosted after
the Horizon2020 project by the Artistic Bokeh Initiative. Details for the
software used and implementation specifics will be outlined in Version 2 of
the DMP.

  5. _How will this data be curated and preserved?_

  

  

The described policy reflects the current state of consortium agreements
regarding data management and is consistent with those referring to
exploitation and protection of results. Data is curated by team members at the
University of applied arts and will be preserved using current state-of-
technology in data backup and data availability. Mission-critical data is
always stored at least with dual-redundancy at all times, together with the
long-term archival procedures data is avaailable on tripple-redundancy level.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Tier**

</th>  
<th>

**Curating**

</th>  
<th>

**Preservation strategy**

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

1

</td>  
<td>

Pre-ingest

</td>  
<td>

Immediate duplication on Intranet Raid. Selection by WP8 responsible team
members.

</td>  
<td>

Dual redundancy on Intranet Raid and source media.

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

2

</td>  
<td>

Intranet Raid

</td>  
<td>

Definition of initial folder structure and selection by WP8 responsible team
members. Selection of missioncritical data for immediate archival by WP8
responsible members.

</td>  
<td>

Additional redundancy via direct archival (to LTO) for missioncritical data.
Weekly incremental backup to LTO tape.

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

3

</td>  
<td>

Archival

</td>  
<td>

Archival and long-term storage: LTO-6 Tape drive with redundant storage.

</td>  
<td>

Weekly incremental backups, redundant archival of all research data to LTO-6
(storage of physical tapes on two different sites). MDisc for additional
failover.

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

4

</td>  
<td>

Storage Cluster

</td>  
<td>

Selection by WP8 responsible team members.

</td>  
<td>

RAID-6 with ZFS file-system

(tripple redundancy). Backups to LTO tape drive. Additional backup to cloud.

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

5

</td>  
<td>

Cloud collaboration

</td>  
<td>

Selection by whole consortium, responsibility at the project lead.

</td>  
<td>

Pull-backups to Storage cluster and to incremental backup to LTO tape drive.

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

6

</td>  
<td>

Dissemination

</td>  
<td>

External, outsourced storage

</td>  
<td>

Pull-backups to Storage cluster and to incremental backup to LTO tape drive.
Storage of

dissemination results at Google Drive (Cloud Collaboration) as well as
publishing to Phaidra system (University long-term database).

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

**Page**  
  
<table>  
<tr>  
<th>

LTO-6 Drive

</th>  
<th>

Tape Backup Drive

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

M-DISC Drive

</td>  
<td>

M-Disc (Long term storage BluRay discs)

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

Cloud Storage

</td>  
<td>

SpiderOak Cloud Services

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

Local RAID

</td>  
<td>

Synology RAID-System incl. 4x4TB Hard Disks

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

Virtual Server

</td>  
<td>

Virtualized Server (Linux) for dissemination and storage

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

  6. Dissemination of data and project outcomes 

  

  
  
<table>  
<tr>  
<th>

Apertus° Wiki

</th>  
<th>

Internal Hardware/Software documentation

</th>  
<th>

_http://wiki.apertus.org_

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

Apertus° Website

</td>  
<td>

Primary dissemination outlet via project website

</td>  
<td>

_http://apertus.org_

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

External video hosting service

</td>  
<td>

Finished edited documentation and demonstration videos for publication/
distribution.

</td>  
<td>

_http://youtube.com_ _http://vimeo.com_

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

External photo hosting service

</td>  
<td>

Edited photos hosted for maximized availabilty

</td>  
<td>

_http://flickr.com_ _https://_

_commons.wikimedia.org_

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

Social Media

</td>  
<td>

Generic information and texts for wider audience.

</td>  
<td>

_http://facebook.com_ _http://twitter.com_ _http://plus.google.com_

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

Academia.edu

</td>  
<td>

Research papers and articles.

</td>  
<td>

_http://academia.edu_

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

Phaidra

</td>  
<td>

Selected documentation, texts and research content for long-term archival in
Phaidra (Permanent Hosting, Archiving and Indexing of

Digital Resources and Assets)

</td>  
<td>

_https://_

_phaidra.bibliothek.uniak.ac.at/_

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

Cern Open

Hardware

Repository

</td>  
<td>

A place on the web for electronics designers at experimental physics
facilities to collaborate on open hardware designs, much in the philosophy of
the free software movement.

</td>  
<td>

_http://www.ohwr.org_

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

Github

</td>  
<td>

Source code, source files for collaborative development

</td>  
<td>

_http://github.com_

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

#  g) Responsibilities and resources

Data will be collected (Pre-ingest, Intranet Raid) by the lead partner, and
will be selected for archival and storage by the team responsible for WP8
(P1). Data-backup and archival tasks will be undertaken in the facilities of
the lead partner (University of Applied Arts) with support of an external 3rd
party to supervise and consult regarding the technical requirements.

_resources used_

**Page**

#  **Literature list / sources**

e-Infrastructures Austria. (Version 2.0 Mai 2015). Data Management Plan: Eine
Anleitung zur  Erstellung von Data Management Plänen. Retrieved from
_https://fedora.phaidra.univie.ac.at/ fedora/get/o:367863/bdef:Content/get_

European Commission. (2016). Guidelines on Data Management in Horizon 2020
(Version 2.1).  Retrieved from
_http://ec.europa.eu/research/participants/data/ref/h2020/grants_manual/hi/oa_pilot/
h2020-hi-oa-data-mgt_en.pdf_

Open Stand. The Modern Paradigm for Standards. (2015). Retrieved from
_https://open-stand.org/ about-us/principles/_

The GNU General Public License v3.0 - GNU Project - Free Software Foundation.
(2014,

November 8). Retrieved February 19, 2016, from
_http://www.gnu.org/licenses/gpl-3.0.en.html_

GNU Free Documentation License v1.3 - GNU Project - Free Software Foundation.
(2014, April

12). Retrieved February 19, 2016, from
_http://www.gnu.org/licenses/fdl-1.3.en.html_

Johnson, D. (2010, May 14). Is PDF an Open Standard? Retrieved February 14,
2016, from _http:// talkingpdf.org/is-pdf-an-open-standard/_

CERN Open Hardware Licence v1.2. (2013, September 6). Retrieved February 19,
2016, from  _http://www.ohwr.org/attachments/2388/cern_ohl_v_1_2.txt_