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

Paged behavior on Collections #15

Open
mikeapp opened this issue Mar 20, 2019 · 1 comment
Open

Paged behavior on Collections #15

mikeapp opened this issue Mar 20, 2019 · 1 comment
Assignees
Milestone

Comments

@mikeapp
Copy link
Member

mikeapp commented Mar 20, 2019

Original Issue
IIIF/api#1680

Issue
Behaviors such as individuals and continuous are valid at the Collection level, but paged is not.

Background
The paged behavior could be used to indicate that a Collection should be presented in a page-turning interface if one is available. For example, when a multivolume work is represented as a paged multi-part Collection, clients might provide a page-turning interface that can easily advance from one Collection member to the next.

Solution
Allow the paged behavior on Collections.

@mikeapp mikeapp added this to the March 2019 Call milestone Mar 21, 2019
@azaroth42
Copy link
Member

Issue 15 (Paged behavior on Collections)

+1: 25 [aisaac awead azaroth42 cubap gigamorph hadro irv jbhoward-dublin jonhartzler joshuago78 jronallo julsraemy jwd kzhr markpatton mcwhitaker mixterj regisrob rentonsa rsinghal scossu sredick tomcrane tpendragon zimeon]
0: 1 [jtweed]
-1: 0 []

Result: 25 / 26 = 0.96

Super majority is in favor, issue is approved

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

No branches or pull requests

3 participants