hi RJ,
Say I have accessioned a batch of seeds into the database, then propagate some of those seeds, how do I record that?
let me first make sure we both understand ›propagate‹ in the same sense, I have the impression you're talking of ›germinate‹.
also, maybe since you're handling seeds in your database, you might be interested in our second batch of ›Contributed user recipes‹, ›using-ghini-for-a-seed-database‹.
It seems that you can only make propagation records on plants, not accessions.
well, yes, obviously… accessions are instances of an abstract
concept, not physical objects.
seeds are, as far as ghini is concerned, a form of plant. if you germinate them, you are altering their form, and you are very likely giving them a treatment, and moving them from one location to an other. this is conceptually similar to sending seeds, described in the above recipes page.
if on the other hand you're really talking of ›propagate‹, then please add more information of what you do in practice, like describing the details of your handling and which are the physical objects involved, because I do not manage to imagine propagating anything else than a plant (if you're doing a cutting), or two plants (if you're pollinating a seed). as stated in the docs:
In the case of a seed propagation trial, you have a pollen parent, and athanks for asking and for using ghini.
seed parent. You should always associate the Propagation trial to the seed
parent.
Mario Frasca
--
You received this message because you are subscribed to the Google Groups "ghini/bauble" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bauble+un...@googlegroups.com.
To post to this group, send email to bau...@googlegroups.com.
Visit this group at https://groups.google.com/group/bauble.
For more options, visit https://groups.google.com/d/optout.
Hi Robert and Jaap!
On 08/24/2018 09:51 PM, rjwhi...@gmail.com wrote:
Thank you Jaap and Mario for your explanations.
If I understand correctly, this is the process I need to follow:
When I receive a batch of seeds of the same species and from the same source, I create a new accession.
yes, and a first new plant
When I withdraw seeds from storage I create a new plant.
yes, by splitting the seeds plant
When I attempt to propagate plants from the seeds I withdrew I add a propagation record to the plant.
this I'm not so sure. you didn't comment on my question about
›propagate‹ and ›germinate‹. if you're germinating the seeds in
your accession, you are only altering the form in which plants are
kept in the garden, and moving them from one location to an
other.
as Jaap is rightfully stressing, it depends on what's the purpose of your collection, if you're interested in keeping precise track of generations, for example if you're doing annuals.
I would use propagation records when collecting seeds from a plant, not when germinating seeds.
but if it serves you this way, you're welcome to use it this way.
If the propagation was successful, I create a new accession and associate it with the propagation attempt.
this is indeed what a propagation record is meant for, yes.
Please correct me if I am wrong.
:-)
also, as Jaap suggests: make experiments with your data. you can also write a script describing the events in a couple of years in your garden, run it and see if you get into excessive trouble with limited advantage.
this is a screenshot from a presentation by an employee at the mobot, held a couple of years ago at the regional conference 'building botanical bridges':

they are using a `-` instead of a `.` as a separator, that's the only difference.
accession 2016.0100 arrives in seeds, and you germinate them (bit
by bit). when you germinate a seeds-plant, you get a
living-plant, and it stays in the same accession, but it should be
a different plant.
accession 2016.0038 arrives in plant form, and you place it at different locations in the garden.
ciao, regards,
Mario
Hallo Robert and Jaap
- When I receive a batch of seeds of the same species and from the same source, I create a new accession.
let me describe a more complex scenario and please help me correct and complete it (scenario and/or description).
imagine you are authorized to collect plant material in a wild area within your country…
actually, you might need to keep track of your authorizations, too, and the software at the moment does not help. feel free to open an issue describing the case. we've never dealt with this part.
the material you collect is in dried form, in practice: vouchers
and seeds, but you leave (most of) the (living) plant in place.
(consider the role of the multiplier 'quantity' to a Plant
object.)
if you do this, I would add to the database an accession describing the parent plant, and I think I also would keep the parent plant in the database, indicating its (approximate) location. vouchers, they may be plant parts, or whole plants. if they are whole plants, that's easy: add them to the database as plants with pictures and notes. if you keep them yourself in your herbarium, that would be your location. if it's plant parts I would not know. consider your practice, check it against the software, and come with hints.
collected seeds, in this case, would be propagation trials of the
parent wild plant. you may also be able to collect seeds from the
same plant in different occasions. if successful, these would
become separate accessions, and their association to the parent
wild plant makes it possible to relate them to each other.
maybe too complex for a simple herbal garden, maybe needing further refinement for a scientifically oriented garden?
regards, and interested in comments.
Mario
buongiorno Jaap
I see, I had forgotten this behaviour, and I would not know what is the best thing to do. as my scientific taxonomic advisor said: "providing a binomial without authorship is a mistake".

