Documenting Top-Level IIIF Collections.json

[Mek Karpeles]

Hi all,

Can everyone please update this document with a link to the url of your institution's iiif presentation service and/or top-level collection.json:

https://docs.google.com/spreadsheets/d/1apQKFkfBV89BvycaBPN6v-LjeaKaVVMaMUsY6L4KRJo/edit?usp=sharing

[Mek Karpeles]

Alternatively, if you can post your link to this thread, I can update the spreadsheet (and the links will still be searchable through the list)

[Mek Karpeles]

13 services listed so far, only about 4 top-level collections.

Please update the spreadsheet with your service's information

[Régis Robineau]

Hi all,
Thanks Mickael for sharing this spreadsheet, it's a useful starting point for a registry. I'd suggest adding another column for HTTPS (yes/no/planned etc.), for ease of readibility.
It would be interesting to also have a column for comments, and maybe another one (or several ones) to point to manifests/collections that could be of particular interest for testing and demo purposes (manifests with ToC, annotations, detail images or image choices, collections with "members" or other advanced features of the API etc.).
Cheers,
Régis

--
Régis Robineau
Coordinateur web de l'Equipex Biblissima
regis.r...@biblissima-condorcet.fr
+33 (0)1 55 93 93 88

Campus Condorcet
20 avenue George Sand
93210 La Plaine Saint-Denis
www.biblissima-condorcet.fr
@biblissima

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

[Tom Crane]

Number of Image API endpoints as well as number of manifests? 

[Mek Karpeles]

Thanks for your kind words Régis. I (agree with you and) strongly believe with every ounce of my being that every institution should (using their IIIF presentation service) publish a top-level collection which lists all or a notable subset of notable manifests or collections.

I wish this was the required behavior of every IIIF presentation API (that if you visited the service's root, it returns a top-level collection.json). I strongly urge this be a requirement of the IIIF presentation spec.

The internet archive does this at: https://iiif.archivelab.org/iiif/collection.json

Because we don't have this, institutions are using `portals` to present their manifests and collections. In my humble opinion, this is just causing further fragmentation instead of delivering on the promise of interoperability.

Tom -- Image API endpoints are important to IIIF's adoption, so I'm happy having a column for this. My key concern is that we can discover content. Granted, discovering the actual presentation service itself is a prerequisite and a good start :)!

- mek

[Rafael Schwemmer]

I have added the top-level collection endpoint URI for e-codices to the spreadsheet.

[Matt McGrattan]

I've added the Bodleian's top-level collection. The number of manifests will be continually changing, but the top level collection will remain the same, and will be up to date (or at most 24 hours behind the latest manifest ingest).

Matt

[Ubbo Veentjer]

Hi,

TextGrid now also provides a toplevel collection, which distinguishes between
sandbox and published data. Link added to Spreadsheet.

Cheers, Ubbo

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

> <mailto:iiif-discuss...@googlegroups.com>.

> For more options, visit https://groups.google.com/d/optout.

--
Ubbo Veentjer
Research and Development

Georg-August-Universität Göttingen
Göttingen State and University Library
D-37070 Göttingen

Papendiek 14 (Historical Building, Room 2.409)
+49 551 39-7700 (Tel.)
+49 551 39-3856 (Fax)

veen...@sub.uni-goettingen.de
http://www.sub.uni-goettingen.de/
http://www.rdd.sub.uni-goettingen.de/

[Rafael Schwemmer]

I (agree with you and) strongly believe with every ounce of my being that every institution should (using their IIIF presentation service) publish a top-level collection which lists all or a notable subset of notable manifests or collections.

