We need to make sure that any subgenera are properly parsed by the app, especially when it comes to novel taxa.
NHMD Entomology has several taxa with a subgenus, but only three are marked with parentheses around the subgenus name.
In order to infer the rank of a novel taxon that has a subgenus, the presence of parentheses are currently used. I.e. the digitizer needs to put the subgenus name in parentheses.
The question is whether we should:
Stick to this convention
Have the subgenera in Specify updated accordingly, i.e. add parentheses around the subgenus name
It's hard to find a good example but as a general rule, I think the following should be the status:
In the Specify database, subgenus (atomic) names are recorded without brackets
On the Specify app(s), as part of binomial names, subgenus names should be displayedwith brackets
In our app's taxon spine, subgenus names should either be recorded with brackets, or in any cases displayed with brackets
a. The fullname field should show the bracketed subgenus
b. The name field of a subgenus should hold the atomic name
During post-processing, subgenus names should be placed in their own column and any brackets removed
We need to make sure that any subgenera are properly parsed by the app, especially when it comes to novel taxa.
NHMD Entomology has several taxa with a subgenus, but only three are marked with parentheses around the subgenus name.
In order to infer the rank of a novel taxon that has a subgenus, the presence of parentheses are currently used. I.e. the digitizer needs to put the subgenus name in parentheses.
The question is whether we should: