kazlauskis
commented
1 year ago We can mandate the stage field, but with the current setup we can't do this for the whole species list, only per species group. Various species groups already have attributes that are based on species-specific iRecord forms, like bryophytes and dragonflies, which have their own stage-specific attributes (e.g. "exuviae-count", "bulbil-true/false"). We could remove these and add a single mandatory stage field, though.
Unlike the website, the app doesn't contain the full taxa hierarchy, it's only a flat list of species with an informal group ID attached. The app's dynamic species attributes that are based on informal groups so far were OK, but I feel that this setup is[ pushed to its limits when a new attribute needs to be added to species from different groups.
To re-build a new species dictionary with a different structure and rework how the dynamic attributes work so that we could add attributes for certain branches of the taxonomic hierarchy will be a substantial task. So maybe, for now, we can continue doing this per species group. What do you think? Can you specify which groups we should mandate the stage field?
This is relevant to this issue.
kitenetter
DavidRoy
Most of the requests for this come from verifiers of butterfly and moth records, although it also applies to other insect groups. When adding individual records it is currently possible to submit a record without filling in a stage term. The stage term should be mandatory (although it can be set to "not recorded").
The stage term is already mandatory for the moth survey mode, but not for individual records.
On the main forms on the iRecord website we have made the stage term mandatory for all taxon groups (not just insects), and I don't see a problem with doing likewise in the app.