Open michaelpirrello opened 4 years ago
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:
https://www.inaturalist.org/observations?place_id=any&taxon_id={0:query}&view=observers
The ,topids
customcom produces a URL from the taxon id argument like this:
https://www.inaturalist.org/observations?place_id=any&taxon_id={0:query}&view=identifiers
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:
,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