reword 'Plant' to 'Planting' or 'Lot' for clarity?

Bug #861077 reported by Shane Litherland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bauble
Confirmed
Medium
Unassigned

Bug Description

For a trained user, this is minor, but for new/occasional users, the word 'Plant' is used a few times in Bauble to mean different things, with potential for confusion.
I am also noting this here because current help docs are very lacking and In the next coupla weeks I will be writing more stuff to contribute for docs so would like other opinions on this to help explain all the differences...

1. From an Accesssion, adding a 'Plant' means adding an individual or group of plants of that species that were propagated/planted/cultured as a 'batch' or 'lot'.
2. The infobox for a species shows "# of plants:" which is not the number of *individual* plants as might commonly be thought, but the number of 'plant entries'. e.g. I have one 'plant entry' with 5 individuals, this shows in infobox as "# of plants: 1 in 1 accessions". One may interpret this as one single plant, when in fact it is one *planting* of 5 plants.
3. in Plant Editor, the Accession type has a few options including 'plant'. In this case, 'plant' seems to be referring to the physical structure that gave rise to the individuals being entered in the Plant Editor
4. The infobox for a plant entry shows under 'General' the item "Accession type:" which displays the option set in previous point. Further down under 'Properties' is "Type: Plant" referring to this being a 'plant entry'

A quick look at some tables, python scripts etc indicates changing the wording anywhere for one or more of these situations could involve a lot more than just changing 'plant' to 'lot' in a window heading, or could this be achieved whilst keeping the internal processes as-is using the word 'plant' in numerous situations?

The alternative to no changes, is to explain in the docs the meaning of 'plant' for each context. Not so difficult, but still potentially confusing lay users.

Tags: docs help
Revision history for this message
Shane Litherland (litherland-farm-deactivatedaccount) wrote :

As a footnote to this, current help doc states "You can create multiple Plants by using ranges in the code entry." This, it seems, would allow multiple plant entries with the same location, date, etc, and if 'quantity' was entered as '1', creating one plant entry for each individual plant?
If this is the correct use of Bauble, then why for a Plant entry can one put any number for 'quantity' because at the moment, I could enter one plant entry with 'quantity' of '5' or I could enter 5 plant entries with quantity of '1' to record the same 5 specimens planted in the same location etc. If I mistakenly left quantity as '5' whilst still using multiple plant option for 5 entries, I'd end up with 25 specimens on record...

The multiple entry option is good. The options for 'quantity' is good. Just seems to be a bit of overlap or potential for inconsistent data entry at moment. Again, could be tweaks of code, or expand on the docs.

tags: added: docs
tags: added: help
Revision history for this message
brettatoms (brettatoms) wrote :

The "ranges" part in the docs needs to be removed. At one point this was possible but it was removed in order to keep things simple.

All the "Plant" meanings are confusing. Especially mixing up the quantity of plants planted and the numbers of Plant qualifiers/codes within an accession as in the "# of plants" part of the accession infobox. Could change this to something like:
# of plants: total of 16 in 4 qualifiers/codes in 2 accessions
...though it can start to get wordy and confusing.

Also should make the quantity able to accept "mass" for mass plantings. Could just store -1 or something in the field if someone types in "mass".

Changed in bauble:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.