Comments on manifest identifiers passing through Zooniverse

[mialondon]

Sharing Jim's original comment on zooniverse/Panoptes-Front-End#6095 (comment)

@mialondon Here's a couple of annotations from the dates workflow. The canvas IDs have an ARK number, so hopefully that's enough to link each annotation back to the image that it's annotating.

https://zooniverse.github.io/iiif-annotations/annotations/dates/0.json

to collect feedback on whether the information available allows ingest back into BL systems.

[mialondon]

Also zooniverse/Panoptes-Front-End#6095 (comment)

@mialondon Here's a couple of annotations from the dates workflow. The canvas IDs have an ARK number, so hopefully that's enough to link each annotation back to the image that it's annotating.

https://zooniverse.github.io/iiif-annotations/annotations/dates/0.json

Hi, I hope its OK to jump in here but the IIIF spec doesn't mandate that the canvas identifiers resolve and for the majority of implementations they don't resolve to anything.

Please do jump in! I've published a couple of annotation collections now:

* Dates: https://zooniverse.github.io/iiif-annotations/annotations/dates.json

* Titles: https://zooniverse.github.io/iiif-annotations/annotations/titles.json

They're linked up to annotation pages, containing lists of annotations. I still need to assign IDs to the annotations, but other than that I think those files should be complete, or complete enough to work in a viewer. One question I had is: should I link up each AnnotationCollection to the manifest that it's annotating? I've made the assumption that we're only ever working with one manifest at a time, and that we would publish multiple collections if a workflow annotated multiple manifests.

Are the coordinates (xywh=291,797,2207,337) relative to the canvas dimensions?

Yeah, those numbers are scaled from the Zooniverse annotations to the canvas width and height found in the BL manifest. I've added a config file that stores the manifest URL and the Zooniverse image dimensions (for scaling.) https://github.com/zooniverse/iiif-annotations/blob/main/_data/config.json

The inputs for a build are that config file plus the two workflow CSV files, containing the Zooniverse classification annotations (also in the _data directory). Builds are run by GitHub actions, reading those files and publishing the JSON output as GitHub pages.

[eatyourgreens]

That screenshot reminds me that the published annotations don't have IDs at the moment (#3.)