Add 'Date of Planting' option in Plant Editor?

[Shane Litherland]

In scenario where I have some plants with minimal or no propagation detail (e.g. donated, bought at community markets, fell of back of a truck etc), recording propagation info for one or more batches (plant entries) is somewhat unnecessary, except for using one of the date fields to note planting date. This field is available under the 'seed' propagation option, but do I want to add a mostly-blank entry for 'seed' just to have the planting date recorded? I may not even know if the plants were grown from seed to start with, so I'd be cheating in some ways.
Maybe an alternative for ease-of-use would be for planting date to be one of the options on the general tab, under 'quantity' and 'location'... ? It seems to me the better place to view/edit such info. The 'date planted' field in the propagations tab might be better used for noting 'date the seedling was potted up' etc, given it is with germination data.

[brettatoms (brettatoms)]

Agreed, a "Date Planted" field should really be there already. Unfortunately it would require a schema change which would have to wait for a 1.1 series.

The initial date the Plant is given a location is record as a PlantChange which somewhat indicates the date it was planted there. I could also include a "Date Planted" in plant_change.reason as a temporary fix.

[Shane Litherland (litherland-farm-deactivatedaccount)]

I don't think this is significant enough to fiddle with a temp fix, if you feel it could be added 'neatly' in a future version - temp fixes mean more random bits to tidy up later, don't they? ;-) There's probably enough 'workarounds' in current setup, such as using the seed entry as above, or just one of the notes fields.

[Shane Litherland (litherland-farm-deactivatedaccount)]

I take that back, I've had a closer look at how that part works, if you are suggesting just adding the words 'Date Planted' to the list-box 'Reason' on the plant editor I can see that would be OK. Then it's saved to the table, with a date, it may not display in the most intuitive place but that's no big deal.

On that topic, I just played with the 'date changed' and 'reason' settings in a plant editor to see how it committed to table etc. When re-opening the plant editor, the latest change/reason doesn't show in that list-box, but a date does. The list box looks like it's just a 'select' option not a 'display' so this behaviour seems correct, or is this something I should list as a separate bug?

[brettatoms (brettatoms)]

I went back and forth on being able to browse the plant changes in the
plant editor or not. e.g. adding each one to a list where you can see
the previous ones. In the end I made it so that when you change the
reason and date of change then it implies the current change and then
you can browse the changes in the infobox. That way there is a
seperation between edit mode and browse mode. The jury is still out
on if this is better.

On Sun, Sep 25, 2011 at 9:48 AM, Shane Litherland
<email address hidden> wrote:
> I take that back, I've had a closer look at how that part works, if you
> are suggesting just adding the words 'Date Planted' to the list-box
> 'Reason' on the plant editor I can see that would be OK. Then it's saved
> to the table, with a date, it may not display in the most intuitive
> place but that's no big deal.
>
> On that topic, I just played with the 'date changed' and 'reason'
> settings in a plant editor to see how it committed to table etc. When
> re-opening the plant editor, the latest change/reason doesn't show in
> that list-box, but a date does. The list box looks like it's just a
> 'select' option not a 'display' so this behaviour seems correct, or is
> this something I should list as a separate bug?
>
> --
> You received this bug notification because you are subscribed to Bauble.
> https://bugs.launchpad.net/bugs/857978
>
> Title:
>  Add 'Date of Planting' option in Plant Editor?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bauble/+bug/857978/+subscriptions
>

[Shane Litherland (litherland-farm-deactivatedaccount)]

Separations are good for novices, less chance of altering info that isn't supposed to be altered (in this case, any previous changes and reasons).
Anyone adept enough at Bauble/db stuff that should be changing historical data, probably knows how to do it in the tables anyway.
(I had no dramas doing that to edit/delete 'test' entries for plant changes)

[Mario Frasca (mfrasca)]

seems an easy addition with which to start - and a useful test case for database schema migration.