Ben Armstrong

This is something that will be more important as we build out support for matching multiple observations instead of returning a single result.

This is partially supported via `opt without_taxon_id=#` (and can take a comma-delimited list of id#s). I say *partially* because it is unwieldly for users to lookup and type the id...

Adding this to the query language as `not` rather than `without` clears up 2 separate issues: 1. We already use `with` for annotations. Using `without` for taxa would just cause...

Mockup of per species detail when ✅ is pressed with default 🔢 **tot** and first user **benarmstrong** selected:  -embed fromdata ``` {"color": 9498256, "description": "**Obs. comparison per species vs....

The resulting "Obs. comparison per species vs. ..." display in the mockup in the previous comment has two columns, one for the first user, and the other for "others" (since...

Parts of this issue are not easy at all to implement due to missing API endpoints to update the project rules. Therefore, over the past month, I have worked on...

The event members list should also include project members who *are not* known to the bot on this server. This has happened a couple of times and is hard to...

ee22e6827faeae18e8d22a9e3c978f124c2816af implements the idea in the previous comment

The last kind of discrepancy is if people reacted to the menu who aren't known to the bot. That is most likely because they haven't shared their profile yet and...

I changed my mind and am reopening this issue to implement the complete automation of project updates rather than only semi-automating it with the new event project support. My reasons...