Bulk import detection

Hello Anastasia,

I wanted to know if it would be possible for you to force the detection of two bulk imports. I have already tried deleting and re-uploading them, but the detection still doesn’t work. Similarly, I attempted to reduce the size of the photos and re-import the two bulk imports, but nothing is working. The two bulk imports in question are these:
• Pe.CrossingABC.20240828.2
• Pe.CrossingABC.20240829
I hope this is possible, and I thank you in advance.

Hi @rebeca

I mentioned this in a previous post, but can you start giving me direct links to the bulk imports you need me to look at? In addition, also send your spreadsheets to services@wildme.org any time you run into a bulk import issue. Following both of these steps will help me help you faster.

Thanks!

Here are the two links in question:
https://www.flukebook.org/import.jsp?taskId=ac15b127-7195-4ff4-bfd5-f2f90ceadd8b
https://www.flukebook.org/import.jsp?taskId=b314a099-0e0f-4bdb-980b-a259f03b96dc
I’ll e-mail you the excels right away.

Thank you very much for your help,

1 Like

Thank you!

I see that Encounter.locationID was entered as “Caribbean sea” instead of “Caribbean Sea”.

Because location IDs have to be entered in your spreadsheet exactly as they appear in Wildbook, this means that the encounters you have imported will only match against themselves if you leave it with the “S” in lowercase.

I also checked a few of the images from the encounters. In one example, a single image was 38MB and 9300 x 6300px, which is a very large file. Our Photography Guidelines help doc recommends that your maximum image size is 1600px or less.

Can you also double-check for the file extensions? In your spreadsheet, you have the media assets as “.JPG” but when I saved one, the file extension was “.jpeg”. According to our Bulk Import Cheat Sheet, your media asset file names must match exactly with how they appear on your computer.

Thank you very much Anastasia, I’ll take it all back and re-import it !

Sorry to bother you again Anastasia, but I had a new question following one of your comments. Indeed, some bulk were imported in the past with the location ID: “Caribbean sea” instead of “Caribbean Sea”. Is there a way to correct this quickly directly on flukebook without having to restart everything?

We were wondering whether the use of a lower-case “s” instead of a capital “S” posed a problem when comparing with other imported bulks?

Yes, location ID’s have to match exactly with how it’s coded in the site, so they’re case-sensitive. We hope to get total field validation in bulk import in the future so it will flag anything that will cause problems before you commit the spreadsheet. Right now, validation only works on a handful of fields so we occasionally see problems like this.

No, not from the user side. If you plan on re-sending all of those encounters to ID anyway to see updated matches for the correct location, then it would be better to delete the import and upload it again with the corrected location. Otherwise, if you’ve already reviewed those matches and just want to location correct so that it works correctly if matches need to be run again in the future, we can fix it on our side, but it may take a little while. Let me know!

Hello Anastasia, Thank goodness you’re here! After checking, this only concerns a few bulk imports, but they’re quite important and the matches have already been made. It would be fantastic if you could correct our error on the following bulks:

• Pc.Expe2024.2.2 : https://www.flukebook.org/import.jsp?taskId=9e20eba5-1fa9-49ff-a254-d9a0acc22e80
• Pe.Expe2024.2.1 : https://www.flukebook.org/import.jsp?taskId=eba15ad7-4bf1-4ae4-b5ff-7cbdb1ecec0b
• Pe.Expe2024.2.2 : https://www.flukebook.org/import.jsp?taskId=862b2965-8aba-4614-b2bd-fce9aa7a9459
• Gm.Expe2024.2.1 : https://www.flukebook.org/import.jsp?taskId=3c335684-af88-498e-bfe5-679f34e6e614
• Gm.Expe2024.2.2 : https://www.flukebook.org/import.jsp?taskId=d7f90e38-e4c4-4d7f-8f74-2d0047ae547b
• Gm.Expe2024.2.3 : https://www.flukebook.org/import.jsp?taskId=9142c592-aa79-4c77-abce-a38838b57fd4
•Gm.Expe2024.6 : https://www.flukebook.org/import.jsp?taskId=c2e3d305-e483-4d28-9b0d-8cde29118770

Thank you so much for your help!

Great; thanks! I’ll let you know as soon as these are ready.

All of the old encounters now appear under “Caribbean Sea”. Thanks for your patience!

Fantastic ! Thank you very much Anastasia!

1 Like

Hi Anastasia,

I’m really sorry but I’d like to come back to you regarding the two bulks imports mentioned in the past.
• Pe.CrossingABC.20240828.2 : https://www.flukebook.org/import.jsp?taskId=632a9da1-a1b3-493c-8eb5-878781121aee
• Pe.CrossingABC.20240829 : https://www.flukebook.org/import.jsp?taskId=4928591c-143a-43cc-a785-9b2372a37ce2
Indeed, despite the changes made, the detections don’t want to take place. Is it possible to force them?
I’ve also sent an e-mail to services@wildme.org to send you the excels associated with the bulks imports.

So sorry to bother you again with this. Thank you very much for everything.