Closed synrg closed 4 years ago
To avoid cluttering the channel, if last
refers to a previous taxon
result that was made by the requesting user, it should by default replace the previous embed.
We went a different way with this, providing numerous subcommands of last
to give equivalent functionality. parent
is a completely different thing that belongs to a different issue. 2nd last
is a concept we discussed and don't want to support (i.e. too confusing / no demand for it).
Extend the query language to include a
last
qualifier to match the taxon of anyhttp{s}://{www.}inaturalist(.org|.ca)/observations/#
URL recently mentioned in channel. It could supportby [user]
to filter on the last observation mentioned by the specified Discord user (without @ so they're not pinged) ormy last
(equivalentlast by me
) to reference the requesting user's last observation mentioned. Finally, some qualifiers to skip over most recent would be good, e.g.[ordinal] last
to count backwards from current, e.g.2nd last
,my 2nd last
, ortheir
/by them
to skip requesting user's own. Perhaps if an ordinal is given, the actuallast
keyword could be optional. Support browsing higher in the taxonomy tree to link to an ancestor (e.g.[p]taxon last genus
would show the genus matching the last observation or,[p]taxon last parent
would show the immediate ancestor of the last observation). Again, the keywordlast
might be omitted if there is nothing in the query but a rank that is an ancestor of the last observation (instead of the usual "I don't understand"), e.g.[p]taxon family
where "of the last observation" is implied.Consider if
last
should include othertaxon
queries, e.g. someone types[p]taxon zono
to match Zonotrichia and then[p]taxon last parent
, or again with optionallast
understood by context,[p]taxon parent
to show its immediate ancestor to family Passerellidae (New World Sparrows).