Reporting service data model extension

[mafragkopoulos]

It would be useful for the data model of reporting service to support several more things in order to be feasible for eco-shemes -related usage.

Indicatively:

1. Apart from start and end times, also a simple date is important.
2. Free text attribute is useful on all operations.
3. In both fertilizations and plant protection operation application method (e.g. foliar_spay, soil_application) is also useful.
4. Soil management operation is common along with method (e.g. rotavator, cutter)
5. Agricultural care operation is useful along with method (e.g. prunning, tying)
6. Harvest operation is also crucial along with product type and output amount/unit.

These additions will make reporting service an ultra fit for commercial farm calendars' official reporting!

[JoleVLF]

@mafragkopoulos
Hello,

1. First suggestion is confusing me. We already use dates (not datetimes) and both are optional and not inclusive (if one is used, second not etc.). Also reporting API only forwards filters to Farm Calendar, so query logic depends on FC implementation.

2. Free text attribute would also depend on service which provide data, implementing them on RP is not a big issue.

3 (and others) - Filters depend on API from FC (so any information we have depend on JSONLD representation of data).

[mafragkopoulos]

@JoleVLF thank you for the response.

As we are not using the Farm Calendar but instead our own solution on this side we would like to explicitly know what is supported exactly.

As state of reference we are taking the jsonlds in this link:
https://github.com/agstack/OpenAgri-ReportingService/tree/main/scripts

Please update jsonlds if possible and if more attributes that also mentioned in the first post are available.

[arruda]

@rapw3k can you help us map out the list mentioned in this issue? are all of these concepts already present in OCSM?

[JoleVLF]

@mafragkopoulos We did not receive any feedback to @arruda question above.
Also jsonlds used you can see that when FC is not used json files are sent with data to generate reporting.
Not sure how free text attributes and other filters would be usable here when we generate RP from JSON files directly.

If you have your own solution from where data must be gathered, it is a new feature to be discussed (to point to specific new endpoints to get data)