In which Wildbook did the issue occur?
Deerspotter
What operating system were you using? (eg. MacOS 10.15.3)
Windows 11
What web browser were you using? (eg. Chrome 79)
Chrome Version 128.0.6613.120
What is your role on the site? (admin, researcher, etc)
Admin
What happened?
When I click on the link in the “Match Results by Class” column of the import task it opens a new window with results except there are no results there:
Problem is occurring with new import tasks as well as old import tasks that previously worked and has been like this for about a month.
What did you expect to happen?
I expected to there to be an image of the encounter interest and a series of other encounters scored in relation to the encounter of interest
What are some steps we could take to reproduce the issue?
Open an import task from the bulk import logs and click on the “Matched Results by Class” link. If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
Thank you! It looks like the Location ID was missing from the encounters, which means the Encounter.locationID field likely was missing from the spreadsheet. DeerSpotter determines match candidates based on species and location. If the location is missing, it doesn’t know where the deer should be matched.
Before you delete the import and update your spreadsheet, can you email me the current spreadsheet so I can verify if everything else looks good? services@wildme.org
Your spreadsheet’s all good; thanks for sending it! The bulk import workflow doesn’t always flag stuff that it should, so I like to take a look at the spreadsheet to rule out anything might contribute to odd behavior.
To answer your question about the map still pinning the correct location despite the missing location ID: that’s because you used coordinates to denote the location instead. There are 3 different ways to report a location in a bulk import and as long as at least one is included, it’s all good. I don’t see coordinates without a location ID too often, so that’s why I initially thought it was the culprit.
It looks like there was an exception WBIA (the image analysis pipeline) that’s the cause of the missing match results. We’re still working on it and will update you again as soon as we have a fix.
