The Collection That Grows Faster Than the Care Knowledge
A serious orchid collection can accumulate 50 to 150 plants in a few years of active acquisition, and the care requirements across those plants are not uniform. A Cattleya alliance hybrid and a Pleurothallidinae miniature require fundamentally different temperature ranges, light intensities, and watering intervals. A Vanda mounted on a bare root needs near-daily watering in summer and a completely different approach in a lower-humidity winter growing space. A Catasetinae goes completely deciduous in its dry rest period and must not be watered.
Managing these differences from memory, or from a collection of sticky notes pinned near each plant, breaks down around the 40-plant mark. A single care mistake on a mature Paphiopedilum rothschildianum that took 12 years to reach blooming size is an expensive lesson. The collection database is the system that makes care requirements retrievable without remembering which plant is which in a crowded growing area.
The Fields That Separate Serious Collectors from Casual Growers
The Type field carries 18 alliance and subfamily classifications: Cattleya alliance, Dendrobium alliance, African orchid, Oncidium alliance, Zygopetalinae, Maxillariinae, Phalaenopsis alliance, Vanda alliance, Coelogyninae, Stanhopeinae, Lycastinae, Bulbophyllinae, Catasetinae, Species, Paphiopedilinae, and Pleurothallidinae. This is not decorative taxonomy — it is the primary filter for care group segmentation. All Catasetinae in the collection share a dry rest protocol. All Vanda alliance plants have hanging-basket or mounted culture implications. Filtering by type surfaces the care cohort.
The Parents field is the hybrid genealogy record. A Rhyncholaeliocattleya cross carries the thermal tolerance and light requirements inherited from its Rhynchlaelia parent alongside the bloom form and color contributions of the Cattleya parent. Knowing the parentage — both pod parent and pollen parent — helps predict how a hybrid will behave in your specific growing conditions before you lose it. The Syn. field carries the synonym, because orchid taxonomy reorganizations have moved many familiar names across genera: what was sold as a Sophronitis is now Cattleya, and what was Sophrolaeliacattleya has been reorganised under different genus names depending on the registrar. The synonym field is where you track the trade name alongside the current accepted name.
Temperature, Light, Humidity, and Media as Care Records
These four fields are free-text because orchid care requirements are gradient data, not binary states. Temperature is not just "warm" or "cool" — it is a minimum night temperature, a preferred day range, and a seasonal differential. A Lycaste aromatica wants a pronounced cool dry winter with night temperatures dropping to 8–10°C to trigger bloom. A Phalaenopsis hybrid in the same space, happy at 20°C nights year-round, will never bloom. The Temperature field carries the specific range, not a category.
Light is footcandles or lux, or a practical descriptor like "bright indirect with two hours of direct morning sun." Media is the potting mix: bark, sphagnum, rockwool, mounted on tree fern slab, bare root in an open basket. The media determines watering frequency — bark dries faster than sphagnum, mounted culture dries faster than any potted medium. A plant record without media type is missing the context that explains why the watering interval is what it is.
The observations field carries what all the structured fields cannot: "spiking from new growth as of March 14," "root tips actively growing, repotting window open," "two consecutive failed blooms — check root health before next season."
The vendor and purchase date fields track acquisition provenance. When a division of a well-performing clone becomes available from the same vendor, you know where to call.