I wish this was the required behavior of every IIIF presentation API (that if you visited the service's root, it returns a top-level collection.json). I strongly urge this be a requirement of the IIIF presentation spec.

 

I agree with that. I am currently working on integrating some sort of "Discovery" into to the IIIF manifest editor. The spreadsheet shared in this thread and IIIF Universe were my main (very helpful) sources. If I could have just gone to each IIIF service's root to get the top-level collection list it would have been a lot more straightforward. 

Some of the (still quite few) available top-level collection URLs don't work at all or don't work via Ajax because of missing CORS headers. So as a reminder to everybody, please add CORS headers to the top-level collection URL as well, not just the manifests. Because of these issues, I initially used hard-coded JSON data for top-level collections discovery as a first pass, which of course is not a great approach and was addressed in this issue: https://github.com/bodleian/iiif-manifest-editor/issues/40. 

While updating the code to fetch data from top-level collection URIs directly instead of from hard-coded JSON, I encountered the following issues: 

• Biblissima (http://biblissima.fr/iiif/collection/top): does not work with Ajax because of missing CORS headers
  
• From the Page (http://fromthepage.com/iiif/collections): ditto
  
• Manuscriptorium (http://collectiones.manuscriptorium.com): ditto
• Stanford (https://graph.global/static/data/universes/iiif/stanford.json): ditto (@Stanford: do you have a dedicated top-level collection URI to use instead of the graph.global one?)
• National Library of Wales (http://dams.llgc.org.uk/iiif/2.0/4387112/manifest.json): Not a top-level collection URI (see spreadsheet)
• Chronicling America Newspapers by State (http://showcase.iiif.io/shims/chroniclingamerica/prezi/top.json): 403 Forbidden
  
• The Internet Archive Universal Collection (https://iiif.archivelab.org/iiif/collection.json): Internal Server Error
  

I hope these issues can be fixed so that there will be a lot more great content to discover via the IIIF Manifest Editor and other clients.

For the moment, these are the ones that work (i.e. when queried via Ajax in the IIIF Manifest Editor):

• Bodleian Library, Oxford (http://iiif.bodleian.ox.ac.uk/iiif/collection/All)
• Durham University (https://iiif.durham.ac.uk/manifests/trifle/collection/index)
• e-codices (http://www.e-codices.unifr.ch/metadata/iiif/collection.json)
• National Library of Scotland (https://view.nls.uk/collections/top.json)
• Sentences Commentary Text Archive (http://scta.info/iiif/scta/collection)
• Shared Shelf Commons (https://labs2.artstor.org/iiif/ssc/manifest.json)
• TextGrid (https://textgridlab.org/1.0/iiif/manifests/collection.json)
• Villanova University (http://digital.library.villanova.edu/Collection/vudl:3/IIIF)
• Wellcome Library (http://wellcomelibrary.org/service/collections/)
• Yale (http://manifests.ydc2.yale.edu/manifest)
• Yale Center for British Art (http://manifests.britishart.yale.edu/collection/top)

If anyone knows of any other top-level collection URI that is not listed here, please post them here or in the referenced spreadsheet or add it to IIIF Universe.

Thanks,

Rafael

[Benjamin L Albritton]

Rafael,

Thanks so much for doing this analysis - very helpful for everyone in the community!

As to:

"Stanford (https://graph.global/static/data/universes/iiif/stanford.json): ditto (@Stanford: do you have a dedicated top-level collection URI to use instead of the graph.global one?)"

I'm afraid not - I tried very hard to get this done during a development cycle this summer, but development and departmental priorities shifted before it could be completed. It's definitely something I'm advocating for within Stanford.

Best,

B.

---

From: iiif-d...@googlegroups.com <iiif-d...@googlegroups.com> on behalf of Rafael Schwemmer <rafael.s...@textandbytes.com>
Sent: Tuesday, September 5, 2017 1:37:00 PM
To: IIIF Discuss
Cc: michael....@gmail.com
Subject: Re: [IIIF-Discuss] Re: Documenting Top-Level IIIF Collections.json

 

[Shaun Ellis]

+1 

Rafael's approach would also allow for an Accessible way to load IIIF Resources into viewers/editors. See: https://github.com/IIIF/iiif-stories/issues/90

Rafael, I mentioned using Custom Search a while back for something like this, but I'm curious about your implementation. Does the Manifest Editor accommodate all Prezi API versions, or do you filter/flag unsupported ones before attempting to load?

On Tue, Sep 5, 2017 at 4:49 PM, Benjamin L Albritton <blal...@stanford.edu> wrote:

Rafael,

Thanks so much for doing this analysis - very helpful for everyone in the community!

As to:

"Stanford (https://graph.global/static/data/universes/iiif/stanford.json): ditto (@Stanford: do you have a dedicated top-level collection URI to use instead of the graph.global one?)"

I'm afraid not - I tried very hard to get this done during a development cycle this summer, but development and departmental priorities shifted before it could be completed. It's definitely something I'm advocating for within Stanford.

Best,

B.

---

From: iiif-d...@googlegroups.com <iiif-d...@googlegroups.com> on behalf of Rafael Schwemmer <rafael.schwemmer@textandbytes.com>

-- 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+unsubscribe@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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
-- 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+unsubscribe@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+unsubscribe@googlegroups.com.

[Robert Sanderson]

This is one of the approaches being discussed in the Discovery group, along with SiteMaps/ResourceSync, ActivityStreams, Schema.Org and others.

It falls under this section:  http://iiif.io/community/groups/discovery/charter/#crawling-and-harvesting

It would be great to participate in those discussions :)

Rob

--
-- 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+unsubscribe@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+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Rob Sanderson

Semantic Architect

The Getty Trust

Los Angeles, CA 90049

[Rafael Schwemmer]

Thanks Ben, Shaun and Rob for your feedback! @Ben: it would be great to have Stanford content in the IIIF Manifest Editor, so please keep advocating :-)

Rafael, I mentioned using Custom Search a while back for something like this, but I'm curious about your implementation. Does the Manifest Editor accommodate all Prezi API versions, or do you filter/flag unsupported ones before attempting to load?

My implementation is rather "primitive" for now. I basically copied the IIIF Universe JSON file into the manifest editor and updated it with all top-level collection URIs I could find. This JSON file is then used by the Discovery component to render a list of labels and logos with links to the top-level collection URIs. I manually tested each URI in the discovery component and only included those that work.

When clicking on the link for a "content provider", the component fetches that JSON and checks whether it is of type: "collection" or type: "manifest", allowing users to drill down into sub-collections until they reach a list of manifest links (a good example being the Wellcome Library, where you can browse by topic, author, genre etc.). Clicking one of these manifest links then loads the manifest into the editor. The code for the component is here: 
https://github.com/bodleian/iiif-manifest-editor/blob/develop/app/components/DiscoverManifestsDialog.jsx

While simple and only featuring 11 content providers so far, this already gives users access to thousands of manifests without having to go to different portals and copying individual manifest links or dragging and dropping them into the UI. Actual search would be much better though. 

[Nuno Freire]

On Thursday, February 18, 2016 at 10:27:27 AM UTC, Mek Karpeles wrote:

Thanks for your kind words Régis. I (agree with you and) strongly believe with every ounce of my being that every institution should (using their IIIF presentation service) publish a top-level collection which lists all or a notable subset of notable manifests or collections.

I wish this was the required behavior of every IIIF presentation API (that if you visited the service's root, it returns a top-level collection.json). I strongly urge this be a requirement of the IIIF presentation spec.

 

+1 here. To enable crawling and harvesting as mentioned by Rob Sanderson:  http://iiif.io/community/groups/discovery/charter/#crawling-and-harvesting

Cheers