so we have the author, and we're not reporting it in accession nor plant.
meaning that, if you have a result list with plants or
accessions, you will not know if the authorship is missing, since
ghini anyway doesn't report it.
it's a very small correction, and if you want to report it, please do so.
Mario
I will come back to you on this one. I haven't used the voucher editor yet, for example. I suppose an institute can also have a herbarium beside of the garden. Or work together with a herbarium.
--
you didn't comment on my question about ›propagate‹ and ›germinate‹
this is a screenshot from a presentation by an employee at the mobot, held a couple of years ago at the regional conference 'building botanical bridges'
did Jaap and I help you answer your question?
Hi Mario and Jaap!Sorry for my late reply, I've been quite busy.
you didn't comment on my question about ›propagate‹ and ›germinate‹
I use 'propagate' to mean produce a new plant from a parent plant and 'germinate' to mean sprout seeds or spores.
this is a screenshot from a presentation by an employee at the mobot, held a couple of years ago at the regional conference 'building botanical bridges'
That screenshot was very helpful. Do you happen to have the full presentation?

one more thing, not often mentioned in best practices, missing in ghini (and I don't know who's ever financing that part) is the old "issue-9", now https://github.com/Ghini/ghini.desktop/issues/92.ciao, enjoy,
we have workarounds, check the contributed recipes.

hi everybody from me too again,
On 09/12/2018 01:26 AM, Jaap Uilhoorn wrote:
[…] The propagation editor is about recording data about propagation attempts. Which is usefull, so we don't have to invent things twice. But I think there is no link with creating new accessions or linking generations off accessions.
well, actually it does, I mean there is a link between Propagations - generations and new Accessions. when you create a new Accession, you may switch to the second pane, called 'Source'.
among the Contacts there is a hard coded value, reading 'Garden Propagation'.
you choose that, and you get the chance to relate your new Accession to a successful plant Propagation. only those Propagations will show which are successful, and have not yet been accessioned in full.
I think I have a video about this, or you can experiment yourself.
https://www.youtube.com/user/mrgsfs/videos?shelf_id=0&sort=dd&view=0
no, looks like I only have how to "follow propagations", not how to create them.
Is this what you were hinting at?
my concern is that if you have an Accession where the Plant material is still in seeds form, and you are changing the form by germinating the seeds, these plants are absolutely still in the same Accession as the seeds, same genetic material, same source, same time (entering the collection), so same Accession. you are really not adding anything to your collection, only changing form.
a different thing if you collected seeds from your own Plant, are germinating them, and you are still keeping all the action within a propagation attempt, that is, still within the parent Plant. then, at the moment you decide the attempt was successful, you would create a new Accession and you go through the steps I described above.
I also suppose that, if you do annuals and you don't precisely care about the genetic traceability of generations, you would not go through the whole nuisance of propagations etc, and you would simply sow your seeds in your garden, and possibly renew the plant count estimate when you think so.
I have been pondering about these generations of annuals also. Creating new accessions on a yearly base is a lot of work.
your idea, of having annuals inside the same accession, is something I have seen in other sources too. your Popular Republic of China TLA is a bit funny. the hint I had seen was about removing the year altogether, and have these accessions as ----.####. from ghini's point of view, this is easier, for it does not conflict with ghini counting for you. you can have two accession templates in your ID format, like this:

and you would be able to let ghini count for you, which would be
the next available accession code. … actually, you better have
also this one: »%{Y-1}.####«, helping you add (in January) stuff
still related to the previous year. the trailing PRC in your idea
stands in the way of ghini automatic counting. (btw: you really
need to press <enter> after you edit a template format.)
you are not exactly breaking anything special, just this help mechanism, and it easily fixed if you insist, but I would expect more practical difficulties at several points downstream, for example reserving space on your labels, and possibly with the print and scan resolution needed to produce QR codes, possibly with bad written code we may have, where I rely on the four(dot)four(dot)any structure. these are practical things, not database related, but I would keep them in consideration.
I noticed (in my test database) that the format of the accession number could be changed manualy . So I invented Perpetual Reproduction Cycle. I thought that with a similar numerical value and a simple code one keeps al the important data together, And in case info is needed in the context of the reproduction cycle one can do the math himself. Of course my question, am I violating any data integrity?
again, not really violating, but you are defining logical links that you can follow, but which the software and much less the database knows anything about. it's risky, I think.
The accession number, in my example, without the PRC code I used for the seed in storage.
I'm not sure I follow this part, and I'm wondering. you do so, only to keep track of the year when the seeds were collected, or any other reason? if it is only so that you know when to germinate them, I'm afraid I would do this with a note to the plant (in seeds form). something like deciding that every jar or bag of seeds has a note with category collection-season, or germinate-by, or whatever fits you, that help you choose it (the jar) when you decide you want to germinate stuff in your annuals. the code of such a plant might be `----.0032.13`. this is what I would do, or what I suppose I would do.
again too many words, I hope that some were useful,
best,
Mario