I’m using Windows 10 Enterprise (version 21H2) and Chrome version 109.0.5414.210
1 Like
I wasn’t able to replicate this in my end when testing across multiple imports. Can you email me your spreadsheet from your other import to review (services@wildme.org)? I still have a copy of Flukebook_MetadataImport_initialDataset_Batch2 to compare with.
Sent - let me know if you have any other questions
1 Like
I’m not seeing anything in the spreadsheet that might be contributing to it (such as if some IDs had a trailing space and other’s didn’t) but everything looks fine. I’m combining this with a similar bug report for African Carnivore Wildbook.
Since this bug isn’t likely to be fixed quickly, I’m going to recommend that you leave a single pair of duplicate individuals and you can manually resolve the remaining duplicate matches so that you can continue with your research. This way, there’s something for our devs to work from without leaving you stuck in your progress.
Hi Anastasia, I took a look to try to merge those duplicated individuals and was trying to do so following the ‘Merging individuals from the Individual Overview page’ instructions, but I don’t see ‘the 3-dot menu on the top right corner of the Individual’s page’. Do you know if this method is possible in Flukebook, and if so, how I do it? Thanks in advance!
That’s my fault; these instructions apparently are only relevant for Seal and Zebra Codex. I talked to Jason about this issue last week and it’s actually more widespread than we had anticipated as it’s affecting records in African Carnivore Wildbook, too. I hope to have an update on this one soon!
Thanks for the update. So to clarify, does that mean there isn’t a easy way to merge individuals manually within Flukebook in the meantime?
The short answer is in general, yes, but not for this specific issue.
I’ve only found this information about merging in Wildbooks from our docs:
I’ve discovered that two individuals in the system are the same animal. How do I merge them?
Move all encounters from one individual to the other. When the individual you don’t want to keep has no encounters associated with it anymore, it will automatically be removed from the system.
This is done from the Identity section on the Encounter page. When you edit it, there’s a Manage Identity section that lets you remove the individual it’s currently assigned to.
When you click on the Remove button, the section’s appearance changes and lets you change it to an existing individual.
However, given the issue with the duplicate marked individual names, I’m not confident this approach is helpful as it will show you both names in the menu and doesn’t allow you to open them in a new window to verify which is which.
I’ll let you know as soon as I have an update on this.
Thanks for the details Anastasia - but yes, that would be my concern as well, that it would be a finicky trial and error to try get all encounters moved over to the same individual. It would be quite tedious also, given that there are 20 or more encounters for the duplicate ID for several individuals. Do keep me posted on any updates/solutions
1 Like
Pardon the multiple posts, but I want to make sure all of the relevant threads get updated with this info:
I recently learned we can force a merge between individuals. I’ve added instructions on how to do it in our new Merge FAQ.
2 Likes
Updating this thread with the ticket link where we’re tracking this: Multiple pages for the same individual in Flukebook and ACW · Issue #285 · WildMeOrg/Wildbook · GitHub
Hi @CMKonrad
We’ve finally found the error that was causing duplicate individuals to be created during the bulk import process and have deployed a fix. We’re waiting for current jobs in Flukebook to complete before de-duplicating the data later this evening. I’ll follow up with more info when that’s done.
1 Like
@CMKonrad The bug has been fully fixed in Flukebook and all duplicate records have been merged. If you check the previous link you shared earlier that listed all duplicate individuals, it now shows one Marked Individual page per ID: Flukebook | Login
Thanks for your patience while we worked to resolve this.