-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
viewingHint for collections to distinguish curated vs multi-work object role #466
Comments
@tomcrane ... |
Example: http://wellcomelibrary.org/player/b18031511 A six volume work. Each volume needs its own structural information; it is an independent "readable object" with its own covers, TOC and chapters. Initially I tried to model this in IIIF as one manifest with six sequences, because we were using one package (in our pre-IIIF silo) per catalogue record. A package is (at first glance) very similar to a manifest, but with one crucial difference - a package has structures that are allocated assetSequences, and an assetSequence has sections that are allocated assets (http://player.digirati.co.uk/data-model.html#domainModel). So volumes/books are structures in the package, and chapters are sections in the assetSequence. The similarity of the names in the model sent me off on the wrong path I think. In a IIIF manifest, the structural information is asserted at the manifest level; ranges can be allocated canvases across sequences. There is no separation of structure of sequences and structure of canvases within sequences, because (I think) sequences are not modelling quite the same things I was modelling. In this model, b18031511 is one package with six sequences: http://wellcomelibrary.org/package/b18031511 (the zeroth assetSequence is in this JSON, and the other 5 are referenced right at the end of the file). Each sequence is independently dereferenceable and carries its own structural information about covers, TOC, chapters. In the IIIF Presentation API, while a sequence is obviously dereferenceable, any structural information is lost because it lives in the manifest. This is where I realised that I can't model it the same way; IIIF sequences are not modelling the same thing as my assetSequence - my interpretation of the IIIF model now is that a manifest models a single "readable object" (a manuscript, or one volume of this six volume work). Attempts to make one manifest per catalogue record will fail if the catalogue record describes multiple independent readable objects (although usually we DO have one catalogue record per readable object). A manifest might have more than one sequence if there are alternative proposed orderings of the canvases, but this example is six discrete books, therefore six manifests. This means that a sequence can't lose its structure when dereferenced; a sequence doesn't need its own independent structure. So now I do (or intend to do) this: Step 0 (for people and templates that don't know b18031511 is a multiple volume work): 302 Found, redirect: Step 2 (not implemented yet) Compare with a viewer loading http://example.org/iiif/collection/dutch_golden_age
What would this manifest look like for this book? And then, taking it to extremes: http://wellcomelibrary.org/player/b19974760 This package has 6361 sequences. In the periodicals/newspapers case, one manifest per issue with a hierarchy of collections above it seems sensible. With dates of course! |
Needs proposal... |
Closed with multi-part viewing hint; and added individuals viewing hint for non-multi-part |
Affects how the display might be presented, e.g. to step from one manifest to the next in a multi-work object rather than simply displaying them in a list for a curated set of distinct objects.
The text was updated successfully, but these errors were encountered: