Can you describe what the issue is you’re experiencing?
I am trying to merge an encounter that to the first match in the match candidates. When I click the box, and hit “Merge Individuals”, it goes to the page with the “loading components for merge. This may take a few minutes…” but it never resolves. Am I not waiting long enough? How long could this take, or is it stuck?
Can you provide steps on how to reproduce what you’re experiencing?
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
Good question! Depending on the number of records its updating, it could take a little while to complete.
I can test this in the morning when I’m back online if it’s still not behaving, but I recommend leaving that tab open for a few minutes and checking back later to see if it’s ready.
Can you let me know which browser you’re using so I can test if this is a browser-specific issue? For example, sometimes Firefox doesn’t play nice with Wildbooks. It worked for me in Brave and Chrome.
Alternatively, you can try clearing your browser’s cache and cookies and then try merging the individuals again. This often helps address loading issues.
I just cleared my cookies and cache (and also have a brand new laptop) but it still doesn’t work for me. But Christy just tried it on her computer and it merged in seconds. She double checked that she gave me edit permissions and she has, so it is strange that it doesn’t work for me.
So after merging our ‘new id’ 1331 to the historical ID 868, the Marked individual merge tool page, shows… Eubalaena glacialis#1331.
See photo of page. Also, we would hope that the ID # would be updated to reflect #868 in the matching table. Does this not happen? ?? Is it too much to hope that all 1331, encounters would be updated to be #868?? or do we have to merge each encounter separately?
Can you let me know which browser and OS you used when you tried? @clsims Let me know which browser and OS you used, as well. I wonder if it’s a potential bug that’s browser-specific.
For the rest, I think it might be best if we got on a call together to talk through this and the Historical Data issue. I want to get Jason on the call, too. Can you give me some times that work for you and I’ll schedule a meeting time that works for everyone?
@Anastasia@jwaite, I have Chrome, Version 117.0.5938.134. Janice and I should probably have the exact same as it is govt computer. Tomorrow I can let her log on to Flukebook from my computer and see if it makes a difference.
I can meet tomorrow 9-1030, or anytime after 11:15. Friday my schedule is clear.
I’m using a slightly different version of Chrome (Version 117.0.5938.149). But I just got a new laptop and it didn’t work on either. The last laptop was probably the same version as Christy’s. I’m free the same times as Christy.
It’s a little arbitrary, but it also helps prevent random bot behavior from spamming the forums.
Thanks for meeting with us today! Based on our discussion, this is likely a bug that we need more time to research and may need to bring in other teammates to help troubleshoot. We’ve temporarily reset @jwaite’s account password while we use it to test a fix. As soon as we’re done with that, we’ll help you update your password.
With the ongoing server outage the team has been focusing their efforts on getting WBIA back online, so I don’t have any updates on the merge issue yet. I’ll follow up on it once the outage is resolved.
Now that the WBIA outage is resolved, we should be able to continue investigating the bug that’s preventing @jwaite from merging individuals. I hope to have an update for you next week. Thank you for your patience.
It’s a little arbitrary, but it also helps prevent random bot behavior from spamming the forums.