-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intergeneric Hybrid flag at genus level #443
Comments
after all that work, you probably recall, on 1.1 and rewriting the hybrid logic, I realized that that same whole construction would apply to other ranks as well. that was one of the |
All we need is the flag, same as species. No need for all the logic, in fact I'd discourage it and it is not the same across all ranks. A note would be plenty to record the list of genera that comprise the the nothogenus, a dedicated field like the synonym list maybe. As you'll see from my comment in Bauble/bauble.classic#179 (comment) :
a nothogenus name is about any combination of the listed genera. e.g. a × Trisuloara hybrid is made up of any combination of Barkeria, Brassavola, Cattleya, Epidendrum, Laelia, Sophronitis. So a × Trisuloara hybrid may have taken many many generations and one example may be predominantly Laelia (e.g. by back crossing) while another may be predominantly Epidendrum and another may be an equal mix. It doesn't mater, the only thing that defines the Nothogenus is that some combination of the listed genera are in its heritage at some point. |
it's a good thing, having issues to solve. whenever I manage to convince a (bunch of) garden to finance the work, I have work to do! |
Search
genus where genus like 'x %'
returns several genera that start with a letter x (to represent the multiplication sign that should be there, as it is in species) followed by a single white-space before the epithet.example
Opinions and suggestions
Include the Intergeneric Hybrid Flag as described in ITF2 C.5
Similar to the species hybrid flag that already exists
The text was updated successfully, but these errors were encountered: