Table of Contents Component #3
brittnylapierre
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Background Information about the CRKN Manifests:
Use case for building indexes into CRKN IIIF manifests as ranges.
Subsections of newspapers, books, etc. especially with our Héritage microfilm reels.
Breaking reels out into volume numbers would save a massive amount of time for both our end users and our staff.
For example, this is a digitised reel:
https://heritage.canadiana.ca/view/oocihm.lac_reel_c370
Which corresponds to this in LAC (Libraries and Archives Canada:)
https://recherche-collection-search.bac-lac.gc.ca/eng/home/record?app=fonandcol&IdNumber=128876
With the individual volumes listed here:
https://recherche-collection-search.bac-lac.gc.ca/eng/Home/Search?DataSource=Archives|FonAndCol&SearchIn_1=PartOfEn&SearchInText_1=128876
Researchers need to know how to go from LAC’s website to heritage.canadiana.ca then need to know how to find the reel (oocihm.lac_reel_c370) in Héritage. Then, they manually must look for the individual volume they are interested in. These reels can contain thousands of individual images, and the volume numbers provide valuable guideposts for locating a specific file or image.
Example - these are starting pages for 3 volumes that are on this reel,
https://heritage.canadiana.ca/view/oocihm.lac_reel_c370/2
https://heritage.canadiana.ca/view/oocihm.lac_reel_c370/115
https://heritage.canadiana.ca/view/oocihm.lac_reel_c370/163
People need to flip through the reel manually as they are not indexed into a table of contents. LAC also does not offer positional information for where a volume might start on a digitized reel.
By adding a table of contents into our manifests, making them visible in the UI, and possibly making those searchable, we will greatly reduce the pain points of a Héritage researcher needing to navigate back and forth between the two websites, and needing to flip through a reel blindly in heritage.canadiana.ca to find the volume they are looking for.
Table of Contents Component Use Case:
We would like to have ranges per each volume in a reel in the CRKN IIIF manifest representing the reel.
We would like a table of contents on the side of the viewer shown in heritage.canadiana.ca to show the volumes in the reel.
This table of contents element should handle nested ranges - in case there is a table of contents for an individual volume that is also represented as a sub-range within the manifest.
This component can offer a standardized way of navigating through manifest ranges.
By offering a standardized way of navigating manifest ranges, we can help the community improve UX of all IIIF software overall. Effectively creating a manifest range navigation ‘UX pattern.’
“UX patterns increase usability. UX patterns are useful in aligning with common standards and expectations for how your product should work based on how other products have worked.” (Excerpt from: https://dianecronenwett.com/how-ux-patterns-create-intuitive-user-experiences/)
Beta Was this translation helpful? Give feedback.
All reactions