Leading subspecies IDs should change the obs taxon like leading IDs of other ranks

Feature Requests
,
71

In a recently closed redundant thread @fffffffff mentioned “impossible to find a workaround”. I just wanted to point out that there is one that works in typical situations, flow is

  1. first id is broad category (eg, Lepidoptera)
  2. second id is subspecies (eg, Limenitis arthemis ssp. astyanax)
  3. After this, record stays in the “Lepidoptera” pile, as far as normal identifiers can see.

An inconvenient workaround for 3), mentioned above, is for the first id to be withdrawn.

A more convenient workaround, if there is no one on hand right away to offer a second subspecies id in agreement:

  1. third id can be something narrower within the identifier’s capability although not to subspecies (eg, Papilionoidea or Limenitis or something in between those).
  2. Usually, the record will now bounce out to the ssp pile for identification at “Needs ID” level
  3. Subspecies-capable identifier is now more likely to see it, and comes by to confirm = Profit!
1 Like