Questions from Collections Metadata

[mialondon]

My colleague Jan asked:

I’m afraid I’m similar to Victoria in that I’m just not clear on how we technically link between the manifest and the annotations and to the images.

Will we have a Playbills manifest which links to the AnnotationsCollections manifest which contains the individual annotations for a Playbill? If so then we need links for the manifests (usually ARKs which are resolvable and permanent).

Or will the AnnotationsCollection (List?) manifest information and individual annotations within the AnnotationCollection be within the Playbills manifest? In which case we still need links as above.

We need identifiers to link to/from/and within the Playbill manifest; including the AnnotationsCollection manifest; the individual Annotations within the AnnotationsCollection and their canvas IDs. We also then need links from the annotations via their IDs to the images (the canvas/page). I think we currently use ARKs so these would be persistent and resolvable.

Sorry, I’m just trying to work out in my own mind how this works as a workflow.

[mialondon]

@eatyourgreens some questions from colleagues about working with manifests from Zooniverse

[eatyourgreens]

I think @glenrobson can answer that better than I can, but the link between a collection and a manifest is the manifest ID, with each annotation page in the collection then annotating a single canvas in that manifest.

https://iiif.io/api/presentation/3.0/#58-annotation-collection

[glenrobson]

Usually in IIIF you link a Canvas in the Manifest to an Annotation Page. With the changes @eatyourgreens did in #5 each annotation contains a link back to the Manifest and you could create a workflow that starts with the AnnotationCollection and follows the links to the AnnotationPages and then to the Annotations. Once you have an annotation you can get the manifest and canvas Ids and then add these to your manifests. This is what I did in the script linked from here:

https://glenrobson.github.io/iiif_stuff/zooniverse/Mar_2022/

The manifest IDs seem to contain the ARK for example:

https://api.bl.uk/metadata/iiif/ark:/81055/vdc_100022589176.0x000002/manifest.json

so I don't know if that helps with your internal workflow.

[Jashton123]

Thanks very much for the helpful replies and especially the manifests. I'll go through the manifest examples to follow the various links to see the workflow.

[eatyourgreens]

Here's a consensus date from the annotation page for the first playbill in the test set. The annotation target links to the canvas and manifest.

{
  "type":"Annotation",
  "motivation":"tagging",
  "body":{
    "type":"TextualBody",
    "value":"18190202",
    "language":"en",
    "format":"text/plain"
  },
  "target":{
    "type":"SpecificResource",
    "source":{
      "id":"https://api.bl.uk/metadata/iiif/ark:/81055/vdc_100022589176.0x0001c3",
      "type":"Canvas",
      "partOf":{
        "id":"https://api.bl.uk/metadata/iiif/ark:/81055/vdc_100022589176.0x000002/manifest.json",
        "type":"Manifest"
      }
    }
  },
  "id":"https://zooniverse.github.io/iiif-annotations/bldigital/in-the-spotlight/consensusDates/0"
}

[eatyourgreens]

By the way, I've been experimenting with generating subjects from IIIF manifests for the Siberian Photography project, to see if the process works, and I notice that in those manifests, like this one:
https://eap.bl.uk/archive-file/EAP016-1-1/manifest
manifest['@id'] is a link that resolves to a HTML page, not a JSON manifest.
https://eap.bl.uk/archive-file/EAP016-1-1

[mialondon]

@eatyourgreens I think EAP items have a different workflow because they're not actually held by the BL, but I can't recall if the manifests were setup internally or by an agency.