I'm starting to think of the-thing-you-plant as a "planting" so if I use that term that's what I'm talking about.
A planting goes through a lifecyle:
sow tend harvest use/share
A planting has a couple of different states it can be in:
wishlist current past
Something like a lemon tree, once planted, stays current for years. Other vegies and herbs, though, come and go with the seasons. A query for "current" plantings will show you what you currently have in your garden(s).
I mentioned, above, the idea of "pending" activities. I was talking about "tending" at the time, but it would also apply for sowing and harvesting. You could make a pending "sow" event to remind you when to sow that particular thing, or a pending "harvest" event to remind you that a fruit tree will be ripe in whatever month.
So, my idea of the data structure at present is something like:
* person (should be obvious)
* garden (each person has one or more; they can be shared with other people)
* planting (each garden has one or more plantings; equivalent to mrsbrown's "project")
* actions (each planting has sow/tend/harvest/etc actions/events)
I'll be thinking through all the different flows for this and see if anything doesn't fit. The main one that comes to mind is actions that relate to the whole garden or are more general, eg. "turn compost heap".
no subject
on 2012-07-29 07:44 am (UTC)A planting goes through a lifecyle:
sow
tend
harvest
use/share
A planting has a couple of different states it can be in:
wishlist
current
past
Something like a lemon tree, once planted, stays current for years. Other vegies and herbs, though, come and go with the seasons. A query for "current" plantings will show you what you currently have in your garden(s).
I mentioned, above, the idea of "pending" activities. I was talking about "tending" at the time, but it would also apply for sowing and harvesting. You could make a pending "sow" event to remind you when to sow that particular thing, or a pending "harvest" event to remind you that a fruit tree will be ripe in whatever month.
So, my idea of the data structure at present is something like:
* person (should be obvious)
* garden (each person has one or more; they can be shared with other people)
* planting (each garden has one or more plantings; equivalent to
* actions (each planting has sow/tend/harvest/etc actions/events)
I'll be thinking through all the different flows for this and see if anything doesn't fit. The main one that comes to mind is actions that relate to the whole garden or are more general, eg. "turn compost heap".