-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export crop plans #21
Comments
Yes @cora: This (as explained in this issue i posted before i saw yours -oops!) is a pressing need for me -and anyone else using the module, i imagine. As to the doubt you raised in response to my Issue report, @mstenta , i.e.:
Both logs AND assets related to the Crop Plan for export are relevant and should be included... But if it's too complicated to aggregate those in one export, then perhaps they can (as proposed above) be filtered and exported separately, using existing affordances -yes? |
@ludwa6 Yea I think that makes sense. It would be great to devise a common export format that includes everything. Or eve a combination of different export options! In 2.x there will also be more abilities to access Plan data via the API - so I could see this being implemented outside of farmOS too, potentially - tailored for specific needs. A Python script + farmOS.py could be written to format it into a CSV in a very customized way. We are currently discussing a core data architecture question, in that regard: https://www.drupal.org/project/farm/issues/3187877 |
Feedback from Cora at Wolfe's Neck:
The text was updated successfully, but these errors were encountered: