Deleting multiple encounters from bulk import

What Wildbook are you working in? Flukebook

Is there a feature yet to delete multiple encounters in batches, rather than deleting one by one? We filter as out as many images as we can prior to bulk import but end up with many photos of the same individual after the matching process and would like to delete these at the end, to produce a clean ‘processed’ folder with just the best photos of each individual from a range of aspects. So far I’ve preferred uploading the extra photos during the bulk import since Flukebook is good at detection, particularly when there are multiple individuals in a photo. It also saves lots of time not manually cropping. But the result is a lot of photos needing to be uploaded, some of which are the same individuals, and ideally they would be subsequently deleted. I would be curious to hear how others do it, when they have large numbers of photos from a large group of animals to process. I’m aware of the Wild Ex app to export images but feel it would be good practise to remove unnecessary photos (post-processing) from the Flukebook platform.

Also, does RWildbook work on Flukebook. I’m getting errors trying to export anything.

Many thanks,

Gemma

What is the entire URL out of the browser, exactly where the error occurred?

Can you describe what the issue is you’re experiencing?

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

Not yet, but it’s a good candidate for a feature request! This is a question that comes up with some frequency, but surprisingly hasn’t been officially put in as a feature request.

This sounds like a good question to post to the community as a topic in the Community Research category of the forum.

RWildbook is an open-source project from Simon Bonner, so he’d be in the best position to reach out to for any troubleshooting with it. His contact info is in the PDF at the link. I do want to call out the Flukebook is due for its upgrade to Wildbook 10.6.0 this Thursday and that the new React pages in the newer version of Wildbook may not play nicely with RWildbook.