[ARW] Help needed with new Bulk Import Interface

What Wildbook are you working in?
Amphibian and Reptile Wildbook
What is the entire URL out of the browser, exactly where the error occurred?
https://amphibian-reptile.wildbook.org/react/bulk-import-task?id=25047d9e-c530-4093-9eb8-6ed0a8b0304b
Can you describe what the issue is you’re experiencing?

Hi,
I’m using the new bulk import feature in the ARW. Accidentally, I used “KF” instead of “Kottenforst” as location ID but apparently it should be possible to update the location ID in the bulk import now. Where can I do that?
THE UI looks like this for me:

and I can’t find the option to change anything with the bulk import encounters.

Secondly, I can’t seem to send the encounters to identification (see screenshot). Perhaps, this is related to the problem with the location ID?

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

Hi @Max.Muehlenhaupt

I went ahead and fixed the locationID in the database. Would you like me to send these on to bulk ID?

We will huddle Monday and try to recreate your jourey through the new UI.

Thank you,
Jason

1 Like

Hi @Max.Muehlenhaupt

I tested with your spreadsheet, and this is what I see in the new Bulk Import interface:

Note: I blurred username and GPS coordinates intentionally.

I am not able to submit with KF for the locationID, and the system is prompting me to fix it.

I am wondering if there might have been an old URL or cache issue. Did you see a screen similar to this one?

Thank you,
Jason

Hi Jason,
thanks for changing the locationID for me!
The screen that I see is still the one in my screenshot of my initial post. It doesn’t look like the screen that you are seeing.
I’m using firefox as my browser btw.

Also, I was checking other bulk imports of other users (I have admin rights) and the bulk import log page looks exactly like the one of my latest bulk import (see screenshot).

Hi @Max.Muehlenhaupt

When you were submitting, did the user interface look like the old one or like the one I posted above? I think your screenshot is from the end of that process.

Hi @Max.Muehlenhaupt!

After you upload your spreadsheet, you should see a review page that lets you edit any fields that looks like @jason’s screencap above. If that doesn’t look familiar, is it possible you accessed the bulk import workflow from your bookmarks instead of the Submit > Bulk Import menu?

Hi Jason, Hi Anastasia,

sorry for the misunderstanding from my side! The bulk import process did not look like the one from @jason 's screenshot but I do not have any screenshos from the process. It was my first bulk import after ~ 2 months.
I just started a new bulk import. This time, the interface looks like in Jason’s screenshot. I can tell that the interface is different because with this bulk import, I get the warning message that the max. number of uploaded photos cannot exceed 200. However, I have submitted 285 encounters in my initial bulk import :slight_smile:
For us fire salamander researchers, it is not unusual to upload more than 200 encounters/photos in one go, so perhaps this is something to consider, i.e., increasing the max. number of uploadable photos in a bulk import :slight_smile:

I would just run a new bulk import and delete the old one if that’s ok?
Perhaps, I just started the initial bulk import during the transition of the system to the new version?

No worries! From our side, the issues you described could only appear from the previous bulk import workflow so we were just trying to understand how you got there. ARW was updated the first week of August. I think the likely explanation was that your browser loaded a cached version of the bulk import submission page instead of the latest version.

Feel free to delete the previous import and try again.

Regarding the maximum number of uploaded encounters, that has always been the recommended guidance because bigger imports will increase wait times for detection and identification for all users of a Wildbook, not just the person uploading the import.

In the past, users have slowed down Wildbooks with imports containing thousands of encounters. This new version of bulk import is helping us enforce those limits to keep the site usable for everyone.

1 Like

Quick update: we’ve increased the limit to 400 in ARW. You may need to do a hard refresh in your browser for the change to load.

1 Like

Alright, thank you!
I will delete the old bulk import and will inform you how the new bulk import is going.
Great, that we can import up to 400 encounters in one go!

1 Like

The bulk import seems to be working!
I noticed two things, though:
1.) The same problem as:

Germany is not recognized as a country in the bulk import sheet.

2.) Encounters between midnight and 01:00 a.m. make problems as the “0” in the Encounter.hour column is not recognized. For encounters with Encounter.hour = 0, I get this error message in the check-up:

I could work-around it, by changing the cell in excel as text and then changing the value to “00” but it would of course be easier if “0” would be recognized by itself. Interestingly, “1”, “2”, “3” do not seem to make problems.

Thanks, @Max.Muehlenhaupt!

We do have a ticket for the Encounter.country issue here: Encounter.country values not recognized in bulk import · Issue #1227 · WildMeOrg/Wildbook · GitHub

I need a little more time to look into the time reporting issue. I’ll follow up as soon as I ave an update.

It looks like 0 isn’t a supported entry for Encounter.hour. According to our bulk import help docs, only 1-24 are valid entries:

Are you also using Encounter.minutes? If an encounter happened at 12:05 AM, those columns in the spreadsheet should look like this:

Screenshot 2025-08-29 at 2.19.57 PM

Ah, alright. Got it. I will use “24” instead of “0” for encounters occurring at midnight. I’m also using the Encounter.minutes entry.

Interestingly, however, “00” seems also to be working instead of “24”.
I have several encounetrs after midnight, before 1 am with “00” as entry for Encounter.hour
https://amphibian-reptile.wildbook.org/react/bulk-import-task?id=db359737-2d90-4e50-9267-4b3892427d70

Thanks for following up! I’ve talked to the devs, who agree that the way you’re using 00 to represent midnight is accurate and we’re updating the help documentation to reflect that: https://github.com/WildMeOrg/wildbook-docs/pull/125

1 Like

The Encounter.country bug has been fixed. Germany is accepted as a valid entry now.

1 Like