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

Logo/label #3

Open
mikeapp opened this issue Sep 24, 2018 · 3 comments
Open

Logo/label #3

mikeapp opened this issue Sep 24, 2018 · 3 comments

Comments

@mikeapp
Copy link

mikeapp commented Sep 24, 2018

It would be helpful to see the logo represented (or did I miss it?). Also, in addition to the requireStatement there is discussion of changing the logo to provider in order to allow a label. This would provide a label with identity of the agent/institution providing the manifest, as well as the logo. See IIIF/api#1639

@regisrob
Copy link

regisrob commented Oct 4, 2018

I agree the Manifest logo should be clearly displayed (this is a requirement for many institutions and it is clearly stated as a MUST in the Presentation API spec): it should appear somewhere in the catalog (at least in the album preview?) and also in the information/metadata panel of the album window.

I feel like the question of "attribution" will be quite challenging for the Mirador 3 UI design, because if Mirador 3 is meant to support both P-2 and P-3 Manifests, it would be expected to handle the display of both the requiredStatement and provider properties (P-API v3) and the old logo and attribution from P-API v2.1...

@regisrob
Copy link

regisrob commented Oct 4, 2018

related to #1

@ggeisler
Copy link
Collaborator

Thanks for pointing this out @mikeapp and @regisrob. We see ways to address this within our current design.

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

No branches or pull requests

3 participants