IRC logs for #farmOS, 2022-03-31 (GMT)

2022-03-30
2022-04-01
TimeNickMessage
[10:58:32]<TheSlurpee[m]>mstenta: does log entity work with Feeds? Example, I want to import a fair amount of log data.
[10:59:40]<mstenta[m]>i haven't tried it myself in Drupal 9, but it worked in Drupal 7
[11:00:03]<mstenta[m]>Feeds is what we used for the CSV importers in farmOS v1
[11:00:12]<mstenta[m]>not (yet) ported to v2
[11:00:25]<mstenta[m]>https://farmos.discourse.group/t/csv-importers-in-v2-x/942
[11:00:54]<mstenta[m]>Some have been experimenting with alternatives using Python scripts that push to farmOS API
[11:02:25]<TheSlurpee[m]>ACTION reads thread 942,,,
[11:02:27]<TheSlurpee[m]>ACTION * reads thread 942...
[11:03:40]<mstenta[m]>Farmer Ed also wired up NodeRed to import CSVs for his needs
[11:04:56]<TheSlurpee[m]>Feeds in D9 works better than ever. I was looking into the new Storage entity module because Chart module suggests storing log data in it for charts in D9. Figured I would ask before I try same thing with the log entity.
[11:07:11]<mstenta[m]>Oh good to hear! I haven't had a chance to explore yet
[11:08:29]<mstenta[m]>Still deciding if farmOS core should implement core CSV importers, and if so, whether or not to pursue that with Feeds or Migrate API
[11:08:56]<paul121[m]>Storage entity is interesting https://www.drupal.org/project/storage 👀
[11:10:04]<mstenta[m]>TheSlurpee: have you seen this? https://www.drupal.org/project/feeds_migrate
[11:12:20]<TheSlurpee[m]>Feeds UI is simple enough these days that you can (probably) allow FarmOS users use the default module's UI/UX. I imagine a bit of custom FarmOS stuff can help a lil but, but not much is needed. Feeds finally just works as expected these days.
[11:14:28]<TheSlurpee[m]>Example, farmos will want to verify all the fields are exposed in the Feeds mapping section. That is the biggest piece. Allow user to create a Feed type. Create a Feed of CSV, tab, |, whatever. Then verify all the log entity field stuff is exposed to the Feeds mapping to clean up the CSV. Tamper module works great these days too for additional clean up.
[11:14:54]<mstenta[m]>Cool
[11:15:08]<mstenta[m]>Yea in v1 we had some custom logic to auto-generate Feeds importers for each asset and log type
[11:15:18]<mstenta[m]>Along with standard tamper plugins
[11:15:25]<TheSlurpee[m]>paul121: I'm starting to think there is a bit of overlap between log entity and storage entity accomplishing similar goals.
[11:16:14]<TheSlurpee[m]>paul121: Now I want to know what the Chart module people think about this log/storage topic :)
[11:18:10]<TheSlurpee[m]>The only reason I found the storage entity method of storing this type of log data, was finally finding a video that showed charts working properly in D9 with this method @ https://www.youtube.com/watch?v=DlMIYQ6VhLc&t=414s
[11:23:03]<paul121[m]>Yeah, it actually reminds of our data stream data as well. The simple data stream stores simple timestamps + values in the SQL DB. I had started integrating this with Charts, was working well!
[11:24:01]<paul121[m]>But the latest version of the Charts module isn't super stable.. so we've been holding off
[11:24:18]<paul121[m]>Maybe we could chat more about this on the dev call in 30 min?