New version in Google doc
What are we doing here?
Combo of text from the Google doc and text from the process recipe/index.md
(the answer to this might be completely different for DDS on AWS - e.g., a massive location-resolving key-value store.)
Given a relative file path in a METS file (e.g., a JP2 or ALTO file), the DDS needs to resolve the S3 location of that file.
The simple way to do this is load the storage manifest, find the entry corresponding to the path in METS, and deduce the S3 URI. But that would be very inefficient.
So the DDS caches a StorageMap for each storage manifest, which is this object, serialised:
As an editor, you have been given the task of making the slideshow seen here:
The materials you have been given to work with are a list of IIIF Image API endpoints. The thumbnails below are not to be used, they are just to be able to see which image is which. The only data to use is the Image Service URL.
It's a better test of the tools if you type at least some of the text by hand, creating links and styling where appropriate. However, there is quite a lot of text, so you could also copy and paste bits from the manifest directly. However, you should treat this text as if it were in a document given to you by a content editor.
Many Wellcome works are printed books with illustrations, figures, tables and so on that are identified by OCR during digitisation.
Many of those will have text nearby, that is likely to be a caption that describes the image.
The IIIF representation offers a quick way of getting pixels for the region of the page occupied by the image, and could be a way of finding nearby text.
- Given an identifier b28047345
- I can get a IIIF representation https://wellcomelibrary.org/iiif/b28047345/manifest
I hereby claim:
- I am tomcrane on github.
- I am tomcrane (https://keybase.io/tomcrane) on keybase.
- I have a public key whose fingerprint is B254 DAA7 0D2A 9B8C 7697 4158 05D4 84F2 921F F0E8
To claim this, I am signing this object:
Update, March 2019
Many of the discussions below have been synthesised into this slide deck: https://docs.google.com/presentation/d/1zAmXDlfvuwlQtp9uVgFLS7RVcfNqTcyEJybnNdQ2TgY
The links below are more comprehensive and are kept here for posterity. The other document worth considering is this:
Universal Viewer design principles
(in progress) Inspired by discussions at UVCON; an attempt to set out some guiding principles for the UV; comments sought!
- Tom: https://www.dropbox.com/s/0uqfvbbbym79grm/UVCON.pptx?dl=0
- Jennifer: https://www.dropbox.com/s/851p2lsoxxm7kwy/UVCon%20UX%20roles%20presentation.pdf?dl=0
- Jack: https://drive.google.com/file/d/1HZsW086JdkNL8td31lU1nsOz62sb0xI-/view
- Ed: https://docs.google.com/presentation/d/1AtN3m2aZDxfsrJ5f_X2S49fndPfhBOPCKOQfWVeT89M/edit
Wikimedia and IIIF
Why should Wikimedia implement IIIF? And what does that mean? There are several things they could do, some possibly quite straightforward.
Clarify two different things:
- Bring Wikimedia assets (images, audio, video) into shared IIIF annotation space, so that they become part of the IIIF Universe, can be annotated, referenced, mashed up, reused as Presentation API
- Allow image reuse via IIIF Image api:
- statically, via level 0 (extreme level 0) service