Now that i’ve got all my Crop data migrated into v2 (uploaded via API) and am exploring what views are available in the UI, i can see that- of those
Plant asset attributes by which one can filter & sort records- i.e.:
… There is one one (
Crop/variety) that i’ve not been using to best advantage, and two (
Group) that i’ve not yet used at all, mainly because those attributes were not available in the v1.x “Import CSV” template (that being the way that all our farm records, maintained in spreadsheets, were previously being entered into farmOS).
So: to better understand what is now possible in v2, i’m looking at the Terms section of Data Model docs, which does help some, but could i think benefit from a practical example. Here’s one:
Let’s consider Chard -a species with several varieties that we grow (Ruby, Yellow, Rainbow)- which belongs to the Chenopod (i.e. Amaranth) family, along with Beetroots and Spinaches and probably some others (not to get any deeper into botanical nuances than necessary, to know how best to map such relations).
Until now, for simplicity of management, we’ve not been distinguishing between varieties of Chard in our crop record keeping; they are all identified simply as “Swiss chard” in our Plant asset naming convention (e.g.
2021-W19 Swiss chard SGH2-S was the crop transplanted in Week#19 of 2021 into SummerGreenHouse Bed#2, South section).
To enable a more nuanced view, i guess we might name each of the 3 Chard varieties as own Plant type, each of which could then have its own related Image file, according to those docs, along with its own “Days to transplant” (integer) and “Days to maturity” (integer), according to the docs. In fact those intervals would be the same across Chard varieties, so that’s not the best example… But in case of “Beetroot” varieties, e.g. Chioggia and Kogel, those intervals would differ across varieties, so that could be a useful distinction. To decide about how granular to go in our
Plant type definitions, there’s a cost/ benefit analysis we’ll need to run on these different examples.
In any case: i need to better understand how best to apply these other terms, namely:
- Companions: references some other term(s?) in the ‘Plant type’ vocabulary," i gather; as in “Companion cropping,” like baby lettuces planted under an overstory of chards? Or is this rather for “siblings” in a family of plants?
- Crop family: defined as referring to some other term in the “Crop Family” vocabulary: would that that best be used here as a pointer from say “Ruby chard” variety to “Swiss Chard” family? but then…
- Parent: Is this where we should declare Chenopod as the parent? Must that be declared at level of Swiss chard, and at level of all it’s 3 child varieties? or is this a multi-inheritance relation, where only the immediate parental relation need be declared, and subsequent generation(s) are included?
- Group: I get no clue about this one from that “Terms” page (docs could benefit from a search widget, b/t/w)… But as it is available as a filter in the UI -like Parent, but unlike the previous two terms- Group looks to me like being even more useful in that sense. This being one of those attributes available as an “Action” in the UI: is this intended to be used for “tagging” records that might not be classifiable along any other dimension?
Sorry for the length of this post; feel free to parse out whatever bits are easily answerable, or else needing more clarification, as the case may be… But if anyone can shed more light about how family relations among plants might be best represented in farmOS, i should be most grateful.