Sorry for the absolute-newbie question.
This is just about interpretation of image-validator output, but let me explain (you might have suggestions for solving my real problem connecting a particular IIIF client-server combination).
I have been using for several years a iipmooviewer+iipsrv+IIP protocol combination in a LAN.
I am really happy with how that combination works in our lab, but we want to open our images to public access 24/7 and my institution servers infraestructure is simply not enough.
So I am planning to use Zenodo instead, as its api is supposed to provide IIIF endpoints for stored images.
As iipmooviewer is also supposed to be IIIF-compatible, I'd like to keep using it as a client to Zenodo server.
But there is still an open iipmooviewer issue about that particular client-server combination (if anyone can help your comments are indeed very welcome!!).
There have been no updates in iipmooviewer for the last couple of years, and almost no participation in issues during the last 6-7 years, so I am a bit lost. I don't really know whether the issue is a wrong implementation of IIIF protocol by either iipmooviewer-client and/or zenodo-server, or perhaps they just simply use different (but correct) versions of the protocol.
I passed the above parameters and this is the image-validator output.
I see "green messages" for some items, but many other "red messages" which I don't fully understand.
Do they mean Zenodo is using a wrong IIIF implementation (so I should open an issue at zenodo)?
Or perhaps I am just using a wrong Version for this server? (I saw several 'image/2' substrings in info.json so I supposed I should check against that version)
Sorry for the absolute-newbie question. This is just about interpretation of image-validator output, but let me explain (you might have suggestions for solving my real problem connecting a particular IIIF client-server combination).
I have been using for several years a
iipmooviewer+iipsrv+IIP protocolcombination in a LAN. I am really happy with how that combination works in our lab, but we want to open our images to public access 24/7 and my institution servers infraestructure is simply not enough.So I am planning to use Zenodo instead, as its api is supposed to provide IIIF endpoints for stored images. As iipmooviewer is also supposed to be IIIF-compatible, I'd like to keep using it as a client to Zenodo server. But there is still an open iipmooviewer issue about that particular client-server combination (if anyone can help your comments are indeed very welcome!!).
There have been no updates in iipmooviewer for the last couple of years, and almost no participation in issues during the last 6-7 years, so I am a bit lost. I don't really know whether the issue is a wrong implementation of IIIF protocol by either iipmooviewer-client and/or zenodo-server, or perhaps they just simply use different (but correct) versions of the protocol.
I guess the first thing to do is checking whether the Zenodo served images' IIIF endpoint is correct. So I tried to use the validator here: https://iiif.io/api/image/validator And covered the form for this example image I got from a zenodo public record: https://zenodo.org/api/iiif/record:7354162:DSCF0021.JPG/info.json
https://zenodo.org/api/iiif/record:7354162:DSCF0021.JPGI left the defaults for the remaining data:
Version 2.0Level 1 - recommendedI passed the above parameters and this is the image-validator output.
I see "green messages" for some items, but many other "red messages" which I don't fully understand.
Level 1is too strict choice?Thanks a lot in advance for your help @abubelinha