You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for the program to be useful for seed ordering, we will have to
track the following data:
* amount needed per foot (or per 100'; in oz or grams)
* sources of variety (ie catalogs)
* item # and page (per source or catalog)
* longevity of seed viability (order every year, 5 yr, 10 yr, etc...)
* others??
These would tracked in the CropDB and users wanting to use the seed order
functions would have to use the CropDB.
In lieu of a proper in-program catalog aggregation and seed ordering
feature, we could then generate a "Seed Ordering Worksheet" from a
particular crop plan. These worksheets might include the following data:
* crop
* variety
* total plantings
* total beds
* total rowfeet
* total flats
* seed/foot (if appl.)
* total seed needed (if appl.)
* source/sources
* cat # and page
* planted last year?
* have left over seed?
* amt adjusted for leftover seed
* notes?
* how much ordered last year
* how much is left from last year
* did we reorder last year
The user could then use this information or print out (specifically, the
source, cat#/page and total seed needed) to make ordering seeds easier.
Original issue reported on code.google.com by cropplan...@gmail.com on 1 Apr 2008 at 3:07
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
cropplan...@gmail.com
on 1 Apr 2008 at 3:07The text was updated successfully, but these errors were encountered: