Open Online Newspaper Initiative (Open ONI) and IIIF Sheila Rabun IIIF Community and Communications Officer International Image Interoperability Framework (IIIF) Consortium srabun@iiif.io Twitter: #IIIF @iiif_io I’m Sheila Rabun, IIIF Community and Communications Officer. My background is in digital libraries and digital newspapers specifically - Thank you all for being here - How many people have heard of IIIF? - How many have digital newspaper content? - Open ONI is a software development project and product for digital newspaper delivery that is incorporating IIIF APIs

Overview IIIF at a glance Benefits of IIIF for Newspapers (and all digital images) IIIF and the Open Online Newspaper Initiative (Open ONI)

IIIF At a Glance: A Community, That develops Shared APIs, Implements them in Software, And exposes interoperable Content Learn more at iiif.io Focus = common standards for web-based image (and media) delivery, started in 2011 IIIF at a glance (I only have 9 minutes!) Community Shared APIs Software Content Credit to: IIIF Editors (Rob Sanderson, Jon Stroop, Mike Appleby, Tom Crane, and Simeon Warner) and Tom Cramer

IIIF Community - iiif.io/community IIIF Consortium Currently 38 state and national libraries, universities, museums, tech firms Provides sustainability and steering for the initiative Wider community 80+ cultural heritage institutions, software companies, and projects using IIIF standards iiif-discuss email list = 550+ members IIIF Slack = 190 members Community Groups Newspapers, Manuscripts, Museums, Software Devs, A/V Growing community: Community The IIIF Consortium is a group of (currently 38) libraries and museums who have signed an MOU to provide sustainability and steering for the IIIF community It has been challenging to keep track of the overall size of the wider IIIF community of institutions and tech firms who have been adopting IIIF standards.. Community Groups: Newspapers, Manuscripts, Museums, Software Developers, and A/V Technical Specification group

What does IIIF Provide? Image API Presentation API Search API Transfer image pixels Image manipulation Presentation API Presentation of an object (pixels + navigation and metadata) Easily share and re-use, mix and match content Annotate content Search API Search annotations Authentication API Provide interoperability for access-restricted content What does IIIF provide? There are 4 APIs that provide the ability to: - Transfer image pixels - Image manipulation - Presentation of an object (pixels + navigation and metadata) - Easily share and re-use, mix and match content - Annotate content - Search annotations - Provide interoperability for access-restricted content As long as you are using a compatible image server and image viewer and you are following the standards for IIIF json files, you can mix and match software and give users access to the rich functionality that IIIF provides…

IIIF APIs – iiif.io/technical-details Image API 2.1 Facilitates systematic re-use of image pixels HTTP(S) Requests – URI specifies region, size, rotation, quality, and format of image Get pixels via RESTful web service - The Image API allows for transfer of image pixels through HTTP requests, so for example, you could manipulate an image from a different repository via the URL / img-1234 / 125,15,120,140 / pct: 75 / ! 345 / gray.jpg (identifier) (region) (size) (mirror) (rotation) (quality.format) Credit: IIIF Editors (see slide 2)

IIIF APIs – iiif.io/technical-details Presentation API 2.1 Provides descriptive info, annotation layer, structure/navigation for complex objects Utilizes JSON.LD and Shared Canvas model Search API 1.0 Allows for searching within annotations Authentication API 0.9 Provides user auth for access- controlled images A/V API – coming soon… Presentation API requires just enough metadata to drive a remote viewing experience, so descriptive metadata, object structure and navigation - Presentation API also supports annotations. The Search API allows for searching within annotations, and the Authentication API, still under community review, allows for user authentication for access-restricted images. The community is currently working on a specification for A/V materials, so stay tuned for that…

IIIF-Compatible Software Implementations Examples: Hydra-in-a-box repository product CONTENTdm 6.0 release Mirador viewer Universal Viewer Internet Archive Book Reader Diva.js Plugin for Omeka Etc. Many examples of IIIF specs implemented in software - The IIIF APIs have been implemented to various degrees in a number of new and existing applications, such as Hydra-in-a-box repository product CONTENTdm 6.0 release Mirador viewer Universal Viewer Internet Archive Book Reader Diva.js Plugin for Omeka And the list goes on… Mirador Viewer: projectmirador.org

Benefits of IIIF for Newspapers Shared standards for presenting digital newspaper data – OCR, annotations Enriching the newspaper- based research experience Ability to share, mix, and match newspaper content from across repositories Image shows a newspaper page with an article highlighted entitled “A crusade on corsets” – with keyword hit-highlighting and corresponding OCR text. Images and content from this slide forward give credit to Karen Estlund, “IIIF and Open ONI” at https://docs.google.com/presentation/d/1zlnsURvzivW3AFyaIROC68XKU-2DAy3uIP5VylH-cws/edit?usp=sharing Image from the National Library of Wales: http://newspapers.library.wales/view/4342439/4342445/53/

