#  INTRODUCTION

The M4F H2020 project on multiscale modelling for fusion and fission materials
1  is participating voluntarily in the Open Research Data (ORD) pilot
according to the H2020 guidelines on data management  2  and the requirements
specified in Article 29.3 of the H2020 Model Grant Agreement.

The purpose of this document is to provide an analysis of the main elements of
the data management policy that will be used by the M4F project partners with
regard to all the data sets that will be generated by the project.

The M4F data management plan (DMP) is a living document that will evolve
during the lifespan of the project. In this respect, the DMP will be updated
and revised at each reporting period.

#  GLOSSARY

CEN European Committee for Standardization

DMP Data Management Plan

DOI Digital Object Identifier

EBSD Electron Back Scatter Diffraction

EERA European Energy Research Alliance

EMMC European Materials Modelling Council

H2020 Horizon 2020

HDF5 Hierarchical Data Format 5

JPNM Joint Programme on Nuclear Materials

M4F Multiscale Modelling for Fusion and Fission Materials

MODA Modelling Metadata

NINA Nanoindentation for Nuclear Applications

NPP Nuclear Power Plant

ODIN Online Data and Information Network

ORD Open Research Data

SEM Scanning Electron Microscopy

TEM Transmission Electron Microscopy

#  DATA SUMMARY

##  DATA MANAGEMENT

With the M4F consortium undertaking materials testing and modelling tasks,
there is a requirement for services in support of effective collection and
exchange of data. Consequently, a carefully considered data management
strategy has been formulated with a view to enabling exchange of test data
between project partners; benchmarking of modelling data; and re-use beyond
the term of the project. Thus, test data will be deposited in MatDB (a domain-
specific, OpenDOAR-listed  3  repository) in a timely manner; pre-normative
formats for nanoindentation test data to facilitate data transfer and systems
integration will be developed in the scope of an 18-month CEN Workshop; and
data citation will be used to enable discovery and harvesting of data sets. To
augment its data management strategy, M4F is participating voluntarily in the
Horizon 2020 ORD pilot.

As described in the following subsections, while initially the data will be
restricted to project partners, data citation will ensure the data can be
discovered, thereby providing a viable approach to exposing research data of
inherent commercial value without necessarily making the data sets themselves
immediately available. The conditions for data exchange amongst project
partners will be agreed at the M12 project meeting. At project midterm, M4F
project partners will be consulted on the topic of changing the dissemination
level of the data from restricted to Open Access. This approach is consistent
with the ORD 'as open as possible, as closed as necessary' principle, whereby
there is a balance that respects commercial, research, and public interests.

###  MatDB  
  
<table>  
<tr>  
<th>

</th>  
<th>

Deliverable nº D7.1: Data Management Plan

</th>  
<th>

Page

</th>  
<th>

5/15

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

Rev

</th>  
<th>

0

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

Date

</th>  
<th>

23/02/2018

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

At _https://odin.jrc.ec.europa.eu_ the European Commission JRC hosts an Online
Data and Information Network (ODIN) in support of energy and transport
research. The facility consists of a collection of scientific databases
organized into various categories. In the engineering category, MatDB is a
relational database application that contains over 20.000 test results coming
mainly from European R&D projects on engineering materials and provides a web-
interface for data content, data entry, data retrieval and analysis routines.
The database covers thermo-mechanical and thermo-physical properties data of
engineering alloys at low, elevated and high temperatures for base materials
and joints, including irradiated materials for nuclear fission and fusion
applications, thermal barrier coated materials for gas turbines and properties
of corroded materials. M4F test data will be deposited at MatDB in a timely
manner and data citation will enable discovery and harvesting of data sets.

##  DATA SET DESCRIPTION

With a view to benchmarking the results of the M4F modelling activities,
reference database will be created consisting of data sets from approximately
100 nanoindentation tests, including the results of TEM and SEM-EBSD
microstructural analyses  4  . Further, since M4F is devoted to physics-based
multiscale simulation activities, two different activities are coupled
together, namely dedicated experiments (mechanical testing and microstructural
analysis) and computer modelling. Effective data exchange between both
activities is of paramount importance for the purposes of validating the
models. For this the modellers need digital, numerical representations of
microstructures at a length scale that is consistent with that of the model
e.g. atomic modelling codes need details of vacancies, interstitials, etc.
whereas crystal plasticity models need grain size, grain orientation, etc. The
challenges associated with the quantification and storage of microstructural
data were already identified in previous EU-funded projects, including PERFECT
5  (FP6) and PERFORM60  6  (FP7) and are also the subject of ongoing
discussion within the H2020 SOTERIA  7  project, where the main challenge is
the quantification of radiation damage induced features. The numbers that
modellers need are mean size, density and chemical composition of radiation
damage features such as clusters and matrix damage. However, the error
quantification depends on each microstructural technique used e.g. TEM, SANS,
and APT. Further, radiation damage features are not homogeneously distributed
in the microstructure but instead are preferentially located near
dislocations, grain boundaries or other sinks, so spatial distribution is
another of the key issues for quantification of the microstructure. Other
issue is related to the different scales in describing microstructure: grains,
precipitates, vacancies. While the development of a robust materials
information management system to enable the connections at various lengths
scales to be made between experimental data and corresponding multiscale
modelling toolsets  8  is out of the scope of the project in terms of budget
and time, a proposal will be forthcoming for an adequate database structure
and to screen the difficulties associated with the data collection,
verification and storage, especially from microstructural examination and
model parameterization.

###  Existing data

Data for non-irradiated samples of materials of interest to M4F obtained
during the EERA JPNM NINA pilot project on nanoindentation for nuclear
applications will be uploaded.

###  Mechanical test data

Nanoindentation data coming from the WP6 (nanoindentation) test campaign will
be uploaded by project partners to MatDB. In the absence of a pre-existing
module, a single-cycle nanoindentation module has been implemented according
to the specifications listed in Table 1 through Table 5 and shown in Figure 1,
noting that the field names are consistent with the ISO 14577 standard for
instrumented indentation testing  9  . This is because the fields listed in
Table 1 through Table 5 are largely based on a preliminary examination of the
ISO 14577 standard, namely the entries in Clause 3 – Symbols and designations.
In accordance with accepted software development practices, the
nanoindentation module will be refined over a number of development iterations
based on the findings of further requirements gathering (meaning a close
examination of all normative clauses of the ISO 14577 standard) and feedback
from WP6 partners.

**Table 1.** Specimen dimensions  
  
<table>  
<tr>  
<th>

**Label**

</th>  
<th>

**Units**

</th>  
<th>

**Type**

</th>  
<th>

**Requirement**

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

Disc diameter, d

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Disc thickness, t

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Cuboid width, W

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Cuboid breadth, B

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Cuboid height, h

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

**Figure 1.** Miniature plain disc and plain cuboid specimens, respectively.  
  
<table>  
<tr>  
<th>

</th>  
<th>

Deliverable nº D7.1: Data Management Plan

</th>  
<th>

Page

</th>  
<th>

7/15

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

Rev

</th>  
<th>

0

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

Date

</th>  
<th>

23/02/2018

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

**Table 2.** Test data (general)  
  
<table>  
<tr>  
<th>

**Label**

</th>  
<th>

**Units**

</th>  
<th>

**Type**

</th>  
<th>

**Requirement**

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

Test result key

</td>  
<td>

N/A

</td>  
<td>

Number

</td>  
<td>

Generated

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

Test/specimen identifier

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Mandatory

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

Test standard

</td>  
<td>

N/A

</td>  
<td>

Mutable list

</td>  
<td>

Optional

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

Quality remark

</td>  
<td>

N/A

</td>  
<td>

Immutable list

</td>  
<td>

Optional

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

Reference to report

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Optional

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

Test machine

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Optional

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

Test date (yyyy-mm-dd)

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Optional

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

Data tested by

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Optional

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

Test remark

</td>  
<td>

N/A

</td>  
<td>

Text

</td>  
<td>

Optional

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

**Table 3.** Test data (procedure)  
  
<table>  
<tr>  
<th>

**Label**

</th>  
<th>

**Units**

</th>  
<th>

**Type**

</th>  
<th>

**Requirement**

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

Temperature

</td>  
<td>

°C

</td>  
<td>

Number

</td>  
<td>

Mandatory

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

Ambient temperature

</td>  
<td>

°C

</td>  
<td>

Number

</td>  
<td>

Optional

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

Test control

</td>  
<td>

N/A

</td>  
<td>

Immutable list {Stepped force; Continuous force; Stepped displacement;

Continuous displacement }

