If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
In which Wildbook did the issue occur? Flukebook
What operating system were you using? Windows 11
What web browser were you using? Latest Chrome
What is your role on the site? Researcher
What happened? Marked individuals are not showing the Project ID name that they are given when they are matched. The project name is correct in the metadata but the link for the marked individual shows a different name.
What did you expect to happen? The third column from the left would have all the correct project names.
What are some steps we could take to reproduce the issue?
Sometimes Flukebook would show the message āError updating encounterā but it was not consistent with when the error would show up.
These are the links to the individuals that currently have the error.
There does not seem to be a pattern to when the error occurs. Today I have added new individuals to the catalogue and the name is correct, I have matched resightings and the project name has transferred to the new encounter with no problem, and I have matched a resighting and there has been an error (the last link above).
Best wishes, Ruth
Update: more of the matches are with the same problem;
When I click āconfirm actionā for the resighted individual to add it to a marked individual, a message confirms that the update was successful, but the individual name is changed from the Project name that has already been given (e.g. WPA/PM-302) to the random name that you see.
Hi @ruth.wpa
Which project are these part of?
Nevermind, I found your project!
When you assigned marked individual IDs to these encounters, did you do it from the match page or did you update it manually from the Identity section of the encounter page?
Now you mention it, sometimes there would be an error when I tried to assign IDS on the match page, then I would update it manually from the Identity section of the encounter page.
Just to clarify: what you entered and saved for the ID on the encounter page was in the project name format (WPA/PM-###) but what it actually ended up displaying as was the long, alphanumeric string of characters?
Thank you! While I look into this, if you see the āError updating encounterā message again while working on this project, can you share the match page link here and hold off on manually updating the ID on it so we can refer to it while testing?
Yes I can do that. Thank you!
1 Like
Hi @ruth.wpa
One more question: when you were assigning IDs, were you creating new individuals or were you adding encounters to existing individuals?
I was adding encounters to existing individuals. I think I had one situation when creating a new individual with the action button on the matching page, that there was an error in updating. I left the project and continued with matches another day. However, when there was a resighting of that individual, I would need to assign an ID by adding the encounter to an existing individual.
Thank you! I hope to have an update for you soon.
1 Like
Hi Anastasia,
I have a few more examples which I was going to send to see if it helps in solving the problem, but I apparently cannot include links in my posts.
Which email address would be best to send these links to?
Best wishes, Ruth
Thanks for letting me know. Iāve updated the forum settings to be less restrictive on link posting. Can you try posting again? Or you can email them to services@wildme.org.
1 Like
Hi Anastasia,
Here is a link to another encounter with the same problem. I have not confirmed the match, but it is individual WPA/PM-302.
This next link is for a match that I have not confirmed - it is WPA/PM-413. As you can see when it offers the action to confirm a match, the project name shows (WPA/PM-###) and there is now the additional alphanumeric name. I had just confirmed a previous sighting of this individual as a match and the alphanumeric name was not shown.
What I am referring to is, like in the example I include in this link: Flukebook
, the match (WPA/PM-346 in this case) shows up without the alphanumeric name. In the example above, I confirmed the match, but then the alphanumeric name was given, which was not there before. Maybe you can test to see what happens with this example when it is matched, as I am not sure if I am explaining very well.
Should I hold off on confirming more matches while we wait to work out why this is happening?
Best wishes, Ruth
1 Like
Thanks for examples! You can still work on confirming matches, but leave these example links alone so we can test with them.
You should still be able to update the individual IDs from the marked individual page of any whales that arenāt displaying the correct ID.
Broadly, the issue is that Wildbook has the assigned individual ID saved correctly, but isnāt displaying it. Itās choosing to show the animalās UUID instead (the number in the marked individual page URL that uniquely identifies that animal in a Wildbook). We know the bug is related to projects, and it will likely take us a few more days to untangle.
Okay. Thank you for the update and advice.
