Can someone tell me what is wrong with this manifest

[Terry Reese]

Apologies if this duplicates -- I thought i posted this last night but I don't see it showing up on the list....

At Ohio State Lib., we recently have moved all our images into a repository that uses Loris to serve them.  This has allowed us to support the IIIF Image API.  I'd like to start working on supporting the Presentation API and as a quick proof of concept, just mocked up a manifest for a couple items assuming that I could then load this into mirador.  The problem is the validator is failing say that its not receiving a content type of JSON -- though when I look at the headers, it should be.  This makes me think something else might be wrong.  I'm sure it would be obvious to someone that has made many of these -- can someone take a quick look.  Here's the manifest: http://manifest.reeset.net/manifest.json

Thanks, 

--tr

[Esmé Cowles]

Terry-

I'm not sure. The content looks OK when I load it in a browser, but the manifest doesn't work if I try to plug it into mirador.stanford.edu. I tried to look at the headers with curl, but I get a 403 Forbidden. Trying to fetch /robots.txt also gives me a 500 Internal Server Error. So maybe there's something going on that's preventing the viewers or validator from fetching the manifest?

-Esmé

> --
> -- 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.

[Terry Reese]

Thank you Esme -- I had been using some tools on chrome to read the headers which is why I was confused.  This helps.

Thanks,

--tr

[Terry Reese]

Thanks Esme -- ended up being my host.  I got this sorted, now getting a different error in the validator regarding types.  Not seeing where I'm missing a type -- its too bad the validator doesn't provide a bit more feedback because I can't tell if this is a problem with this particular manifest or if it's trying to read other files referenced by the manifest?  

--tr

On Thursday, May 12, 2016 at 8:50:12 AM UTC-4, Esmé Cowles wrote:

[Robert Sanderson]

The annotations in the manifest are missing their @type.

Rob

--

Rob Sanderson

Semantic Architect

The Getty Trust

Los Angeles, CA 90049

[Terry Reese]

Thanks Rob.  I thought this block handled that: 

"@id":"http://manifest.reeset.net/canvas-1/annotation/p0001-image",

              "@type":"oa:Annotation",

              "motivation":"sc:painting",

But is this set in the otherContent block.  Does the annotation block need to be there at all?  

--tr

[Robert Sanderson]

Apologies, I was looking at an older version -- after refreshing the manifest I see the @type on the annotations in the images blocks :) Does it validate now?

Rob

[Terry Reese]

I added the otherContent section (just did) and now it validates.  (Whooho).  

New question --  I point this at Mirador and nothing happens.  Can I assume that each image then needs to have more than just the information presented from the image api, but must also have a manifest reflecting the presentation api in and of itself?  

Sorry for what I'm sure are basic questions -- but I'm trying to understand what has to be available in order to demonstrate the process with our data and be able to understand what needs to be created to make this work.

--tr

[Singhal, Rashmi]

Are you dropping http://manifest.reeset.net/manifest.json into Mirador? Or a different URL?

Rashmi

Rashmi Singhal
Senior Software Engineer

Arts and Humanities Research Computing

Harvard University Information Technology

rashmi_...@harvard.edu

[Terry Reese]

Rashmi, 

I'm dropping that URL (http://manifest.reeset.net/manifest.json)  into the mirador demo, and I'm not seeing anything happen.  

--tr

[Robert Sanderson]

You have a typo in the header name:

    Access-Content-Allow-Origin: *

Should be:

    Access-Control-Allow-Origin: *

Rob

[Terry Reese]

And so there is.  I changed the header and I'm seeing this now in curl: 

< Content-Type: application/ld+json

< Content-Length: 6142

< Connection: keep-alive

< Last-Modified: Thu, 12 May 2016 15:18:41 GMT

< Accept-Ranges: bytes

< Access-Control-Allow-Origin: *

This looks right now?  Still not seeing Mirador pull anything (from the demo site).  What am I still missing here?

Thanks all,

--tr

[Terry Reese]

Ok -- this loads in the Universal browser: http://universalviewer.io/examples/?manifest=http%3A%2F%2Fmanifest.reeset.net%2Fmanifest.json&locale=en-GB#?c=0&m=0&s=0&cv=0&z=-0.3225%2C-0.0733%2C1.645%2C1.4662

Still not seeing it in the mirador demo -- I'll build my own to see if I can get more info -- but I think I'm good now.  

Thank you so much everyone,

--tr

[Ed Summers]

Terry, I'm not sure if it helps but your manifest seems to work for me over at:

    http://projectmirador.org/demo/

[Mark A. Matienzo]

Hi Terry,

I might be mistaken, but the demo instance of Mirador on projectmirador.org might not be up to date to support the drag and drop feature. As Ed notes, if you add a new object to that Mirador instance, your manifest loads fine in that instance.

Mark

--

Mark A. Matienzo <ma...@matienzo.org> | http://anarchivi.st/

[Terry Reese]

Interesting -- I'm not seeing the same thing.  Maybe caching (on my end) at this point.  I'll clear caches and try again.  

Thanks,

--tr

[Singhal, Rashmi]

You might need to refresh the manifest a few times because I am now getting it to work in my Mirador instance.

The individual canvas requests also need to have the Access-Control-Allow-Origin header, though it's not breaking anything in Mirador.

.

[Singhal, Rashmi]

Also working on mirador.stanford.edu for me.

Rashmi

[Terry Reese]

I got it -- clearing my browser cache (chrome) is what seemed to do it.  

Thanks.  

--tr