</td>  
<td>

Mandatory

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

Test control mode

</td>  
<td>

N/A

</td>  
<td>

Immutable list {linear; quadratic}

</td>  
<td>

Optional

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

Loading rate

</td>  
<td>

N/s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Unloading rate

</td>  
<td>

N/s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Displacement rate (loading)

</td>  
<td>

mm/s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Displacement rate (unloading)

</td>  
<td>

mm/s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Indenter shape

</td>  
<td>

N/A

</td>  
<td>

Immutable list {pyramid with square base; pyramid with triangular base; ball;
cone}

</td>  
<td>

Mandatory

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

Indenter material

</td>  
<td>

</td>  
<td>

Immutable list {diamond; metal}

</td>  
<td>

Mandatory

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

Radius of spherical indenter, r

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

**Table 4.** Test data (test results)  
  
<table>  
<tr>  
<th>

**Label**

</th>  
<th>

**Units**

</th>  
<th>

**Type**

</th>  
<th>

**Requirement**

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

**Label**

</td>  
<td>

**Units**

</td>  
<td>

**Type**

</td>  
<td>

**Requirement**

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

Maximum test force, F(max)

</td>  
<td>

N

</td>  
<td>

Number

</td>  
<td>

Mandatory

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

Time at F(max), t(hold)

</td>  
<td>

s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Indenter contact depth at F(max), h(c)

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Mandatory

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

Projected area at h(c), A(p)

</td>  
<td>

mm2

</td>  
<td>

Number

</td>  
<td>

Optional

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

Maximum indentation depth, h(max)

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Permanent indentation depth, h(p)

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Tangential indentation depth, h(r)

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Calculation method

</td>  
<td>

N/A

</td>  
<td>

Mutable list {Linear extrapolation; Power law}

</td>  
<td>

Optional

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

Indentation hardness, H(IT)

</td>  
<td>

GPa

</td>  
<td>

Number

</td>  
<td>

Optional

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

Test piece indentation modulus, E(IT)

</td>  
<td>

GPa

</td>  
<td>

Number

</td>  
<td>

Optional

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

Plane strain modulus, E*

</td>  
<td>

GPa

</td>  
<td>

Number

</td>  
<td>

Optional

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

Reduced plane strain modulus of the contact, E(r)

</td>  
<td>

GPa

</td>  
<td>

Number

</td>  
<td>

Optional

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

Indentation Creep, C(IT)

</td>  
<td>

%

</td>  
<td>

Number

</td>  
<td>

Optional

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

Indentation relaxation, R(IT)

</td>  
<td>

%

</td>  
<td>

Number

</td>  
<td>

Optional

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

Poisson's ratio, nu(r)

</td>  
<td>

None

</td>  
<td>

Number

</td>  
<td>

Optional  10

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

Elastic reverse deformation work, W(elast)

</td>  
<td>

Nm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Total mechanical work, W(total)

</td>  
<td>

Nm

</td>  
<td>

Number

</td>  
<td>

Optional

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

W(elast)/ W(total), eta(IT)

</td>  
<td>

None

</td>  
<td>

Number

</td>  
<td>

Optional

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

**Table 5.** Test Result - Curve Data  
  
<table>  
<tr>  
<th>

**Label**

</th>  
<th>

**Units**

</th>  
<th>

**Type**

</th>  
<th>

**Requirement**

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

Time, t

</td>  
<td>

s

</td>  
<td>

Number

</td>  
<td>

Optional

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

Force, F

</td>  
<td>

N

</td>  
<td>

Number

</td>  
<td>

Optional

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

Indentation depth, h

</td>  
<td>

mm

</td>  
<td>

Number

</td>  
<td>

Optional

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

Surface area, A(s)

</td>  
<td>

mm2

</td>  
<td>

Number

</td>  
<td>

Optional

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

Actual temperature

</td>  
<td>

°C

</td>  
<td>

Number

</td>  
<td>

Optional

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

As depicted in Figure 2, individual test results will be accompanied by
metadata (ancillary information) that puts the test result into context. This
metadata includes source information (describing the provenance of the data);
material pedigree data (of which there are two in the case of a dissimilar
weld); specimen data; and test conditions. As shown in the table in the
diagram, any single category (the material category in this case) consists of
subcategories of data, each of which in turn will include many individual
fields.  
  
