Bulk uploads (sharkbook) not progressing

Sarah_Aus_SpotaShark · April 8, 2025, 12:15pm

The following bulk uploads are stuck and not automating the annotations for a few days now. Can you please look into them?

https://www.sharkbook.ai/import.jsp?taskId=e46cf6ff-d62c-4c42-a43f-d9ae7aee083b
https://www.sharkbook.ai/import.jsp?taskId=a2f9975d-8284-4a66-a5c1-0fa8f3b1f5f4

Anastasia · April 8, 2025, 4:29pm

Hi @Sarah_Aus_SpotaShark

None of these imports appear to have been sent to detection yet. They’re not stuck; they were never started

Screenshot 2025-04-08 at 9.27.31 AM

Sarah_Aus_SpotaShark · April 9, 2025, 9:52am

Hi Anastasia - bit confused, is this a step I need to do?

Anastasia · April 9, 2025, 4:28pm

Yes, users need to click on the Send to detection button at the bottom of the import table in order for detection to start.

Sarah_Aus_SpotaShark · April 11, 2025, 1:26pm

Hi Anastasia

I have never had to do this before, and so I tried for one of the uploads and it seems to have created errors for all the photos that were included (they were previously fine, but now when you go into each encounter the photos have disappeared and just shows a thumbnail without a shark image).
https://www.sharkbook.ai/import.jsp?taskId=e46cf6ff-d62c-4c42-a43f-d9ae7aee083b
This is a problem for me as I don’t want to continue sending bulk uploads to detection if it then disrupts all the images in the batch.

Can you please reload this batch upload so that the photos load correctly again, and can you please help me send the items to detection? I am worried that it will cause a bug for all the imports (you may have noticed I had spent a whole weekend and many hours uploading lots of images)

Thanks
Sarah

Anastasia · April 11, 2025, 7:04pm

Hi @Sarah_Aus_SpotaShark

Requiring users to kick off bulk import detection has been in place for a couple of years now, but there was definitely a point in the past where upload a bulk import meant that detection and identification were automatically started. We moved away from that to alleviate backlog issues in the bulk import process when Hotspotter was the norm across Wildbook.

For this import you linked to, if you scroll to the bottom of the import table, it’ll let you know if there’s a problem with any of your images. In this case, it’s flagged two of them as being corrupted:

When there’s a problem with an image during detection, it stops detection from completing. In this case, id’s recommend deleting the image from these encounters and it should allow the rest of the encounters in the import to complete detection. Corruption can occur during upload and may not necessarily mean the file itself is damaged. I’d recommend letting detection complete and starting ID on the import before going back in to manually upload the image on the encounter and see if that helps. If not, then the issue is with the image file itself.

These are the encounters:

Sarah_Aus_SpotaShark · April 12, 2025, 8:50am

Hi Anastasia

Im just trying to understand this one, because the bulk upload prevents you uploading corrupt images. So why would detection then find issues? It would be helpful to understand what causes it to try and work out how to prevent these from upload. I also would love a way of knowing which image was not uploaded (visually rather than file name, so that I can just do a screenshot or something to easily retry). Any way you can help with that?

Im working through the rest and it seems to now work - so thanks! Just would be good to understand how to prevent this in the future.

Thanks

Anastasia · April 14, 2025, 6:52pm

Currently, there is no validation in bulk import for corrupt images. Sometimes, the image itself is fine, but becomes corrupted during the file transfer for an unknown reason.

That’s the catch; if the image is corrupted (either before or after it was uploaded), Wildbook can’t show you a preview of it. Your best bet is to search the filename in the image folder it was uploaded from to view it and either screencap it and upload the screenshot, or just try uploading the image again in case it was an errant issue during the transfer that caused it.

For what it’s worth, The Wildbook 10.8.0 release will focus on long-overdue improvements to the bulk import process, including field validation. The goal is for the most common bulk import issues to get flagged early so users can fix them on their own, before the import is committed.