Due refactoring with given <mets:fileGrp USE="MAX"> precedence over anything else if present, the stage before PDF rendering still holds the image paths the workflow started with, because these point to what Kitodo2 Export Workflow enriches there - which are the TIF-images.
Therefore it sets these altered fix like xlink:href="MAX/00000001.tif" , which leads in the end to intermediate paths like IMAGE_80/00000001.tif which are nonsense, since they are JPG files.
There's need to change the PDF input depending on the actual real input files, which have changed during previous derivans steps.
M3ssman
commented
1 year ago
Description
Due refactoring with given
<mets:fileGrp USE="MAX">precedence over anything else if present, the stage before PDF rendering still holds the image paths the workflow started with, because these point to what Kitodo2 Export Workflow enriches there - which are the TIF-images.Therefore it sets these altered fix like
xlink:href="MAX/00000001.tif", which leads in the end to intermediate paths likeIMAGE_80/00000001.tifwhich are nonsense, since they are JPG files.There's need to change the PDF input depending on the actual real input files, which have changed during previous derivans steps.