You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently re-enabled the Annotator.js comment field for adding and editing comments about annotations (#118). However, this turned out to be not what the customer wanted 🙂 Instead: while keeping the user interface exactly the same, the content of the comment field should instead be saved to the description field of the code.
This is workable, as we use Annotator.js in such a way that one annotation can only contain one tag ("code"). So the code description can be added and edited via the comment field.
The behavior would have to be like this:
When creating codes on the fly by entering a name of a not-yet-existing tag, the comment field's content would be added as the description of that code.
When selecting an existing code in the Annotator.js overlay by clicking on an entry in the auto-suggestion list, the comment field would be initialized at that time with that code's description. The description can be edited and will be saved to the code when saving the annotation.
When entering an existing code's name into the Annotator.js overlay (without clicking on an entry in the auto-suggestion list), the comment field should not be filled. Because otherwise, it would have to be re-filled on every keypress event, and it may lead a user to lose content from the comment field when correcting the name of a code before submitting. And to prevent data loss when submitting a code alongside with an empty comment field, as can happen in the case described above, the code description field must not be deleted but should stay unchanged.
The text was updated successfully, but these errors were encountered:
It turns out that adding and editing code descriptions on the fly was not a very important requirement, and users rather want a way to add code translations on the fly.
For this feature, it seems more appropriate to just make it faster and more comfortable to add code descriptions, namely by providing a tabular view that allows to edit them together with code names and their translations. This is managed in #121.
We recently re-enabled the Annotator.js comment field for adding and editing comments about annotations (#118). However, this turned out to be not what the customer wanted 🙂 Instead: while keeping the user interface exactly the same, the content of the comment field should instead be saved to the description field of the code.
This is workable, as we use Annotator.js in such a way that one annotation can only contain one tag ("code"). So the code description can be added and edited via the comment field.
The behavior would have to be like this:
When creating codes on the fly by entering a name of a not-yet-existing tag, the comment field's content would be added as the description of that code.
When selecting an existing code in the Annotator.js overlay by clicking on an entry in the auto-suggestion list, the comment field would be initialized at that time with that code's description. The description can be edited and will be saved to the code when saving the annotation.
When entering an existing code's name into the Annotator.js overlay (without clicking on an entry in the auto-suggestion list), the comment field should not be filled. Because otherwise, it would have to be re-filled on every keypress event, and it may lead a user to lose content from the comment field when correcting the name of a code before submitting. And to prevent data loss when submitting a code alongside with an empty comment field, as can happen in the case described above, the code description field must not be deleted but should stay unchanged.
The text was updated successfully, but these errors were encountered: