Metadata-file: How can we add modsCollection to the MODS/METS file?

Hi,

We want to import data (METS-file) to a service that demands that the <mods:mods></mods:mods> is enclosed in a <modsCollection></modsCollection>.

If I understand correctly, this cannot be added using the ruleset. How can we add it?

Kind regards,
Maria

(Or more exactly
<modsCollection xmlns=“http://www.loc.gov/mods/v3
xmlns:xlink=“http://www.w3.org/1999/xlink
xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=“http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-5.xsd”></modsCollection>
)

Hi @mirkh

there are different options possible from my point of view:

Option 1

You could try to change every export mapping in the ruleset from "./mods:mods/..." to "./mods:collection/mods:mods/...". We did not test this, though.

Option 2

Another solution could be that you use the default export mechanism and add an automatic step with an XSLT transformation afterwards. This will work but you need to be aware, that after clicking the export icon (globe) you need to run the other step, too. Not very user friendly in case of manual changes and probably quite error-prone…

Option 3

You could use the goobi-plugin-step-exportPackage plugin and call the XSLT there. As this is a step plugin you need to be aware, that this does not have an effect to the globe icon, too. If it is the only export step in the workflow you won’t see the globe, too. This makes it less error-prone but not very user friendly, too.

Option 4

We develop an extension to the default export mechanism to call an optional XSLT transformation. If you are interested in this development feel free to contact us to clarify further things.

Best wishes from

Jan :slight_smile:

1 „Gefällt mir“