Closed tomcrane closed 6 months ago
@jtweed @Rioghnach if you give me (or we work out) some XML I could add the poster image to the transform process and the bag; the transform code can fetch the posterImage that the DDS has already deduced and put it in the bag:
Example (live):
https://wellcomelibrary.org/posterimages/0055-0000-4202-0000-0-0000-0000-0.jpg
This means Intranda would need to produce the same output.
Any other resources like this?
Contributor logos are different, I think: https://wellcomelibrary.org/biblio/b19862921/repositoryLogo
The DDS can manage them later.
I'm not aware of there being any other assets like these, I think that they're outliers.
@jtweed - can you take the XML question? I don't mind asking Intranda via a ticket on how best to deal with these in the future if that helps (although GitHub might make more sense).
Closing as context lost.
The association of a b number with its poster image isn't asserted in METS at all; the poster image isn't mentioned in METS or in any other system of record. It's deduced by convention. The DDS searches a location for jpgs that match the original file name of the media file. There are a number of naming conventions and the code tries to find a match.
In the absence of a local file system for the DDS to find the poster image in, where does it live?
Is it possible for the METS to include this information, and that a poster image is stored relative to the METS so that it ends up in the bag with the other assets?
A poster image is a bit of a grey area. Is it part of the digital object? Not in the same way the bytes of the AV stream are. An editorial decision could substitute a more fitting poster image for that object down the line, for use of that object in a particular context. But... a suitable poster is captured or associated as part of the digitisation workflow, whatever editorial activity might later follow. And at that point, the METS is the only place it can go. The photograph of Florence Nightingale that accompanies her wax cylinder recording is not part of the intellectual object, and neither is it a derivative like a thumbnail. Convenience would suggest it goes in the METS in some way, but other considerations may disallow it.
I need a suggestion for what the XML would look like in the METS that provides a
xlink:href
to the relative path of the poster image jpeg.Are there other assets that would be lost in this way if all Goobi's output goes into a bag?