-
Notifications
You must be signed in to change notification settings - Fork 7
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
Emails for My Annotation may have some records which do not have comments(annotations) #346
Comments
Based on this query: Assume A and B both subscribe MyAnnotation alerts Case 1: fixed Case 2: fixed Case 3: fixed Proposal: |
Test cases have been built |
Thanks Bai, I'll do a final run through on test and let you know how it goes |
A potential bug on multiple annotations: And then The current algorithm does not have the ability identify whether those 'verified assertions' have been notified to User A Current solution: |
Confirming I just received a scheduled hourly My Annotations on test with a second verification comment (Verification_2) on the first (and only) flag. The verification 2 comment shows in the My Annotations email, and also the regular Annotations email. Next test case I'll try: a second flag, with verification |
Confirming I just received the My Annotations email with the first verification on a second flag. for reference, the flagged record is: https://biocache-test.ala.org.au/occurrences/e52f68ea-a058-45a2-bc2c-0feca9ac2e7a |
Thus, my annotation email always displays the latest assertions
However, it always shows the "verified" annotations.
Reason:
The diffService of MyAnnotation and Annotation share the same algorithm at this moment. It detect different type of annotations, including: 'open_assertions', 'verified_assertions', 'corrected_assertions'
However, MyAnnotation only asks and displays 'verfied_assertions', so if 'I' make an 'open' or 'corrected' assertions on a record, the record will be collected and put it into the alerts email.
todo:
Modify the diffService of MyAnnotation to find only 'verified_assertions'
The text was updated successfully, but these errors were encountered: