question! Is there a ‘export all’ kind of fuctionality in FarmOS for CSVs? I’m just looking into the csv importers / exporters. A few quick notes on them as is today:
- It would be great to export the CSV in the exact format as the CSV Import (right now they aren’t the same). The reason is as someone trying to set this up, the by far simplest starting point is to export what I have, whiddle it down to my repeated activities, and then save them knowing with confidence they are formatted correctly.
- If I could basically export everything (meaning assets, logs, and tax terms), I could probably pretty easily use them to quickly generate new stuff, either in a big fancy spreadsheet, a big fancy baserow, or with big fancy llms that can validate entered data against actual’s (so things don’t break). I can do it manually now but it’s a lot of buttons presses.
It’s important to understand that the CSV exports do not include all data!
(^ I started writing that later in my comment but decided to move it to the top and make it bold so everyone reading this sees it. 
)
CSVs are inherently limited because they are 2-dimensional, while most data in farmOS is multi-dimensional. The CSV exports that farmOS provides only provide a subset of the data available in each record, and the CSV importers can only import a subset of potential data.
No, right now each asset type, log type, and quantity type has its own export format with its own columns (since different types can have different fields on them). In theory, a module could be written that calls out to all of those and packages them into a single zip/tarball, but that doesn’t exist right now.
Also there are no CSV export options for plans/plan records, users, files, or taxonomy terms currently.
Relevant issue (dating back to farmOS v1 in 2017): https://www.drupal.org/project/farm/issues/2900239
Tl;dr: Still some work to do to align them, but we’re closer now than we’ve been in the past.
1 Like