User cannot add a term to an annotation created by a job

[elodieburtin]

The issue can be reproduced in the application as follows:

1. Access an image containing annotations created by a job
2. Select one of those annotations
3. In the Ontology right panel, try to associate a term to it by checking a checkbox next to the desired term Result: the action has no effect, and the term is not associated to the annotation

If trying to add a term with POST /api/annotation/{idAnnotation}/term/{idTerm}.json, the server returns the following error:

AnnotationTerm must have a valide userannotation:{idAnnotation}

[rmaree]

It's not a bug, it's a feature. ;-) What is your goal here ? Shouldn't you use the reviewed annotations instead ?

[elodieburtin]

We could imagine a situation in which a job annotates regions of interest, so that they can be associated to the appropriated term later on by a human user. In such a case, is it really appropriate to use the review process? (it is more of a human-machine collaboration than a review IMHO) Furthermore, I find it misleading for the user to have different behaviours depending on the annotation type (especially since this annotation type cannot be found easily I think?). There should at least be an error message explaining why it is not possible to add a term. Finally, if we cannot associate term, why is there the possibility to modify the annotation? Shouldn't it be performed in the review as well?