IRC logs for #farmOS, 2022-08-18 (GMT)

2022-08-17
2022-08-19
TimeNickMessage
[23:39:10]<perfectinfoseeke>i have started to grow a food forest on a small farm of 1Ha, want to keep the logs of the condition of each type of plant / tree which are growing right from swing till harvest
[23:41:33]<perfectinfoseeke>* symbioquine: i have
[23:47:57]<perfectinfoseeke> * symbioquine: i have started to grow a food forest on a small farm of 1Ha, want to keep the logs of the condition of each type of plant / tree which are growing right from sowing till harvest
[23:49:17]<symbioquine[m]>Cool
[23:49:57]<perfectinfoseeke>any option to integrate account module to keep track of farm income and expenses?
[23:50:58]<symbioquine[m]>Yeah, I think there's a farm ledger module, but I can't remember if it's ported to 2.x yet.
[23:53:03]<perfectinfoseeke>need help in integrating asset link in my docker farmos
[23:53:17]<perfectinfoseeke>* docker farmos (how do i install?)
[23:56:05]<symbioquine[m]><perfectinfoseeke> "i have started to grow a food..." <- Both Asset Link and Field Kit will tend to produce a subset of the kinds of asset/log changes one can make via the main web UI so a good place to start would be creating some assets/logs through the main web UI so you can familiarize yourself with the data model and maybe produce some example data...
[23:57:10]<symbioquine[m]>perfectinfoseeke: Maybe best to wait a few more days for the alpha release.
[00:05:19]<perfectinfoseeke>can someone share with me example site where i can see how the logs are kept?
[00:05:53]<perfectinfoseeke>* example site (like of a food forest ) where i
[10:44:18]* farmBOT has joined #farmos
[10:51:57]<mstenta[m]>@room farmOS weekly dev call is today at 12 noon Eastern time: https://meet.jit.si/farmos-dev
[10:52:25]<mstenta[m]>I will be late to join today. Need to pick up my son.
[12:02:54]<paul121[m]>I'm on hold with insurance company might be 30 min late sorry :-/
[13:03:48]<symbioquine[m]>mstenta: RE: eggs in Asset Link... the data model bit where an asset [can be marked](https://github.com/farmOS/farm_eggs/blob/2c3c31e342edc3724a37e32890d9fe0...) as "producing eggs" would need to exist somehow first
[13:05:45]<mstenta[m]>Yea maybe... although I've been thinking about ways around that
[13:06:26]<symbioquine[m]>or some more general machine-readable tagging mechanism I suppose :)
[13:08:45]<mstenta[m]>Yea, it might still be useful to have a general purpose mechanism
[13:12:42]<FarmerEd[m]>Must have a proper look at this this week symbioquine, could be useful for recording heats in the field.
[13:13:11]<FarmerEd[m]>Did you say you already did something like that for the rabbits?
[13:13:38]<FarmerEd[m]>does it create 2 logs then, service date and due date?
[13:13:41]<symbioquine[m]>FarmerEd[m]: In 1.x, but very soon I need to implement it on top of Asset Link
[13:14:40]<symbioquine[m]>FarmerEd[m]: Right now it just creates one or more "attempted to breed A with B" logs and extrapolates the anticipated possible pregnancy term from that log.
[13:15:27]<symbioquine[m]>FarmerEd[m]: Do you have some example farmOS logs you'd be willing to share? I'd be curious whether a common model for Rabbits and larger livestock might be viable...
[13:17:08]<symbioquine[m]>You can get them as JSON by going to `https://my.farmos.domain/api/log/activity?filter[drupal_internal__id]=3475` where 3475 is the log id
[13:17:30]<symbioquine[m]>Assuming they're activity logs of course :)
[13:18:23]<FarmerEd[m]>possibly, I had created a node-red flow at one stage which read from a google calendar entry and the created 2 farmos logs and a second calendar entry. Its abandoned now as breeding season is over and I'm building farmos modules
[13:22:10]<FarmerEd[m]>Gestation period would need to be variable to account for different livestock types.
[13:24:29]<FarmerEd[m]>I may have told a lie, the node red flow was only creating 1 log, which was the calving Due, but my planned replacement is going to produce 2.
[13:24:53]<FarmerEd[m]>* 1 log and 2 calendar entries, which, * produce 2 logs.
[13:25:49]<symbioquine[m]>What happens with the second log if the pregnancy didn't take or doesn't go to full term?
[13:26:54]<symbioquine[m]>That's why I've been going with the strategy of just creating logs that represent the breeding attempt, then creating a log once the birth happens
[13:31:21]<FarmerEd[m]>manual archive with notes
[13:31:42]<symbioquine[m]>FarmerEd[m]: archive of what?
[13:34:48]<FarmerEd[m]>Oh, marked complete with a appropriate note, I guess.......... hasn't happened yet
[13:35:39]<FarmerEd[m]>I've only 12 breeding females at the moment and a stock bull
[13:36:24]<mstenta[m]>Maybe logs need a `canceled` status
[13:37:26]<symbioquine[m]>Rabbit breeding is a bit more hit or miss - especially if it's warmer out
[13:39:05]<FarmerEd[m]>Cattle are fairly on target, bit more hit/miss with AI though
[13:39:43]<FarmerEd[m]>yep cancel status probably makes sense
[13:40:42]<FarmerEd[m]>what's the code tags for these chats?
[13:40:59]<symbioquine[m]>`\`\``
[13:41:08]<symbioquine[m]> * ``` `` ```
[13:41:23]<symbioquine[m]>Just markdown code fences/blocks
[13:44:29]<mstenta[m]>https://www.drupal.org/project/log/issues/3304608
[13:44:42]<mstenta[m]>Created an issue in case we want to explore that - it seems like it would be useful!
[13:45:19]<FarmerEd[m]>`"attributes": {... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/2517cf195d...)
[13:45:29]<symbioquine[m]><mstenta[m]> "Yea maybe... although I've..." <- Is there an issue for the alternative strategy you were considering for this?
[13:45:38]<symbioquine[m]><symbioquine[m]> "mstenta: RE: eggs in Asset Link...." <- RE ^
[13:46:59]<mstenta[m]>No just in my head... with Asset Link in mind maybe simply navigating to the group asset would be enough.
[13:47:15]<mstenta[m]>eg: click on my flock, then click "Record egg harvest"
[13:47:28]<mstenta[m]>(still... that's not ideal... it would show up on all groups/animals i imagine)
[13:47:35]<symbioquine[m]>Yeah
[13:47:50]<mstenta[m]>Thinking more generally... what about a simple "Record harvest" which could remember what units you used on a per-asset basis
[13:48:15]<mstenta[m]>(nav to flock, click "Record harvest", set units to "egg(s)" and it gets preset to that next time)
[13:48:33]<mstenta[m]>(probably overthinking this by avoiding the extra data field/flag)
[13:48:51]<mstenta[m]>(maybe we just add a key_value field to all assets?)
[13:49:10]<symbioquine[m]>mstenta[m]: That makes sense, but is perhaps a departure from the minimalism I think I'm targeting...
[13:49:45]<symbioquine[m]>i.e. the idea is you shouldn't have the distraction of all the other possible harvest fields - even if you would just ignore them
[13:52:02]<mstenta[m]>Yea makes sense - although I was picturing a very simple harvest form - just a quantity and unit
[13:52:16]<mstenta[m]>Which is all I need most of the time, for veggies, mushrooms, etc
[14:03:27]<mstenta[m]>symbioquine: maybe you answered this before... how do plugins get added to asset link? can another module add them?
[14:34:03]<symbioquine[m]><mstenta[m]> "symbioquine: maybe you answered..." <- When you say module, you mean another farmOS module right?
[14:34:36]<symbioquine[m]>If so, then the answer is yes
[14:35:01]<mstenta[m]>Yes. Cool!
[14:35:34]<mstenta[m]>So (in theory, dunno if this is what we'd do), https://github.com/farmOS/farm_eggs v2 could just add asset link plugins
[14:36:32]<symbioquine[m]>https://github.com/symbioquine/farmOS_asset_link/blob/release/config/ins...
[14:37:52]<symbioquine[m]>It just needs a config entity like that and a js/vue file somewhere web accessible
[14:38:04]<mstenta[m]>Nice!
[14:54:06]<FarmerEd[m]>mstenta: Do you mind if I have pushed Arm64 images to my repo on Docker hub?
[14:54:29]<mstenta[m]>go for it!
[14:56:20]<FarmerEd[m]>Cheers I'll push some when I update my own at least until you figure out the obstacles on Github Actions,