3. • 7 years (2012-2019)
• Observatory of written Heritage from
Middle Ages anf the Renaissance
(Arab, French, Greek, Hebrew, Latin)
• Total budget is 7.1 M€
• 8-people technology/metadata team
18 octobre 2013
LIBER Conference in Munich 26-28th June 2013
3
5. Objectives
• Contribute to a better understanding of
text dissemination, history of libraries
and knowledge dissemination in
Europe from 8th to 18th centuries
• Make our information about Middle
Ages and Renaissance materials
accessible to the general audience
• Ensure sustainability and
interoperability of new and already
existing materials
18 octobre 2013
COST Meeting – Budapest – 17-19 october 2013
5
7. The Portal
Provenances
Illuminations
Production
environment
BVMM
Gallica
BVH
Authority files
OpenSource
XML Editor
Catalogues
E-learning
tutorials
Bindings
Over 50 databases
Over 50 databases
and catalogues
and catalogues
RDF
18 octobre 2013
Publishing
toolkit
33major digital
major digital
libraries
libraries
SharedCanvas
TEI editions and tool
TEI editions and tool
for researchers
for researchers
IIIF syntax
COST Meeting – Budapest – 17-19 october 2013
7
9. SharedCanvas
• XML datamodel based on RDF and
OpenAnnotation
• Developped for 2 years in Stanford by the
Digital Manuscripts Technical Council.
• Specifications nearly finished. Actual phase
is to implement SharedCanvas manifests in
the partner institutions
• Documents and tests avaliable at
http://www.shared-canvas.org/
18 octobre 2013
COST Meeting – Budapest – 17-19 october 2013
9
17. Roadmap
• Study of all the partners’ ressource
• Building up an functionnal ontology of the
whole corpus compatible with CIDOC-CRM
and FRBRoo
• Improving the multi-layers prototype viewer
• Publishing an online “toolkit” for describing
medieval manuscripts, paleography…
• Disseminating information about what we do
: http://doc.biblissima-condorcet.fr
18 octobre 2013
LIBER Conference in Munich 26-28th June 2013
17
Producing an XML manifest for each document which is listing avaliable ressources (one or several digitals docs, EAD record, Mandragore descirptions, links to partner institutions)
Each data producer is issuing its own manifest, linked to the unique ID created by the library hosting the digital surrogate. Partners can choose (or not) to mention other manifests in their owns
The manifest is also indentifying precisely the image or part of image from which an annotation/editing has been made, so the final user can go back to the original image.
This datamodel was originally suggested by libraries which are regurlarly involved in new collaborative projects with very low standardization regarding the exchange of digital images.
IIIF API is basically a syntax that allows a distant image client (topped with a viewer) to send parameters to an image server and get the right images at the right resolution.
A compatible viewer has been developped by Stanford : Mirador. http://dmstech.github.io/mirador/demo/
Implemented at Biblissima: http://demos.biblissima-condorcet.fr/mirador/