2.1 Engineering Metadata
21
Table 2.1 Existing standards that were used in EngMeta and VIMMP with respect to the four
categories defined in Sect. 1.3
EngMeta Metadata Model
VIMMP Ontology
Technical
PREMIS
–
Descriptive
DataCite
MMTO, OTRAS, VICO
Process
CodeMeta, ExptML, UnitsML VISO
Domain specific
–
VISO, VOV
that different metadata standards cover certain aspects of the EngMeta entities. This
coverage is shown in Table 2.1 with respect to the four metadata categories. CodeMeta
is a description of software tools and serves for the software part in EngMeta. DataCite is the standard for descriptive metadata and moreover, enables the data to get a
DOI and was therefor integrated into EngMeta. PREMIS is a standard for technical
metadata, and ExptML was integrated for experimental device, which can also be
modelled by EngMeta. As Prov is a standard for provenance, a crosswalk for this
standard was developed in order to achieve semantic interoperability [1]. Moreover,
in this table, a comparison to VIMMP, which is discussed in Chap. 4 regarding
existing standards is shown. The model has been implemented as an XML Schema
Definition (XSD) and is available for open use and modification.
4
2.1.2.3 The Metadata Processes Supporting EngMeta
As discussed in Sect. 2.1.1.4, a metadata model needs to be complemented with
metadata processes. Otherwise, it will not be fully effective to make research data
FAIR. In the example of EngMeta, the model was complemented by an automated
metadata extraction, the establishment of a research data management competence
centre and an institutional repository. Details on the repository can be found in
the following section on research data infrastructures, especially in Sect. 2.2.3.1.
FOKUS was established as the main competence centre for questions and support
regarding research data management at the University of Stuttgart. The automated
metadata extraction ExtractIng was designed and implemented. It works in a way
that all the existing metadata, stemming from log-, job- and various other files in the
HPC and simulation environment, are extracted and are converted to the EngMeta
metadata model. It can be integrated in the specific research process, and it was
shown how an automated approach would look like for simulation sciences. Right
after the simulation run, the ExtractIng tool will be triggered, transforming all the
scattered metadata in a standardized form according to EngMeta. Then, the metadata
can be automatically uploaded to the repository, all together with the data, forming
a dataset within the repository including all relevant semantic information for FAIR
interoperability.
4 https://www.izus.uni-stuttgart.de/fokus/engmeta/.
21
Table 2.1 Existing standards that were used in EngMeta and VIMMP with respect to the four
categories defined in Sect. 1.3
EngMeta Metadata Model
VIMMP Ontology
Technical
PREMIS
–
Descriptive
DataCite
MMTO, OTRAS, VICO
Process
CodeMeta, ExptML, UnitsML VISO
Domain specific
–
VISO, VOV
that different metadata standards cover certain aspects of the EngMeta entities. This
coverage is shown in Table 2.1 with respect to the four metadata categories. CodeMeta
is a description of software tools and serves for the software part in EngMeta. DataCite is the standard for descriptive metadata and moreover, enables the data to get a
DOI and was therefor integrated into EngMeta. PREMIS is a standard for technical
metadata, and ExptML was integrated for experimental device, which can also be
modelled by EngMeta. As Prov is a standard for provenance, a crosswalk for this
standard was developed in order to achieve semantic interoperability [1]. Moreover,
in this table, a comparison to VIMMP, which is discussed in Chap. 4 regarding
existing standards is shown. The model has been implemented as an XML Schema
Definition (XSD) and is available for open use and modification.
4
2.1.2.3 The Metadata Processes Supporting EngMeta
As discussed in Sect. 2.1.1.4, a metadata model needs to be complemented with
metadata processes. Otherwise, it will not be fully effective to make research data
FAIR. In the example of EngMeta, the model was complemented by an automated
metadata extraction, the establishment of a research data management competence
centre and an institutional repository. Details on the repository can be found in
the following section on research data infrastructures, especially in Sect. 2.2.3.1.
FOKUS was established as the main competence centre for questions and support
regarding research data management at the University of Stuttgart. The automated
metadata extraction ExtractIng was designed and implemented. It works in a way
that all the existing metadata, stemming from log-, job- and various other files in the
HPC and simulation environment, are extracted and are converted to the EngMeta
metadata model. It can be integrated in the specific research process, and it was
shown how an automated approach would look like for simulation sciences. Right
after the simulation run, the ExtractIng tool will be triggered, transforming all the
scattered metadata in a standardized form according to EngMeta. Then, the metadata
can be automatically uploaded to the repository, all together with the data, forming
a dataset within the repository including all relevant semantic information for FAIR
interoperability.
4 https://www.izus.uni-stuttgart.de/fokus/engmeta/.