METS exported from Kitodo3 contains nowadays the element mets:metsDocumentID which holds the local DB-process ID as first child element. This isn't the case with Kitodo2 or VLS.
If derivans adds it's agent entry to the mets:metsHdr, it just appends this element as last child. This was no problem if only other agent-mark were present. But with Kitodo3 it results in schema invalid METS, since the METS specification expects agent elements to precede all other header children.
Description
METS exported from Kitodo3 contains nowadays the element
mets:metsDocumentIDwhich holds the local DB-process ID as first child element. This isn't the case with Kitodo2 or VLS.If derivans adds it's agent entry to the
mets:metsHdr, it just appends this element as last child. This was no problem if only other agent-mark were present. But with Kitodo3 it results in schema invalid METS, since the METS specification expects agent elements to precede all other header children.