Viewing post #887442 by dave

You are viewing a single post made by dave in the thread called Custom data fields for Crop Plants.
Image
Jun 24, 2015 9:22 AM CST
Garden.org Admin
Name: Dave Whitinger
Southlake, Texas (Zone 8a)
Region: Texas Seed Starter Vegetable Grower Tomato Heads Vermiculture Garden Research Contributor
Million Pollinator Garden Challenge Charter ATP Member I was one of the first 300 contributors to the plant database! Garden Ideas: Master Level Region: Ukraine Garden Sages
Here's my thinking: the custom data fields were designed because some plants have unique characteristics that are separate from other kinds of plants. For example, most plants don't need to have ploidy indicated, but in daylilies it's very important so we have it there.

At this point, asking for the same fields in 24 different custom databases tells me that these fields really should belong in the primary plant details.

Hybridizer should be a universal field among all cultivars. Nearly every cultivar has a hybridizer that could be listed. Same with history and year introduced.

Heredity is universal among all vegetables.

I propose we make all these fields primary fields, and that I then phase it out of the databases that currently have it in their custom architectures.

« Return to the thread "Custom data fields for Crop Plants"
« Return to Plant Database forum
« Return to the Garden.org homepage

Member Login:

( No account? Join now! )

Today's site banner is by IrisLilli and is called "Purple Crocus Mix"

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.