Closed saracarl closed 6 months ago
Good idea! I think rendering should be used instead of seeAlso for some resources like PDF (especially the raw PDF without the text)
Am I right in thinking the related
in the v2 example above has been replaced by what we are populating for homepage
in the v3 versions?
Also, do we want to include all the derivatives, or just a subset? Can we come up with a list of which ones we think belong in rendering
and which should be in seeAlso
?
The language of the spec, specifically:
The rendering resource MUST be able to be displayed directly to a human user
seems to make it clear that we must make this distinction between e.g the PDF and the SQLite representations
I am starting on the plumbing for this, so although we don't need to answer these questions immediately, it would be useful to resolve soon.
Part of our mandate is to include as much data as possible to find via the API (I think of it as lighting the way for others who might want to include similar data). (see here for another discussion of this: https://github.com/ArchiveLabs/iiif.archivelab.org/issues/11#issuecomment-1473006921)
I'll work on which properties should be rendering
and which seeAlso
.
These are the human readable derivatives I decided should be rendering
rather than seeAlso
:
{
"label":"Item Tile",
"@id":"https://archive.org/download/hhfbc196-bingenontherhine/__ia_thumb.jpg",
"format": "image/jpeg"
},
{
"label":"Animated GIF",
"@id":"https://archive.org/download/hhfbc196-bingenontherhine/fbc.bs.196.bingenontherhine.jpg.gif",
"format": "image/gif"
},
{
"label":"Text PDF",
"@id":"https://archive.org/download/hhfbc196-bingenontherhine/fbc.bs.196.bingenontherhine.jpg.pdf",
"format": "application/pdf"
},
I'm a bit confused about IIIF's required type
property for each of these; the example in the spec uses "Text", but that isn't a type listed IIIF's Additional Types or in the W3C Web Annotation Data Model.
Am I right in thinking the related in the v2 example above has been replaced by what we are populating for homepage in the v3 versions?
Yes, agreed, the homepage
includes what seems to be the v2 related
.
This may be an edge case, but I'm wondering about the hOCR file type in https://archive.org/download/journalofexpedit00ford
PDF should plainly be rendering
, while DjVu should be seeAlso
, but hOCR is--at least in theory--human readable. That said, when I attempt to view the file, none of the bounding box information displays as there is no CSS or JS to process it, so I'm tempted to put this in seeAlso
since it requires an external program before a human can work with it.
seeAlso and format types:
Add more descriptive label than just format. See viewer behaviour:
Another example with lots of derivatives is https://archive.org/metadata/journalofexpedit00ford
A/V example with derivatives: https://archive.org/metadata/DuckandC1951
Create a curated list of formats we want to see in rendering
and seeAlso
. Current list:
(with Web Anno format)
I pulled all the derivatives out of both a book and a movie and put them in the following spreadsheet:
https://docs.google.com/spreadsheets/d/1C3CXCvTPBxi-kmF9KfakXT_CLHlOs3XVvR-2P6QH5Fk/edit?usp=sharing
I marked the rendering
properties; the others are all potential seeAlso
s. There's a lot. And we should discuss.
TODO: I think we should also look at an image item's derivatives.
Decided today:
seeAlso
s have profiles in the list of profiles, so no profiles needed.See spreadsheet for list of derivatives and their seeAlso/rendering classification.
<moved from https://github.com/ArchiveLabs/iiif.archivelab.org/issues/71 >
The IIIF spec supports use of linking properties like seeAlso and related to refer to other resources about an item from inside a manifest. The Internet Archive's abundant derivative files could be linked from IA manifests, allowing clients to consume these resources easily.
(Real-world use case: a IIIF client that imports a printed document, then wants to import the OCR text.)
To take an example, this item has a manifest with these simple linking properties 👍
Adding the derived files to the manifest would look like this: