API
Single Asset Manifest

Single Asset manifest

⚠️

The single asset manifest does not yet represent in IIIF from everything the platform knows about your asset and all the services and adjuncts it can offer.

For every asset, there is a single asset manifest: a IIIF Presentation 3.0 Manifest that includes all the outputs of all the delivery channels specified for the asset.

This manifest has one canvas, with a single painting annotation.

If the asset is an image, audio or video, the canvas dimensions are taken from the source asset. Otherwise, the canvas dimensions are set to width = 1000, height = 1000, with no duration.

  • For the iiif-img delivery channel, the body of the painting annotation is a full/max parameterisation of the v3 image service, with that image service as a service property of the body image.
  • For the iiif-av delivery channel, the body of the painting annotation is a Choice resource listing all the transcoded outputs. Note that it is always a Choice resource, even if there is only one output. (?) Each output is a Content Resource with width, height and/or duration, mediaType, label, and additional profile information where available (e.g., codec).
  • If the asset is an image and does not have the iiif-img delivery channel but does have the thumbnail delivery channel, the body of the painting annotation is a full/max parameterisation of the v3 thumbnail image service.

If the asset has the iiif-img delivery channel, the body of the painting annotation has two services, one for v2 and one for v3 of the Image API. If the asset has access control, the auth services are included inline on the image services.

If the asset has the thumbnail delivery channel, the canvas.thumbnail property is an image resource whose id is the full/max parameterisation of the v3 image service. This image resource has v2 and v3 thumbnail services.

The output of the file delivery channel is always available as canvas.rendering, with auth services emitted inline (if available).

If the asset only has file delivery channel, the body of the canvas painting annotation is a placeholder image provided by the platform. The canvas is then given the additional placeholder behavior, and the rendering is given the additional behavior original. (from https://github.com/wellcomecollection/docs/pull/77 (opens in a new tab))

Any adjuncts are listed as seeAlso properties of the Canvas, with auth services if they have them.

In addition to the above, which are intended to be most useful in third party viewers, the single asset manifest has an additional extension property dlcs:channelOutputs, which is an array of content resources and services; each member of the array includes the channel it is the output of. This is more consistent in form than the regular manifest, and can be used for quick programmatic access to channel outputs.

Examples

Audio with one transcode derivative

 

Video with two transcode derivatives and two adjuncts

 

Image with image service and thumbnail

 

Image with image service, thumbnail and file outputs, and three adjuncts

 

Word document on file channel with one adjunct

 

Image with no delivery channels

 
touched 2025-09-23T12:04:54