/
Page Turners : The Landscape

Page Turners : The Landscape

Background

Book Reader Bingo: Which Page-Turner Should I Use? by Eben English

Hydra-Tech Discussions

https://groups.google.com/forum/#!searchin/hydra-tech/page$20turners/hydra-tech/JV9EyBNQckI/2aIIEH7CVkQJ

https://groups.google.com/forum/#!searchin/hydra-tech/page$20turners/hydra-tech/pFIO-lHudQU/Fs_gLuSBKgsJ

International Image Interoperability Framework (IIIF)

See: http://iiif.io/

In short, IIIF is a standards-based approach to serving and presenting images.

IIIF publishes two APIs:

Implementing IIIF requires three steps (as described in the IIIF Quick Start Guide)

  1. Deploy an image server, such as Loris or IIPImage
  2. Publish metadata that conforms to the Presentation API
  3. Deploy an IIIF-compliant viewer, such as Mirador, OpenSeadragon, the Wellcome Player, or develop your own.

The IIIF apps & demos page has a good summary of server and viewer options with a note on their IIIF compliance. 

Example IIIF Manifests

Note – some of the manifests above are still version 1.0, but 2.0 is almost backwards compatible.

Hydra (or Ruby on Rails) and IIIF

Notes of discussion at Hydra Connect, January 2014 on  Hydra and IIF

Discussion about  IIIF and Hydra Works

DCE have created RIIIF, an IIIF-compliant image streaming rails engine.

OSullivan - a ruby gem by Jon Stroop for producing IIIF Presentation JSON manifests: https://github.com/jpstroop/osullivan

 

Spiiiffy - ruby gem for creating IIIF manifests from METS files: https://github.com/pulibrary/spiiiffy

 

 

 

Related content

Hydra and IIF
Hydra and IIF
More like this
Thursday 19th February, 2015
Thursday 19th February, 2015
More like this
2015-03-26 Meeting Agenda/Notes
2015-03-26 Meeting Agenda/Notes
More like this
Page Turners - Current, Future and Requirements
Page Turners - Current, Future and Requirements
More like this
Image Swap Meet
Image Swap Meet
More like this
IIIF and Hydra Works
IIIF and Hydra Works
More like this