Image Viewing/Browsing, Page Turner:
• Multiple images brought together
• "viewer requirements"
○ Side-by-side images, or multiple images "non-contiguous"
○ Select a bounding box
○ Reading "directionality" (in multi-image and thumbnail) (W3C rec.)
○ Resize viewport
○ Full-screen support (fsi, zoomify)
○ Thumbnails of other set (additional menu display functionality)
Image Viewing/Browsing, Page Turner:
We have all three groups of Fedora users here - active users, prospective user and abandon-ers
- Uses Fedora API and object model, but nothing else from Fedora
- Uses Fedora in a more expendable way
- Have a custom REST layer on top of Fedora
- Uses Solr to handle majority of the queries
- Is moving towards Fedora
- Currently using Fedora for building digital repository
- Uses Fedora content and object models
- Parker Library on the web content is not in Fedora
Various systems for uniquely identifying resources: ARK, DOI, TinyURL, UUID
Can provide more than one reference, using more than one system, for the same resource. Can use something internally, e.g. UUID internally, but also provide others externally, like TinyURL, and DOI.
Human readable can be helpful. For example to verify that a link is working.
Ben provides a summary of experience collecting metadata from 6
repositories for inclusion into a common index.
* only received XML, but collected:
** Dublin Core
What are the common elements across the different corpora?
For EAD, the challenge of navigating the EAD up and down the hierarchy
to produce the index at the right level of analysis.
The BnF concatenates all levels to crosswalk to Dublin Core to expose
The challenge of transforming structured format to flat format.
Our discussion revolved largely around a standard way of capturing sequence
images (ordinal numbering) versus naming/titling the images (cardinal:
roman, arabic, 1r, 1v, etc.)
Here is our list of topics that we wanted to discuss re: images; * marks the
ones we actually talked about
1. FORMAT: Tiff vs. JPEG2000
2. Filenaming conventions *
3. sequence and organization / foliation *
4. technical metadata *
5. technology for streaming and delivering
6. page turning *
7. capture standards; organization *
Main thought: Smaller chunks of interlinked services (eg James, Neil, Tom)
Transcription: REST calls (JSON) to save. API is the rest call to do
one function, can be implemented in any way at the back end.
Broadcast list of MS descriptions
Expose full/brief metadata
Image streaming (dimensions, format etc)
Citation (down to page region)
Access Control (Auth'n and Interoperability)
Neil: Objects in system for registry
Raphael: What is a common API? (to be discussed)
Mediaeval only? Gives focus on use cases
Physical, digitally described, cultural?
Manuscript catalogs are pretty unique
Need to keep touch with broader community for tool re-use possibilites
Eastern manuscripts blur written/print distinction '
"Mediaeval" only well defined for Western materials
RTL, Top-to-bottom visualisations (page turners etc.)
Folio-recto-verso vs page numbering
Stay with Western MMS's for discussion in point, look to expand in the
future possibly via SIGS
Items to share/discuss:
- matrix or registry of tools
- page turner
- extract folio structure (TPEN)
- search term highlighting
- list of preferred technologies
- (internal) API list
- merits & demerits of using a Fedora repository
- standards: TEI, EAD, etc
- PID/PURL issues
- broader applicability for other content types in addition to digi medieval manuscripts
- what do we need to do to our image resources (what are reqs) for image streaming?
- metadata streaming flavors? (what data do consumers/partners want?)
- OAC reference implementation
Rob's architectural list of possible styles:
Authentication: Shibboleth vs OpenID/OAuth
Web API style: Grid/SOA[P] vs REST/Linked Data
User Interface: Flash vs HTML5
Client Type: Rich Client vs Web
Server Type: Repo vs Simple