-
Notifications
You must be signed in to change notification settings - Fork 5
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
Include rights and requiredStatement in metadata display component #331
Comments
Aviary utilizes the requiredStatement: https://weareavp.aviaryplatform.com/iiif/hm52f7jz70/manifest or https://yalemssa.aviaryplatform.com/iiif/028pc2tq0m/manifest |
Dananji has styled this to be similar to Mirador. |
This can be tested on Ramp demo site. |
@Dananji Do you have an example of an accessible manifest you were using for test that has these components? |
I used the demo manifest in Ramp which only has the changes in local dev environment. |
This is working fine for the examples Dananji listed. @Dananji is the code pulling in the label in the requiredStatement as the display label? All the examples listed here use the label "Attribution" so it's hard to tell. |
Yes the labels in the |
Description
This suggestion comes from the January IIIF A/V community call. For those who use rights and requiredStatement, they would probably like to have those displayed in the metadata component.
requiredStatement MUST be displayed, so that's a IIIF requirement.
rights is intended to be a machine-actionable uri, so we probably don't need to include that in metadata display: https://iiif.io/api/cookbook/recipe/0008-rights/
Done Looks Like
The text was updated successfully, but these errors were encountered: