In which Wildbook did the issue occur? SeadragonSearch
What operating system were you using? (eg. MacOS 10.15.3)
I’m using MacOS 11.1; I’m not sure what participants are using.
What web browser were you using? (eg. Chrome 79)
I’m using Chrome 88; I’m not sure what participants are using.
What is your role on the site? (admin, researcher, etc) Admin
We’ve heard from several participants that they are not receiving notifications when an encounter they’ve submitted is assigned to an existing ID (a re-sighting/rematch). They receive notifications thanking them for the original submission and letting them know if a new individual ID is assigned, but not if an encounter is matched to an existing time series.
What did you expect to happen?
We were also having trouble with this before the email server change, and the issue seems to be persisting. I noticed that similar topics have been marked as resolved in the forum, so wanted to start a new thread. We expected that participants would receive a notification when an encounter they’ve submitted is identified as an existing individual in the database.
What are some steps we could take to reproduce the issue?
It’s difficult to reproduce unless you know you have a match, but I could share some recent rematches if that would help!
If this is a bulk import report, send the spreadsheet to email@example.com with the email subject line matching your bug report