WildMeOrg / Wildbook

Wild Me's first product, Wildbook supports researchers by allowing collaboration across the globe and automation of photo ID matching
https://www.wildme.org/wildbook.html
GNU General Public License v2.0
104 stars 67 forks source link

Public encounter submissions do not email users with identification updates #640

Closed goddesswarship closed 4 weeks ago

goddesswarship commented 3 months ago

Expected behavior Submitters receive an email when the following actions occur:

Current behavior In Seadragon Search, a submitter reports that they receive encounter submission emails, but are not emailed when their animal is identified or resighted.

Testing notes Past reports of missing emails have been due to users accidentally unsubscribing, but for the submitter with email atj@atj.net.au, they are actively subscribed with 100% deliverability.

Setting an ID via the encounter page's (/encounters/encounter.jsp) Identification section (either by creating a new individual or assigning an existing ID) always generates a notification email to the submitter.

However, confirming a match on an existing individual from the match page (/iaResults.jsp) does not notify the submitter. Confirming no match on the encounter page also doesn't notify the submitter due to #598.

This traces down to iaResultsSetID.jsp. It is just missing the same block to send the email that is present in IndividualAddEncounter and other blocks.

Community link https://community.wildme.org/t/no-automated-submission-emails/2687

goddesswarship commented 3 months ago

Additional testing in QA and potentially SAS USA needed to verify if this is platform specific.

goddesswarship commented 3 months ago

Notification emails are disabled in QA and because SAS USA uses spot-mapping, I can't test confirming IDs on the match page. @TanyaStere42 Should I mark this as platform-specific or is there a way we can allow notification emails in QA to validate this?