Download - Digital Manuscript Interoperability Via Shared Canvas

Digital Manuscript (DMS) Interoperability Via Shared Canvas

A Case Study in Open Annotation OA Rollout * Stanford * April 9, 2013

Tom Cramer Chief Technology Strategist Stanford University Libraries

[email protected]

Borrowing liberally from… and->

Rob Sanderson Los Alamos National Labs

[email protected]

Ben Albritton DMS Program Manager

Stanford University Libraries [email protected]

Parker on the Web

Roman de la Rose

E-‐Codices

Walled Gardens: Custom, Func<onal, Isolated

Consider …an art historian who would like to compare and annotate illustra<ons from manuscripts at two different repositories, available via two different interfaces …a codicologist who would like to study the original state of the Codex Sinai<cus, fragments of which are now dispersed across four different sites …a linguist who would like to cite the first wriIen use of old English words in manuscripts, referring to both digital images and transcrip<ons …a paleographer who would like to analyze scribal hands using a custom-‐built, image analysis tool

Digital Medieval Manuscripts Today: A World of Silos & Duplica<on

•  Dis<nct applica<on func<onality •  Separate data stores •  Unique data models •  Different (or no) API’s

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

Dis<nct 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

API’s Enable Reuse

Dictionary of Old English

ImageDelivery

Parker Data

Images MD Annot.

RepositoryCanonical Data Store for Images, Description,and TechMD

ApplicationsUser interfaces present DMS datawith specialized tools and contexts

Des-cription

Parker App

ImageDelivery Search

Des-cription

TPENTranscription Tool

ImageDelivery

Trans-criptions

API's

Import & ExportDMS 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'sRESTful Web Services

API’s -‐> Framework -‐> Ecosystem

GallicaParker App


Des-cription

Annotation & Transcription Tools

ImageDelivery

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


Des-cription

Cross Repository Search & Delivery Environments


Specific Use Cases for Interoperability

1.  Drive a page turner with a sequence file (harder than you might think!)

2.  Enable 3rd party transcrip<ons: Relate transcrip<ons to pages, and to regions of interest (ROI) on pages (text blocks)

3.  Enable 3rd party annota<on: Relate annota<ons (scholarly commentary) to specific manuscript elements – pages, images, text, marginalia, etc.

Page Turner

DM – Image Annota<on Tool

T-‐PEN: Transcrip<on Tool

DMS Interop Par<cipants

with support from the Andrew J. Mellon Founda7on

Universi<es •  Stanford * •  Cambridge •  Oxford * •  Harvard •  Yale * •  Johns Hopkins * •  St Louis * •  Drew * •  Ghent •  Oregon

Libraries, Archives and Labs •  Bri<sh Library * •  BNF * •  e-‐codices * •  Los Alamos Na<onal Lab * * ac<vely building tools

Technical Approach to DMS Interop

Shared Canvas Data Model

IIIF Image Delivery

+

IIIF Image Delivery API

hIp://library.stanford.edu/iiif/image-‐api

Requirements for Data Model

1.  Reflect the physical and structural complexi<es of medieval manuscripts

–  Enable ordered delivery of (page) images and associated (transcrip<on) texts

2.  Relate mul<ple (and poten<ally overlapping) images, texts and other resources to a single page

3.  Reliably relate addi<onal annota<ons (scholarly commentary) to the manuscripts (whole item, range of pages, page-‐level, or specific region)

4.  Express via an easy transforma<on of exis<ng descrip<on & resources

CCC 26 f. iiiR

Naïve Approach: Annotate an Image

SharedCanvas: Collaborative Manuscript Facsimiles Open Annotation Collaboration, July 26-27, Chicago IL, USA

CCC 26 f. iiiR Fold A Open

Naïve Approach: Annotate which Image?


CCC 26 f. iiiR Fold A Open Fold A and B Open

Naïve Approach: Annotate which Images?


CCC 26 f. iiiR Fold A Open Fold A and B Open f. iiiV

Naïve Approach: …?!


Naïve Assumption: Everything is Square

Non-‐rectangular objects

•  Fashionable heart shaped

manuscripts

•  Fragments

•  Pages with foldouts

Facsimile of BNF Rothschild 2973 hDp://www.omifacsimiles.com/brochures/montchen.html


Naïve Assumption: Image Equals Page Parts of Pages:

•  Only illumina<ons digi<zed

•  Fragments of page

•  N.B. Informa<on about non-‐digi<zed parts may s<ll exist

Mul<ple Pages: •  Open spread •  Fragments from mul<ple

pages in single image Cod. Sang. 1394: 10.5076/e-‐codices-‐csg-‐1394


Naïve Assumption: Image Exists The page may not be digi<zed at

all

•  Not "interes<ng" enough

•  Digi<za<on destruc<ve

•  Page no longer exists

•  Page only hypothe<cal

•  Lack of money, <me, …

This page inten<onally, but unfortunately, lej blank

Countless manuscripts, all around the world!


Naïve Assumption: Only One Image Alignment of mul<ple images

of same object

•  Mul<-‐spectral imaging

•  Mul<ple resolu<ons

•  Mul<ple digi<za<ons

•  Image <ling

Bonus naïvete:

•  Page has one orienta<on

•  Page has one text

Archimedes Palimpsest Mul7-‐Spectral Images hDp://www.archimedespalimpsest.org/


Canvas Paradigm •  A Canvas is an empty space in which to build up a display •  Well-‐known concept, eg HTML, PDF


Canvas Paradigm •  A Canvas is an empty space in which to build up a display •  A SharedCanvas's top lej and boIom right corners correspond to the equivalent corners of a [rectangular bounding box around a] page


Canvas Paradigm: Implementation

Empty space is not hard to implement!


Painting the Canvas? Requirements:

•  Need to allow distributed associa<on of resources with the Canvas, or part of the Canvas •  Any type of resource, or part of a resource, should be able to be painted •  Need to allow users to comment about the Canvas, or part of it, or any of the resources

Solu<on:

•  Associate resources and commentary using Open Annota<ons!


Annotations to Paint Images Open Annota<on with single Target (Canvas) and Body (Image)


Annotations to Paint Images An oa:Choice with a default and 1 or more op<ons for the image.


Annotations to Paint Images: Implementation


Annotations to Paint Text Specific Resource with Selector to define an area of the Canvas

And also need Text Selectors to describe the appropriate part of the text...


Annotations to Paint Text


Annotations to Paint Text: Implementation


Image Segments


Image Segments: Implementation


Audio Segments


Audio Segments: Implementation


[Scholarly] Commentary


[Scholarly] Commentary: Implementation


Ordering: Missing Pages


Ordering: Rebinding


Non Medieval Use Cases


SharedCanvas Data Model


In Summary

•  DMS Interoperability requires common approaches to serving data and images

•  Shared Canvas provides an open, extensible data model based on OAI-‐ORE and Open Annota<on constructs – Using the original, physical object as the absolute frame of reference

•  New scholarly work produced in OA-‐compa<ble tools add to and enrich the scholarly record –  Crea<ng a virtuous circle – And truly transcending silos!

Using OA Adds to the Ecosystem

GallicaParker App


Des-cription

Annotation & Transcription Tools

ImageDelivery

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


Des-cription

Cross Repository Search & Delivery Environments


Digital Manuscript Interoperability hIp://lib.stanford.edu/dmm Shared Canvas hIp://shared-‐canvas.org IIIF (Int’l Image Interop Framework) hIp://lib.stanford.edu/iiif

Download - Digital Manuscript Interoperability Via Shared Canvas

Top Related