Downloaded 12 times
![Sample Image Requests – Rotation
( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} )
0
{$BASE}/full/full/0/native.jpg
90
{$BASE}/full/full/90/native.jpg
(etc.)
[Arbitrary]
{$BASE}/full/full/75/native.jpg](https://image.slidesharecdn.com/iiifforcni2014s-final-140401150135-phpapp02/85/IIIF-for-CNI-Spring-2014-Membership-Meeting-42-320.jpg)
![Sample Image Information Response
( {$BASE}/info.json )
{
"@context": "http://library.stanford.edu/iiif/image-api/1.1/context.json",
"@id":
“http://libimages.princeton.edu/loris/pudl0052%2F6131707%2F0000000
1.jp2",
"formats": [ "jpg", "png", "gif" ],
"width": 122877,
"height": 3783,
"profile": "http://library.stanford.edu/iiif/image-
api/1.1/compliance.html#level2",
"qualities": [ "native", "bitonal" ],
"scale_factors": [ 1, 2, 4, 8, 16, 32, 64, 128 ],
"tile_height": 1024,
"tile_width": 1024
}](https://image.slidesharecdn.com/iiifforcni2014s-final-140401150135-phpapp02/85/IIIF-for-CNI-Spring-2014-Membership-Meeting-45-320.jpg)
![API Responses
• Content-Type: application/ld+json
• Example: Canvas
{
// Metadata about this Canvas
"@context":"http://www.shared-canvas.org/ns/context.json",
"@id":"http://www.example.org/iiif/book1/canvas/p1.json",
"@type":"sc:Canvas",
"label":"p. 1",
"height":1000,
"width":750,
"images": [
{
"@type":"oa:Annotation"
// Link from Image to Canvas should be included here, as below
}
],
"otherContent": [
{](https://image.slidesharecdn.com/iiifforcni2014s-final-140401150135-phpapp02/85/IIIF-for-CNI-Spring-2014-Membership-Meeting-54-320.jpg)
More Related Content
Similar to IIIF for CNI Spring 2014 Membership Meeting
IIIF for CNI Spring 2014 Membership Meeting
- 1. Tom Cramer Chief TechnologyStrategist Stanford University Libraries @tcramer CNI Spring Member Meeting St. Louis, MO * March 31, 2014
- 2. Agenda • Introduction toIIIF – Meet Ben and Otto • Image API • Metadata API • Exemplar Software Implementations • Discussion
- 3. Digital Image Deliveryis… …too hard …too slow …too expensive …too disjointed …too ugly …and we <repositories, software developers, users, funders> suffer because of it.
- 4.
- 5. Rocket Ships ofDigital Scholarship Parker on the Web e-codices
- 6. Houston …we havea problem Parker on the Web Roman de la Rose DIAMM eCodices Gallica Oxford Chuck Bryant -- http://www.fotopedia.com/redirect?u=http%3A%2F%2Fwww.flickr.com%2Fphotos%2F11707181%40N03
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Bibliothèque nationale deFrance 14
- 15. National Library ofNorway 15
- 16.
- 17. Welcome to Silo-ville Grainelevators, Caldwell, Idaho, by Lee Russell, 1941. http://www.loc.gov/pictures/resource/fsac.1a34206/
- 18. A World ofSilos & Duplication • Every repo a silo ( no interoperability) • Every app a one-off (overhead to code and keep) • Every user forced to cope ( many UIs, little integration) Parker Data Store Parker App Rose Data Store Rose App BnF Data Store Gallica St. Gall Data Store St. Gall App X Data Store App X
- 19. 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
- 20. APIs Enable Reuse Dictionaryof Old English Image Delivery Parker Data Images MD Annot. Repository Canonical Data Store for Images, Description, and TechMD Applications User interfaces present DMS data with specialized tools and contexts Des- cription Parker App Image Delivery Search Des- cription TPEN Transcription Tool Image Delivery Trans- criptions API's Import & Export DMS apps and tools can both consume and contribute data via common web services. E.g., transcriptions or annotations can be deposited in the source repository, enriching the corpus for future researchers. API's RESTful Web Services
- 21. APIs -> Framework-> Ecosystem GallicaParker App Image Delivery Search Des- cription Annotation & Transcription Tools Image Delivery Trans- criptions Parker Data Images MD Annot. Oxford Data Images MD Annot. Rose Data Images MD Annot. BnF Data Images MD Annot. API's API's API's API's Image Delivery Search Des- cription Cross Repository Search & Delivery Environments Image Delivery Search
- 23. Oxford, BnF, NPDL,LoC, Stanford, KB?, Europeana, BL, Norway?, JHU $, Mellon?, JISC, CLIR Bodeguita del Medio 3/19/11 Sean Neil Tom Consortial development Small donation Free-for- academic license? Web services + APIRich Clients Html 5 djatoka Image interoperable framework
- 24. Books Manuscripts Newspapers Art/ Vis. Resources Archival Materials Maps (Sheet) Music Scrolls STEM Imagery Architecture IIIF: Extend DMS To…
- 25. Use Cases …a paleographerwho 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)
- 26. More Use Cases …arepository 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 doesn’t want to pay for the development of yet another, stand-alone, digital collection web site from scratch
- 27. Meet Ben &Otto Otto Ege, 20th c. Biblioclast Ben Albritton 21st c. manuscripts scholar
- 28. Otto Ege, MS1 - 1940
- 29. Otto Ege, MS1 - 2014
- 30. Stanford Leaves ofEge MS 1 MISC 0305 - http://purl.stanford.edu/kq131cs7229
- 31. Stanford Leaves ofEge MS 1 http://guillaumedemachaut.com/mirador/index_ege.html
- 32. IIIF Vision Create aglobal 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.
- 33. IIIF Participants • ARTstor •Bibliothèque nationale de France • Bodleian Libraries, Oxford University • British Library • Cambridge University • Cornell University • DPLA • Europeana • Harvard University • Johns Hopkins 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
- 34. IIIF Objectives • DefineAPIs for – Image Delivery – Metadata (to drive image 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
- 35.
- 36.
- 37. Audience • The Web! •Assumes a curated set of source images • Compression, color management, etc. are out of scope
- 38. IIIF Image APIURI Syntax # Base URI {scheme}://{server}{/prefix}/{identifier} # Image Request {$BASE}/{region}/{size}/{rotation}/{quality}{.format} # Image Information (Metadata) {$BASE}/info.json
- 39. Sample Image Requests– Region ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) Full Size {$BASE}/full/full/0/native.jpg By Pixel {$BASE}/780,100,1100,1000/full/0/native.jpg By Percentage{$BASE}/pct:50,50,50,50/full/0/na tive.jpg
- 40. Sample Image Requests– Size ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) Full {$BASE}/full/full/0/native.jpg By Percentage {$BASE}/full/pct:10/0/native.jpg By Width {$BASE}/full/200,/0/native.jpg By Height {$BASE}/full/,200/0/native.jpg
- 41. Sample Image Requests– Size cont’d ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) By Width and Height, Aspect Preserved {$BASE}/full/!200,200/0/native.jpg By Width and Height, Aspect Forced {$BASE}/full/200,200/0/native.jpg
- 42. Sample Image Requests– Rotation ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) 0 {$BASE}/full/full/0/native.jpg 90 {$BASE}/full/full/90/native.jpg (etc.) [Arbitrary] {$BASE}/full/full/75/native.jpg
- 43. Sample Image Requests– Quality ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) Native {$BASE}/full/full/0/native.jpg Color {$BASE}/full/full/0/color.jpg Greyscale {$BASE}/full/full/0/grey.jpg Bitonal {$BASE}/full/full/0/bitonal.jpg
- 44. Sample Image Requests– Format ( {$BASE}/{region}/{size}/{rotation}/{quality}{.format} ) JPG {$BASE}/full/full/0/native.jpg PNG {$BASE}/full/full/0/native.png * See http://iiif.io/api/image/1.1/#parameters-format for a complete list of extensions
- 45. Sample Image InformationResponse ( {$BASE}/info.json ) { "@context": "http://library.stanford.edu/iiif/image-api/1.1/context.json", "@id": “http://libimages.princeton.edu/loris/pudl0052%2F6131707%2F0000000 1.jp2", "formats": [ "jpg", "png", "gif" ], "width": 122877, "height": 3783, "profile": "http://library.stanford.edu/iiif/image- api/1.1/compliance.html#level2", "qualities": [ "native", "bitonal" ], "scale_factors": [ 1, 2, 4, 8, 16, 32, 64, 128 ], "tile_height": 1024, "tile_width": 1024 }
- 46.
- 47. IIIF Metadata • Justenough metadata to drive interoperable image delivery – labels, title, sequence, attribution, etc. • Based on http://shared-canvas.org – Synthesis of OA (Open Annotation) and DMS • 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: produce IIIF Metadata dynamic trransforms; deliver via API on request
- 48. • Developed outof the Digital Manuscript Interop Work • Provides a “lingua franca” for modelling image & text- based digital resources • Based on Linked Data: Web and annotation-friendly! Shared Canvas Data Model
- 49. http://www.shared-canvas.org Shared Canvas toRelate Parts
- 50. Primary Resources There areother types of resource including Annotation Lists, Annotations, Ranges and Layers
- 51. Metadata Fields Other metadatafields are possible if required – by extension or endorsed by the community
- 52.
- 53. API Requests • Base:{scheme}://{host}/{prefix}/{identifier} • Resources: – /manifest.json – /sequence/{name}.json – /canvas/{name}.json – /annotation/{name}.json • See Open Annotation for more details • http://www.w3.org/community/openannotation/
- 54. API Responses • Content-Type:application/ld+json • Example: Canvas { // Metadata about this Canvas "@context":"http://www.shared-canvas.org/ns/context.json", "@id":"http://www.example.org/iiif/book1/canvas/p1.json", "@type":"sc:Canvas", "label":"p. 1", "height":1000, "width":750, "images": [ { "@type":"oa:Annotation" // Link from Image to Canvas should be included here, as below } ], "otherContent": [ {
- 55.
- 56. IIIF Software Wishlist •Performant, community-supported image server (or equivalent) • Super-slippy 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
- 57. Software Tiers froma 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
- 58.
- 59.
- 61. Looking Forward • “SearchWithin” API • 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
- 62. Acknowledgements • IIIF WorkingGroup • IIIF API Authors & Editorial Boards, especially… – Ben Albritton, Stanford University – Rob Sanderson, LANL & Stanford University – Stuart Snydman, Stanford University – Jon Stroop, Princeton University – Simeon Warner, Cornell University
Editor's Notes
- #4 There are bright spots: SeaDragon, Deep Zoom, ChronoZoom, Djatoka, Google Art Project, Gallica, National Library of Norway newspaper viewer
- #5 From an era of microscopes and close reading, move to telescopes, distant reading, aggregation. It’s a metaphor that works well both because of the capabilities to study materials not only from a distance, but also en masse – surverying whole solar systems, galaxies.
- #8 Stanford’s Book Reader (based on the Internet Archive book reader).
- #9 Stanford map viewer.
- #10 Cornell map viewer.
- #11 Cornell book reader (based on DLXS)
- #12 Cornell annotated art collection, hosted in Luna.
- #13 Oxford one-off manuscript viewer.
- #14 Oxford one off viewer.
- #15 Gallica from BnF
- #16 MediaInfo newspaper viewer from Nat’l Library of Norway.
- #17 British Library MSS viewer.
- #19 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.
- #20 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.
- #21 API’s to access image and description from a repository enable access to content from other applications and systems for viewing or analytics (transcription, annotation, e.g.) Some of this data could be reimported to the repository for reuse by others (e.g., transcriptions).
- #22 If multiple repositories supported the same API’s for access to images, metadata and annotations, one can envision the beginnings of a framework with shared application code across different sites, and interoperable image-based resources, enabling simultaneous access to multiple scholarly repositories through a single interface.
- #23 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.
- #24 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.
- #25 There are bright spots: SeaDragon, Deep Zoom, ChronoZoom, Djatoka, GoogleArt
- #26 DMS Tech is a Mellon Funded project
- #27 DMS Tech is a Mellon Funded project
- #29 Noted biblioclast Otto Ege owned a glossed bible, likely French 12th century
- #30 He broke up the manuscript in the 40s and 50s to include in one of his manuscript leaf portfolios, which were then sold throughout North America. In the intervening years, many leaves have appeared in collections, but many have also gone missing. We can identify 33 separate institutions owning pieces of this manuscript currently – but there are more institutions and individuals out there that have bits.
- #32 18 leaves, not previously recognized as belonging to the Ege book until Albritton began working on them in late 2013
- #37 We started on common software stack, but quickly shifted to an API