Additional requests are recorded comprehensibly in the internal ticketing-
system.

Remote access is possible through a secure VPN access solution and two factor
authentication. Project specific: If required, it is possible to monitor the
changes of data (along with the reason of change provided by the user) by
adding version control to the file repositories. Access rights are managed
within the lifecycle of the project.

#  Risk management

AIT focuses on two aspects of risk management initiatives – user awareness and
preventive technology.

With regard to user awareness several guidelines are defined to support users
in handling data. In addition users are frequently informed about new
developments and threats.

With regard to preventive technology there are several security measures in
place to ensure data protection from unauthorized access.

#  Secure Access and Transfer

Every connection to a data-processing system from a remote location is done by
certificate based authentication and strong encryption methods (e.g. for the
“Online Document Sharing Service”). Secure and safe data transfer is managed
through SSL based protocols (e.g. HTTPs, FTPs, SFTP, SCP) or a virtual private
network.

**Storage and backup (short and mid-term):**

#  Types of data

The available storage space on the file storage is separated by location and
department. Permission for access is claimed comprehensibly over the internal
ticketing system. The permission management is organized with active directory
groups by the central IT.

Specific project initiatives can be handled with higher restrictions or with a
differentiated support.

#  System related backups

Backup of virtual machines, backup of local client data, backup of Linux
systems and full image client backups are designed for disaster recovery, not
for mid-term preservation. On request it is possible to preserve a system for
mid or long term.

#  General backup procedure

Company data is stored for 10 years after the project end, because, according
to the internal AIT-quality management specifications, project data must be
kept for this period.

The central backup procedure in overview:

File-Service: on a regular base data is secured on LTO tapes:

Daily: differential backup, where the LTO tapes are overwritten weekly.

Every Friday: full backup, where the LTO tapes are overwritten each month.
Exception: No overwrite of the last full backup in a month is made. This LTO
tape is stored securely in a data safe (security class EN 1047-1) with
restricted access.

Exchange-Service: daily full backup to disk.

Virtual machine: daily backup to disk of the whole central managed virtual
infrastructure, with an available restore period of the last 7 days. Longer-
term backups have to be requested separately.

SharePoint: daily differential backup and weekly a full backup to a file share
which is kept for 30 days

FTP: no backup needed because it is only used for data exchange

OneDrive for Business: managed, externally hosted (EU) cloud storage solution
for each user for data exchange and project activities with a guarantee of
high availability. Therefore, there exists no centrally managed internal
backup strategy.

Data backup and recovery of the central infrastructure is the responsibility
of the central IT.

Decentralized initiatives can be handled with higher restrictions or with a
differentiated support.

**Archiving and preservation (long term):**

According to the internal AIT quality management specifications, project data
must be stored for 10 years after the end of the project (see above: general
backup procedure). For this period, AIT can guarantee the availability and the
restricted access to stored data for eligible persons. Besides the standard
backup procedure, AIT has no further dedicated central data archiving system.
Because of that, AIT cannot guarantee the unchangeability of stored data. If
necessary, data archiving needs to be executed through decentralized
initiatives.

#  2.1.2 Albert-Ludwigs-Universität Freiburg (ALU-FR)

**MARA data manager:**

Sonja-Verena Albers

**Available / necessary resources:**

We have person specific accounts in which the raw data are saved. These are
backed up at the IT centre of the university. Moreover, we have a NAS (network
attached storage) system in the lab where we make a second copy of the raw
data. For the recording of all experimental procedures, we use an electronic
lab journal at  _http://www.labguru.com/_ .

**Data access and security:**

All the raw data are saved within accounts that are password protected and
also the individual Labguru accounts are password protected. As the lab head,
the MARA data manager, Sonja-Verena Albers, has access to all information
saved on labguru.

**Storage and backup (short and mid-term):**

As described above, the people initially save their raw data in their personal
accounts. These drives are backed-up daily on a server at the IT centre of the
university and in regular intervals to our own NAS system. Moreover,
experimental procedures and results are saved in the personal Labguru
accounts.

