Richard Eckart de Castilho

In INCEpTION, one can search for annotations and then bulk-delete the annotations.

> Also, I believe INCEpTION allows bulk-assign tags, too? Yes. That said, I think adding the ability to select multiple annotations might be doable as well. It's not a small...

Well, these are somewhat different use-cases. For bulk-deletion, one can select multiple annotations regardless of which layer they belong to and just delete all of them. For bulk-change, the annotations...

I think if/when this is tackled, it definitely makes sense to first implement the multi-select + delete feature. Then building on that, one could implement a basic version of multi-update...

Supporting bulk-changes on annotations from multiple layers IMHO doesn't make much sense at all, because usually they will have different or incompatibly configured features. I expect that the case where...

"Hide Un-constraint feature:" means that if a feature is not covered by a constraint rule, then it will be hidden from the UI. I.e. if certain features are only applicable...

What we have is "Hide Un-constraint feature". But what @neumannm wants is "Hide Un-constraint feature _values_". These are two different things.

AERO 1.0.0 does not specify the name or project type as result information.

When the user selects an item from the dropdown, the next immediate action is indeed probably to press the *add* button. But doing away with the add button completely won't...

It's something we can definitely try.