Interoperability in practise

[Janusz S. Bień]

Hi!

The manifests of my IIIF documents are served by uv-app-starter at

https://jsbien.github.io/Parkosz4IIIF/collection/ParkoszJBC/index.json
https://jsbien.github.io/Parkosz4IIIF/collection/ParkoszMF/index.json
https://jsbien.github.io/Parkosz4IIIF/collection/ParkoszPWN/index.json

When I use "Add resource" to add them to my local installation of
Mirador 3, the document is opened but pages are not displayed.

On 30th April I asked about on the Slack #mirador channel (in case of
mailing list I would be able to give the link to the thread...). I got
several reactions, in particular

--8<---------------cut here---------------start------------->8---
shaune: I wonder if Mirador 3 is currently assuming Image Resources and
not able to handle simple image URLs?

aeschylus: Yes, I don’t think it has the right processing logic for
static image urls at the moment.
--8<---------------cut here---------------end--------------->8---

To say the truth, I don't understand what is wrong: mirador?
uv-app-starter? something else?

Would you like to comment?

Best regards

Janusz

--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

[Edward Silverton]

I think Mirador isn't supporting IIIF level 0 image profiles

--
You received this message because you are subscribed to the Google Groups "Universal Viewer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to universalview...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/universalviewer/868sv8m9yf.fsf%40mimuw.edu.pl.
For more options, visit https://groups.google.com/d/optout.

[Janusz S. Bień]

On Wed, May 15 2019 at 8:56 +01, Edward Silverton wrote:
> I think Mirador isn't supporting IIIF level 0 image profiles

Any constructive proposal to serve on GitHub Pages documents usable by
Mirador without waiting for possible modifications of Mirador?

[Demian Katz]

Unfortunately, if the diagnosis is correct, this is really a problem on the Mirador side -- Mirador is assuming that you are using a full-fledged dynamic IIIF image server (known as "level 1" -- the recommended IIIF standard), and it isn't downgrading itself to handle the simpler static images you are hosting on GitHub (known as "level 0" -- the bare minimum IIIF standard). This seems like a problem that should be fixed in Mirador, since I’m sure you're not the only one who will be affected by it -- but I can't speculate on how long that will take, or where it would fall in the Mirador community's priority list.

In the meantime, one alternative might be to experiment with cloud-hosted IIIF images. I'm aware of at least one service (https://www.iiifhosting.com/) that offers this without requiring you to run your own server, and it looks like you can try it out for free. Alternatively, if you have the resources to run your own server, there are many good free packages to accomplish that... but you'll need heavier infrastructure than GitHub alone to accomplish it.

- Demian

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsites.google.com%2Fview%2Fjsbien&amp;data=02%7C01%7Cdemian.katz%40villanova.edu%7C3d4649fe04434dbac0e908d6d90ea5a2%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636935054274338385&amp;sdata=FNUy1DtHdFBra55XfkGpUsdfREN0zlF3LqiQ2fJs8Fg%3D&amp;reserved=0

--
You received this message because you are subscribed to the Google Groups "Universal Viewer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to universalview...@googlegroups.com.

To view this discussion on the web, visit https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Funiversalviewer%2F86h89wi0s4.fsf%2540mimuw.edu.pl&amp;data=02%7C01%7Cdemian.katz%40villanova.edu%7C3d4649fe04434dbac0e908d6d90ea5a2%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636935054274338385&amp;sdata=9oGhVWzB3Vm3a%2B8p6d5rawURnWwepHqkT3JsIDbF6ro%3D&amp;reserved=0.
For more options, visit https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&amp;data=02%7C01%7Cdemian.katz%40villanova.edu%7C3d4649fe04434dbac0e908d6d90ea5a2%7C765a8de5cf9444f09cafae5bf8cfa366%7C0%7C0%7C636935054274338385&amp;sdata=58sxqgj%2FhtmtXyVdvjoaJ9nEAL4xNFKRXjkcf1xHHx0%3D&amp;reserved=0.

[Janusz S. Bień]

On Wed, May 15 2019 at 11:27 +00, Demian Katz wrote:
> Unfortunately, if the diagnosis is correct, this is really a problem
> on the Mirador side -- Mirador is assuming that you are using a
> full-fledged dynamic IIIF image server (known as "level 1" -- the
> recommended IIIF standard), and it isn't downgrading itself to handle
> the simpler static images you are hosting on GitHub (known as "level
> 0" -- the bare minimum IIIF standard). This seems like a problem that
> should be fixed in Mirador, since I’m sure you're not the only one who
> will be affected by it -- but I can't speculate on how long that will
> take, or where it would fall in the Mirador community's priority list.

I will make a formal feature request and we will see :-)

>
> In the meantime, one alternative might be to experiment with
> cloud-hosted IIIF images. I'm aware of at least one service
> (https://www.iiifhosting.com/) that offers this without requiring you
> to run your own server, and it looks like you can try it out for
> free.

I'm aware of it and it seems exactly as you said: you try for free, but
not to use systematically for free.

> Alternatively, if you have the resources to run your own server,
> there are many good free packages to accomplish that... but you'll
> need heavier infrastructure than GitHub alone to accomplish it.

In other words, serving the recommended level 1 from GitHub Pages is
impossible?

That's what I suspected... Fortunately I have some ideas how to solve
the problem in the future.

Best regards

Janusz

--
,
Janusz S. Bien
emeryt (emeritus)

https://sites.google.com/view/jsbien

[Demian Katz]

> I'm aware of it and it seems exactly as you said: you try for free, but not to use systematically for free.

Exactly. It might be a way to test setting things up in the short term, but unless you're willing to pay, you would eventually need to replace it with something else.

> In other words, serving the recommended level 1 from GitHub Pages is impossible?

As far as I know -- the problem is that level 1 accepts a very broad range of parameters to generate image derivatives. It would not be practical to pre-generate the nearly infinite variety of tiles you would need in order to make a GitHub page respond correctly to every possible request. The advantage of level 0 is that it constrains the legal requests to a much smaller range, allowing static pregeneration.

- Demian

[Tom Crane]

I was sure Mirador had done this too but maybe I'm mistaken.

https://github.com/ProjectMirador/mirador/issues/520

... and look
https://github.com/ProjectMirador/mirador/issues/520#issuecomment-339714843

I have seen it working... so not sure what's up, maybe a regression?

Tom

--
You received this message because you are subscribed to the Google Groups "Universal Viewer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to universalview...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/universalviewer/86d0kk6iy2.fsf%40mimuw.edu.pl.
For more options, visit https://groups.google.com/d/optout.
________________________________

Confidentiality notice: This private and confidential e-mail has been sent to you by Digirati Limited. This is a UK limited company, registration number SC235053. The information in this e-mail (which includes any files transmitted with it) is confidential and may also be legally privileged. It is intended for the addressee only. Access to this e-mail by anyone else is unauthorised. It is not to be relied upon by any person other than the addressee except with our prior written approval. If no such approval is given, we will not accept any liability (in negligence or otherwise) arising from any third party acting, or refraining from acting, on such information. Unauthorised recipients are required to maintain confidentiality. If you have received this e-mail in error please notify the originator immediately, destroy any copies and delete it from your computer system. The unauthorised use, dissemination, forwarding, printing or copying of this e-mail is prohibited.

Thank you.

Digirati Limited, Unit G4, The Hub, 70 Pacific Quay, Glasgow G51 1EA | Dunstan House, 14A St Cross St London, EC1N 8XA
Telephone: +44 (0) 845 643 4370 | Website: digirati.com<https://digirati.com>

[Janusz S. Bień]

On Wed, May 15 2019 at 11:47 +00, 'Tom Crane' via Universal Viewer wrote:
> I was sure Mirador had done this too but maybe I'm mistaken.
>
> https://github.com/ProjectMirador/mirador/issues/520
>
> ... and look
> https://github.com/ProjectMirador/mirador/issues/520#issuecomment-339714843
>
> I have seen it working... so not sure what's up, maybe a regression?

Looks like a regression in Mirador 3.

> shaune 8:17 PM, May 1st
> * I wonder if Mirador 3 is currently assuming Image Resources and not able to handle simple image URLs? @Janusz
> S. Bień If you can copy/paste any JavaScript console errors, it could help us debug. @aeschylus Do you know off
> the top of your head?

The suggestions made on Slack to me appeared not feasible for the time
being, I would need to learn too much. I posted however the links to the
manifests, but there was no reaction.