If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
In which Wildbook did the issue occur?
What operating system were you using? (eg. MacOS 10.15.3)
Windows 11 Pro
What web browser were you using? (eg. Chrome 79)
Chrome
What is your role on the site? (admin, researcher, etc)
admin, researcher
What happened?
When naming a new individual that does not match to another on the system, the naming convention is not correct.
What did you expect to happen?
See example here. We should be able to have the ability to name the individual or give the individual the next name available for that location. Eg. OLJ123
What are some steps we could take to reproduce the issue?
Visit this link and click on the confirm no match.
It looks like the Location ID wasn’t enetered exactly as it appears in Wildbook. It was originally “OL JOGI”, but when I selected “Ol Jogi” from the dropdown menu and saved the change, it suggests the next ID in the series from the Identification section on the encounter:
The “A new individual will be created with the name null” message is a known bug that was fixed in later versions of Wildbook. When GiraffeSpotter gets updated to 10.3.0 or newer, the popup window will actually display the correct ID.
That sounds like WBIA got stuck retrieving match results. According to our Matching FAQ if that status doesn’t clear after the usual amount of ID time, then the match should be re-run.
I also went back to the bulk import this came from and see many of the ID statuses are suppressed, which according to our Bulk Import FAQ also points to something going wrong with ID. It’s not likely related to the location ID issue. Just some separate errors compounding on each other.
Jason would normally be the one to update these on the database level, but he is traveling for a conference this week. If you don’t mind waiting, I can ask him to do it when he returns. If you think it would be faster for you to change the locations manually instead of waiting, you can do that. Let me know.
It looks like WBIA’s been restarting itself throughout the morning due to the high number of folks using Hotspotter over MiewID for matches. We’ll keep an eye on it. But you might want to try matches again later when the queue activity dies down more.
Hello! The location IDs have been updated and this import was re-sent to WBIA after we cleared the WBIA cache.
GiraffeSpotter WBIA seemed overwhelmed by the requests and down overnight. I think some of the “OL JOGI” requests, since they didn’t match a location ID, were causing it to try to match against all locations. This created massive and slow HotSpotter caches, which themselves are problem-causers.
You all are the best! Thank you so much for your help with this!
One last question…sorry! Was the match just run against Ol Jogi or all northern Kenya locations? Don’t want to run it again and bug things up but we need it to look for potential matches across conservancies
I believe it was just for Ol Jogi. It looks like there are about 1100 pending jobs in the queue right now. You can re-send to the updated locations now or you can wait a bit for the queue to clear before resending. It’s up to you.
