Send batch of historically unidentified to re-ID

[CourtneyMarne]

What Wildbook should this feature be in? GiraffeSpotter / all

What would you like to see? Send all currently unidentified encounters from a location/time filter to ID again. Maybe this is already possible but I’m not sure how to do this most efficiently?

How would this functionality help you? ID older data based on newer data information.

If requesting a new location ID, include

• Is this is nested beneath another location in the hierarchy?
• Is there a prefix for region-based naming? (optional)
• GPS coordinates in decimal format (optional)

Note: Not all feature requests can be accepted, but all of them are reviewed by our product team. We’re unable to provide implementation timelines for accepted requests. We are a small team with many competing priorities. Thanks for your understanding!

[Anastasia]

Hi @CourtneyMarne

I think this might be something we roll into a Projects update. There have been similar requests for taking bulk actions on a set of encounters before; I’ll write up a ticket for this soon and post it here when it’s ready.

Resend many encounters to identification at once

Hi, I am working in the ARW. I want to resend a bunch of encounters from one of our projects to identification amd start new matches for them. Those were only matched with hotspotter before, about two years ago, and i hope to find more recaptures by rerunning the matching with mewID. I know how to start new matches manually, over the encounter page but I was wondering whether there is a way to send all of them at once (around 1,000) or at least send them in packages of 100 encounters. It would …

Batch delete multiple encounters

What Wildbook should this feature be in? Flukebook What would you like to see? It would be useful to have a way following matching, to delete multiple encounters easily, so that we can keep only the best images of each individual from various aspects on the platform. It would be useful if this could be filtered by sighting/occurrence ID as well as by bulk import if possible. The former is useful, because sometimes bulk imports are split by photographer or something else, but still represent th…

[Anastasia]

I forgot to mention, if there’s a Classic search result you want to link to where we can re-run the unidentified encounters for you in the meantime, let us know and we can help with that.

[CourtneyMarne]

Thank you @Anastasia , if you could please run this search term (2016-2018) through re-ID for all Luangwa (Zambia) that would be great! Through Hotspotter specifically please

https://giraffespotter.org/encounters/searchResults.jsp?locationCodeField=Luangwa&locationCodeField=North+Luangwa+National+Park&locationCodeField=Luambe+National+Park&locationCodeField=South+Luangwa+National+Park&locationCodeField=Lower+Luangwa+Valley&datepicker1=2016-01-01&datepicker2=2018-12-31&male=male&female=female&unknown=unknown&alive=alive&dead=dead&numSearchedObs=1&lifeStageField=None&patterningCodeField=None&label0=None&numResights=1&unassigned=true&satelliteTagName=None&biomeasurement13C(operator)=gteq&biomeasurement15N(operator)=gteq&biomeasurement34S(operator)=gteq&organizationId=None&projectId=None&submitSearch=Search+Encounters

[Anastasia]

Thanks! Will let you know when these are ready.

Here’s the placeholder ticket in the meantime: Projects - Take action on multiple encounters at once · Issue #1578 · WildMeOrg/Wildbook · GitHub

[Anastasia]

BTW, sending 3400 encounters to Hotspotter will massively slow down the GiraffeSpotter queue. It may be more efficient to resend the encounters to ID as you work on them. Giraffespoter is currently slowly working through a large backlog of Hotspotter ID jobs right now that’s been going since the weekend. We can wait until the current queue is back down and put these through, but it will cause a similar backup. Let me know how you want to proceed.

Also, this will be less of an issue with the new 10.10 update because Hotspotter and and MiewID will have separate pipelines that won’t compete with each other for resources. It won’t make Hotspotter any faster (there’s an upper limit to how fast it can perform), but it will make MiewID and detections faster overall.

[CourtneyMarne]

Thanks @Anastasia, I wasn’t aware that the recent big bulk import was sent to HotSpotter and not MiewID

Please send this request to MiewID, and any remaining unidentifiable can be sent to HotSpotter manually thereafter.

[Anastasia]

We’ve re-sent these encounters back through MiewID today as the queue was nice and quiet. Thanks for your patience!