Vault - Extracting choice data

[stephenwf]

This demo uses "Vault" api to load in a presentation 2 or 3 manifest and traverse through the canvas, annotation page, annotation and finally down the body. The body is a choice. Hyperion does not dereference each of the choices, but maybe it does need to do this.

---

Demo | Interactive sandbox

[stephenwf]

Hyperion could extract each of the images:

{
  "id": "2eba27a0",
  "type": "Choice",
  "items": [
    {
      "id": "https://iiif.io/api/image/3.0/example/reference/421e65be2ce95439b3ad6ef1f2ab87a9-dee-natural/full/max/0/default.jpg",
      "type": "ContentResource"
    },
    {
      "id": "https://iiif.io/api/image/3.0/example/reference/421e65be2ce95439b3ad6ef1f2ab87a9-dee-xray/full/max/0/default.jpg",
      "type": "ContentResource"
    }
  ]
}

but the problem is that choices have labels that are properties of the choice (e.g. "Natural light" doesn't label the resource on it's own).

An alternative may be:

{
  "id": "2eba27a0",
  "type": "Choice",
  "items": [
    {
      "id": "https://iiif.io/api/image/3.0/example/reference/421e65be2ce95439b3ad6ef1f2ab87a9-dee-natural/full/max/0/default.jpg",
      "label": {"en": ["Natural light"]},
      "type": "ContentResource"
    },
    {
      "id": "https://iiif.io/api/image/3.0/example/reference/421e65be2ce95439b3ad6ef1f2ab87a9-dee-xray/full/max/0/default.jpg",
      "label": {"en": ["X-Ray"]},
      "type": "ContentResource"
    }
  ]
}

[tomcrane]

Bug (?) body of the Choice anno is reported as type: ContentResource, but it's a Choice when resolved.

You'd need to see it was a Choice before this de-ref?

[stephenwf]

Yes possibly makes sense to keep choices inline and not dereference them

[stephenwf]

Related behaviour / bug: #35

[tomcrane]

(More generally, should everything include its label in the ref that comes back from Vault? You often need the labels on things, to render in UI, and this might be before fetching the full object from the Vault). See similar discussion on (link tbc).