The administrative metadata section contains all technical and digital provenance
metadata section for the object and its files. There mustn't be any other
technical or digital provenance metadata outside of this section.
A conforming METS document must contain at least one techMD section for metadata
on the whole archive object and one techMD section for each file belonging to
The techMD section for the whole archive object must include elements from
LMER-Object. Mandatory is only persistentIdentifier that names the external ID.
groupIdentifier can be used repeatedly. objectVersion defines the state as
original or migration and should be „1“ for an original. If startFile exists,
that element contains the value of the ID attribute of the corresponding file of
the File Section of METS. If existent, numberOfFiles must correspond to the
number of files listed in the File Section of METS.
The respective techMD section of each file must include elements from LMER-File.
Only format with an appropriate attribute REGISTRYNAME to identify the used
namespace is mandatory. linkedTo is repeatable and, like in startFile, names the
corresponding file elements of METS. The following elements from LMER-File
should be left out, because they already appear mandatory in the File Section of
METS: fileIdentifier, path, name, size, fileDateTime, fileChecksum and mimeType.
In the LMER-File element xmlData, further technical metadata in an arbitrary XML
schema can be stated for each file (e. g. MIX, TechMD, JHOVE output). The
element is repeatable.
A conforming METS document may contain digiprovMD sections for the whole object
and for each file.
The digiprovMD sections must include elements from LMER-Process. The elements
oldMetadataRecordCreator, oldObjectIdentifier and oldOb-jectVersion can only
exist when referring to the object. oldObjectIdentifier states the internal ID
of the predecessor of the described migration. oldMeta-dataRecordCreator
provides the context within which the internal ID is valid.
All techMD and digiprovMD sections must have the ID attribute so that they can be
referenced in the File section.