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
Since all tokens are in the form consecutive words, it would be much faster to select multiple words and select the label. All the labels could be inferred this way. Take this example:
پیست اسکی نسار بیجار استثناییترین ...
You can only select پیست as the starting word, بیجار as the ending word, and select the label مکان and it would be all done. No need to label each token separately.
However, I'm not sure if it's wise to make this the only way to label tokens. I'm not sure if there are examples of this method not working, but I'm almost certain you can find weird examples that cannot be labeled using this method.
This method may or may not be exposed in the API, but I believe it would make labeling by hand in the web interface much easier and faster. (Honestly, since submitting labels reloads the page, labeling tokens is tiresome. Combining this feature with #2 would make manual labeling much faster.)
The text was updated successfully, but these errors were encountered:
Thank you. It's a good suggestion and we will consider it in development backlog but as you mentioned it shouldn't be the only way to label tokens. Currently, we are working on an improved version of the user panel that may resolve some UX issues such as this one
https://github.com/chakki-works/doccano is an open source annotation tool which has a similar approach to what has been suggested here and in #42. I don't get why do we need to specify the beginning of a token separately.
Since all tokens are in the form consecutive words, it would be much faster to select multiple words and select the label. All the labels could be inferred this way. Take this example:
پیست اسکی نسار بیجار استثناییترین ...
You can only select پیست as the starting word, بیجار as the ending word, and select the label مکان and it would be all done. No need to label each token separately.
However, I'm not sure if it's wise to make this the only way to label tokens. I'm not sure if there are examples of this method not working, but I'm almost certain you can find weird examples that cannot be labeled using this method.
This method may or may not be exposed in the API, but I believe it would make labeling by hand in the web interface much easier and faster. (Honestly, since submitting labels reloads the page, labeling tokens is tiresome. Combining this feature with #2 would make manual labeling much faster.)
The text was updated successfully, but these errors were encountered: