Interoperability through Library APIs Library Technology Services Open House 7/30/15

Metadata Digital Content Inventory Data Sets API APIs Interesting Web Apps The Opportunity 18M titles, authors, subjects, locations, etc 45M Images, books, audio, video holdings availability scientific data geospatial Faculty papers etc. Semantic Web

Metadata

Digital Content

How to re-use this stuff? APIs

Library API landscape Library Cloud - Unified Metadata API Combines silos of descriptive metadata into a single Web Service API Descriptive info like title, creator, subject – what you see in HOLLIS PRESTO – bibliographic item data API HOLLIS search Bibliographic data from HOLLIS PUBMED, DOI, VIA data Item availability (checked out?) Digital content delivery API International Image Interoperability Framework (IIIF) DRS delivery services (paged objects, audio, documents) In the future: Semantic Web APIs (grant funded development) Linked Open Data RDF Triples (no more “records”), SPARQL API

Guiding principles Support innovation, interoperability, and reuse through: Standard HTTP web service API protocols - REST, SPARQL, JSON, XML Community supported metadata schemas – e.g. MODS, MARC, Dublin Core, RDF Community supported digital content APIs - IIIF Open access

Available today: Library Cloud ● A queryable metadata hub (solr indexed) of Harvard library holdings ● 13M HOLLIS records, 4M visual image records, 2M archival and special collections items ● A pipeline for updating and enriching records ● Deployed in Amazon Web Services ● Open source software

Library Cloud 5/5/15 books images archives More... Ingest DPLA, OCLC Innovation apps LD4L BIBFRAME NormalizeEnhance Distribute API OAI-PMH Metadata sources AWS Queue pipeline APIConsumers

Library Cloud API name=Schulz Faceting ets=name,resourceType Search on a facet eType=“still image” Api documentation - yStaffDoc/LibraryCloud+Item+API yStaffDoc/LibraryCloud+Item+API

IIIF International Image Interoperability Framework Opens Harvard library digital content for reuse over the Web and allows Harvard to reuse external content A content delivery Web API (the digital book or digital image) Not a discovery API (title, author, subject) Sample Use Cases Teaching: Displaying a “Virtual manuscript” where Harvard holds some pages and Yale holds other pages Research: Comparison of a Harvard and British Library copy of the same work Library or Museum: Creating on-line collections that include material from multiple institutions

IIIF Harvard University Bibliothèque Nationale de France British Library Oxford University Stanford University Johns Hopkins University University of Fribourg Saint Louis University Drew University TextGrid Los Alamos National Laboratory Yale University Cambridge University ARTstor Cornell University Princeton University Walters Art Museum National Library of Norway The National Archives (UK) DPLA Europeana … and more – see Community driven ( Defined APIs for digital object linking and reuse Plug & Play software (such as Mirador)

Mirador

IIIF APIs at the Library Image API Presentation API Uses the Shared Canvas data model and W3C Open Annotation Mirador uses both APIs

PRESTO Availability for Moby Dick HOLLIS+ Search for Moby Dick Dick”

Metadata (Titles, Authors, Subjects, etc) Digital Images Inventory Holdings, availability, etc Data Sets Social science, astronomy, GIS Library Cloud API IIIF APIPRESTO API Open APIs Interesting Web App OPEN APIS - Third parties can reuse, embed, and repurpose library data… HOLLIS VIA OASIS … Harvard DRS Harvard Canvas? HarvardX? Aleph HOLLIS+ … Dataverse HGL DASH DatasourcesDatasources 5/5/15

Metadata (Titles, Authors, Subjects, etc) Digital Images Related Authorities Names, Places Data Sets Social science, astronomy, GIS IIIF Presentation API IIIF Image APILinked Open Data Open APIs … and Harvard can reuse data from other institutions Stanford Yale Oxford (etc) British Library etc. Stanford Yale Oxford (etc) British Library etc. DBpedia DPLA Library of Congress Europeana … Dataverse Open Geoportal DPN DatasourcesDatasources e.g. Mirador 5/5/15

Examples ● Mirador ● Digital collection builder ● DRS metadata migration tool — to efficiently retrieve descriptive metadata for migrated digital objects ● Library hackathon apps o On an Amazon page, a button tells you if the book is in Harvard Library o Visualization of library content via Google Fusion o List Harvard of relevant items for a feminist web site o Search the Library from Android phone o Which library is best for a particular subject? 

The Future

Tim Berners-Lee’s 4 Rules for the Semantic Web 1.Use URIs as names for things 2.Use HTTP URIs so that people can look up those names. 3.When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL) 4.Include links to other URIs, so that they can discover more things.

Semantic Web API (linked data grant project) Uses RDF, the language of the web thisBook “has title” “Moby Dick” – “thisBook” is a URI: 671/catalog 671/catalog – “has title” is a URI: e e – “Moby Dick” is a URI: m m One uniform API for querying and inferencing (SPARQL)

Thank you!

Reference - API Documentation APIDocumentation Library Cloudhttps://wiki.harvard.edu/confluence/display/LibraryStaffDoc/Libra ry+Cloud PRESTOhttp://hul.harvard.edu/ois/systems/webservices/#lookup Dataversehttp://thedata.harvard.edu/guides/dataverse-api-main.html Course reserveshttps://github.com/harvard- library/ecru/blob/master/ecru_url_patterns.md DRS Delivery Services for Image Delivery Service, File Delivery Service, Streaming Delivery Service, Full Text Search Service DASHhttp://openmetadata.lib.harvard.edu/content/digital-access- scholarship-harvard-dash-dataset

Appendix B - Bulk download documentation DatasetDocumentation Bibliographic data sethttp://openmetadata.lib.harvard.edu/bibdata Virtual Collection OAI- PMH data provider harvesting.html Harvard Geospatial Library OAI data provider main.html#data-sharing-api