Rapid Digitization of Latin American Ephemera with Hydra
IIIF for Index of Christian Art
1. Jon Stroop
Library Digital Initiatives
Princeton University Library
The Index of Christian Art
Princeton, NJ * 26 June, 2014
2. Agenda
• Introduction to IIIF
• Image API
• Presentation API
• Exemplar Software Implementations
• Questions/Discussion
3. Digital Image Delivery is…
…too hard
…too slow
…too expensive
…too disjointed
…too ugly
…and we <repositories, software developers,
users, funders> suffer because of it.
4. Welcome to Silo-ville
Grain elevators, Caldwell, Idaho, by Lee Russell, 1941. http://www.loc.gov/pictures/resource/fsac.1a34206/
5. Distinct Concerns
Find, Use,
Analyze, Annotate
Want: Mix &
Match, Best of
Breed
Scholars
Tool
Makers
Repositories
Build useful
tools and apps
Want: Users &
resources
Host, Preserve (and Enrich) Resources
Want: Use of Resources, Enriching
services, Enriched content
6.
7. Books Manuscripts Newspapers
Art / Vis. Resources Archival Materials Maps
(Sheet) Music
Scrolls
STEM
Imagery
Architecture
IIIF Scope
8. Use Cases
…a paleographer who would like to compare scribal
hands from manuscripts at two different repositories
…an art & architecture professor who would like to
assemble a teaching collection of images from
multiple sources
…a humanities scholar who would like to annotate a
high resolution image of an historical map (but her
preferred annotation tool only is deployed against
other sites)
9. More Use Cases
…a repository manager who would like to drop a
newspaper viewer with deep zoom into his site with
no customization required
…a national library that would like to host digital
surrogates for resources held by smaller institutions
(without local IT capabilities), but let them present
resources with local branding
…a funder who would like to underwrite the
digitization of a new scholarly resource, but does
not want to pay for the development of yet another,
stand-alone, digital collection web site from scratch
10. IIIF Vision
Create a global framework by which image-based
resources (images, books, maps, scrolls, manuscripts, musical
scores, etc.)
…from any participating institution can be
delivered in a standard way
…via any compatible image server
…for display, manipulation and
annotation in any application,
…to any user on the Web,
…in any combination of elements.
11. IIIF Objectives
• Define APIs for
– Image Delivery
– Presentation
• Recruit repositories for API adoption
• Catalyze software development
– Zoomers, Viewers, Page Turners, Anno tools
– Really fast, really slippy image delivery
• Establish an ongoing effort
12. IIIF Participants
• ARTstor
• Bibliothèque
nationale de France
• Bodleian Libraries,
Oxford University
• British Library
• Cambridge
University
• Cornell University
• DPLA
• Europeana
• Harvard University
• le Louvre
• National Library of
Denmark
• National Library of
Norway
• National Library of Wales
• Princeton University
• St. Louis University, TPEN
• Stanford University
• Wellcome Trust
• Yale University
15. Audience and Scope
• The Web!
• Assumes a curated set of source images
• Region, Size, Rotation, Quality, Format
• Compression, color management, etc. are out
of scope
16. Image API URI Syntax
# Base URI
{scheme}://{server}{/prefix}/{identifier}
# Image Request
{$BASE}/{region}/{size}/{rotation}/{quality}{.format}
# Image Information (Metadata)
{$BASE}/info.json
20. IIIF Presentation API
• Just enough information to drive interoperable
image delivery
– labels, title, sequence, attribution, etc.
• Implements http://shared-canvas.org
• Relate parts of image-based resources
– Images, Text, Annotations, Transcriptions, Sequence /
Structure
• Good URI’s for linking data
• Support for annotation tools & initiatives
• No need to change internal data model or
internal data store
25. IIIF Software Wishlist
• Performant, community-supported image
servers
• Suite of zoom-pan-rotate clients
• “Next generation” page turners, cover flow &
gallery view clients
• Comparative and analytic tools
– multi-up, annotation, transcription
• Open source AND Commercial solutions
26. Software Tiers from a IIIF View
Open
SeaDragon
IIIF APIs
• Aware
• Content DM
• Djatoka
• FSI Server
IIP Moo
Viewer
OpenLayers
Internet
Archive
BookReader
Mirador
• IIP Image Server
• Loris
• Luratech
• Etc.
etc.
etc.
Image Servers
• Local data model
• Local data store
of choice
Metadata
• Marketplace
to pick “best
of breed”
• Plug and play
deployments
• Mix & match
clients for
different
needs
• Add new
capabilities
without new
development
• Swap out any
individual
component
28. Looking Forward
• Server (REST) API
• Authorization/Authentication
• Annotation API
• Discovery of IIIF-compatible Resources
• Adoption and Expansion
– Repositories & Software Developers
– Seasoning with Use Cases
– Connect!
• http://iiif.io
• IIIF-Discuss@googlegroups.com
29. Acknowledgements
• Mellon Foundation
• IIIF Working Group
• IIIF Editors
– Ben Albritton, Stanford University
– Tom Cramer, Stanford University
– Rob Sanderson, Stanford University
– Stuart Snydman, Stanford University
– Simeon Warner, Cornell University
Notes de l'éditeur
There are bright spots: SeaDragon, Deep Zoom, ChronoZoom, Djatoka, Google Art Project, Gallica, National Library of Norway newspaper viewer
The repositories and applications providing access to Digital Medieval Manuscripts in today’s environment are heavily silo’ed, with access to each repository provided through one off applications. This is a microcosm of the wider world of access to image based scholarly resources.
An idea is born at dinner after DMS Tech Meeting #3 among the BL, Oxford and Stanford: if it works for Manuscripts, why can’t the same principles and some of the same tools also work for all image based resources. Idea is diagrammed on the (paper) tablecloth.
There are bright spots: SeaDragon, Deep Zoom, ChronoZoom, Djatoka, GoogleArt
DMS Tech is a Mellon Funded project
DMS Tech is a Mellon Funded project
We started on common software stack, but quickly shifted to an API