Updating cluster view on filtering

In a catalog in Cluster view, the view doesn’t seem to update the points shown when I add a filter. Is this on the roadmap?

Background: I have a catalog called Product 1. Every time we manufacture a batch of this product we upload the pictures takes. When adding the images to an annotation project it’s very easy through cluster view and we can use “Add classification” directly when we add to project and go directly to Review step. But if the selected images are already in the project we just get a notification that those images already have a label.

Hey @mathias.ronnlund1 ,

So let me get this right you would want the selection to omit the asset already present in the project at the Cluster point level?

We do seem to provide this option already but at the bulk classification level.

Hi,

Basically like that, but the filter might be better the other way around “Project is not one of ‘class mass’” so we would only see images not yet in that project.

Our pictures are clustering surprisingly well in initial testing.

The images mostly grouped according to classes in our ontology but there are in every batch a few that are wrong.

Now when I select the pictures in one of the groups I get a preview of the pictures, I can unselect the wrong ones and add the rest directly to verification, skipping the labeling step.

When I add new pictures to the catalog and select the same group, the preview will show both the old and the new pictures. Shortly there will be hundreds or thousands of pictures in the same group and I need to unselect the same ones every time.

The solution, of course, is to create a new catalog for every uploaded batch of pictures. So we would have catalogs like product1_2024112, product1_20241015 etc.