Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVAnnotate Grant Work #430

Open
elynema opened this issue Feb 23, 2024 · 3 comments
Open

AVAnnotate Grant Work #430

elynema opened this issue Feb 23, 2024 · 3 comments
Labels

Comments

@elynema
Copy link

elynema commented Feb 23, 2024

Sample AVAnnotate manifests:

Tanya's presentation from the IIIF Online Meeting workshop has a nice list of sample manifests, including multi-item manifests.

Aviary

Structural ranges that cross file boundaries - we don't have an example AVAnnotate or Aviary manifest for this yet

Some things noted that Ramp needs to support:

  • multiple motivations in an annotation
  • multiple TextualBody elements
  • range / point selectors
  • transcripts as textual annotations
  • multiple annotation sets (annotation pages)
  • multiple canvases in a manifest
  • structure that spans files/canvases
  • commenting and supplementing annotation display (label + value) - need to test to identify other types of annotations might need to support?
@elynema elynema added the Epic label Feb 23, 2024
@elynema
Copy link
Author

elynema commented Sep 4, 2024

Questions for AVAnnotate folks:

  • Currently providing filtering based on annotation pages. However, do annotation pages really have semantic value? Should filtering occur by some other mechanism? Sometimes there are tagging labels on the individual annotations, but no label on the annotation page itself. Sometimes there are labels on the annotation page, but no tagging labels on the individual annotations.
  • When providing a label to filter annotation sets and to display next to each annotation, do we use the AnnotationPage label (Aviary and AvAnnotate provide) or the textualBody with purpose=tagging label (just AVannotate provides but might be better solution)?
  • If there are multiple annotation pages, but no motivation=tagging labels on the annotations themselves, are we supposed to display the annotation page label as a tag on each annotation from that annotation page?
  • When an annotation has multiple items in an annotation body, and one of them has a tagging purpose, should we assume that should be displayed as a tag for the annotation text?
  • How to handle multiple annotation bodies in a single annotation? Do they all get concatenated into a single annotation? Do we want all textualbodies regardless of purpose or just some?
  • Annotations with motivation of commenting (AVAnnotate) and supplementing (Aviary) were called out. Are there other motivation types that we need to support?
  • Will textualbodies that have HTML have the format=text/html attached so we know to expect HTML?
    -- From Ben: "I think that's an artifact of us designing the datamodel and then users putting HTML into the app. We probably should change the format to text/html."
  • Aviary currently uses motivation=transcribing and motivation=subtitling. Can we ignore annotations with those motivations for now as we expect there to be a new provides property to label them?
  • New AVAnnotate manifests have supplementing, commenting, and tagging annotations. For annotations that have both supplementing and commenting motivations, should they be displayed on Transcripts tab, on the Annotations tab, or both? (see annotation page in this example). Should these annotations have a supplementing annotation?

Some examples:

@elynema
Copy link
Author

elynema commented Sep 30, 2024

Updated the second manifest linked to a working version. Still having issues with the annotation pages linked in the third manifest.

@elynema
Copy link
Author

elynema commented Oct 10, 2024

Should have updated manifests that work now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant