Database back end

DB backend will be U1DB

Garden items will have
* Unique ID (non grouped by plant, completely unique)
* Common Name (IE Cayenne Pepper, Long)
* taxonomic name (IE Capsicum Annum, var)
* member id ("Heather's Yellow Grape Tomato plant #4 of 8)
* Plant family (Brassicae, lycopersicum, capsicum, etc) grouping field
* hybrid/heirloom
* Determinate/indeterminate (mainly for tomatoes
* Leaf type (potato/regular/etc) mainly for nightshade (tomatoes/potatoes/etc)
* annual/perennial/etc
* detail (hot, purple, different)
* source
* svg representation based on plot type/size
* location
  - garden/seedling tray/etc
* location requirements/light requirements
* planting window
* Planting date
* germination period
* temperature requirment
 - heat tolerance
 - frost/freeze tolerance
* Yeild period
* space requirements in garden (plot size)
* Plot type (container/raised/bed/etc)
* transplant date
* expected removal date
* actual removal date
* removal reason (exp, freeze, sale)
* approx yield
* item type (plant, landscape, irrigation)
NOTE: Garden items can include non-plants (such as a 16" x 16" paver). Many fields will not be populated in this case.

Historical fields... many entries for each item
* feeding date
 - type of feed
* harvest (per harvest, got 4 peppers this day, 9 that day)

Garden fields (for whole garden)
* zone
* location
* Geo location
* size
* actual svg of plot, within which garden objects will be placed