As we produce mainly photo files from DNA electrophoresis gels or SDS PAGE
gels, it is not expected that space will be limiting. Only movie files
recorded on our microscope can be larger, but these are stored at the
microscopy computer and also on our NAS system.

Our data can always be retrieved via the IT centre of the university, which
has a security and retrieval procedure at hand.

Experiments documented and finished in Labguru are finished by the executing
person, and then witnessed by the MARA data manager. Then these experiments
have time stamps and cannot be changed anymore. All the data from Labguru are
also saved monthly as a PDF file which is also saved in Sonja-Verena Albers’s
account and on the NAS system.

**Archiving and preservation (long term):**

See above. Once a student leaves, the data are transferred to an account
belonging to Sonja-Verena Albers. And this again is backed up every day as
described above. The Labguru data are always accessible to the MARA data
manager at ALU-FR.

#  2.1.3 Imperial College London (IMPERIAL)

**MARA data manager:**

Morgan Beeby

**Available / necessary resources:**

We currently have a dedicated ~55 tb RAID6 server running Linux Mint 17.2 for
primary data storage. Backup is provided by nightly mirroring this to a larger
server running similar infrastructure in a separate building on campus. Rsync
is used to provide nightly snapshots using crontabs, enabling storage of
different versions of files over a time period. Logs are emailed to me nightly
to assess complete backup. Use of RAID6 means double redundancy of hard
drives, reducing the likelihood of RAID array failure to negligible.

It is likely that we will need to expand this in due course, but currently we
project that this will be satisfactory for the immediate future. Expansion
plans will be to purchase additional server pairs as described.

**Data access and security:**

The MARA data manager, Morgan Beeby, is the only person with superuser access.
As such, he is the only person capable of deleting data. Deleted and altered
files are nevertheless recoverable via our mirroring backup system. We do not
anticipate collaborators having direct access to data on our filesystems and
will rather – if necessary – provide copies of pertinent data to
collaborators.

Servers are housed in dedicated server rooms with restricted swipecard access.

If data is collected at electron microscopy facilities off-campus, data will
be transferred via hard drive by courier (the de facto standard of the field).
The facilities will retain copies of data until confirmed receipt at ICR.

Recovery will be performed manually if/when needed.

**Storage and backup (short and mid-term):**

Described under “Available / necessary resources”. **Archiving and
preservation (long term):**

Data is treated as “permanent”. We anticipate pruning datasets to only
relevant and published data upon attaining appropriate milestones (i.e.,
publication) to avoid storage of irrelevant data.

#  2.1.4 Apta Biosciences Ltd (APTA)

**MARA data manager:**

Yap Sook Peng

**Available / necessary resources:**

Apta has engaged a third party IT vendor (Cordeos Pte Ltd) for all our IT
support which includes software, hardware and backup system. Additional
resources are required from the IT vendor for data backup for MARA project,
which is additional backup tapes (1TB each).

**Data access and security:**

All data for the MARA project will be stored in the Shared Drive, a storage
device on a local access network (LAN) of Apta’s server. An exclusive project
folder will be created for MARA project. The MARA project folder will only be
accessible to approved personnel and project team members who need access to
complete their tasks. The access control is set as (1) No Access, (2) Access
with Read only, (3) Access with Read, Write and Delete.

For the MARA project folder, non-project members with a need to access the
data will have read only permission.

Sensitive data is password protected. Permissions to other files are set by
the data manager.

The data is in support of potential new products for commercialisation. Any
leak of the data will affect the commercial potential for any product coming
from MARA data.

Security measures have been put in place to reduce the risk of data leaks.

Control Read, Write and Delete access measures have been put in place.

Collaborators will have read only access to the data except in certain
circumstances where there is a need for them to use the data in its original
format.

Only the people with Read, Write and Delete access are permitted to add data.

For the MARA project folder, non-project members with a need to access the
data will have read only permission. Project members will have Read, Write and
Delete access to the project folder.

Sensitive data is password protected. Permissions to other files are set by
the data manager.

**Storage and backup (short and mid-term):**

MARA Project Folders will be stored in shared drive and backed up daily. The
data is backed up externally in a physical tape format for its affordability,
reliability and portability. The third party IT Vendor will be responsible for
data backup and recovery. In the event of an incident, the latest data
recovery will be the night before at 11pm.

For non-electronic data, e.g. lab notebooks, HPLC spectra, etc., the data will
be scanned and converted to electronic PDF files. The scanning of lab
notebooks will be done at quarterly basis, and the original data will be
archived and stored for at least 5 years after the MARA project ends.

Additional tapes (1TB each) will be purchased for MARA project data. The
additional tapes come with additional cost, which is ~600 Euros per tape.

IT Vendor (Cordeos Pte Ltd) will be responsible for data backup and recovery.

Data up to the night before (11pm) will be readily available if there is an
incident in the laboratory or office.

**Archiving and preservation (long term):**

The data will be backed up in a physical tape on daily basis, till it is fully
stored, and the tape will be labelled based on the duration period. Example:
01 Jan 2016 – 28 April 2016 (MARA Project Tape 01). The backed up tapes will
be archived and stored at an offsite location, both away from the IT provider
and the Apta laboratory site, for long term preservation, or at least 5 years
from the date of project closure.

The approximated end volume of data to be generated from MARA project is about
60GB. However, as the data will be backed up daily by storing it in the tape
format without overwriting the previous data, it is a great challenge to
predict the accumulated data saved and backed up throughout the entire course
of work at this point in time.

All data for MARA project will be stored in the Shared Drive of Apta server.
An exclusive project folder will be created for MARA project. The MARA project
folder will only be accessible to approved personnel and project team members
who need access to complete their tasks. The access control is set as (1) No
Access, (2) Access with Read only, (3) Access with Read, Write and Delete.

For the MARA project folder, non-project members with a need to access the
data will have read only permission.

Sensitive data is password protected. Permissions to other files are set by
the data manager. Apta will rely on the archiving and preservation
capabilities provided by our IT Vendor.

#  2.1.5 Aarhus Universitet (AU)

**MARA data manager:**

Jacob Lauwring Andersen

**Available / necessary resources:**

An electronic lab book service (  _www.labwiki.au.dk_ )  is available and back
up is running daily. This will be applied for data management.

**Data access and security:**

Aarhus University has a thorough information security policy dedicated to
protect Aarhus University's information and, in particular, to ensure that the
confidentiality, integrity and availability of critical and sensitive
information and information assets are retained.

**Storage and backup (short and mid-term):**

Data is stored for 10 years after deposition and back up procedures are
running on daily basis. Aarhus University will provide sufficient storage for
the project. Data can be recovered from backup on hourly basis and deposited
data can be recovered on daily basis.

**Archiving and preservation (long term):**

Once deposited, data is stored for minimum 10 years at Aarhus University.
Protein structures will be deposited in the Protein Data Bank (  _www.pdb.org_
)  and stored.

#  _2.2 Data set descriptions_

Dissemination levels within MARA:

PU = public

CO = confidential, only for members of the consortium and the involved EC
services

##  2.2.1 MARA-AIT-001

**Data set reference / name / creator:**

Reference: MARA-AIT-001

Name: DNA and oligonucleotide sequence data

Created by: AIT – Ivan Barisic, Yasaman Ahmadi, and Regina Soldo **Data set
description:**

Data format: electronic: XLSX, GB

Software used for data generation: Excel, Cadnano, etc.

Hardware used for data generation: IonTorrent PGM

Typical file size (for electronic data): Kilobytes

Approximate amount of data: Megabytes

