I’m giving it a quick try at https://toolsadmin.wikimedia.org/tools/id/mirador ; but no clue what I’m doing so let’s see ^_^

Huh, that was easy: https://tools.wmflabs.org/mirador/?manifest=https://www.nga.gov/api/v1/iiif/presentation/manifest.json?cultObj:id=26

Ok, so:

• repo is at https://github.com/JeanFred/mirador-wrapper
• deployment instructions are included
• Maarten added as co-maintainer
• Tool added to Hay’s directory.

Anything else ? :)

I'm mostly just curious, how does https://github.com/JeanFred/mirador-wrapper/tree/master/deploy work?

Note that there has been some discussion on the IIIF mailing list as to whether a https://www.wikidata.org/wiki/Property:P1630 URL formatter should be added for the property:

https://groups.google.com/d/msg/iiif-discuss/J6mFf5gAAkk/v0ko1tpUBgAJ

Balance has I think so far been against adding such a default formatter, on the basis that (i) things that look like URLs ought to resolve to the URL they appear to be, rather than some different site; and (ii) given that there are multiple IIIF viewers, it could give a misleading view of IIIF to prefer one viewer over any of the others.

But discussion there wasn't a slam-dunk, and there was also sympathy for the idea of linking to something that will show what the IIIF manifest actually does, rather than just to a block of JSON.

In the short term, would it make sense to add appropriate P3303 values for multiple different viewers, perhaps with one preferred "anointed" one for Reasonator to follow?

Longer term, there's been a suggestion to create an intermediate jump-station with links to multiple different viewers, similar to the way that GeoHack acts as a portal to multiple different map views. But it remains to be seen whether anything will come of this proposal.

In T209697#4754750, @Jheald wrote:

Note that there has been some discussion on the IIIF mailing list as to whether a https://www.wikidata.org/wiki/Property:P1630 URL formatter should be added for the property:

https://groups.google.com/d/msg/iiif-discuss/J6mFf5gAAkk/v0ko1tpUBgAJ

Thanks for the link!

Balance has I think so far been against adding such a default formatter, on the basis that (i) things that look like URLs ought to resolve to the URL they appear to be, rather than some different site; and (ii) given that there are multiple IIIF viewers, it could give a misleading view of IIIF to prefer one viewer over any of the others.

But discussion there wasn't a slam-dunk, and there was also sympathy for the idea of linking to something that will show what the IIIF manifest actually does, rather than just to a block of JSON.

To be honest, I don’t have strong opinion either way − I saw that task lying there and mainly thought it would be fun to spin up a mirador instance on the Wikimedia Cloud. :)

In the short term, would it make sense to add appropriate P3303 values for multiple different viewers, perhaps with one preferred "anointed" one for Reasonator to follow?

Longer term, there's been a suggestion to create an intermediate jump-station with links to multiple different viewers, similar to the way that GeoHack acts as a portal to multiple different map views. But it remains to be seen whether anything will come of this proposal.

That being said, *if* we were to link to one or several IIIF viewers, I can see a strong argument for being ones that we host under the Wikimedia umbrella, for privacy reasons. For example, https://iiif.si.edu/mirador/ which is currently being a secondary third-party formatter URL for the IIIF property, does third-party requests requests to Google domains − I don’t think we should link to this if alternatives exist.

Also, I’m not sure the GeoHack/BookSources analogy is completely a good one: they are entry-points to vastly different services. By contrast, if there are 50 institutions out there hosting a Mirador instance, I don’t see any benefit in listing links to all 50 of them, since they all provide the same service.

Hi @JeanFred . The point is not so much to link multiple versions of the same viewer, but rather to link to some of the different viewers available, for example here is the Alba Madonna in the "Universal Viewer" used as a default by the Wellcome Collection and the British Library and others.

http://universalviewer.io/uv.html?manifest=https://www.nga.gov/api/v1/iiif/presentation/manifest.json?cultObj:id=26

Other viewers include OpenSeadragon (though I don't know if a live web-preview is available), possibly soon the Internet Archive viewer, and probably others.

In T209697#4754840, @Jheald wrote:

Hi @JeanFred . The point is not so much to link multiple versions of the same viewer, but rather to link to some of the different viewers available,
<snip>
Other viewers include OpenSeadragon (though I don't know if a live web-preview is available), possibly soon the Internet Archive viewer, and probably others.

Yes, I understood as much :) I should have made myself clearer − I specifically meant "if the various links are the same underlying viewer".

That's awesome @JeanFred . I updated the property to use our own viewer.

In T209697#4754583, @Legoktm wrote:

I'm mostly just curious, how does https://github.com/JeanFred/mirador-wrapper/tree/master/deploy work?

It’s an Ansible playbook − if you’re not familiar with it, it’s a configuration management tool through SSH. It’s called with ansible-playbook -i deploy/hosts deploy/main.yml -u jeanfred − it SSHs into the bastion host, become the tool, and runs the provisioning steps . In this case it’s not doing that much − https://github.com/JeanFred/wikiloves/blob/master/deploy/main.yml for Tool-wikiloves is a bit more interesting :)

In T209697#4754840, @Jheald wrote:

link to some of the different viewers available, for example here is the Alba Madonna in the "Universal Viewer" used as a default by the Wellcome Collection and the British Library and others.

http://universalviewer.io/uv.html?manifest=https://www.nga.gov/api/v1/iiif/presentation/manifest.json?cultObj:id=26

That was not too hard as well, so here you go :) https://tools.wmflabs.org/universalviewer/#?manifest=https://www.nga.gov/api/v1/iiif/presentation/manifest.json?cultObj:id=26

(Code at https://github.com/JeanFred/universalviewer-toolforge)

Oh, this is going a bit meta − but that plays well with @LucasWerkmeister wd-image-positions tool :) https://tools.wmflabs.org/mirador/?manifest=https://tools.wmflabs.org/wd-image-positions/iiif/Q1231009/P18/manifest.json

In T209697#4756034, @JeanFred wrote:

Oh, this is going a bit meta − but that plays well with @LucasWerkmeister wd-image-positions tool :) https://tools.wmflabs.org/mirador/?manifest=https://tools.wmflabs.org/wd-image-positions/iiif/Q1231009/P18/manifest.json

Just noticed R2422:dccf1d7a3678 :D

@JeanFred https://tools.wmflabs.org/universalviewer/ just gives a blank page? Shouldn't it give some sort of interface?

Thanks @Aklapper, that sounds good.

I’m happy to take bugs for either mirador or universalviewer projects.

@JeanFred I didn't create new ticket yet, but would it be possible to update the Mirador and Universal viewer to latest versions? Current ones are old and least Mirador latest has lot better mobile support now. Also latest Tify viewer would be nice addition for the viewers.

In T209697#7294371, @Zache wrote:

@JeanFred I didn't create new ticket yet, but would it be possible to update the Mirador and Universal viewer to latest versions? Current ones are old and least Mirador latest has lot better mobile support now. Also latest Tify viewer would be nice addition for the viewers.

Please do (one per tool)