Tagging conventions for the same code under two concept

[Simamohammad]

Imagine that code X is linked to two concepts, Y and Z. In the concept tab, if I first tag concept Y as narrow, the associated code X inherits the narrow tag. Later, if I scroll down and tag concept Z as possible, code X then inherits the possible tag from concept Z and loses its previous narrow tag.

Is there a way to avoid this? Ideally, both tags should be retained so that the reviewer can clearly see that code X has been flagged with two different tags and can decide which tag is most appropriate.

[benozol]

We should detect and handle such conflicting tags directly instead of waiting to resolve the conflict later (see #84). Our model is one optional tag per code, and representing conflicting tags would be opposed to that.

As a first step, I propose to detect and describe such conflicts and ask the user to confirm or reject the whole tagging operation, which is implemented in #85, here a screenshot:

The idea is to bail to code-level tagging if we do not want to tag the shared codes. If we see that this case is too frequent and too annoying, we can provide a user interface to confirm/reject the tagging on the code level but for now I'm not sure if this effort is warrented.