Provide Goobi process ID in ruleset export definitions
It's nearly impossible to determine the correct Goobi process once a project has been exported. Ruleset mappings should allow for mapping the internal Goobi process ID to METS XML elements on export.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I think quite every customer has the catalogue ID in METS as metadata value. The file names usually contain the process names of Goobi. Can these values not be used, to retrieve the correct volume in Goobi?
--
Steffen Hankiewicz, intranda
There are several reasons, why this may not be sufficient. We are for example working on a Fedora based repository which should hold all the METS data produced with Goobi. So we won't have single files any more and therefore can't rely on file names if the Goobi process ID is needed. The catalogue ID on the other hand isn't a unique identifier because you can have more than one process with the same catalogue ID in Goobi. Generally the metadata should be in the METS file and not part of its name.
--
Sebastian Meyer, SLUB
