Default annotation motivation filter excludes valid W3C motivations, causing confusion

[flamsens]

By default, Mirador only displays annotations with motivations tagging and commenting in the annotation panel. Annotations with other valid W3C Web Annotation motivations (such as describing, highlighting, classifying, etc.) are filtered out and not displayed.

Why this is problematic:

• User confusion: When testing Mirador with standard IIIF annotations, users may believe there's a bug when their valid annotations don't appear
• Interoperability: Many IIIF resources use other W3C-standard motivations like describing for accessibility descriptions or identifying for named entities
• W3C compliance: All motivations defined in the W3C Web Annotation Data Model should be treated as valid

Proposed solution:

• A. Remove the default filter entirely, displaying all annotation motivations by default
• B. Include all W3C-standard motivations in the default display: assessing, bookmarking, classifying, describing, editing, highlighting, identifying, linking, moderating, questioning, replying

The filter could remain configurable for users who want to restrict which motivations are shown.

Settings

mirador/src/config/settings.js

Line 443 in 15b6015

filteredMotivations: ['oa:commenting', 'oa:tagging', 'sc:painting', 'commenting', 'tagging'],

[marlo-longley]

Thank you @flamsens. I will investigate and bring it up at our next meeting. I don't know the history behind this filter. In the meantime, if you are able to provide any links to manifests containing these other motivations, it would be helpful for our work.

[flamsens]

Hi @marlo-longley,

the W3C web annotation data model contains a list of motivations.

The annotations of the Basic newspaper example use a "supplementing" motivation. The manifest renders in Mirador, with an empty Annotation panel but with annotation bounding boxes that can be clicked/hovered.