1 / 25

Digital Manuscript Interoperability

Explore the SharedCanvas and IIIF framework in digital manuscript technology, aiming for content sharing and comparative viewing across institutions. Learn more about the implementation, development process, and future steps in this innovative project.

mikko
Télécharger la présentation

Digital Manuscript Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Digital Manuscript Interoperability SharedCanvas and IIIF in Practice Benjamin Albritton Digital Manuscript Product Manager blalbrit@stanford.edu @bla222

  2. Summary: 2010-2013 • Funding from Andrew W. Mellon Foundation • Initial meeting of scholars and curators – Paris, 2010 • Digital Manuscript Technical Working Group – 2010-pres. • Data Model: SharedCanvas • Data Sharing Framework: IIIF (International Image Interoperabiity Framework)

  3. DMSTech and IIIF • Bibliothèquenationale de France • British Library • Oxford University • Stanford University • Johns Hopkins University • University of Fribourg (e-codices) • Saint Louis University (T-PEN) • Drew University (DM) • TextGrid • Los Alamos National Laboratory • Yale University • Harvard University • Cambridge University • ARTstor • Cornell University • Princeton University • Walters Art Museum • National Library of Norway • The National Archives (UK) • … and more

  4. Interoperability – One Definition • Primary Goal: • Image and metadata sharing across collections and institutions • “Killer app”: • a single viewer that reads content from multiple repositories

  5. Imagine an image viewer…

  6. With content from any repository…

  7. That lets scholars compare…

  8. And investigate in detail…

  9. http://iiif.io/mirador/

  10. Synopsis • Two primary motivators • Comparative viewing of images • Viewing of annotations • Part of the current Stanford-led Mellon grant for Digital Manuscript Interoperability • Goals: • Support for use-cases at Yale, University of Toronto and Johns Hopkins University • Comparative viewing for manuscript images in a book, across books, across collections, across repositories • Support annotation and transcription viewing • Support light-weight annotation creation

  11. How do we do it? • Represent the physical object in a common data model (SharedCanvas) • Deliver the data via common API (IIIF)

  12. Data Model: SharedCanvas http://www.shared-canvas.org

  13. How do we do it? • Represent the physical object in a common data model (SharedCanvas) • Deliver the data via common API (IIIF) http://iiif.io

  14. IIIF API Development and Current Status • Work driven by real-world use-cases • Scholarly projects and interviews • Personae developed • http://www.stanford.edu/group/dlss/dms-viewer/personas/ • Development work referred back to these use-cases on an ongoing basis • Confirmed that APIs actually support real needs • Status • Image API at 1.1 release • Metadata API at 1.0 release

  15. Deliver via API: IIIF http://library.stanford.edu/iiif/image-api

  16. Implementation • Meeting at Harvard in October 2013 • Eight institutions • Stanford • Yale • Harvard • University of Kentucky (vHMML) • Oxford University • University of Fribourg (e-codices) • Los Alamos National Laboratory • Biblissima (France) • Goal: 6-8 institutions with: • Mirador installed • Showing content from all other institutions • Prototype ability to add more content • Development contributions?

  17. Result: 9 institutions sharing content

  18. Mirador Development Process • Two-year grant cycle: • Design • Creation of personas: • http://www.stanford.edu/group/dlss/dms-viewer/personas/ • Creation of mock-ups and wire-frames • http://www.stanford.edu/group/dlss/dms-viewer/mocks/#1 • Development • Phased development of different components • Comparative image viewing – COMPLETE • Annotation and transcription viewing – IN PROCESS • Annotation creation - FUTURE • 1.0 public release planned for December 2013 • 2.0 public release planned for December 2014 • Post-2014: ongoing development of a community of adopters and committers for this open source project

  19. Next Steps: Image Choice

  20. Next Steps: Image Choice

  21. Next Steps: Annotation viewing

  22. Next Steps: Transcription viewing

  23. Next Steps: Multiple text representations

  24. Next Steps: Workspace Sharing

  25. The Beinecke as Institutional Leader • Technical implementation is relatively easy • Institutional buy-in to share content, and lots of it, is more of a challenge • The Beinecke could play a leading role as one of the major North American manuscript repositories • Benefits: • Increased access to scholarly and public use of the content • Transcription and annotation of Beinecke content • Crowd-supported cataloging • Comparison of Beinecke books with related or comparable books in other repositories in a single interface

More Related