You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
michaelpirrello
changed the title
Incoporation of iNat based customcoms into bot commands
Incorporation of iNat based customcoms into bot commands
Aug 26, 2020
I'm going to cover ,topids and ,topobs in this bug. please file a separate one for ,maverick, as that's something entirely different, where individual identifications should be output, something we don't even have a display for yet.
The ,topobs customcom produces a URL from the taxon id argument like this:
My idea is that these two are both best implemented as ,tab displays, where per observer and per identifier (different lists of iNat user ids, with numbers beside them) are the tabulated rows. We'd probably want abbreviations for these: per user and per ider, respectively (where user elsewhere in bot displays is already used to describe "the observer", e.g. in ,tab <taxon> by me).
So, for example:
,tab cuckoo bees from ns per user
Output should be like ,tab cuckoo bees from ns by me, except:
the people listed don't have to be registered to the bot as members of the server
no reaction buttons are provided to add/remove anyone
the list could be rather long, so output would be paged if some reasonable maximum is exceeded
the title would be "Observations of Subfamily Nomadinae (Cuckoo Bees) from Nova Scotia, CA per observer", which would be a link to the URL that the ,topobs customcom currently produces
,tab cuckoo bees from ns per ider
Just like the first example, except "per identifier" in the title & URL, and in the listed users in the table.
As discussed, migrate
customcoms into Dronefly commands
The text was updated successfully, but these errors were encountered: