Digital Scholarly Editions as API Consuming Applications


Digital Scholarly Editions AND API Consuming Applications

Jeffrey C. Witt (Loyola University Maryland) | @jeffreycwitt

Graz, September 24th, 2016

Slide Deck:

Can we conceptualize machines as users? How can we include application programming interfaces (APIs) in the discussion on DSEs as interfaces? --- Plurality in representation is a core feature of DSE. How do interfaces realize this plurality? Do we need different interfaces for different target audiences (i.e. scholars, digital humanists, students, public)?
Data Display (Interface) Redundancy
How do we stop making redundant interfaces and instead promote the creation of interfaces that present a dataset in unique and revelaing ways?
Our Data
Our Data Model and API
- WorkGroup (Work) - The idea of Moby Dick - Expression - The idea of Melville's expression (as opposed to a screen play expression) - Manifestation - The idea of the 1959 edition of Moby Dick - Item - One physical copy of the 1959 edition in a particular library - Transcription - the idea of a digital transcription of the 1959 edition of Moby Dick - includes properties like hasXML, hasJson, hasPlaintext, hasHtml
- Manifestation Surface - the idea of page 1 in 1959 edition of Moby Dick - Item Surface - the physical page 1 in a particular copy of the 1959 edition of Moby Dick - IIIF Canvas - IIIF image annotation - images taken of the physical page 1 in a particular copy

Creating the data set with RDF extraction

Critical Corpus Database Visualization
Building common libraries for common tasks
LombardPress Interface Display
Mirador IIIF Image Interface
Lbp Print Interface
###Suggested Readings ####Introduction ####Modeling and Workflows []( []( []( ####On Information sharing and linked open data []( []( ####On Peer Review []( ####On LombardPress web []( []( [](