The Wellcome Trust is examining the possibility of a cloud platform for the storage and delivery of digitised artefacts. This platform is intended for the Trust's own use as well as others. A version of this presentation with embedded notes and video can be viewed on Google docs: http://bit.ly/1GRKqN4 or PowerPoint online: http://bit.ly/1CwGsrE
2. Agenda
13.00 – 13.30 Lunch
13.30 – 14.45
Session 1: Service Overview
How will it work? What will the service be able to
provide your institution?
Why is this service needed? What are the benefits
over the current options?
What are the costs likely to be?
14.45 – 15.00 Tea/coffee
15.00 – 16.15 Session 2: Platform Overview
How IIIF (http://iiif.io/) gives us an image delivery
standard to conform to
Commodity services for image serving, OCR and
searching
Integration scenarios
Discussion around specific use case scenarios
16.15-16.30 Wrap Up & Next steps
3. The Wellcome story
• Imaging significant volumes of content
• Developing software to render this content and
integrate it with our existing systems
•DAM, Library Catalogues, Discovery platform
4. Imaging – over 2.5m pages imaged last year
0
500000
1000000
1500000
2000000
2500000
3000000
2011 2012 2103 2014
Ingests to SDB
Ingests to SDB
…volume of digital content continues to grow
5. Need infrastructure to support this scale
• There are standards-based
commodity services that could
be developed and presented as
cloud platform services
• Wellcome will need this
infrastructure….but with input
from community we can ensure
that others can use these
services too
• Suggestion – we establish a
new corporate entity to deliver
these shared services to the
cultural heritage sector
6. Vision
• To provide a set of highly
available and affordable
cloud-based, managed
services to support
organisations who wish to
make their digitised content
available in rich and
engaging ways, but without
incurring the cost of
developing and maintaining
their own systems
infrastructure
7. Motivation
• Selfish…
We will need a DLCS for our own purposes – to
support the scale of activity and the development
of new services (annotations, Linked Data etc.)
• Open
Building on our principles of openness we want
others to be able make use of such services
and will release all code under open source
licence
• Access
The use of common standards (IIIF, ALTO, Open
Annotation) will facilitate research across
collections & public engagement
• Collaboration
We are better working together than apart
9. Who is the DLCS for?
• Anyone interested in presenting large images or structured
sequences of images on the web;
• Anyone interested in presenting whole collections on the web;
• Anyone interested in annotation of images (both curated and user-
generated) and handling those annotations at scale - searching,
moderating, other processing;
• Anyone interested in searching text of digitised books, rendering
PDF or HTML versions of digitised books, etc;
• Anyone interested in building ad hoc web applications - discovery,
experience, education - on top of your own image resources, and
interoperating with the image resources of others;
• Anyone (including funding agencies) concerned about the long
term viability and maintenance of digitised collections beyond
digitisation programme funding.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23. National Libraries
• British Library
• France
• Denmark
• Israel
• New Zealand
• Norway
• Poland
• Serbia
• Wales
Research Institutons
•C2RMF (France)
•Cornell University
•Johns Hopkins Univ.
•Harvard University
•Oxford University
•Princeton University
•Stanford University
•Wellcome Library
•Yale University
Projects
• Biblissima
• e-codices
• TPEN
• TextGrid
Aggregators
• Artstor
• DPLA
• Europeana
Museums
• YCBA
• British Museum
24. Just enough metadata to drive
a remote viewing experience.
(e.g. sequence, labels,
attribution, license)
Image API Presentation API
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44. Summary
• A critical mass of images –
exposed as IIIF endpoints,
with open annotations, and
full-text searching – would
facilitate research (as well
as provide a dazzling user
experience)
• The DLCS seeks to provide
this platform to make this
happen – and do so in a
way which allows interested
parties to pick and choose
the services they require http://wellcomelibrary.org/player/b19584088
45. How will this be charged?
• On-going charges
• Based on storage and data
transfer (like the AWS model)
• Based on service(s) you use –
full text search, discovery layer,
generating IIIF end-points
•Other charges
• New services/enhancements
• Other agency services
• Bottom line: Will be more
affordable than a DIY
approach and priced within
the reach of the target
audience
46. Questions
1. Is there a need for a shared
service to support the
delivery of digital assets?
2. If yes, how useful would this
be for your organisation and
what services would we need
to provide to make it
invaluable?
3. What organisational structure
would be most appropriate to
deliver these services?