Encounters intermittently missing from Encounter Annotation Export

In which Wildbook did the issue occur? Flukebook

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

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

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

Hi, we’re seeing encounters drop in and out of encounter search results and the Encounter Annotation Export between exports a day apart.

  • Sighting: S_MTY_20260615_5, submitted by user lpallin, in project BTBEL.

  • The affected encounters are all ones whose individual was merged into an individual from another sighting (created by me, user=sbent).

  • The encounters open normally, are approved, and are in the BTBEL project, but don’t appear in an encounter search for 2026 or in an sighting search for that sighting.

  • Example encounters: 5810018e-9e02-4953-84fd-2d5fffbda69c, 724d00a1-db20-49a0-b21b-bbd560f3f085, 07a98e2d-579f-42c3-a85c-893f6e0ade7f, 0def6184-6223-4d43-bfa3-231b8992e315

  • On 10/11 all of them exported normally; since then the set present in each export has changed (11 reappeared on 10/22, 10 dropped out on 10/23).

We are wondering if merging individuals across users is affecting search indexing?

Hi @sbent

Can you let me know which encounter search you’re using? Is this happening with the Classic encounter search or the standard encounter search?

Hi Anastasia, I’m using the standard encounter search

Thanks for confirming! We do have a couple of tickets that are going to be part of the upcoming Wildbook 11.0 update that will improve opensearch indexing in the standard encounter search and reduce these kinds of discrepancies.

I know one of the issues related to individual indexing, such as recently assigned individuals still appearing as unassigned in search results but had IDs on the encounter pages. It makes sense the recently merged individuals are having a similar indexing issue.

We hope to have 11.0 ready in early November.

Ok thank you!

1 Like