Closed mfrasca closed 8 years ago
ITF2 Intergeneric Hybrid Flag?? Yes please!
(I get a little concerned that your desire to "flatten" the data structure with "taxon" for family/genus/species is a fairly significant break from any off the botanic record systems I have seen over the years, but, as long as it is easy enough to get the data out in a ITF2/ABCD/etc. compatible format, e.g. for PlantSearch updates, I guess its no big deal?)
currently Genus.hybrid_marker
, the genus hybrid indicator, is computed from Genus.genus
:
if Genus.genus starts with x
or ×
, then it's ×
if Genus.genus starts with +
, then it's +
if Genus.genus contains a ×
then it's H
(after the above checks)
correspondingly, Genus.epithet
is computed removing any leading x
, ×
, +
.
these fields are available in reports, not in queries.
you can search for hybrid marker using the like
construct:
genus where genus.genus like '×%'
BIG FAT BUT
the data we use to initialize the database does not contain that leading ×
nor +
.
if you do put a leading ×
or +
, then you need to use it when matching the genus epithet.
the pull down completion logic does not consider the leading × as an optional character.
This issue was moved to Ghini/ghini.desktop#7
Brassocattleya and Dracuvallia should really have a »×« preceding the epithet. one more issue that would be solved if we represented family/genus/species as taxon.