<table>  
<tr>  
<th>

</th>  
<th>

Deliverable nº D7.1: Data Management Plan

</th>  
<th>

Page

</th>  
<th>

9/15

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

Rev

</th>  
<th>

0

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

Date

</th>  
<th>

23/02/2018

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

**Figure 2.** Metadata that accompany a result for a mechanical test.

In the figure, the material category is expanded to show the various
subcategories that constitute material pedigree data. The other categories can
be similarly expanded, so that specimen data for example extend to test piece
configuration, dimensions, surface preparation, coatings, etc.

Although the final WP6 test matrix has yet to be delivered, M4F materials
selection is well advanced. For WP6, the preliminary materials and their
conditions are listed in Table 6.

**Table 6.** Specification of materials and performed irradiations.  
  
<table>  
<tr>  
<th>

**Material**

</th>  
<th>

**Producer (heat)**

</th>  
<th>

**Project relation**

</th>  
<th>

**Provider in M4F**

</th>  
<th>

**Existing neutron irradiation**

</th>  
<th>

**Performed ion irradiation/NI**

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

**Common to WP6 and WP2**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Eurofer97

</td>  
<td>

Böhler

(E83699)

</td>  
<td>

EFDA,

MatISSE

</td>  
<td>

SCK·CEN

</td>  
<td>

300°C; 0.3–3 dpa

300°C; 0.06/0.6/1 dpa

290 & 450°C; 0.11 dpa

</td>  
<td>

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

Fe-9Cr

(ferritic)

</td>  
<td>

OCAS

(G385)

</td>  
<td>

MatISSE

</td>  
<td>

SCK·CEN HZDR

</td>  
<td>

290°C; 0.11 dpa & 450°C; 0.10 dpa

</td>  
<td>

300°C; 0.1 dpa

200°C; 0.5 dpa

300°C; 0.5 dpa

450°C; 0.5 dpa

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

**Specific to WP6**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Gr. 91

</td>  
<td>

Industeel (255518)

</td>  
<td>

Demetra, MatISSE

</td>  
<td>

SCK·CEN

</td>  
<td>

450°C; 0.1 dpa

</td>  
<td>

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

Fe

</td>  
<td>

OCAS

(G379)

</td>  
<td>

MatISSE

</td>  
<td>

SCK·CEN HZDR

</td>  
<td>

450°C; 0.1 dpa

</td>  
<td>

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

**Optional**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

T91

</td>  
<td>

Ugine

(36224)

</td>  
<td>

SPIRE,

MATTER

</td>  
<td>

</td>  
<td>

200°C; 2.95/4.36 dpa

[3,9,11]

300°C; 0.06/0.6/1 dpa

</td>  
<td>

three-step ion irr., 200°C; 2.5 & 3.5 dpa

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

**Material**

</td>  
<td>

**Producer (heat)**

</td>  
<td>

**Project relation**

</td>  
<td>

**Provider in M4F**

</td>  
<td>

**Existing neutron irradiation**

</td>  
<td>

**Performed ion irradiation/NI**

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

Fe-9Cr

(martens.)

</td>  
<td>

OCAS

(L252)

</td>  
<td>

GETMAT, MatISSE

</td>  
<td>

SCK·CEN

</td>  
<td>

300°C; 0.06/0.6/1 dpa

290 & 450°C; 0.11 dpa

</td>  
<td>

200°C; 0.5 dpa

300°C; 0.5 dpa

450°C; 0.5 dpa

\+ GETMAT

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

Pure Fe

</td>  
<td>

</td>  
<td>

</td>  
<td>

SCK·CEN

</td>  
<td>

</td>  
<td>

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

Pure W

</td>  
<td>

</td>  
<td>

</td>  
<td>

SCK·CEN

</td>  
<td>

</td>  
<td>

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

For each of the materials listed in Table 6 and as per the example shown in
the Figure 3 screen capture for the Gr. 91 material, a MatDB record exists
based on the corresponding material certificate (for commercial steels) and
material reports for model alloys.

**Figure 3.**

MatDB Gr.91 material record.

###  Microstructural data

With MatDB already providing support for microstructural data, the possibility
of a generic template for capturing microstructural characterisation data will
be explored within M4F. Some suggestions can be collected from previous
projects. Further, the analysis and storage of microstructural data was

one of the main activities of the FP7 ICMEG project  11  that ended in 2016
and that now continues in the frame of the European Materials Modelling
Council (EMMC)  12  , which is itself an H2020 CSA project. One outcome of
ICMEG was the identification of an hierarchical structure comprising both a
spatially resolved and simultaneously also a statistical description of data.
Especially for microstructures, a spatially resolved description was
identified as a mandatory basis for a sound physics description of phenomena.
Schmitz et al  13  provide a comprehensive system of metadata descriptors for
the description of a 3D microstructure that may serve as a first basis for
standardization and will simplify the data exchange between different
numerical models, as well as promote the integration of experimental data into
numerical models of microstructures. In particular, HDF5-formatted files are
proposed  14  to allow for both a spatially fully resolved description and for
a statistical representation of the data. With MatDB already supporting
rudimentary features for storing microstructural characterisation data from
analyses performed prior to and after testing, an opportunity exists during
M4F project execution to examine of the ICMEG data exchange format in the
context of an existing solution.

###  Modelling data

Although MatDB does not presently support a module explicitly for modelling
data, where modelling of a specific test is undertaken there is the
possibility to associate the modelling results with the corresponding test
result by way of attached document(s). Usefully, a template and vocabulary for
materials modelling has been delivered by the recently completed MODA CEN
Workshop (CEN/WS MODA)  15  , which itself builds on the results of prior EU
funded materials modelling projects  16  . Use of the MODA template for
capturing M4F modelling data will be the subject of investigation for the
duration of the project.

#  FAIR DATA

##  MAKING DATA FINDABLE, INCLUDING PROVISIONS FOR METADATA  
  
<table>  
<tr>  
<th>

</th>  
<th>

Deliverable nº D7.1: Data Management Plan

</th>  
<th>

Page

</th>  
<th>

12/15

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

Rev

</th>  
<th>

0

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

Date

</th>  
<th>

23/02/2018

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

All the experimental data coming from M4F mechanical testing will be enabled
for citation with DataCite DOIs, for which the naming convention will rely on
the corresponding database technical keys and the bibliographic metadata will
be compliant with the most recent version (v4.1) of the DataCite Metadata
Schema  17  . Thus, the title and abstract accompanying each data set will
ensure the data are findable. Further, with the bibliographic metadata also
including the DOI version number, specific versions of each data set can be
identified. As shown in the Figure 4 screen capture, for ease of referencing
of large numbers of data sets created in the scope of M4F, the MatDB data
citation service also supports DOI catalogs, whereby a group of data sets can
be allocated a DOI, thereby allowing a specific group of data sets i.e. a data
catalog, to be referenced from a single citation.

**Figure 4.** MatDB DOI catalog.

As depicted in Figure 2, an ad hoc data model exists that defines the metadata
that accompany each individual test result. With a view to promoting re use, a
subset of the metadata are mandatory.

##  MAKING DATA OPENLY ACCESSIBLE

The H2020 ORD pilot follows the principle 'as open as possible, as closed as
necessary' and focuses on encouraging sound data management as an essential
part of research best practice. M4F data management is entirely consistent
with this principle.

Scientific data typically have a significant financial and intellectual value.
Consequently, there is (1) a need to ensure the data are properly understood
in order to insure appropriate reuse e.g. for analysis and design, and (2) an
opportunity to promote data exchange by way of bilateral arrangements. With a
view to encouraging appropriate reuse and to promoting data exchange, M4F data
access policy is formulated accordingly.

All relevant M4F WP6 test data will be deposited at and made available from
the European Commission materials database, MatDB. As shown in the Figure 5
screen capture, data retrieval is an intuitive process that requires no
additional software or documentation and relies on a preliminary selection
(based on test type, source, and material) and optional advanced selection
(typically based on test conditions and parameters). Having made the
selection, the corresponding data sets can be browsed online and/or downloaded
manually in PDF, MS Excel, and/or XML formats.

**Figure 5.** MatDB Open Access data retrieval interface.

All M4F data sets will be citable, meaning that there will be bibliographic
metadata in the public domain. This serves two immediate purposes, namely to
promote discovery and to insure data owners are acknowledged in derivative
works (and hence have an incentive to share their data). Perhaps more
importantly, data citation respects predefined data access levels, meaning
that Open Access data remain open, while restricted data remain restricted. In
which case, there is the possibility for third parties to request access to
restricted data sets, so that the data owners have the opportunity to release
restricted data under terms that meet their interests, whether these are
intellectual or commercial. In this respect, the M4F data sharing policy will
extend to the consortium (1) considering all data access requests with a view
to making data sets available in the circumstance that it would add value to
the overall objectives of the project and related activities and (2) reviewing
the Open Access option at midterm.

Where citable data sets are restricted and data access requests are submitted,
these requests will be forwarded to the technical co-ordinator for their
consideration. In the circumstance that M4F data sets are made Open Access,
MatDB allows direct access to the data according to the terms of the EU
Copyright Notice  18  . In all circumstances, where data are cited in
derivative works, the individuals and organizations that have accessed the
data will be known.

##  MAKING DATA INTEROPERABLE

For managing the data, M4F will utilize established metadata and harvesting
standards, including the

DataCite Metadata Schema. As already indicated, each of the data sets will be
assigned a DataCite DOI, so that all data sets can be cited in derivative
works. The result will be that for every data set, bibliographic metadata
corresponding to the mandatory fields of the DataCite metadata schema v3.0
will be openly accessible. All records will be available from the DataCite
metadata server. Since

DataCite supports both Dublin Core and OAI PMH, these metadata data can be
searched and harvested programmatically.

As evidenced by the lack of engineering science data formats registered at the
RDA metadata standards repository  19  , formats in support of
interoperability in the engineering sector are almost non-existent. To address
this shortcoming, M4F will contribute to a series of CEN Workshops on formats
for engineering materials data  20  by organizing an 18-month CEN Workshop to
develop prenormative standards for nanoindentation test data. In the scope of
this new CEN Workshop, data models and formats will be derived from the ISO
14577 standard for instrumented indentation testing  9  in accordance with the
methodology established during the prior CEN Workshops.

##  INCREASING DATA RE-USE

The data license is specified by way of the DataCite rights property. For Open
Access data sets, the default license is the EU Copyright Notice  18  for JRC
data sets and CC-BY for non-JRC data sets, while for restricted access data
sets the license is by arrangement with the creator organization.

As already indicated, at the outset of the project the data will be restricted
and any requirements for an embargo period will be given consideration at the
time access requests are received.

It is anticipated that the data will remain re-usable beyond the term of the
project. With re-usability largely dependent on the quality and completeness
of the data sets, the existing MatDB quality assurance procedures will be
relied upon to promote re-use over the longer term. These procedures extend to
the requirement that tests are performed according to internationally accepted
standards and protocols; to mandatory metadata requirements; and to validation
of individual data sets by a subject matter expert prior to their becoming
available from the MatDB data retrieval module.

Beyond the reliance on MatDB quality assurance procedures, at its M12 project
meeting the M4F consortium will give consideration to the appointment of an
expert panel responsible for data quality, including setting project-specific
mandatory data requirements and reviewing individual data sets.

#  ALLOCATION OF RESOURCES

M4F will take advantage of existing JRC services for managing engineering
materials data and thus there are no costs for repository services. In case of
modifications, such as new metadata fields, the work is anticipated in the M4F
grant agreement (GA).

As the service provider, JRC will host webinars to demonstrate the data entry
procedure so that all partners can work effectively. Beyond the term of the
project, the JRC will continue to host the data sets. In all circumstances,
the JRC simply provides a hosting service, so that ownership of the data
always remains with the creator organization.

Individual project partners are responsible for uploading their test results
to MatDB and the work is planned in WP6 as an integral component of the test
campaign.

#  DATA SECURITY

The MatDB database is the subject of continual development and maintenance and
is backed-up daily.

#  ETHICAL ASPECTS

Possibly the release of the experimental data to states that are subject to
the embargo of technical data on nuclear power plant (NPP) construction may be
relevant. However, given that the data will be restricted at the outset of the
project, any ethical issues will be taken into consideration at the time
access requests are received. These same considerations will be taken into
account when the Open Access option is reviewed at midterm.

Other than the names of data creators and project leads, there is no personal
data and hence no requirement for informed consent.

#  OTHER ISSUES

The JRC abides by the principles of the JRC Data Policy  21  , which although
not extending to organizations other than the JRC, does ensure best working
practices when managing data coming from sources other than the JRC.