The idea of seasons is as follows: Users can create a season for a farm. A season has a start and end date. When using the application users can select a season and see only the assets and actions active in that season. In that way information shown to the user can be more specific, default dates more helpfull and we prevent issues when working with "years". Also users can have the ability to adapt seasons if required, make it longer or shorter. Not sure if seasons should be allowed to overlap.
Implementation can be to add a table connected to farm, adapt all functions in fdm-core to accept a season id and an option for the user to select a season in the app
The idea of seasons is as follows: Users can create a season for a farm. A season has a start and end date. When using the application users can select a season and see only the assets and actions active in that season. In that way information shown to the user can be more specific, default dates more helpfull and we prevent issues when working with "years". Also users can have the ability to adapt seasons if required, make it longer or shorter. Not sure if seasons should be allowed to overlap.
Implementation can be to add a table connected to farm, adapt all functions in
fdm-coreto accept a season id and an option for the user to select a season in the app