| [04:51:12] | * phschafft has joined #farmos |
| [04:59:37] | * phschafft has left #farmos () |
| [10:44:39] | <Greg[m]> | mstenta: I have a question but maybe it's relevant for others. I'm developing a workflow for my friend Nano for a soil health benchmarking project, and the initial part of the flow (onboarding a farm via an intake form, an... (full message at <https://matrix.org/oftc/media/v1/media/download/AdVoV5FZRKwST0lxAitwecCD...) |
| [10:44:43] | * mstenta has joined #farmos |
| [10:45:26] | * mstenta has joined #farmos |
| [10:46:14] | * mstenta has joined #farmos |
| [11:14:15] | <mstenta[m]> | <Greg[m]> "mstenta: I have a question but..." <- > In short, it's a bit hard to know when it's best practice to spin out modules, and when to just review / copy / modify bits. |
| [11:14:15] | <mstenta[m]> | Yep agreed! It can be a nuanced choice... |
| [11:16:15] | <mstenta[m]> | mstenta[m]: Ultimately, generalizing the `farm_rcd` intake form would require work on that end too, which would slow down your process, so you might be best off just copying and modifying it. |
| [11:16:48] | <mstenta[m]> | mstenta[m]: Here is the form class for the intake form: https://github.com/farmier/farm_rcd/blob/1.x/src/Form/IntakeForm.php |
| [11:17:36] | <mstenta[m]> | mstenta[m]: When that form gets submitted, it creates a `rcd_intake` log: https://github.com/farmier/farm_rcd/blob/2d3b650b2d298afe3e5d4b8ebfe6404... |
| [11:18:05] | <mstenta[m]> | mstenta[m]: This is a custom log type with all the fields collected in the form. So you would need to make something like that for yourself as well. |
| [11:18:22] | <mstenta[m]> | mstenta[m]: But that's an important decision you need to make first: do you want/need the intake submissions to be logs? |
| [11:18:41] | <mstenta[m]> | mstenta[m]: We decided to do that for the RCD module, but maybe you don't need that. |
| [11:18:52] | <mstenta[m]> | mstenta[m]: Another option to consider is the Drupal Webform module: https://www.drupal.org/project/webform |
| [11:19:02] | <mstenta[m]> | mstenta[m]: That allows you to build forms in the UI. |
| [11:19:26] | <mstenta[m]> | mstenta[m]: And it saves the submissions in their own database table, so there's no need to create new log types or worry about their data model. |
| [11:20:16] | <mstenta[m]> | mstenta[m]: I considered using that for the RCD intake, and we may "upgrade" to that in the future... it would allow more customizable intakes for each RCD |
| [11:20:31] | <mstenta[m]> | mstenta[m]: Logs were an easy first step, which can be migrated away from if we go that route. |
| [11:20:42] | <mstenta[m]> | mstenta[m]: So maybe you can be the ones to explore that option for us. :-) |
| [12:08:58] | <Greg[m]> | <mstenta[m]> "So maybe you can be the ones..." <- hmmmm... ok! Maybe I'll check that out. I think what's key here is that it's easy to 'connect the dots' and enforce from the form to the database (saving the results to organizations--farm for example). If we add too many intermediate steps (like another db that's not a log for storing the form results) I get nervous about adding more steps... but maybe. I will investigate - thank you! |
| [12:09:58] | <mstenta[m]> | Greg[m]: > (saving the results to organizations--farm for example) |
| [12:09:58] | <mstenta[m]> | The farm_rcd intake form does not save anything to the organization entity |
| [12:11:06] | <mstenta[m]> | mstenta[m]: we have a separate "intake review form" that RCD staff use to "continue" with (or "abandon") an intake, which handles spinning off an organization entity (or finding an existing one), creating the resource conservation plan, and linking things together |
| [12:11:59] | <mstenta[m]> | mstenta[m]: part of the reason is to prevent landowners from accidentally creating multiple orgs if they submit the intake more than once |
| [12:12:16] | <mstenta[m]> | mstenta[m]: so it's staff who decide to create a new one or use an existing one |
| [13:04:13] | <Greg[m]> | <mstenta[m]> "so it's staff who decide to..." <- yes... I like that approval flow and do think I want to replicate it here event. It's the right design for lots of things IMO... |