On Mirador and Universal Viewer, images are not displayed from manifest, but thumbnails are.

[Can Özgür Yilmaz]

Hello,

When I use Mirador or Universal Viewer demos to display my manifest, I get black screen on images but the thumbnails are shown. When I inspect the requests the viewers send, I find out that the viewers build a request to my image server like this: "http://fue.onb.ac.at/sacha/services/images/Z152225709/00000003/info.json/1024,3072,1024,672/256,/0/default.jpg" . This request of course doesn't make sense, because it adds the image server parameters after info.json.

I found a similar problem here: https://groups.google.com/forum/#!searchin/iiif-discuss/mirador/iiif-discuss/YxAuTddcmiE/AG1tikf_sxcJ but my responses are conform with CORS mechanism and the IIIF presentation API validator validates the manifest successfully without a warning.

Does anybody know anything related to this?

Manifest example: http://fue.onb.ac.at/sacha/services/presentation/+Z152225709/manifest

My image server works as intended with the following links.
Image server image example: http://fue.onb.ac.at/sacha/services/images/Z152225709/00000003/1024,3072,1024,672/256,/0/default.jpg
Image server info.json example: http://fue.onb.ac.at/sacha/services/images/Z152225709/00000003/info.json

Thanks in advance,
Can

[Tom Crane]

Hi Can,

Your manifest asserts the image service like this:

• service: 

  {

  • @context: "http://iiif.io/api/image/2/context.json",
  • @id: "http://fue.onb.ac.at/sacha/services/images/Z152225709/00000002",
  • profile: "http://iiif.io/api/image/2/profiles/level2.json"

  }

Mirador and UV will append info.json to that @id and fetch the info.json:

http://fue.onb.ac.at/sacha/services/images/Z152225709/00000001/info.json

I think the problem is that this info.json asserts the image service id as:

{

• @context: "http://iiif.io/api/image/2/context.json",
• @id: "http://fue.onb.ac.at/sacha/services/images/Z152225709/00000001/info.json",

(i.e., it has an info.json at the end).

When Seadragon uses this as a tilesource to start making tile requests, it is appending the IIIF params after the id - after the "/info.json" on the end.

I think that's the problem here.

Tom

[Drew Winget]

Yes, this is the problem.

From what I understand, the spec requires the id to conform to the base uri syntax, so the base path must work for both a simple image request and for the image information request.

http://iiif.io/api/image/2.0/#uri-syntax

--
-- You received this message because you are subscribed to the IIIF-Discuss Google group. To post to this group, send email to iiif-d...@googlegroups.com. To unsubscribe from this group, send email to iiif-discuss...@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/iiif-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "IIIF Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iiif-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Drew Winget

Visualisation Engineer

Digital Library Systems and Services

Stanford, CA 94305

(972) 740-7974

[Can]

Yes, that was the problem. Thank you! I suggest that this should be add to the documentation of the presentation API, because I didn't see any specifications for the links to the image API in the presentation API docs. But anyways, thank you for the quick answer and the correct solution.

Can