The Digital.Bodleian project has converted approximately 100,000 images and metadata to a standard format and loaded them into a test system. Additional collections totaling 40-50TB are in progress. Unique IDs and persistent URLs are being assigned as the transformed data and images are migrated to the permanent digital asset management system. Issues remain regarding bulk ingest into the system and making the data available via the OAI-PMH protocol. The default open license is CC BY-NC-SA 3.0 and rights are being checked during ingest. Individual images and metadata are accessible and reusable via their persistent URLs.

1. Digital.Bodleian
JISC Final Programme Meeting
September 28th, 2012

3. Current state of play
• User interface running and performance and user testing
ongoing.
http://digital-dev.bodleian.ox.ac.uk/inquire_1.12/Discover/Search/
• Approximately 100,000 images and metadata
converted to jpeg2000 and ‘DC’ and in use as live test
data.
• Most additional collections including our master image
archive containing all of our legacy digitised content in
progress. [40-50TB of images and metadata so
slow/involved process]
• Migration of the transformed metadata and images to
our ‘DAMS’, with creation of UUIDs and PURLs about to
begin.

4. Outstanding issues
• Bulk ingest mechanism of transformed data and
images into DAMS not finalised.
• OAI-PMH target not operational.
• User interface currently pulling data from a working
store rather than the final master DAMS store.

5. Open Licensing
• Digital.Bodleian using Creative Commons
Attribution-NonCommercial-ShareAlike 3.0 license
as the default.
• http://creativecommons.org/licenses/by-nc-sa/3.0/
• The current user interface doesn’t offer fine-grained
user access rights management.
• No content with stricter license conditions is being
offered in the first wave.
• Project assistant is checking rights during the ingest
process.

6. Persistent identifiers
• Images and metadata are added to our DAMS
(Digital Asset Management System) as data
packages.
• Each data package is an aggregation of a
manifest, jpeg2000 image, the original
metadata, and a standardised (DC-based)
metadata file.
• Each data package is assigned a UUID at ingest.
• Oxford has a PURL (Persistent Uniform Resource
Locator) resolver:
http://purl.ox.ac.uk/docs/index.html
• The UUID for each data package is used to create
a PURL.

7. Persistent Identifiers
• Bodleian google books example:
http://purl.ox.ac.uk/uuid/79b9e193afbd4a7ba03700596afe9832
• Partial redirection allows persistent access to
elements within a data package, or to particular file
types.
http://purl.ox.ac.uk/uuid/XXXXXX/image.jp2
http://purl.ox.ac.uk/uuid/XXXXXX/dc.xml

8. Reuse of data
• The iNQUIRE interface used by Digital.Bodleian sits on top
of:
o a Solr index, which indexes the DC-based metadata for each data package
o A Djatoka server, which serves up jpeg tiles from the jpeg2000 master files
within each data package
o The UI incorporates a DeepZoom wrapper around the Djatoka tiles.
• All of these can be reused by non-iNQUIRE services.
• All of the elements in each data package can be
accessed by PURLs, and can be harvested via OAI-
PMH, accessed directly, or reused in other services.
• The DAMS provides a REST interface to the data.
• The DeepZoom UI can be embedded in other
sites, including sites., e.g.:
http://digital-
dev.bodleian.ox.ac.uk/inquire_1.12/Discover/DeepZoom?i
d=info:plasci012-aci-0001-0&h=600&w=800