You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Ramp generates a conventional TOC when given a Manifest containing a Range that has a property of behavior whose value is thumbnail-nav, contrary to the IIIF Presentation API v3.0.
See the Sections area of the Ramp GUI. Screenshot below shows what it looks like for me.
Expected behavior
When thumbnail-nav is the value of a behavior property in a Range, "Clients SHOULD NOT use them to generate a conventional table of contents." (IIIF Presentation 3.0 API, need to scroll down a bit from there.) IIIF Presentation API 3.0 does not specify deterministically what should happen, but does suggest using the thumbnails along a timeline for a video, in the manner of thumbnail scrubbing.
Screenshots
Desktop
OS: MacOS 14.1.2
Browser: All
Version: All
Additional context
The branch is not building in our IIIF Cookbook repository, so there is no remote location for pointing to a manifest that will have IIIF-hosted URIs for all dynamic content. For the time being it needs to be downloaded and run locally.
The text was updated successfully, but these errors were encountered:
Describe the bug
Ramp generates a conventional TOC when given a Manifest containing a Range that has a property of
behavior
whose value isthumbnail-nav
, contrary to the IIIF Presentation API v3.0.To Reproduce
Expected behavior
When
thumbnail-nav
is the value of abehavior
property in a Range, "Clients SHOULD NOT use them to generate a conventional table of contents." (IIIF Presentation 3.0 API, need to scroll down a bit from there.) IIIF Presentation API 3.0 does not specify deterministically what should happen, but does suggest using the thumbnails along a timeline for a video, in the manner of thumbnail scrubbing.Screenshots
Desktop
Additional context
The branch is not building in our IIIF Cookbook repository, so there is no remote location for pointing to a manifest that will have IIIF-hosted URIs for all dynamic content. For the time being it needs to be downloaded and run locally.
The text was updated successfully, but these errors were encountered: