Individual Update Emails

Now that we have started to see changes in the Sharkbook platform with the logo change, emails that are being sent to users include the old logo.

Presumably you will start updating the emails with the new logo, but I wanted to call out that they are in desperate need of being re-vamped.

The first major change required is the email titles:
The email title is full of coding that should be hidden as it looks like junk. Instead of having an email title that says "Individual update: ecf537e7-959d-4136-bd07-1ba21cca6a49" it should say something like “Shark Update - Individual [insert ID & nickname] resighting”
For example "Individual update: ecf537e7-959d-4136-bd07-1ba21cca6a49" would become “Shark Update - Individual GNS-1163 resighting”.

The second major change required is the content of the email:
We have had so much feedback from contributors that the engagement post upload is really poor and they would be more likely to contribute to citizen science if they received meaningful emails, but the current emails just include links, and a lot of code. They also do not include the names of the individual (for example, in the email I refer to it says:

“Hello!
Just a quick e-mail to let you know that a shark that you sent us encounter data for has been seen again and positively identified. Follow the links below to learn more.
Previously identified shark: ecf537e7-959d-4136-bd07-1ba21cca6a49 (Alternative ID: @INDIVIDUAL_ALT_ID@)…”

Is this something that can be improved? Its the main method to communicate with contributors and is so important to get this bit right to keep people engaged?

Happy to help with brainstorming if needed - but I think some small tweaks would help greatly

Updating this to a feature request.

Your first change is related to a current ticket and has a dependency on dev availability against competing priorities: Encounter emails lists sharks’ alternate name as “@INDIVIDUAL_ALT_ID@” · Issue #368 · WildMeOrg/Wildbook · GitHub

I’ll have to look into whether the second issue is as straightforward as rewriting the template so that it’s more readable vs the action text pulling UUIDs instead of user-friendly names. The latter would require dev involvement.

Here’s the ticket link: Make encounter update template in Sharkbook more user-friendly · Issue #935 · WildMeOrg/Wildbook · GitHub