GithubHelp home page GithubHelp logo

iiif-universe's Introduction

iiif-universe

Build Status

A Universe is a directory of catalogs published by service providers which lists their available assets. This Universe is intended to present a collection which points to other collections as machine-actionable JSON.

In catalogs, community-maintained IIIF collections are available for sites which don't appear to have a top-level IIIF collection.

Pull requests are welcome.

See also: https://graph.global/universes/iiif

iiif-universe's People

Contributors

ahankinson avatar demiankatz avatar dependabot[bot] avatar emmastanford avatar geyslein avatar jeffsteward avatar jennief avatar mattmcgrattan avatar mekarpeles avatar mikeapp avatar najamansari avatar ojlyytinen avatar regisrob avatar ryanfb avatar schwemmer avatar thanneken avatar tomcrane avatar tpendragon avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

iiif-universe's Issues

Broken endpoints and other issues

Some of the links in iiif-universe.json have issues of a few different kinds. I found three kinds of problems

  • Some simply return 404, 500 or some other error page and so just do not work at all.
  • Some use http instead of https. If the viewer is served over https you get mixed content errors. Most of these would actually redirect to https but due to the mixed content problem the browser won't get that far.
  • One endpoint works otherwise but has no CORS policy so cannot actually be used in any viewer.

Here are the details

  • Yale: uses http, no redirect and invalid certificate in https version
  • Yale Center for British Art: Error page, does not work at all
  • Stanford: No CORS policy
  • e-codices: uses http which gets redirected to https, internal URIIDs are https
  • Chronicling America Newspapers by State: 404
  • Sentences Commentary Text Archive: uses http which gets redirected to https, internal IDs are http which again then get redirected
  • Villanova University: uses http, redirects to https, internal IDs are https
  • Wellcome Library: uses http, redirects to https, internal IDs are https
  • The Internet Archive: Internal server error
  • Biblissima: uses http, redirects to https, internal IDs are http which again redirected
  • Shared Shelf Commons: error page
  • Jubilees Palimpsest Project: uses http, no redirect and invalid certificate in https version

I suggest removing the links that just don't work at all. If someone knows, or can find out, updated links then fixing them would of course be preferable to removing completely.

I also suggest that for all the ones which redirect to https and internally use https, the endpoint in iiif-universe.json should instead just have https. This would avoid the mixed content problem and https appears to be their preferred way of access anyway. In addition, currently iiif-universe.json has a collection with ID http://something but when you resolve that you get a collection with ID https://something, which technically is a different object and so the IIIF is broken. Having https to start with would avoid this as well.

The ones which redirect to https but internally use http are trickier. Changing the endpoint to https instead would just move the mixed content problem elsewhere. Also, you would have the problem of https references returning objects with http in the ID. So I suggest leaving these as is. Also obviously no changes should be made to the other ones which use http and have no working https version.

For the Stanford collection, which has no CORS policy, it technically works fine but in practice cannot actually be used. So could go either way, either remove or leave it.

I am happy to make the changes and submit a PR if these suggestions sound good.

graph.global web page needs to be updated

The landing page of the IIIF universe at https://graph.global/universes/iiif is not up-to-date with the latest iiif-universe.json.

There is a mistake in the "Catalogs by Institution" table: at line 3, the Artstor collection is listed in the same row as Biblissima. And the Biblissima collection should be "http://biblissima.fr/iiif/collection/top", as indicated in iiif-universe.json.

Would it be possible to make these changes? Is there a reason why the web page is outside of this repo?
Thanks!

cc @mekarpeles

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.