Crop Timelines

[GoogleCodeExporter]

Associate "timelines" of operations with crops in the database.  These
would be lists of operations, approx time to complete each operation and an
approximate time/date/week after planting for when they would happen.

This data could then be used for other reporting tasks, such as calendar
view (issue 13), todo lists (issue 14) and labor budgets.

Original issue reported on code.google.com by cropplan...@gmail.com on 17 Jan 2008 at 2:29

[GoogleCodeExporter]

This might be a second tab under the CropDB detail view.  A table would be 
created
(something like "CROP_EVENTS") with fields for:
 * event id (unique)
 * crop id
 * event name
 * approx weeks after planting (0 is week of, negative are weeks before, default sort)
 * approx time to complete
 * perhaps an "order" to clarify position (secondary sort)

When we need a timeline for a crop, we could select from this table with WHERE
crop_id = ... ORDER BY weeks_after_planting

Original comment by cropplan...@gmail.com on 19 Jan 2008 at 10:19

[GoogleCodeExporter]

We will also need to track which "date" the action refers to.  This will allow 
users
to enter, for example, "Prepare greenhouse for winter squash curing 1 week 
before
harvest" and will avoid ambiguity about whether the planting date refers to 
seeding
or transplanting.

Original comment by cropplan...@gmail.com on 1 Apr 2008 at 3:29

[GoogleCodeExporter]

Original comment by cropplan...@gmail.com on 28 Sep 2008 at 12:11

• Added labels: Milestone-Future
• Removed labels: Milestone-RC1

[GoogleCodeExporter]

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:44

• Added labels: Priority-Wanted

[GoogleCodeExporter]

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:52

• Added labels: Version-Future
• Removed labels: milestone-future

[GoogleCodeExporter]

Original comment by cropplan...@gmail.com on 11 Dec 2008 at 4:08

• Added labels: Priority-WouldBeNice, Version-1.5