A presentation given at the International Image Interoperability Framework event held at the Museum of Modern Art in New York City on May 10, 2016. Presentation given by Tom Crane of Digirati

1. Tom Crane
Technical Director, Digirati
Digital Library Cloud Services
IIIF: Access to the World's Images – New York 2016
http://digirati.com/

2. DLCS for the Wellcome Library
• 1m images added every month
• Upcoming projects require annotations, more sophisticated search
and more
• Handle large amounts of traffic if necessary
• Build ad hoc applications using IIIF and annotations – crowd sourcing,
tagging…

3. Hypothetical aside…
• Need “Elastic Image Server” and other commodity services
• What does an “Elastic Image Server” service look like?
• Separate out the “commodity” services that conform to open
standards, and provide a managed implementation of them

4. DLCS - who is it for?
• Wellcome Library
...but also…
• Individuals
• School projects
• Small Collections
• Big Collections
• Small projects within Big Collections

5. What does it do already?
• Portal for humans
• API for machines
• IIIF Image API endpoints
• “Click-through” Access Control
• Simple generation of IIIF Presentation API resources based on
metadata

6. Demo
• Queue
• Batch
• Image
• Spaces
• Origin
• Roles
• Auth Services

8. Demo
• Make a IIIF endpoint for an image

11. API
• Might get a bit tedious…
• Wellcome Library have 22m images and counting
• You can upload a CSV file
• Need to integrate into digitisation workflow – or any other application
• => REST API

12. • I have 2 images in my repository (or 2 million)
• Here Github is the repository – but anything that can expose http(s),
ftp(s), s3 protocols will do

14. Given this API…
• Rather than show repository apps, explore some other uses of an
“Elastic Image Server” platform
• Demo app: iiif.ly

16. How does iiif.ly work?
• Your metadata plus “named query”
1. Select all the images in {space-name} with a string1 value of {string1} and order them by
{number1}
2. Project the images into a manifest with one sequence where each canvas in the sequence
corresponds to one image

17. Summary
• Not a repository
• Set of services to build standards-based applications
• build for Wellcome, make available to others
• Can use for IIIF image delivery
• Can generate “skeleton” IIIF resources from metadata
• To come – More authentication scenarios, Search (at various resource
levels), Annotations, PDF generation, OCR, Image Analysis, LDP for IIIF
CRUD

18. Thank you
https://dlcs.gitbooks.io/book/content/
http://digirati.com/iiif
Tom Crane
Technical Director, Digirati
http://digirati.com/
tom.crane@digirati.com