Filter annotations

[mzur]

Largo could be used (by an expert) to review the annotations of a single other user. To do this, the annotations need to be filterable by users. The reviewer/expert can select one (or more) user(s) to see only the annotations of the selected user(s) in Largo.

Summary: Filter by

• user
• file
• date of the image
• date of the annotation
• date of the annotation label
• annotation shape

Ideally, the filters could be combined just like in the volume overview and support less than/equals/more than rules (see biigle/core#359).

[mzur]

This feature should be available for any user, as an editor could use it to review only their own annotations, too.

[mzur]

Large images and videos can have lots of annotations in a single file. Users should be able to review the annotations of a single file, too.

[mzur]

The filtering could be implemented in a sidebar tab that is similar to the one of the volume overview. We might need "sorting" and "settings" tabs in the future, too.

[dbrembilla]

While working on this issue, I realized it could be useful to add to the existing API call for image annotations (api/v1/labels/:id/image-annotations) a query part that takes in elements that can be used in the filter (api/v1/labels/:id/image-annotations?shape=1&user=6 etc.). Do you think this is a good idea? To do this I would need to work on the master branch. Otherwise I would need to implement it here, and it does not really make super sense in my head since it would be more of a global behaviour. What do you think @mzur ?

[dbrembilla]

Vene

While working on this issue, I realized it could be useful to add to the existing API call for image annotations (api/v1/labels/:id/image-annotations) a query part that takes in elements that can be used in the filter (api/v1/labels/:id/image-annotations?shape=1&user=6 etc.). Do you think this is a good idea? To do this I would need to work on the master branch. Otherwise I would need to implement it here, and it does not really make super sense in my head since it would be more of a global behaviour. What do you think @mzur ?

Nevermind, I saw that these parts of the API are already implemented in largo. I will extend the existing ones

[mzur]

Did you have a look at how the filter UI of the volume overview works? I had something similar in mind here because users are already familiar with it. Under the hood the volume overview filter performs one query for each filter rule (i.e. each rule has it's own API endpoint). The results are then combined to the final sequence in the frontend. The alternative would be a single endpoint but with multiple query parameters, as you describe. I don't prefer one of these two as long as the UI is consistent with the volume overview.