If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
In which Wildbook did the issue occur? Flukebook
What operating system were you using? (eg. MacOS 10.15.3) Windows 11
What web browser were you using? (eg. Chrome 79) Crhome
What is your role on the site? (admin, researcher, etc) Admin
What happened? Now when you use the search bar for individuals, there is lots of redundancy since the UIUX update to Flukebook.
What did you expect to happen?
What are some steps we could take to reproduce the issue? Just search any known individual in the search window next to the login.
Hi @ShaneGero
Can you give me some specific examples of what you’re seeing? I wasn’t able to replicate this with the individuals I tested with.
Try searching the individual “Fingers” in the search bar. In the new UI its impossible to tell apart the dolphin, or the two different sperm whales from the Azores or Dominica. These are different catalogue numbers and encounters but now it only shows the nickname
It looks like the example we looked at for Fingers has been corrected.
The ticket I linked is resolved and should be more widely rolled out with the WIldbook 10.10.0 update.
Hi Anastasia, Thanks for this fix! I do think it still has the search problem is you use a catalogue number which is all numbers. Then it still finds that set of numbers in hashes
Thanks for the update, @ShaneGero. Can you give me an example to check out?
When I do the search above, it does find the sperm whale with that catalogue number, but first finds “6219” in what I think is the long “encounter” or “individual” hash.
1 Like
I suspect there may have been an unintended rollback. We’re actually waiting for the jobs queue in Flukebook to die down so we can apply the latest update, which would fix this. We’re hoping for this to get done today or tomorrow.
Quick update: Flukebook was upgraded to Wildbook 10.9.5. If you do a hard refresh in your browser (Cmd + R on Mac or Ctrl + R on PC) and then try searching for 6219 again, you won’t see results that include the individual’s UUID anymore.
