Canvas with content that will never be "seen"

[benwbrum]

Description

There is a lot of material in archives that will never be put online, but there is a need for a IIIF manifest for that material as a place to "hang" public annotations off of.

Variation(s)

We're working on an audio-specific case (for AudiAnnotate), but there is likely applications for items that have not been digitized yet or for copyrighted or restricted image material.

We've also had discussions of a IIIF manifest as a "football" that is passed from system to system, with each enhancing the data available about the object. (In this case, the initial manifest is metadata about a document that hasn't been digitized, then a later process/system adds the digitized images, then a later process/system adds transcription, then another might add scholarly annotations, and then the whole set of things is passed to a publishing system.)

Proposed Solutions

We'll have a sample IIIF manifest for annotations on a reading-room only audio file shortly.

Additional Background

https://github.com/hipstas/AudiAnnotate

[tomcrane]

(checking in on this while rounding up Auth-labelled issues)

Scenarios

• The canvas has no painting annotations (but may have other annotations, as well as metadata etc (i.e., it has an empty items property)
• The canvas does have one (or more) painting annotations, but the image/image service/other media is access-controlled: the image is restricted, or not for public consumption, etc; but still available to some people (e.g., staff).

The second of these is IIIF auth, but I don't think there is anything specific to this use case that isn't part of normal IIIF auth