Skip to content

Wildbook not suggesting existing individual IDs after 10.9.2 update #1394

@goddesswarship

Description

@goddesswarship

Expected behavior
When a user enters an existing individual ID to manually assign an identity from the React Encounter page, Wildbook will auto-suggest the individual that matched the ID that was entered.

Current behavior
Since the 10.9.2 update, IoT , Flukebook, and Snail Wildbook isn't autofilling existing IDs in the Identity field of the React Encounter page.

Existing individual IDs that are typed in don't pop up as suggestions and instead create a duplicate individual.

QA notes
Current workaround appears to be using the Visual Matcher and selecting the correct individual from there.

User wants to assign it to 136_achmus_makw_2023 but the drop-down menu is prompting them to create a new individual instead:

Image

is of marked individual OKI-0318_Gr. User only sees the option to create it when they try to search for its ID in the encounter page:

Image

This individual (1429) is not suggested as an existing ID that can be assigned to the encounter.

This is individual 6026. It is not suggested as an existing ID that can be assigned to the encounter.

Image

Community link
https://community.wildme.org/t/cant-select-individual-ids-that-existed-before-the-wildbook-update/5384
https://community.wildme.org/t/known-individual-not-showing-up-in-id-list/5436
https://community.wildme.org/t/known-id-not-appearing-while-assigning-new-encounters/5583

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugsomething's broken!

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions