Hi, thanks for sharing this bug. This does seem related to the new assigner, specifically the assigner in conjunction with the bulk uploader. We are investigating this now and will keep you updated.
Thanks,
Drew
Hi, thanks for sharing this bug. This does seem related to the new assigner, specifically the assigner in conjunction with the bulk uploader. We are investigating this now and will keep you updated.
Thanks,
Drew
Awesome, thanks Drew! I’ll keep reviewing the uploads and will let you know if I see anything else that doesn’t look right. So far, this is the only problem I’ve seen. I’ll try to run more matches too; haven’t done many of those yet.
cheers
Maureen
Could you share the excel sheet that generated https://africancarnivore.wildbook.org/occurrence.jsp?number=BPC_OvrvwWtd_Fldr161_2020_3_24 please? Either here or via email. No need to include the images for now. Thank you!
Hi @Drew, I’ve just emailed it to you. Let me know if there’s anything else I can do or send.
thanks!
M
Received, thank you. One last question for now: are you pressing the ‘send to detection (no identification)’ or the ‘send to identification’ button at the end of your bulk upload process?
Good question - for all bulk imports, we use the ‘send to detection (no identification)’ option ALWAYS.
thanks!
M
(bookkeeping: tracking under WB-1360 and WB-1381, resume ignoring me)
I’ve been making progress on this but am not done yet. The issue in your original comment should be resolved but I am still looking into those described in your second longer comment, so no need to do further testing until I’ve addressed that as well. Thanks for all the information and links, and you can expect another update tomorrow.
Thanks Maureen! That does sound super similar, whether it’s just the same symptom or the same cause I am not sure. I did wonder if you had pressed the button twice, so it’s good to hear that’s not the case. I’ll keep you updated as I deduplicate the data today, and hopefully prevent this from happening again.
Hi again @ACWadmin1,
These data issues should now be fixed and you should proceed with more using/testing of the platform! Keep your ear to the ground though, and I’ll keep this ticket open because there’s still one issue we don’t understand.
So we will be monitoring this issue. I’ve built scripts to clean up these scenarios and can clean your data more quickly if we see either again. Meanwhile we are tracking the detection-duplications and will work on preventing those in the future.
Thank you SO much for your patience and detailed notes!
-Drew
@Drew - you just MADE MY WEEK!!! This is awesome. It seemed crazy complicated to me and I really didn’t expect a fix as quick as this. My lack of faith is NOT a reflection on you, just that technology sometimes hates me so I expect things like this to be weird and hard to resolve. Although I’m sure it wasn’t a cake walk.
We’ll keep our eyes peeled for any other signs of problems and keep you posted.
thank you again SO MUCH! And have a wonderful weekend.
best regards,
Maureen