We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original discussion can be found in #286 , requested by @johann-petrak
When exporting documents, instead of nesting all annotation features inside a label field:
label
{ "type":"Document", "start":0, "end":10, "id":0, "features":{ "label":{ "text":"Annotation text", "radio":"val3", "checkbox":[ "val2", "val4" ] } } }
We bring it up one level, making features directly accessible and getting rid of the label field:
{ "type":"Document", "start":0, "end":10, "id":0, "features":{ "text":"Annotation text", "radio":"val3", "checkbox":[ "val2", "val4" ] } }
Additional notes
gate-teamware/backend/models.py
Lines 1001 to 1003 in 427821e
gate-teamware/backend/rpc.py
Line 675 in 427821e
gate
raw
annotation_sets
The text was updated successfully, but these errors were encountered:
twinkarma
No branches or pull requests
Original discussion can be found in #286 , requested by @johann-petrak
When exporting documents, instead of nesting all annotation features inside a
label
field:We bring it up one level, making features directly accessible and getting rid of the
label
field:Additional notes
To do
gate-teamware/backend/models.py
Lines 1001 to 1003 in 427821e
gate-teamware/backend/rpc.py
Line 675 in 427821e
gate
andraw
https://gatenlp.github.io/gate-teamware/development/manageradminguide/documents_annotations_management.html#exporting-documentsannotation_sets
field. New annotations should be appended to this field rather than overwritten. #348)The text was updated successfully, but these errors were encountered: