Skip to content
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

Limit playback to selected time segment in structured navigation #778

Open
5 tasks
elynema opened this issue Feb 24, 2025 · 1 comment
Open
5 tasks

Limit playback to selected time segment in structured navigation #778

elynema opened this issue Feb 24, 2025 · 1 comment
Labels
investigation Related research work

Comments

@elynema
Copy link

elynema commented Feb 24, 2025

Description

With the migration of EVIADA content into MCO, Avalon has a use case for having playback based on the structured navigation terminate after the time segment completes playback.

In this case, if the user clicked on a heading in the structured navigation, playback should stop once that time segment completes playing. If the user clicked on a heading that has children, playback should continue through the children time segments and then stop once the parent time segment is completed.

Done Looks Like

  • Is this possible within IIIF?
  • Model what this manifest would like like
  • If we support this, does it break Ramp for other IIIF use cases?
  • Would Ramp default to auto-play?
  • Would it be strange for Ramp to work this way for EVIADA materials but different for other collections?
@elynema elynema added the investigation Related research work label Feb 24, 2025
@joncameron
Copy link
Contributor

joncameron commented Feb 26, 2025

The IIIF behavior property on ranges might be the way to implement this. Attributes on ranges would indicate to the viewer that only a specific portion of the full media should be presented to the user. There are probably a lot of tricky edge cases involved here.

Putting in options to remove default autoadvance etc. for collection managers could be a motivation to have SME handle IIIF ranges and structures more ably. SME creates structure data from manifests, and then uses that structure to update the manifest. In terms of evolution of SME, having the ability to create more flexible structures (like allowing for arbitrary nesting, as is common in IIIF).

We could model some IIIF structure in advance, and then build the desired UX around that.

Would be a good swarm topic: discussing IIIF structures and what they'd look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigation Related research work
Projects
None yet
Development

No branches or pull requests

2 participants