Can you describe what the issue is you’re experiencing?
The page seems to be stuck at running match results at “40 individual computer vision tasks complete of 398 total.” I tried re-sending to identification and it restarted running match results, but then would again not proceed after 40.
Can you provide steps on how to reproduce what you’re experiencing?
I sent in a bulk import and after the photo and spreadsheet upload steps, I sent the images to identification matching against “Pahole” location. It got stuck at 40, so I resent the images to identification matching against “Pahole,” but it is still stuck. I also went back to some older “unassigned” encounters and noticed that those images also say “Still waiting for detection. Refresh to see updates.”
Snail Wildbook (and other WIldbooks that were converted from Codex) were a bit different in that their previous location IDs need to be entered differently in your spreadsheet. For example, instead of entering “Pahole” under Encounter.locationID, it’s expecting to see “fbcf00b0-630d-40fd-a6ec-fd17516edd1b” in that field. Right now, it doesn’t recognize the location ID as entered, so it can’t begin the identification process.
I’m not sure of the background behind that decision, but I believe we can change it so that it’s more user-friendly. Let me get back to you in the morning with an update.
In the meantime, you’ll want to update the Encounter.submitterID field of your spreadsheet to add your Snail Wildbook username here. Without it, only an admin user will be able to confirm matches on those encounters.
Thanks for your patience. The location IDs have been updated so that it will now accept the name as it appears in the drop-down menu in the spreadsheet.
It looks like you’ve already deleted this import, so you can upload your spreadsheet again and should be able to run your encounters through detection without issue.
Just to clarify, are all the encounters that were migrated over from Codex still under these location ID names we gave (i.e., “Pahole,” “Makaleha”)? And therefore the new uploads will match against these location names? Or were they reassigned the other ID like the “fbcf00b0-630d-40fd-a6ec-fd17516edd1b” during migration?
Codex used UUIDs internally, and they were just transferred as such to Wildbook.
We’ve just updated the code so that it now looks for the location ID as displayed instead of an internal UUID. Thanks for flagging this so we can clean this up for other Wildbooks that migrated from Codex.
