Feature requests

[joknjokn]

Hi,

Here are some suggested features/additions/changes. Instead of creating a billion tickets, I guess this is easier.

Idea 1
Option 1.1: Link species name in i.e. the Database view to the corresponding "By Common Name" folder for easy access to files

Option 1.2: Link species names to a species profile-page with relevant stuff like:

• Window or shortcut to "By Common Name" folder
• External link to a google-search with the scientific name
• Link to "pro" information about the species, e.g. the GBIF.org species page
• Link to species page/search query in xeno-canto.org

Idea 2

• Remove "View"-word from the links in the top. I personally don't think they are needed.

Idea 3

• Simple descriptions below the buttons in Tools. It's not too obvious what they do (i.e. is "Shutdown" for shutting down the birdnet-service, or the whole RPi. What is the difference between the 5 restart options. I'm not even sure what Caddy is at the moment :P )

Idea 4

• Simple explanations under the settings options (especially the advanced settings). I.e. a brief mention of the different "full disk behaviors".

Idea 5

• Probably a tough one and maybe out of scope... Expose a (login protected) api for accessing the database of observations/extractions. This would allow someone (i.e. me) to create a supplement mobile-app (Flutter-based) for overview of observations (see spectrograms, play/save/share files, favorite/bookmarked observations) and management of multiple BirdNET-Pi's, for example through fixed ips/urls or by scanning for BirdNET-Pi's on the local network. Is it overkill? Not sure. Could make usability better in the field, and maybe more convenient experience if having a BirdNET-Pi in both your frontyard and backyard.

[mcguirepr89]

@joknjokn Sorry for the delayed reply. I'll try to cover everything.

Idea 1 -- linking recordings to database
1.1

This is something I will try to do

1.2

This is not something I will try to do, namely because I feel that BirdWeather does a better job of this than I would be able to create.

Idea 2 - Remove "View"-word from the links in the top. I personally don't think they are needed.

Agreed! And done ~~ this change is now in the forms branch

Idea 3 - Info in Tools

I'm reorganizing the Tools page to hopefully make that more clear. There will also be a very different "Manage Services" page (which itself is new). For what it is worth, you should never really need to use those, except "Restart ALL Services" since it does the best job. Also, caddy is the web-server that BirdNET-Pi uses :)

Idea 4 - Info in Settings

I all of this is super new, so I have just been building tools and services out to be sure that everything functions properly. I will be putting together accompanying documentation once I know what tools and services are working and worth keeping. I plan to have this documentation both with_in_ and with_out_ the local installation environment, meaning you should be able to know and find out what you need to know when using the software, but can also access that information outside of the installation, in the GitHub Wiki to be precise.

Idea 5 - access database through API (with TLS and Authentication)

This is doable and would be awesome! But I'm not super sure what all you would need. I can help with creating options to open the mariadb port 3306 and can add TLS through caddy proxying (and can add BasicAuth to that proxy for authentication), but I've not worked with tokens much before (if that's what APIs like most), but can work well with keys if that is of any help??? @CaiusX has tinkered a bit with accessing the database to grab statistics and run queries, so he may have some insight into the needs there?

Thanks for the great ideas and requests! Keep them coming!
My best regards,
Patrick