Comparing Newspapers in Mirador Functionality – deep zoom, compare, cite and share, annotate, search within annotations, embed, image manipulation – crop and rotate, etc. Image on the slide shows two different digital newspaper images side by side: From the Salt Lake Tribune (1911-09-07) showing article: “ Confidential Talk on Corsets - Ladies, the most important garment worn is the corset. Stop and consider what it means. Think of it ladies, it’s the foundation of health, comfort, and appearance and the beauty of it is all three combined can be readily given when you put yourself in the hands of an expert corsetier. When properly corseted one can always be well gowned. Your dressmaker or tailor cannot give you the graceful and stylish lines unless properly corseted. Your corset is what moulds your figure and shows your gown off to best advantage” From “Western Mail” (1874-07-08): “A crusade on Corsets – Somewhat more than two months ago, says Brooklyn Argus, a number of Brooklyn ladies many of them prominent in social life, organized a war against corsets, garters, and high heeled shoes, false hair, and the numerous other…which are generally supposed to add beauty and injure health. The crusade on rum having proved a success, these ladies determined to pluck the mote from the feminine eye before attempting to remove the beam from the optics of their brithers...” Image credit: Karen Estlund

Software: Open ONI - https://github.com/open-oni But my focus today is on Open ONI, which is one of the many software products working to integrate IIIF specs Open ONI was started in July 2015, spearheaded by Karen Estlund (at University of Oregon, now at Penn State), with grant funding from NEH as part of the National Digital Newspaper Program (NDNP) Started in July 2015 with grant funding from NEH as part of the National Digital Newspaper Program – developers meeting at the University of Oregon, led by Karen Estlund

LC Newspaper Viewer (chronam) – Open Source, Open API - http://chroniclingamerica.loc.gov/ Based on the chronam software for Chronicling America (Library of Congress) – uses NDNP technical specifications and batch structure The Open ONI software is based on the Library of Congress’ Newspaper Viewer, otherwise known as chronam 11,320,187+ pages

Adapting chronam for State and Local Use A number of libraries involved in NDNP had been using forks of the chronam software for their local repositories, so Open ONI is a joining of forces among these institutions in order to create a stable, easy to deploy and maintain software package geared toward local and state institutions (chronam was originally developed for LC for use at the National level) Target = out of the box solution for digital newspapers – easier to implement and maintain (go further together) Image: Dev instance of Open ONI, Karen Estlund – following slides: credit to Karen Estlund

IIIF Mapping for Newspapers Newspapers metadata (METS XML) IIIF data (JSON.LD) Title Collection Issue Manifest Edition Article Range Page Canvas Image METS ALTO (OCR data) Annotations The Open ONI team and IIIF Newspapers group determined a mapping for newspaper metadata to IIIF json – a shim is available to automatically create the json files needed - Ed Summers at the Maryland Institute of Technology in the Humanities developed a script that will convert NDNP newspaper metadata to IIIF json! ndnp_iiif is a Python program for turning National Digital Newspaper Program data into static IIIF JSON that is ready for mounting on the Web. Shim: https://github.com/umd-mith/ndnp_iiif

Open ONI and IIIF - Manifests Example manifest: http://dams.llgc.org.uk/iiif/newspaper/issue/4342439/manifest.json Link to OCR in IIIF Manifest: "seeAlso": [    {      "profile": "https://www.loc.gov/standards/alto/",      "@id": "http://oni.mith.us/lccn/sn83045396/1911-09-17/ed-1/seq- 1/ocr.xml",      "format": "text/xml"    }  ], Penn State, University of Nebraska, and the University of Oregon are leading the effort Karen Estlund is one of the project leaders and is also a co-chair of the IIIF Newspapers community group along with Glen Robson at the National Library of Wales. Open ONI has been developed with guidance from the IIIF community, with best practices on mapping and manifests, and linking METS ALTO files for OCR data Penn State is getting ready to launch, then Univ of Nebraska, and Univ of Oregon

Open ONI and IIIF – Servers and Viewers RAIS image server dockerized - https://github.com/uoregon- libraries/rais-image-server Loris IIPImage Server IIIF-Compatible Image Viewers OpenSeadragon IA Bookreader Universal Viewer Mirador These are just some examples of compatible servers and viewers that could be used. There are a number of IIIF-compatible image servers and image viewers that can be used; Open ONI uses the RAIS image server, developed at the University of Oregon, and has started with a basic OpenSeadragon viewer, which is native to the chronam software Image credit: Karen Estlund

Thank You: Karen Estlund, Penn State University NEH Ed Summers, Maryland Institute for Technology in the Humanities Northern New York Library Network Stanford University Glen Robson, National Library of Wales Penn State University North Carolina Digital Heritage Center Library of Congress University of Oregon Paul Smith's College University of Nebraska - Lincoln University of South Carolina MITH, University of Maryland LYRASIS Special thank you to: Leaders: Karen Estlund, Penn State University Ed Summers, Maryland Institute for Technology in the Humanities Glen Robson, National Library of Wales Software developers and resources: Library of Congress University of Oregon University of Nebraska - Lincoln MITH, University of Maryland Northern New York Library Network Stanford University Penn State University North Carolina Digital Heritage Center Paul Smith's College University of South Carolina LYRASIS