In which Wildbook did the issue occur? ACW
What operating system were you using? (eg. MacOS 10.15.3) Win 10
What web browser were you using? (eg. Chrome 79) Chrome latest
What is your role on the site? (admin, researcher, etc) Admin
What happened? Running matching on multiple encounters in same MediaAsset, same encounter presented from Image despite kicking off matching for each encounter.
See video link here:
What did you expect to happen? The same encounter I kicked off matching for should be presented in the Match Results
What are some steps we could take to reproduce the issue?
See encounter https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=9a3f0d27-3f7a-4cfa-8271-faf81c6347ce
safeURL(request ): https://africancarnivore.wildbook.org/wildbook_data_dir/6/b/6b286f84-9674-4fa6-b076-e1733af23a1c/c452a8c6-3f8c-45c4-ad54-53219868cd54-master.jpg
Also happening on this MediaAsset & related encounters
Media Asset 25074
Thanks again for making video of this! Makes the problem much more understandable!
This does indeed seem to be some unexpected behavior.
Colin and I chatted briefly about this, and we have some suspicions regarding the problem.
It may have something to do with these all being manual annotations.
Can we ask:
- From which page was this job initiated?
- Have you tried re-running the ones where the match asset mismatches the media asset featured in the encounter page? If not yet, does that fix things?
Sorry about the delay.
Matching was kicked off from the unassigned encounter page
I have not tried rerunning these matches.
Having rerun the matching for these encounters I am now getting the correct encounter being returned as Target encounter - with or without matches being found.
Not sure I follow - is there still a problem, or are you getting expected behavior?
I checked out the encounter, and now I’m getting something similar to your video, but with a new wild dog (second from the left now). Which suggests to me that something is still a little weird? Is this what you’re seeing?
We’re on the same browser and version.
I thought I was getting expected behaviour.
Weird that you are now seeing an issue?
I tried again and got results consistent with your expected behavior. Checked with team, and they were fixing something at the time I tested. All good now! False alarm!
All good now? Resolved?
Thanks for the follow-up.
I think we can call this one closed.