Short description of the data set: DNA sequence data is a letter code
comprising A (adenine), C (cytosine), G (guanine) and T (thymine)
corresponding to a nucleotide. The sequence data will be used to synthetize
DNA. Some sequences will be published within scientific publications.

**Standards and metadata:**

Sequence data obtained from the IonTorrent PGM will be saved in the GenBank
Flat File format.

Oligonucleotide sequences will be saved together with their corresponding
name, length, target, DNA and, if applicable, the origami structure.

**Data sharing:**

Dissemination level: CO

Embargo period: Until publication/patent

Repository/repositories planned for upload: Published sequences will be made
available via Pubmed and/or NCBI Genbank

Further details on data sharing: The data will be accessible and shared within
the AIT business unit Molecular Medicine.

Explanation why CO data cannot be made public: The data cannot be shared due
to intellectual property and commercial issues.

**Data access and security:**

Described in the general part.

**Storage and backup (short and mid-term, during the project):**

Described in the general part.

**Archiving and preservation (long term, after the project):**

Described in the general part.

##  2.2.2 MARA-AIT-002

**Data set reference / name / creator:**

Reference: MARA-AIT-002

Name: Source code for software Created by: AIT – Stephan Pabinger **Data set
description:**

Data format: electronic - various source code files (.python, .cpp, .c, .h …)

Software used for data generation: IDEs (integrated development environments)

Hardware used for data generation: PCs

Typical file size (for electronic data): Kilobytes to Megabytes (including
test files)

Approximate amount of data: Megabytes to Gigabytes

Short description of the data set: During the project, several source code
files will be generated to develop new tools and integrate functionality into
existing tools. Software will be made available within scientific
publications.

**Standards and metadata:**

Documentation of the source code will be either created directly in the source
file or separately in an additional document (metadata). Manuals of the
software will be stored in the repository system. If applicable standardize
input and output formats will be used depending on the design of the software.

**Data sharing:**

Dissemination level: CO

Embargo period: none

Repository/repositories planned for upload: The source code will be stored in
a distributed revision control system that will be hosted at the AIT.

Further details on data sharing: One central repository will be used for
merging and housing the different branches of the software source files. In
addition, each contributor will have the possibility to keep own versions of
the software in their own repository.

Explanation why CO data cannot be made public: The data cannot be shared due
to intellectual property and commercial issues.

**Data access and security:**

In addition to the description in the general part, access to the data will be
given on a per-user basis. The repository will be hosted with the AIT network.

**Storage and backup (short and mid-term, during the project):**

Described in the general part.

**Archiving and preservation (long term, after the project):**

Described in the general part.

##  2.2.3 MARA-ALU-FR-001

**Data set reference / name / creator:**

Reference: MARA-ALU-FR-001

Name: Electrophoresis image data

Created by: ALU-FR – Patrick Tripp, Lena Hoffmann **Data set description:**

Data format: TIFF, JPEG, EPS

Software used for data generation: Imaging software (Quantity One (Biorad),
Chemostar Imager (Intas))

Hardware used for data generation: Biorad Imaging system and Intas Imaging
system

Typical file size (for electronic data): Kilobytes

Approximate amount of data: For electronic data: in order of gigabytes

Short description of the data set: The images recorded show the results of DNA
electrophoresis or protein electrophoresis experiments. In our Labguru account
they are linked to the specific experiment where a detailed description exists
of the experimental procedure.

**Standards and metadata:**

No standards and metadata exist for these data.

**Data sharing:**

Dissemination level: PU

Embargo period: Until published

Repository/repositories planned for upload: Publisher’s repositories Further
details on data sharing: Publishing in “Open access” journals **Data access
and security:**

Please see general part.

**Storage and backup (short and mid-term, during the project):**

Please see general part.

**Archiving and preservation (long term, after the project):**

Please see general part.

##  2.2.4 MARA-ICL-001

**Data set reference / name / creator:**

Reference: MARA-ICL-001

Name: Electron cryo-tomographic imaging data Created by: IMPERIAL – Morgan
Beeby, Amanda Wilson **Data set description:**

Data format: Electronic: MRC files of tomograms

Software used for data generation: IMOD, Tomo3D, RAPTOR, PEET, Relion

Hardware used for data generation: ICT FEI F20 electron cryo-microscope;
possible use of off-campus electron cryo-microscopes.

Typical file size (for electronic data): 3 gb

Approximate amount of data: 100s of datasets amounting to 10s of terabytes of
data.

Short description of the data set: Data will be 3D tomograms generated by
electron cryo-tomography. Data will be useful to MARA participants and the
general scientific community interested in electron cryo-

microscopy and archaellar motors. Published electron cryo-microscopy data will
be archived at publicly accessible EMPIAR and EMDB databases for raw and
processed data, respectively.

**Standards and metadata:**

Data will be stored in de facto standard MRC file formats. Metadata is
required to be stored in the lab database with additional information recorded
by users at the time of data collection. Metadata is stored in a backed-up
MySQL database which is dumped nightly as a text file backup.

**Data sharing:**

Dissemination level: PU + CO. PU - Public: published data will be archived at
publicly accessible EMPIAR and EMDB databases for raw and processed data,
respectively. CO - Confidential: data in the process of being interpreted and
pre-publication.

Embargo period: Data will be made publically available at the time of
publication.

Repository/repositories planned for upload: Published electron cryo-microscopy
data will be archived at publicly accessible EMPIAR and EMDB databases for raw
and processed data, respectively. Empiar:

_https://www.ebi.ac.uk/pdbe/emdb/empiar/_ EMDB:
_https://www.ebi.ac.uk/pdbe/emdb/_

Further details on data sharing: Data will be freely available via publicly
accessible databases listed above. Necessary software for viewing is all
publically and freely available (primarily IMOD and UCSF Chimera). Published
data will be widely open.

Explanation why CO data cannot be made public: Confidential data is data that
is still in the process of interpretation pre-publication.

**Data access and security:**

Please see General DMP section.

**Storage and backup (short and mid-term, during the project):**

Please see General DMP section.

**Archiving and preservation (long term, after the project):**

Please see General DMP section.

##  2.2.5 MARA-APTA-001

**Data set reference / name / creator:**

Reference: MARA-APTA-001 Name: Seligo sequence data.

Created by: APTA – Yap Sook Peng, Yau Yin Hoe **Data set description:**

Data format: Final data files (gel images, Seligo sequences), technical
reports and completed laboratory notebook scanned copies will be in PDF
format. Data files still being accessed will be stored in the appropriate
format, e.g. Excel.

Software used for data generation: Microsoft Excel, BioEdit, FinchTV, Nanodrop
2000/2000c version 1.4.2, CFX Manager Software.

Hardware used for data generation: Gel imager (BioRad), Sanger sequencer (ABI
3730xl platform), NanoDrop 2000 Spectrophotometer, CFX Connect.

Typical file size (for electronic data):

1 raw image data file from GelDoc EZ is 3MB.

1 raw data file from RT-PCR is <0.1MB

1 raw data file from Nanodrop is 0.4MB, Screen shot 0.6MB 1 PDF Bioanalyzer
report is 2MB in average.

1 raw data file for DNA sample sequence is ~ 500KB per sample, 40MB per
96-well plate Approximate amount of data:

~1GB per protein target

~20GB for all data (against 20 bacterial pathogen targets) Short description
of the data set:

One of the main data set to be generated from the development of Seligo is the
sequences of Seligo binders against the 20 most important bacterial pathogens.
The data will be useful to commercial competitors seeking to develop similar
products. Additionally, the Seligo sequences are confidential information and
could be used by competitors to rapidly replicate the MARA work.

**Standards and metadata:**

No existing standards for reference.

