Can't select individual IDs that existed before the Wildbook update

Bug Reports
, ,
1

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

Wildbook: Internet of Turtles

Operating system: Windows 10

Browser: Chrome v144

Role: Researcher

What happened?

When I try to assign an ID that existed before the Wildbook update to a new encounter, the only selectable IDs are new ones that were created since the update. If I type the correct ID, it creates a separate new ID with the same name as the existing one

What did you expect to happen?

I expected to be able to select IDs that existed before the Wildbook update

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

Try to add an individual ID to an encounter with no assigned ID. Only a small number of IDs are selectable

Individual ID dropdown does not include all our marked individuals
2

Hi @Patrick

Thanks for letting us know. I’ll let you know as soon as I have an update on this.

3

Here’s the ticket for this issue: IoT not suggesting existing individual IDs after 10.9.2 update · Issue #1394 · WildMeOrg/Wildbook · GitHub

4

@Patrick Can you share some individual IDs that this is happening with so I can pass it along to the devs for testing?

5

@Anastasia, an example is encounter ID: 971cd0ba-f2bc-4f77-907e-cbdab94c488b.

This turtle was added to IoT in October 2025, but I recently matched it manually to a more recent encounter (ID: a77e0a94-c300-4fff-ae32-15e4a2e3d451). I tried to assign the correct ID (OKI-0318_Gr), but I can only select the most recent new IDs. When I type the correct ID, it creates a new ID with the same name that is not linked to the other sightings.

I can add an ID by clicking on it in the match results page, but I can’t add it via the encounter page

1 Like
6

Great, thanks!

7

I saw the same behavior in IoT but didn’t recognize what was going on at the time. I’ve since resolved it (I think) and do not recall which ID it was.

8

@GoBeach I think we’ve figured out what’s behind it, but feel free to keep sharing examples so I can add them to the ticket while we work on this.

9

@Patrick @GoBeach This looks be be patched now. I’ve tested a few examples and it looks to be working correctly now. Can you both check and verify on your side as well?

10

@Anastasia, I’ve tried it on a few encounters and it looks good to me. Thanks for your help :+1:

1 Like