There are some instances where we want to be able to auto-generate specific logs when importing assets into farmOS.

This will allow the following columns to be added to asset import CSVs:

  • Location (creates a movement log)
  • Seeding/transplanting dates/locations (creates seeding/transplanting logs)
  • Inventory (creates inventory adjustment log)

Comments

m.stenta created an issue. See original summary.

m.stenta’s picture

another nice one would be to add a medical observation that is simply the contents of another column.

-https://github.com/farmOS/farmOS/issues/89

m.stenta’s picture

Requested again in https://github.com/farmOS/farmOS/issues/306

Specifically needed for migrating seedings/transplantings from FarmData:

Seeding and Transplanting Logs have Movement (Area and Geometry) field collections, but their importers do not have a Movement column. So bulk imports of Seeding and Transplanting Logs from other databases cannot currently capture this valuable information.

This issue stems from a longer discussion I've been having with @mstenta in issue #199, where I have been slowly migrating a substantial FarmData database over to a new FarmOS platform. Until this issue is fixed, I cannot import ~5 years of seeding and transplanting logs from that database, since each log carries valuable Area data.

m.stenta’s picture

See this comment (and the one after it) for some thoughts on how to implement this: https://github.com/farmOS/farmOS/issues/199#issuecomment-570353027

m.stenta’s picture

@megandalster Uploaded a zip file to that GitHub issue with some code he is using for importing locations: https://github.com/farmOS/farmOS/issues/199#issuecomment-659446449

m.stenta’s picture

Status: Active » Closed (won't fix)

Closing this as "won't fix" for the 7.x-1.x branch. Importers are still TBD for 2.x (see #3151244: [META] farmOS 2.x Importers) and the community is exploring alternative options as well: https://farmos.discourse.group/t/csv-importers-in-v2-x/942