The bulk of the data generated from Development of Seligo will be the sequence
data of the selected Seligo candidates. From each of the selection rounds,
less than 800 Seligo sequences (94-mer each) will be generated. Sanger
sequencing methodology instead of Next Generation Sequencing (NGS) will be
used to identify the sequences of the Seligo identified from the selection
process. Hence, there won’t be any metadata created, but approximately 400-800
Seligo sequences per selection to be analysed and stored in excel file format.

**Data sharing:**

Dissemination level: CO

Embargo period: 3 years, for IP reasons

Repository/repositories planned for upload: MARA data will be stored in a
separate folder within the shared drive in Apta. A Sharepoint created for MARA
members will be used for data sharing within the consortium. Further details
on data sharing: The data which supports the public dissemination of the MARA
result will be made public.

Explanation why CO data cannot be made public: Datasets will not be made
public where there is intellectual property and/or commercial reasons. All
datasets involved included in support of publications and presentations will
be made public.

**Data access and security:**

Described in the general part.

**Storage and backup (short and mid-term, during the project):**

Described in the general part.

**Archiving and preservation (long term, after the project):**

Described in the general part.

##  2.2.6 MARA-APTA-002

**Data set reference / name / creator:**

Reference: MARA-APTA-002

Name: AUDENA design and development

Created by: APTA – Yap Sook Peng, Yau Yin Hoe, Shuji Ikeda **Data set
description:**

Data format: Final data files (NMR spectra, Mass Spectra, HPLC charts, gel
images, Seligo sequences, BIAcore binding interaction data), technical reports
and completed laboratory notebook scanned copies will be in PDF format. Data
files still being accessed will be stored in the appropriate format, e.g.
Excel.

Software used for data generation: Microsoft Excel, BioEdit, FinchTV, BIAcore
3000 Control Software version 4.0.1, BIAevaluation version 4.0.1, Nanodrop
2000/2000c version 1.4.2, CFX Manager Software, Unicorn 2.0, DNA_H8_F2.

Hardware used for data generation: NMR, ESI-MS, HPLC, gel imager (BioRad),
Sanger sequencer (ABI 3730xl platform), BIAcore 3000 machine, NanoDrop 2000
Spectrophotometer, CFX Connect, NTS DNA synthesizers, AKTA Purifier, AKTA
Explorer and PC.

Typical file size (for electronic data):

1 raw image data file from GelDoc EZ is 3MB.

1 raw data file from RT-PCR is <0.1MB

1 raw data file from Nanodrop is 0.4MB, Screen shot 0.6MB

1 raw log data from NTS synthesizer is 7KB/synthesizer column 1 PDF Processed
report for NMR or MS from NUS is 0.1MB in average.

1 PDF Bioanalyzer report is 2MB in average.

1 raw data file for DNA sample sequence is ~ 500KB per sample, 40MB per
96-well plate Approximate amount of data: ~3GB

Short description of the data set: One of the main goal of MARA project is the
development of AUDENA. The data set to be generated from the design and
development of AUDENA may comprise of but not limited to the sequences of
Seligo binders against the bacterial pathogens, new Seligo random library,
AUDENA design and development, synthesis methodology of new Seligo / AUDENA
designs, HPLC purification methods for Seligos and manufacturing of Seligos.
The data will be useful to commercial competitors seeking to develop similar
products. Additionally, AUDENA design and protocols are confidential company
know-how and could be used by competitors to rapidly replicate the MARA work.

**Standards and metadata:**

No existing standards for reference.

The bulk of the data generated from AUDENA design and development may comprise
of the tests and validation data of AUDENA ideas and designs, e.g. form of
Seligo random library, G-quadruplex validation, etc. There won’t be any
metadata created from this work.

**Data sharing:**

Dissemination level: CO

Embargo period: 3 years, for IP reasons

Repository/repositories planned for upload: MARA data will be stored in a
separate folder within the shared drive in Apta. We have yet to decide on
which repository to be used for external data storage/sharing. Further details
on data sharing: The data which supports the public dissemination of the MARA
result will be made public.

