Encounter shows as "unassigned" in encounter table

Bug Reports
,
1

In which Wildbook did the issue occur? Seal Wildbook

What operating system were you using? Windows 10

What web browser were you using? Chrome 143.0.7499.193 (Official Build) (64-bit)

What is your role on the site? Researcher

What happened? I assigned IDs to all my encounters a couple of days ago, yet when I go to “My encounters” some of them appear as “Unassigned”. When I click on them and a sighting opens, only then “marked individual” column shows the individual ID.

What did you expect to happen? I expected that all individual IDs will appear in the “My encounters” table instead of “unassigned”

What are some steps we could take to reproduce the issue? Not sure in which cases this happens - I think I was going through the same matching process for all encounters. Screenshots of the issue attached

Unassigned
Unassigned1717×918 187 KB

Marked
Marked1793×939 84.5 KB

2

Hi @lstukonyte

Thanks for letting us know. This looks like a search caching issue. I’ll need a little more time to look into this. Thanks for your patience.

3

Quick update from the devs: there seems to be a bug that fails to re-index encounters that had their IDs assigned via the Confirm no match button on the match page. I went through all of your encounters and we’re working on manually re-indexing them.

The longer answer on a fix is that this will be addressed in the 10.10.0 version of Wildbook that’s currently in development.