The upgrade may have fixed this, or this may have been the result of some interruption in data between the back end and front end. I am not quite sure. I will mark this as resolved, but please feel free to re-open if you experience this again.
The issue is part of the interplay between Wildbook and WBIA. In this case, the user selected to match against their data and Botswana. On the Wildbook side, that matches 0 encounters. So technically, there is nothing to match against.
Wildbook sends that to WBIA, and WBIA defaults to “well then if you don’t specify anything, I’ll match against everything”.
WBIA returns the superset of all potential matches (including old annotations that were deleted in WIldbook long ago), and Wildbook displays them, but it also looks at each matched annotation and says “does this still exist in Wildbook” and removes matches that are non-existent. Thus the three potentially matched annotations from WBIA disappear leaving an empty set.
So while we’re discussing internally whether WBIA should change its behavior when it is not given a set to match against or whether Wildbook should intercept and report back fast that “nothing matched your criteria”, the empty results you’re seeing are still valid: there are no matches from that User’s personal data and from Botswana (in combination). A message to that effect from us would be polite though!
@brmscheiner@colin@parham Good food for thought on how Codex/WBIA should behave when the user selects a match-against criteria set that has 0 things to actually match against.
