1. Why IIIF? Shane Huddleston Jeff Mixter Dave Collins Product Manager
CONTENTdm Users Group – August 1, 2018
Why IIIF?
Shane Huddleston
Jeff Mixter
Dave Collins
Product Manager
OCLC
Software Engineer
OCLC
Consulting Software Engineer
OCLC

2. IIIF is the International Image Interoperability FrameworkTM
An emerging web standard for sharing information about images and other media​
Simplifies and standardizes the ways we ask for and consume media data

3. What does that mean? Shared API for access to images
Shared API for access to record structure and metadata
Shared content viewers
Best practices for data management
manuscripts
newspapers
much more

4. What else?
“The IIIF is driven by a community of research, national and state libraries, museums, companies and image repositories committed to providing access to high quality image resources.”
source:

5. IIIF is a community Regular working group conference calls
Conferences and meetups (see
Mailing list & Slack team
IIIF Consortium
This engagement is how it succeeds.

6. How does IIIF work? Four APIs (for now) Image Presentation
Authentication
Search

7. IIIF Image API Request technical information (width, height, scaling)
Request scaled images or portions of images
Often supports rotation, image formats
Create a complete image viewer, like OpenSeadragon
Images for any UI (thumbnails, galleries, etc.)

8. Building an Image API request
{protocol} :// {domain} /
{prefix} /
{identifier} /
{region} / {size} /
{rotation} /
{quality} . {format}
digital/iiif/
p10010coll1/42/
full/full/ 0/
default.jpg

9. Building an Image API request
{protocol} :// {domain} /
{prefix} /
{identifier} /
{region} / {size} /
{rotation} /
{quality} . {format}
digital/iiif/
p10010coll1/42/
full/pct:10/ 0/
default.jpg

10. Using the Image API Use Image API calls like any other image
<img src=
"
18/full/full/0/default.jpg">
For example:
Experiment:

11. IIIF Presentation API Provides structural data about records
Managing annotations
Enough metadata for display in a user interface
Other systems do not need to understand and parse metadata schemas

12. IIIF Authentication API
“pattern for interacting with arbitrary third party protocols”
Presenting authentication to users and applications
Not a replacement for the actual authentication process
CAS; OAuth2
Not implemented in CONTENTdm

13. IIIF Search API Searching within a given IIIF record
E.g. full text search within a digitized manuscript
Search focuses on IIIF Annotations
OCR text
User contributed information
Not implemented in CONTENTdm

14. IIIF and the world of tomorrow!

15. The future of the IIIF Community

16. IIIF Community Groups There are 6 IIIF Community Groups
Develop best practices and use cases around existing IIIF APIs
Newspapers Community Group
3D Community Group
Manuscripts Community Group
Museums Community Group
Outreach Community Group
Software Developers Community Group

17. IIIF Consortium The Consortium is growing!

18. IIIF Managing Director
IIIF Consortium is looking for a Managing Director

19. Annual Working Group Meeting
December 3-6 in Edinburgh Scotland
Mostly technical
Voting on new API versions and work of the Technical Groups

20. Annual IIIF Meeting TBD but will be in May, 2019 somewhere in Europe
More generalized IIIF talks/presentations

21. The future of IIIF API development

22. IIIF Technical Working Groups
There are 3 IIIF Technical Specification Groups
Focused on development of the new/existing APIs
Discovery Technical Specification Group
A/V Technical Specification Group
Text Granularity Technical Specification Group

23. Continued API Refinement
Presentation API 3.0
Image API 3.0

24. Presentation API 3.0 Support for Video and Audio! Alpha Draft
Need to account for time and space in the data model
Alpha Draft

25. Image API 3.0 Support for Video and Audio!
Encode audio and video technical information in the data
Fix some API oddities and irregularities …!?!?
Do things better and in a more consistent way
Alpha Draft

26. And the others
Search API will need updated based on changes to Annotations in the Presentation API 3.0
Authentication API… ?

27. Discovery Working Group
The Discovery Group is focused on developing and Discovery API
Intra and Inter-domain discoverability
Current focus is how to improve discoverability and harvesting of IIIF materials by organizations with an interest/understanding of IIIF
Discovery Working Group Charter -

28. IIIF Discovery API
Provide a standard way for Publishing and Harvesting IIIF content on the Web
Intra-domain discovery – IIIF Provider to IIIF Provider
Inter-domain discovery – Search Engines
Site Maps – HTML
Resource Sync - XML
Activity Streams - RDF

29. IIIF Discovery API
Provide a standard way for Publishing and Harvesting IIIF content on the Web
Intra-domain discovery – IIIF Provider to IIIF Provider
Inter-domain discovery – Search Engines
Site Maps – HTML
Resource Sync - XML
Activity Streams - RDF

30. IIIF Discovery API Currently in version 0.1 Discovery API Draft
Hopefully will be 1.0 soon-ish
Discovery API Draft

31. Community + Standards: OCLC’s Future

32. CONTENTdm Community engagement
Workshops to help CDM users better understand IIIF and how it works with CONTENTdm
Collect feedback on what you want to do with your data in CONTENTdm and see how that maps to IIIF services, tools, features, etc.

33. IIIF Community engagement
Helping develop and improve the IIIF APIs
Representative of the data and services needs of the CDM community
Help develop community best practices for IIIF
Encourage the CDM community to get involved in the Community Groups
Or propose your own!

34. CONTENTdm IIIF Support
CONTENTdm will create and maintain IIIF Collection Manifests
Descriptions of CONTENTdm Collections
Based on the IIIF Presentation API
Collections will point to all individual items
All Items will point back to the collection

35. Continued production support & development
Evaluate new IIIF APIs and new versions for future CONTENTdm support 
Support for Mirador

36. OCLC Research IIIF Work
IIIF R&D
OCLC Research contributes to the development of the IIIF Discovery API
Providing Use Case
Proofs of Concept
Actively supporting a prototype of a Discovery API endpoint
8 CDM Users covering 1.8 Million Items

37. Discovery API Prototype
Endpoints can be harvested and the item metadata can be indexed for searching
OCLC Research is prototyping what a cross-CDM Collection discovery layer looks like

41. Broader opportunities
No reason we have to focus just on CDM
Using the IIIF Standards we could harvest any IIIF resources and build an index for search
specialty indexes

42. So What? Dedicated collaborative effort at OCLC to support IIIF:
IIIF Community
CONTENTdm IIIF service support
CONTENTdm Community understanding of IIIF
“Together we make breakthroughs possible”…
“, both big and small”

43. Workshop links