Explanation why CO data cannot be made public: Datasets will not be made
public where there is intellectual property and/or commercial reasons. All
datasets involved included in support of publications and presentations will
be made public.

**Data access and security:**

Described in the general part.

**Storage and backup (short and mid-term, during the project):**

Described in the general part.

**Archiving and preservation (long term, after the project):**

Described in the general part.

##  2.2.7 MARA-APTA-003

**Data set reference / name / creator:**

Reference: MARA-APTA-003

Name: Seligo manufacturing and purification.

Created by: APTA – Yap Sook Peng, Jeremiah Decosta **Data set description:**

Data format: Final data files (NMR spectra, Mass Spectra, HPLC charts, gel
images, Seligo sequences, BIAcore binding interaction data), technical reports
and completed laboratory notebook scanned copies will be in PDF format. Data
files still being accessed will be stored in the appropriate format, e.g.
Excel.

Software used for data generation: Microsoft Excel, BIAcore 3000 Control
Software version 4.0.1, BIAevaluation version 4.0.1, Nanodrop 2000/2000c
version 1.4.2, Unicorn 2.0, DNA_H8_F2.

Hardware used for data generation: NMR, ESI-MS, HPLC, gel imager (BioRad),
BIAcore 3000 machine, NanoDrop 2000 Spectrophotometer, NTS DNA synthesizers,
AKTA Purifier, AKTA Explorer and PC.

Typical file size (for electronic data):

1 raw image data file from GelDoc EZ is 3MB.

1 raw data file from Nanodrop is 0.4MB, Screen shot 0.6MB

1 raw log data from NTS synthesizer is 7KB/synthesizer column

1 PDF Processed report for NMR or MS from NUS is 0.1MB in average

Approximate amount of data: several GB per Seligo

Short description of the data set: The main data to be generated from the
manufacturing and purification of Seligo may comprise of but not limited to
the Amidites and Seligos synthesis data, HPLC purification of

Amidites and Seligos, and quality control data of Amidites and Seligos. The
data will be useful to commercial competitors seeking to develop and
manufacture similar products. Additionally, manufacturing protocols are
confidential company know-how and could be used by competitors to rapidly
replicate the MARA work.

**Standards and metadata:**

No existing standards for reference.

The bulk of the data generated from Seligo manufacturing and purification will
be the protocols and data for synthesis, purification and quality control of
Amidites and Seligos. There won’t be any metadata created. **Data sharing:**

Dissemination level: CO

Embargo period: 3 years, for IP reasons

Repository/repositories planned for upload: MARA data will be stored in a
separate folder within the shared drive in Apta. We have yet to decide on
which repository to be used for external data storage/sharing. Further details
on data sharing: The data which supports the public dissemination of the MARA
result will be made public.

Explanation why CO data cannot be made public: Datasets will not be made
public where there is intellectual property and/or commercial reasons. All
datasets involved included in support of publications and presentations will
be made public.

**Data access and security:**

Described in the general part.

**Storage and backup (short and mid-term, during the project):**

Described in the general part.

**Archiving and preservation (long term, after the project):**

Described in the general part.

##  2.2.8 MARA-AU-001

**Data set reference / name / creator:**

Reference: MARA-AU-001

Name: MARA-AU-001

Created by: AU – Jacob Lauwring Andersen **Data set description:**

Data format: PDF, electronic lab book (www.labwiki.au.dk).

Software used for data generation: Word, and Adobe. Hardware used for data
generation: Äkta purifier.

Typical file size (for electronic data): Megabytes

Approximate amount of data: megabytes

Short description of the data set: Expression and purifications protocols for
proteins purified for the MARA project.

**Standards and metadata:**

Standard material and methods section for protein purification publication,
including further details on expression and purification experiments.

**Data sharing:**

Dissemination level: CO

Embargo period: Not determined yet. Depending on interests.

Repository/repositories planned for upload: Electronic lab book system (
_www.labwiki.au.dk_ )  .

