Thinking through the implications of treating the IIIF canvas as a resource in itself, not just as an internal building block of a IIIF Manifest.
Presented at the Fall 2020 IIIF Working group on December 2nd.
1. Canvases as First Class Citizens
David Newbury, Head of Software, Getty
IIIF Working Session, Fall 2020
1
2. Background
The Getty is a multifaceted institution, but all of our
facets create and use images. We're:
— A Museum
— A Library
— An Archive
— A Publisher
— A Website
— A Conservator
2
24. Shopping Cart interface
Use case: Select and order a
series of images for download
or view.
Manifests fit this role nicely—
but should include (some of?)
the annotations associated with
those images.
24
26. Observation #2
A given image may appear in many contexts, and may
be part of many objects—either "real" or "contextual".
Annotations (particularly computationally-generated
annotations) are o!en about the image, not the object.
26
29. Observation #3
Metadata is o!en related to the "View", and varies
across images within the context of an "Object"
— Visual description
— Photography Credit
— Alt Text
29
30. Observation #4
Some annotations are related to the image-in-context,
and other are intrinsic to the image-as-content.
— OCR
— Conservation Reporting
— CV Tagging
30
31. Canvases are a conceptual
space that contains
annotations that present a
specific collection of content.
31
32. My Questions:
How do we handle interactions with images +
annotations, not just manifests-as-object-proxies?
What's intrinsic to the object and what's to the image
or view?
Does a canvas change impacts several manifests?
Should we think about the Canvas a first-class resource
within the IIIF environment?
32
33. How do we manage this?:
— From an authorship perspective?
— From a technical perspective?
— From a UX perspective?
33