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).