Issue with naming new individuals - new names not registering

Bug Reports
, ,
1

In which Wildbook did the issue occur? Flukebook

What operating system were you using? (eg. MacOS 10.15.3) MacOS 14.8.1

What web browser were you using? (eg. Chrome 79) Chrome

What is your role on the site? (admin, researcher, etc)

What happened? I am going through the matches of individuals on this bottlenose dolphin bulk import: https://www.flukebook.org/react/bulk-import-task?id=b5d335ea-dddb-4376-9e3b-9c0d24e972bb. When I am confirming that there are no matches and making a new individual this works. But when I then try to assign the same individual number to a different photo in the same bulk import (so another photo of the same individual within my bulk import) on its encounter page (such as this one: Flukebook) under Edit identity and ‘Add to existing individual ID’ the new individual ID which i just created does not appear. I am having this issue with multiple IDs, specifically with CCS_Tt_0398,CCS_Tt_0399 and CCS_Tt_0400

What did you expect to happen? For the new individual ID to register so that I can assign it to other pictures.

What are some steps we could take to reproduce the issue?

2

It sounds like there may be a lag between when the new individual is created from the match page and how soon it appears as an existing individual when you try to assign the ID to an a different unidentified encounter shortly afterward.

Does it help when you refresh the encounter you’re trying to manually assign the existing ID to? Sometimes refreshing the page you’re working on helps if the ID was just assigned in another open tab.

3

Hey Anastasia. I tried this, time does not seem to fix it. However, it does work when I assign the new individual on the encounter page, rather than on the identification page!

1 Like
4

I’m glad you have a workaround in the meantime! I’ll work on trying to replicate this on my end. I’ll let you know if I need additional info.

5

Thanks for your patience. I was able to replicate this in testing. I’ll work a ticket for this and post the link here when it’s ready.

6