Replies: 1 comment 2 replies
-
Would using the The endpoint is undocumented because it's not part of the REST API. Maybe we should update the documentation to include all HTTP endpoints sometime. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We occasionally have quality control flags presented to us from downstream analyses and general QC checks using the csv reporting outputs, for example where the area for an annotation is spurious.
At this stage the annotation is (justly) only directly identifiable by its "id" value. It would be useful if there were a way for an annotator, using the application user interface, to quickly identify the annotation in question so that they confirm the spurious annotation within the system itself.
Potentially solvable by exposing the attribute id as text in the annotation tab like below, for a visual search:
(I can see this id value is already requested from the database to form the "data-annotation-id" attribute in each list item)
Or by allowing annotation id as an option in the annotation tab's filter?
(New functionality rather than a bug)
Beta Was this translation helpful? Give feedback.
All reactions