-
Notifications
You must be signed in to change notification settings - Fork 12
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
Weird behavior when annotating WB strains #12
Comments
In this case I think what I need the curators to do is add a reply to the SciBot annotations and paste the shared link to the curator provided correct annotation in the text box (@judell another use case for allowing replies to have 'exact' annotation anchoring). Nothing else should go in the reply for now, we could add a tag but the reply + shared link is enough for me to be able to sort out what is going on and find the correct anchoring when we release to public. |
ok Tom, I am not understanding what you mean by "curators to do is add a reply to the SciBot annotations and paste the shared link to the curator provided correct annotation in the text box" |
Here are two images showing the steps. Turns out that this papers is not the best example because the hypothesis anchoring machinery is completely screwed up because the Here is the reply I made. |
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5655125/
SciBot asserts that all things that look like this:
RRID:WB-STRAIN: PS4657 are actually just duplicates of this RRID:WB-STRAIN
The typesetting is correct, but there is a space in an unexpected place in this identifier.
Thoughts?
Curation did this: Assert corrected RRID for one of the tags, where the position was correct. Other unresolved tags are duplicates at this position.
Label all correct RRIDs
Another example of this behavior: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5604087/
This one, curation addressed all cases because they were properly anchored.
The text was updated successfully, but these errors were encountered: