I'm trying to implement plant classification as a custom taxonomy for a custom post type.
For now, plant classification should be on three levels:
As I see it, there are two possible ways:
Using taxonomy level as an indicator of taxonomy type, ex:
plant_class (custom taxonomy) '-- Rhamnaceae (level 1 = family) '-- Ziziphus (level 2 = genus) '-- Ziziphus Jujuba (level 3 = species)
- Correct structure; I'd be able to find the family name of a given genus.
- Administrator just selects a species to classify a plant.
- Cannot be extended later on (eg; to introduce sub-species)
- The per-level aspect looks too "magical" to me (unintuitive / confusing to beginners)
Putting each name under the classification type itself, ex:
plant_class (custom taxonomy) |-- Family (group of families) | '-- Rhamnaceae |-- Genus (group of geni) | '-- Ziziphus '-- Species (group of species) '-- Ziziphus Jujuba
- Easily extensible (to add sub-species or even order at a higher level)
- Admin needs to select all applicable classification parts when associating to a plant (eg; a family, genus and species)
- Programatically, I lose the ability to find family from genus (broken hierarchy)
Another (and even wilder) idea I've had is to create several taxonomies (
plant_species) and somehow form a relation between each taxonomy type so that a family can be associated to several geni. I've no idea how this would work.
Wondering why there's no code? Well, it's relatively easy to create custom taxonomies, and what I'm missing is purely a system design issue.