Management of local detected species

[alexbelgium]

Hi, when using the birdnet system one thing that I am interested in is not only accuracy of detections in a daily manner, but also keeping an accurate list of every species that were detected in the location I'm recording in.

Currently the species list is bimodal :

• Shown
• Excluded (disappear from the lists)

So any species not directly excluded is shown in a similar manner, whether it is a new species with 2 detections, a misidentified one with 2k observations due to model bias, or a very common bird.

In birdnet-pi, I had made a tool to specifically "validate" species by having a specific flag and visual icon, plus a species management tab

I was hoping to replicate this kind of feature in birdnet-go, but given validation already exists at the detection level it could be also an additional information used to verify the credibility of a species - therefore I was proposing feature #3405

I was wondering - this is very probably a question many of you have faced : so how do you manage the "putative" species in your list of observation ? In terms of identification, and in terms of verification ?

[birdnet-go-bot]

Automated message from birdnet-go support assistant.

I'm leaving this open for the community to share their workflows. I see you've already filed #3405 to track the UI feature request.

[tariquesani]

I would really like to have this tool, since you have already made it for BirdNET-Pi why not port it for BirdNET-Go? You can mostly vibe code it given the fact that you already know what exactly needs to be done.! Thank you :)

[alexbelgium]

Well, I started with a proposal for adapting the species list, but I didn’t want to include yet a whole new feature of species validation without making sure there is no alternatives that people are already using #3405

if indeed there is interest I’ll propose a feature although vide coding is the keyword there - as much as I learned bash and php, I don’t know svelte and go !

[birdnet-go-bot]

Automated message from birdnet-go support assistant.

I see there's a good discussion going on here. Since you're discussing a potential feature and asking for community input, this is exactly what the Discussions area is for.

I'll stay out of the way for now, but feel free to continue the conversation.