Example farmOS.py CSV import script

[paul121]

@walt

but it fails at run time on line 37 where you define the function: _get_plant_asset_plant_type(crop_name, plant_type_name) , returning the error message: SyntaxError: unexpected EOF while parsing .

Hmmm… I think this means there is a syntax error somewhere before line #37. An un-closed string could cause this issue - is it possible you modified one of the lines/variables above that (like the hostname or username) and have extra and/or missing parenthesis? The original file runs OK for me.

@walt

As you can see, the v2 schema downloaded from …/assets/plant page is designed to hold records of any “Asset type” (which indeed it does in my instance), while the v1.x schema is designed to hold only records of the “Plant(ing”, v1.x-speak) type -so if this were to cause an error on upload, i should not be surprised.

So this just depends how you design your import script! You could design the script to be hard coded for a specific asset type, read the asset type from a column (like the current 2.x CSV export has), or even take the asset type as an argument to the script.

The import_plantings.py example is quite simple - it only reads a few columns from the CSV file and the asset type is hard coded to be plant: farmOS.py 2.x Import example · GitHub

@walt

More generally, i have to ask at this point: is it reasonable to assume that we can download a list of our plantings from farmOS, edit records as appropriate offline (so long as we keep the same “Asset ID”, the names may change if we plant in a different bed than originally planned), append new records as appropriate (leaving Asset ID field blank for assignment by farmOS), and then upload the lot via this script of yours, such that all records are created OR updated as appropriate, without any duplication of data?

Not with this example script - but with a script it would be possible, yes! That said, I think that ideally the use case you are describing could be covered with the core farmOS CSV importers UI - we are working on this here: https://www.drupal.org/project/farm/issues/3151244

But it also seems like it could be useful to provide some farmOS.py/farmOS.js import scripts that would be compatible with the format of the current CSV exports. This script could do what you are describing, update existing OR create new. Although I think the utility of such a script wouldn’t match the fully functioning CSV importer we are building.

@walt

but we finally have our harvest worksheets rendered into form that should be uploadable into farmOS, if i’m understanding this right:

Just to be clear - I imagine you’ll need to create custom script(s) for importing these. The CSV importer UI would likely work for a subset of the fields you are importing but the more complicated pieces might require a script (things like quantities, entity references, special logic, etc). A hybrid approach might work too! It really depends on the format of your worksheets and what all you are trying to do. I think it would be worthwhile for you to work on a custom script right now.

Maybe you could open a new thread for specific questions regarding these worksheets? An example would help too!