Integrating IIIF and Mirador at Harvard
•Download as PPTX, PDF•
1 like•304 views
VRA 2017 Session: Cross Campus Collaboration Presenter: Jeff Steward
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Integrating IIIF and Mirador at Harvard
Similar to Integrating IIIF and Mirador at Harvard (20)
More from Visual Resources Association
More from Visual Resources Association (20)
Recently uploaded
Recently uploaded (20)
Integrating IIIF and Mirador at Harvard
- 1. Integrating IIIF and Mirador at Harvard Jeff Steward Director of Digital Infrastructure and Emerging Technology Harvard Art Museums Cross-campus Collaboration Case Studies March 30, 2017 VRA 34th Annual Conference
- 2. What is ? What is Mirador?
- 4. Why is Harvard interested in them?
- 5. Use Cases Teaching Research Libraries, Museums, Galleries, Archives
- 6. Use Cases Harvard Library HarvardX Harvard course platform (Canvas) Harvard Art Museums
- 7. Brief Chronology 2010 – Harvard library technologists start tracking IIIF 2012 – Focus group of faculty, academic technology, library staff and library technology assess options for a new page turner 2012 – Harvard commits $40M to edX and funds a IIIF developer 2013 – “The Book: Histories Across Time and Space” begins development 2014 – Harvard Library IIIF services for 120,000 books and manuscripts (5M page images) plus 10M still images 2015 – “The Book” launches, art museums IIIF manifest service for 250,000 art objects launches 2016 – Three Mirador-based apps launch: Harvard Library Viewer, Image Media Management LTI-Canvas app, art museums digital tour builder 2016 – University wide IIIF/Mirador working group forms 2017 – And so it goes…
- 8. Some Results
- 12. Harvard Collaborators Harvard Faculty Harvard Academic Technology Services HarvardX Harvard Library Harvard Library IT Harvard Art Museums
- 13. Harvard Collaborators+ Harvard Faculty Harvard Academic Technology Services HarvardX Harvard Library Harvard Library IT Harvard Art Museums Stanford University Cornell University Princeton University The Getty Trust Yale Center for British Art
- 15. Resources IIIF – http://iiif.io/ Intro to IIIF – https://iiif.github.io/training/intro-to-iiif/ IIIF at Harvard – http://iiif.harvard.edu/ Project Mirador – http://projectmirador.org/ The Book – https://www.edx.org/book-histories-across-time-space-0 Library Page Viewer – https://iiif.lib.harvard.edu/manifests/view/drs:5981093$7b NGA Demo – https://www.youtube.com/watch?v=1iADkg_nOiU
- 16. Thank you
Editor's Notes
- Hi. I’m Jeff Steward from Harvard Art Museums. I’m here presenting on behalf of a whole lot of colleagues from Harvard. I’m going to talk about a multi-year (ongoing) collaboration on integrating IIIF and Mirador at the university. You may have seen a variation of this presentation given by Randy Stern, Director, Systems Development in the Harvard Library at other conferences. This presentation is my take from the museum’s perspective.
- There is lots to say about IIIF and Mirador but for this presentation I’m going to give a very quick overview. What is IIIF? IIIF is the International Image Interoperability Framework. As it’s name states it’s a framework. To quote directly from the IIIF website, IIIF is for “Enabling Richer Access to the World's Images”. The framework contains specifications for four different APIs. The collaboration at Harvard is primarily focused on two APIs: Image and Presentation. The Image API describes how you serves images and the Presentation API describes how you want those images presented to the viewer.
- What is Mirador? Mirador is a multi-up viewer for viewing images served up by services that implement IIIF. This video demonstrates some of IIIF and Mirador integration on the Harvard Art Museums website. What you see is example of how you can drag and drop images from IIIF compatible image repositories in to Mirador for comparing images. In this example you see images coming from the Harvard Art Museums and the Yale Center for British Art websites/image servers. This illustrates the third I in IIIF, interoperability, in all its glory. https://www.youtube.com/watch?v=1iEDkdHJJ3c
- Because from a technologist point of view it’s a no brainer. Doubly so once you see them in action. With IIIF in place, you have very robust building blocks with which interoperability can become a reality. IIIF presented an opportunity to open Harvard library (and museum) digital content for reuse over the Web. And it enables reuse of external content by the Harvard community. Plus IIIF is a set of open APIs and has a very active, skilled, and robust community. See http://iiif.io/community/. Mirador presented an opportunity to address the need to improve digital content sharing, improve the ancient book viewer the library was running, and HarvardX needed digital content and a way to present it to students.
- Broadly a few example use cases emerged. 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 GLAMs: Creating on-line collections that include material from multiple institutions
- More specifically there are a number of use cases that emerged that map directly to departments/units at the university. Harvard Library Needs and updated page viewer for the Digital Repository Service (DRS) with smooth zoom/pan, 2 page view, etc. HarvardX Needs an interface to embed an annotated view of Harvard Library images in HarvardX courses delivered on the edX platform Harvard course platform (Canvas) Needs to display and compare library and faculty-uploaded images in on-campus courses web sites Harvard Art Museums Needs to deep zoom capability on collections search interface and to create online publications and digital tours with museum image content from the DRS mixed with content from other repositories At this point in time all of these things have been implemented.
- Here is a really general timeline of the major events in the collaboration. None of this happened over night. There wasn’t some big decision to collaborate on this stuff. As you can see it’s been a very long process that fluctuates between organic and planned. The library staff were keen on the technology long before there was an opportunity to implement it. Faculty and other staff were brought in 2012 and it’s not until Harvard’s financial commitment to edX that things started to happen. edX/HarvardX needed arts and humanities courses to complement the hi tech courses form MIT. Enter “The Book” which required a better way to display manuscripts. As HarvardX developed more course it became clear they would need images from the art museums. That is when we were brought in to the fold.
- Here is an integration of Mirador in the Harvard Art Museums digital tool builder. This digital tool was assembled for a drawing exhibition where the curator wanted to make a few sketchbooks available in their entirety.
- In June 2016, Harvard formed the IIIF/Mirador working group. “The IIIF/Mirador Working Group guides and coordinates IIIF/Mirador-related efforts across the University. Pulling together the interests of the Harvard Library, Academic Computing, HarvardX, the Harvard University Art Museums and users, the working group serves in an advisory capacity, steering the development and use of Mirador in order to harness its capabilities for both teaching and research at Harvard.” The group meets once a month and reports to vice president and university chief information officer, vice president for the Harvard Library, vice provost for advances in learning, and director of the Harvard Art Museums. Needless to say the group also reports and consults with other faculty, department heads all along the way. The group discusses projects, use cases, opportunities to expand the collaboration (including expanding beyond the libraries and humanities in to the sciences), future direction for the infrastructure to support IIIF and Mirador, grant/funding opportunities, etc.
- What does the scale of the collaboration look like?
- At least seven different groups in Harvard. Over 40 individuals with roles ranging from developers to librarians to directors to faculty and on and on.
- Keep in mind this started back in 2010. And within the last year we are seeing the effects of putting this technology in place. Folks from the Nomisma project have harvested the museums collections data (specifically ancient coins), have built a concordance to their dataset, and are starting to test using Harvard’s IIIF servers to display the museums images on the nomisa.org website.
- Here are a few final observation. A good collaboration has to be nurtured Everyone involved has to get something/gain something from it Everyone needs to be open to new perspectives Don’t be afraid to go fishing Good collaborations are often the result of being opportunistic There is no secret sauce. Collaborations work because of a healthy balance of hard planning and operating on intuition Everyone involved is on a loose leash. Meaning everyone can stray a bit but is still beholden to the group. Everyone needs to phone home every so often. Report back. Be honest and open.