Name: Evan Pioneer Valley south, MA, USA (Zone 6a)
Re: listed names. As these link to a specific Parent Plant and the sci. name may not be known by the searcher, should both common and sci. names be noted. At least in some instances.
ex. Elephant Ears can be Colocasia, Alocasia, Xanthosoma, Caladium, ... I didn't understand the distinction early on.
Another example, due to unfamiliarity with the common name, might be American Wood Lilies/Trillium. Are there other examples?
I get what you're saying, Evan. The Parent Plants list has the common name of the plant first followed by the botanical name. So I think the common names are showing up in the Custom List area if the plant has one listed. Does that make sense?
Some of these parent plants may cover more than just a genus.
Some may cover less than full genus, but rather a single species (like Hibiscus syriacus, for example).
Others cover multiple species within a single genus.
So adding the latin name after the common name isn't practical across the board. Having said that, however, we can make the names be whatever we want them to be on a case by case basis. So if there are certain ones that you want me to read "Common (Genus)" or "Genus: Common" or whatever, we can do that. But it wouldn't apply automatically across the board. But I think that flexibility is actually a good thing.
(Agastache) after Anise Hyssops
(Nerine) after Cape Lily
(Alyogyne) after Australian Mallows
(Lycoris) after Surprise Lilies
(Opuntia) after Prickly Pears
(Hymeocallis) after Spider Lilies
If that isn't too much trouble and if those will fit. I'm not great on the technology end of things so I never know. If they don't fit, then those are the botanical names that should appear in the List rather than their common names.
That's good to know. Does the Custom Plant List have room for both common and botanical names or just one or the other?
If they don't fit, then those are the botanical names that should appear in the List rather than their common names.
