missing genus hybrid indicator about ghini.desktop

[mfrasca]

From @RoDuth on December 9, 2015 12:52

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?)

[mfrasca]

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.

[mfrasca]

@RoDuth : still a lot missing.
take as example ×_Brassocattleya_

1. when we import the genus.txt data, this includes a leading x (the 24th letter of the alphabet, not the multiplication sign, separated from the taxon epithet by a space).
   this leading x is not interpreted when importing the data, it's left there as part of the epithet.
2. when we set the nothotaxon property (set the hybrid marker to ×), this is not reflected in the epithet computation. same for graft chimera.
3. should the genus epithet be italicized?