Support multiple motivations for a single annotation

[elynema]

Is your feature request related to a problem? Please describe.
Annotations in manifests produced by AVAnnotate seem to often contain multiple motivations. In the example below, there is a textual annotation that is labeled as both supplementing and commenting.

Describe the solution you'd like
It is currently unclear the best solution. In this example, it seems that the commenting motivation is the most meaningful. Perhaps discuss with AVAnnotate team the purpose of the additional supplementing motivation.

In some scenarios, might we display the annotation twice to respond to both motivations?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Here is an example from this manifest: https://lgsump.github.io/maya-deren-example/meshes-of-the-afternoon/manifest.json

"@context": "http://www.w3.org/ns/anno.jsonld",
      "id": "meshes-of-the-afternoon-canvas-1-shadow-annotation-0.json",
      "type": "Annotation",
      "motivation": [
        "supplementing",
        "commenting"
      ],
      "body": {
        "type": "TextualBody",
        "value": "Here we get the first glimpse at something important to understanding the artist’s play with shadow in that the form already is chosen in Black & White film.",
        "format": "text/plain",
        "purpose": "commenting"
      },
      "target": {
        "source": {
          "id": "https://lgsump.github.io/maya-deren-example/meshes-of-the-afternoon/canvas-1/canvas",
          "type": "Canvas",
          "partOf": [
            {
              "id": "https://lgsump.github.io/maya-deren-example/meshes-of-the-afternoon/manifest.json",
              "type": "Manifest"
            }
          ]
        },
        "selector": {
          "type": "PointSelector",
          "t": "16"
        }
      }

Done Looks Like

• Email to AVAnnotate members about what they would like to see when there are multiple motivations
• How are the Aviary player and AVAnnotate rendering multiple motivations for an annotation in a manifest documents?

[joncameron]

Right now Aviary is able to display these manifests but Ramp is not. We can look at the Aviary player for how implementation goes, and talk to AVAnnotate project members to get more background on how the supplementing motivation is being used. We can then make changes to support the expectations of rendering when there are multiple motivations.

[Dananji]

In the new AVAnnotate manifests, there's an added motivation at the Annotation level where it has motivation: ["commenting", "tagging"].
With this new motivation set, an Annotation in an AVAnnotate Manifest can have the following combinations of values for its motivation:

• "supplementing"
• ["supplementing", "commenting"]
• ["commenting", "tagging"]

Both AVAnnotate and Aviary displays all these annotations as timed annotation under Annotations tab.

In the current implementation, Ramp displays only supplementing and highlighting motivation annotations in Transcript component and MarkersDisplay component respectively.

In some scenarios, might we display the annotation twice to respond to both motivations?

Ramp could display supplementing annotations as transcripts in the Transcript component with just the timestamp and the text value.
In addition to that, display the same annotations with supplementing motivation in the upcoming Annotations component, where it can display extra information related to the annotation like tags.

How are the Aviary player and AVAnnotate rendering multiple motivations for an annotation in a manifest documents?

Both Aviary and AVAnnotate render all these annotations as time synced annotations under 'Annotations' portion of the UI regardless the difference in motivation. Differences in the 2 interfaces, are as follows;

Property/Element value in Manifest	AVAnnotate UI	Aviary UI
target of the Annotation is a media fragment	displays the start and end times with the text value as a single clickable element in the annotations list	displays start and end times as 2 clickable links linking to start and end timepoints in the player respectively with an un-clickable text
target of theAnnotation as a point selecor	displays the same value for both start and end times with the text as a single clickable element in the annotations list	displays a clickable single timestamp alongside the text value in the annotations list
TextualBody typed element in the body of the Annotation with purpose: "tagging"	displays these values as a tag below the annotation timestamp and text and uses these values as filters in the 'Annotations' list display	does not display these values in the annotations list, instead displays the label of the AnnotationPage as a tag

Example manifest:

• https://tanyaclement.github.io/znh-1939/manifests/manifest.json