| [10:55:02] | <symbioquine[m]> | I was just playing with JupyterLite + farmOS and thought a bit more involved of an example might be fun; |
| [10:55:08] | <symbioquine[m]> | ACTION uploaded an image: (181KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/ZeruJaRHebW... > |
| [10:57:03] | <symbioquine[m]> | https://gist.github.com/symbioquine/1ad8708ddf83afb3e907b95002d9e744 |
| [10:59:33] | <ludwa6[m]> | yes! while CSV upload is a fundamental need, it is the ease of applying python's standard dataSci libes (e.g. pandas, matplotlib, plotly, etc.) for data analysis and visualisation that will be such a quick & huge win with this JuypterLite facility. |
| [10:59:34] | <mstenta[m]> | wow |
| [11:01:24] | <ludwa6[m]> | deploy it on farmier, mstenta , and that will instantly elevate the service head&shoulders above all those other cloud-based commercial solutions on the market today |
| [11:01:28] | <mstenta[m]> | what excites me most about JupyterLite is how it can compliment the features of farmOS, and provide a "bleeding edge" place to experiment :-) |
| [11:01:42] | <mstenta[m]> | i'm planning on it ludwa6 ! :-D |
| [11:02:49] | <ludwa6[m]> | "bleeding edge"? as in advancing the state-of-the-art for farm data management, yes indeed... But not in terms of technology, i hope? |
| [11:04:06] | <mstenta[m]> | specifically i am thinking about the CSV importers and graphing (which symbioquine just demonstrated) - this is a place to experiment with ideas before (or in lieu of / alongside) making farmOS/Drupal modules in the farmOS UI itself |
| [11:05:00] | <mstenta[m]> | of course, this could all be done with Python scripts and custom apps already - but this lowers the barrier and provides an easier way to share them |
| [11:06:08] | <ludwa6[m]> | mstenta[m]: oh, yeah: it makes the whole idea of writing import / export/ reporting modules kinda old-fashioned, doesn't it? puts the power of data-driven farming right in the hands of farmers, where it belongs. |
| [11:06:18] | <symbioquine[m]> | For example, I might in the future do one-off data manipulation scripts [like this](https://farmos.discourse.group/t/translating-rotating-historical-geometr...) in JupyterLite. |
| [11:06:21] | <mstenta[m]> | indeed! |
| [11:07:02] | <symbioquine[m]> | Then folks could just copy/paste/customize without worrying as much about recreating my server environment. |
| [11:15:43] | <justgav[m]> | Good afternoon :). I'm in the process of loading up some seed genetic, and have done a few manually, noticed I can export via the asset viewer, is there a way to import the CSV or will I need to do it via the API? |
| [11:16:32] | <mstenta[m]> | justgav: yea farmOS v2 does not have a built-in CSV importer like v1 did (yet) |
| [11:16:48] | <mstenta[m]> | but there is a lot of good brainstorming for options in this forum topic: https://farmos.discourse.group/t/csv-importers-in-v2-x/942 |
| [11:16:56] | <mstenta[m]> | in general, though, yes: you need to use the API |
| [11:17:26] | <justgav[m]> | Okay, I'll write a JSON importer then, and bring in them in. |
| [11:17:38] | <symbioquine[m]> | <ludwa6[m]> "oh, yeah: it makes the whole..." <- In some ways, yes, but there's a balance there. Some features should centrally maintained for the whole community - and be versioned and have automated tests as part of their development process. Also many users won't be comfortable with the code-centric interface represented by JupyterLite. |
| [11:18:46] | <mstenta[m]> | yea - this gives us a very wide spectrum of possibilities! that's sort of what i meant by "bleeding edge" earlier... jupyterlite can allow folks to experiment with ideas which may eventually become modules! |
| [11:20:32] | <mstenta[m]> | symbioquine: would it make sense to open some issues on drupal.org/project/jupyterlite to sketch out next steps |
| [11:21:29] | <symbioquine[m]> | Yeah, sounds good |
| [11:21:48] | <mstenta[m]> | that's the only way i can keep things organized these days :-) |
| [11:21:55] | <symbioquine[m]> | I fixed the issue with the trailing slash in the url. |
| [11:22:32] | <mstenta[m]> | oh nice! |
| [11:22:34] | <symbioquine[m]> | The only other major issue I know of is the potential for direct access to the JupyterLite artifacts. |
| [11:23:34] | <mstenta[m]> | mm yea |
| [11:23:59] | <mstenta[m]> | oh was curious (haven't looked at your packaged code yet): does it include anything in the "content" directory, like Don's demo did? |
| [11:24:12] | <symbioquine[m]> | mstenta[m]: No |
| [11:24:17] | <mstenta[m]> | i feel like it should be empty personally |
| [11:24:18] | <mstenta[m]> | ok cool |
| [11:24:34] | <symbioquine[m]> | Also, I'm actually having trouble reproducing that access issue... |
| [11:24:42] | <mstenta[m]> | i'd also like to open some feature requests around potentially tying into drupal file management... |
| [11:25:23] | <mstenta[m]> | donblair: and I were chatting, he made this good point: |
| [11:25:23] | <mstenta[m]> | > i do think that jupyterlite as it currently works may be ... confusing to folks in terms of how its 'local files' behave |
| [11:25:28] | <mstenta[m]> | s/://, s/// |
| [11:25:36] | <mstenta[m]> | my replies... |
| [11:25:39] | <symbioquine[m]> | mstenta[m]: I'm happy to help maintain/shepherd the module, but I don't know much of that sort of stuff I'll be taking on personally... |
| [11:26:45] | <mstenta[m]> | > i wonder if the drupal jupyterlite module could somehow help to "persist" files...... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/fbdcaa0442...) |
| [11:27:05] | <mstenta[m]> | of course! no expectations - i appreciate all you've done already! |
| [11:27:23] | <mstenta[m]> | these are the kinds of things i might open issues for, as next steps... |
| [11:28:08] | <mstenta[m]> | taking those ideas a step further... another idea i had was: imagine if a farmOS module could ADD scripts to jupyterlite |
| [11:28:45] | <mstenta[m]> | i could see this being useful for "official" collections of scripts perhaps |
| [11:29:23] | <mstenta[m]> | maybe unnecessary though... one could still just "upload file" that they download from such a repo, without necessarily installing any modules |
| [11:29:57] | <mstenta[m]> | there are also some caching considerations to sort through - i've noticed that jupyterlite does not detect changes to the files after it's been loaded - everything is saved in indexeddb until you manually clear it (it seems) |
| [11:30:23] | <mstenta[m]> | (might just copy and paste this chat into a new issue to sort through ideas as a first step..) |
| [11:31:11] | <justgav[m]> | https://farmos.org/development/api Is there any more documentation or should I go schema surfing :P |
| [11:32:03] | <mstenta[m]> | haha good question justgav - that's all the docs we have, but farmOS's API is built on Drupal's JSON:API, which has a lot of docs here: https://www.drupal.org/docs/core-modules-and-themes/core-modules/jsonapi... |
| [11:32:11] | <mstenta[m]> | (we should really add a link to that from our docs) |
| [11:36:44] | <mstenta[m]> | symbioquine: do you have your repo easily accessible? can you push the 1.x branch to drupal.org? |
| [11:37:02] | <mstenta[m]> | i'll create a 1.x dev release (needed to create issues that reference it) |
| [11:37:19] | <justgav[m]> | That's okay, don't mind digging putting it together as I go |
| [12:50:28] | <symbioquine[m]> | ACTION uploaded an image: (223KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/UNLItAgEeui... > |
| [12:50:31] | <symbioquine[m]> | https://gist.github.com/symbioquine/7641a2ab258726347ec937e8ea02a167 |
| [12:52:05] | <symbioquine[m]> | ACTION uploaded an image: (998KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/bOQPeaeYFSq... > |
| [14:01:53] | <mstenta[m]> | 😲 |