Further details on data sharing: Publication and sharing at meetings.

Explanation why CO data cannot be made public: IPR reasons, depending on the
commercial interests of the MARA project partners.

**Data access and security:**

See general procedures. In general the expression and purification data is not
very sensitive and should be shared early. All MARA members will have access
to the data protected by password.

**Storage and backup (short and mid-term, during the project):**

See general procedures.

**Archiving and preservation (long term, after the project):**

Data is stored in the electronic lab book system and stored 10 years after
deposition to the Aarhus University archiving service.

##  2.2.9 MARA-AU-002

**Data set reference / name / creator:**

Reference: MARA-AU-002

Name: MARA-AU-002

Created by: AU – Jacob Lauwring Andersen **Data set description:**

Data format: PDF, electronic lab book and protein data bank files.

Software used for data generation: Word, ccp4 work-package, phenix, pymol.

Hardware used for data generation: Synchrotron radiation.

Typical file size (for electronic data): Gigabytes

Approximate amount of data: Gigabytes

Short description of the data set: Diffraction data and refined protein
structures of proteins relevant to the MARA project.

**Standards and metadata:**

File format: .pdb for the final refined structure. .cbf for diffraction
images.

**Data sharing:**

Dissemination level: CO

Embargo period: Not determined yet. Depending on interests.

Repository/repositories planned for upload: The protein Data Bank (
_www.pdb.org_ )  .

Further details on data sharing: Publication and sharing at meetings.

Explanation why CO data cannot be made public: IPR reasons, depending on the
commercial interests of the MARA project partners.

**Data access and security:**

See general procedures. In general the protein structures are sensitive and
should only be shared when all commercial interests are protected.

**Storage and backup (short and mid-term, during the project):**

See general procedures.

**Archiving and preservation (long term, after the project):**

Diffraction data is stored 10 years after deposition to the Aarhus University
archiving service.

#  _2.3 Data exchange within the MARA consortium_

Within the MARA consortium, data can be exchanged using a password protected
Microsoft Sharepoint system that is only accessible by registered project
members. This system has a very flexible design to tailor different sections
to the specific needs of the project. The system is accessible via a public
web-address  ( _https://portal.ait.ac.at/sites/mara_ )  , which is also linked
from the official MARA website  ( _http://maraproject.eu_ )  . Included into
the exchange system is a document centre where reports, documents, templates,
etc. can be centrally hosted and shared. This allows project members to access
current versions of reference documents and guidelines. User access rights to
the exchange system are managed by Stephan Pabinger (AIT). All data exceeding
100MB will only be stored temporarily on the system. After successful sharing,
it will be transferred into the respective storage systems of the individual
partners (see 2.1). As described previously, daily differential backup and a
weekly full backup to a file share will be performed for the data stored in
the exchange system.

#  Conclusion

As the EC acknowledged in their “  _Guidelines on Data Management in Horizon
2020_ ”  , a DMP is not a fixed document, but evolves during the lifespan of
the project. Several MARA project team members have already announced that
they will report additional data sets during the course of the project. The
DMP will be updated accordingly during the project lifetime.

The information collected within the consortium for this initial version of
the DMP also revealed an aspect of which we haven’t been aware to its full
extent during the writing of the MARA proposal: Although MARA has declared
itself to be part of the “open data pilot” and the MARA consortium is still
committed to give the general public access to its research data, most data
will have to be kept confidential until the related IPR is secured. Thus, at
the current time, hardly any research data within MARA are labelled as PU
(“public”). As soon as IPR is secured, we will change the status of data sets
from CO (“confidential, only for members of the consortium and the involved EC
services”) to PU, provided there are no other reasons for confidentiality (as
outlined in the MARA grant agreement). At this time, we will also choose the
appropriate repositories and document them in the DMP.

The DMP itself has been declared as a PU document by the MARA consortium and
will be made accessible to the public via the MARA web page.