Presentation of Match results by sighting - problem on large sightings

[PaulK]

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? When returning match results - even those kicked off by Sighting - the system is freezing when going into an individual Encounter to view results because all of the results are being presented - not just the ones for that Encounter

What did you expect to happen? Regardless of how the Matching is kicked off - present results only by Encounter.

What are some steps we could take to reproduce the issue? See the Sighting referenced in the screenshot here;

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

[jason]

Can you please provide the direct link to the results from the first screen shot?

[PaulK]

https://africancarnivore.wildbook.org/occurrence.jsp?number=Census_08-09_2.CHEETAH_Original_1_AnnaVenter

This sighting is a good example.

Thanks

Paul

[jason]

Here is the example link I was looking for:

https://africancarnivore.wildbook.org/iaResults.jsp?taskId=0ad206d9-a218-4539-b997-4551e035a021

This is one of the large batch ID jobs kicked off from Bulk Import (I think). It’s a massive data pull and a lot of JavaScript execution. Chrome seems to load fine and then eventually chokes on the amount of computations needed (and I’m running it on a very powerful laptop). Though slow, Firefox handled it elegantly with the rollover display functional but sluggish.

We are redesigning this interface for the next generation of Wildbook, and we can test with large results like this. For now, the workaround is to switch to Firefox for large results like these.