The types of queries we get for data extraction from FarmOS are very variable - they different depending on the user (scientists, farm managers, operators) and purpose (carbon audits, invoicing, scientific reporting). In short, this diversity of requests makes it very difficult for us to create custom reports - the needs are too many and too diverse.
Instead what we would like to do is create an SQL style query (if possible) and then allow users to save and share that query. For example, if I want to extract pesticide records every month for specific fields, I can create the query, export the data and save that query to my own FarmOS account so I can re-run it every month. Alternatively, if someone else requests data from me (e.g. all the management logs from a specific field associated with one of their field trials) I can run the query and they can save the link.
Marked as an extra large issue, as this may need to be broken down into smaller sub-tasks.
The types of queries we get for data extraction from FarmOS are very variable - they different depending on the user (scientists, farm managers, operators) and purpose (carbon audits, invoicing, scientific reporting). In short, this diversity of requests makes it very difficult for us to create custom reports - the needs are too many and too diverse.
Instead what we would like to do is create an SQL style query (if possible) and then allow users to save and share that query. For example, if I want to extract pesticide records every month for specific fields, I can create the query, export the data and save that query to my own FarmOS account so I can re-run it every month. Alternatively, if someone else requests data from me (e.g. all the management logs from a specific field associated with one of their field trials) I can run the query and they can save the link.
Marked as an extra large issue, as this may need to be broken down into smaller sub-tasks.