tomcrane
commented
9 years ago Note for those not familiar with the Wellcome Library's material:
http://wellcomelibrary.org/player/b19974760
Chemist and Druggist is a great testbed for modelling periodicals in IIIF. It is large - ~6400 issues - but not as large as a daily newspaper. It covers over 100 years of publication.
I imagine the initial document loaded by the UV will contain a hierarchy of collections. Possibly ALL manifest references will be in this document (might as well, it compresses well over gzip and prevents multiple HTTP requests to build the nav). A daily newspaper would NOT all be in the initial collection. We could experiment with both approaches, but if we want to offer the ability to sort by date we might need the whole run to generate the navigation.
The link above (as of June 2015) does not use IIIF. We need to achieve the same UI without introducing semantics beyond IIIF 2.1. This feels possible with the two enhancements https://github.com/IIIF/iiif.io/issues/466 and https://github.com/IIIF/iiif.io/issues/442.
This is a refinement of #85.
See also https://github.com/IIIF/iiif.io/issues/442
We can use the current Wellcome Player implementation for http://wellcomelibrary.org/player/b19974760 and try to get as close to this as possible using IIIF 2.1 presentation spec - viewingHint on collection, navDate on manifests and sub collections.
It is possible that we won't be able to drive this UI exactly without additional semantics. If that's the case, then it still should work with navDate and viewingHint for other clients, but in the UV only might need some assistance from a seeAlso pointing to our extra info with a Wellcome-specific profile. But this is the last resort.
(I'm thinking of the division into volumes - but that is probably accomplished by sub-collections. I think we could have the ability to view by year/date (driven by navDate) and bu volume (driven by collection hierarchy) without requiring anything extra.