BartChris
commented
1 year ago That would indeed be helpful. One challenge is probably how customizable a metadata mapping could be. How should the metadata keys be named for example. And more specific: If you want to embed links in the IIIF-metadata for example which come from Kitodo Metadata Groups. (e.g. GND url for a person) this requires custom processing logic. The question would be whether one could come up with an "authoritative" mapping describing how a METS file based on the DFG guidelines should be converted to IIIF. Or with a minimal solution which would produce usable manifests, which would have to be augmented by people who want more. IIIF is way less expressive than METS XML. This was one of the things i struggled with when adopting "generic" transformation solutions.
stweil
solth
Description
The Kitodo toolchain (Kitodo.Production + Kitodo.Presentation) complies to the DFG-Praxisregeln Digitalisierung and provides METS XML files with metadata used for the presentation.
Meanwhile there is growing need in the scientific communities for the additional format IIIF manifests. Such manifest files could be created from an existing METS file on demand, but it would also be possible to create them with Kitodo.Production.
Related Issues
See also the related issue for Kitodo.Presentation.
Expected Benefits of this Development
Providing IIIF manifests in addition to METS XML files is highly desired by users.
Estimated Costs and Complexity
I expect that it is easier to create IIIF manifest files in the production process than on demand, so the costs could be somewhere in the range from low to medium for that.