-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
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
Annotation import process is confusing. #103
Comments
Thank you. It works. I was initially confused by the warning message that it would discard all current annotations when I wanted to import it and the text file was open. |
I can see how the import process can be confusing. I've had more questions about this too. I'm keeping this issue open until this is improved. |
We should be able to import straight from the .json file since it already contains the text. Why is the .txt file necessary? |
The .txt and .json files aren't exactly the same unfortunately. For example, if you skip a sentence then the .json file has a NULL value in the place of the sentence. I also disagree that we should import the text from the .json file. In my own experience, a major use case for importing the .json file is to review the annotations done by someone else. You would then be trusting that the .json file really did include all of the sentences from the original text and that the original text was unmodified. |
Can you add the feature to revise annotations? I have .json file with annotations done by your tool. I want to revise them and check. No option to open .json file and revise it.
The text was updated successfully, but these errors were encountered: