Smart Defaults improvements
NRT Quantification for the latest version of the data sheet
Smart Defaults research
Allow users to edit detected activity data before Smart Defaults imports it into the data sheet
Explore how we can support specifying a regenerative practice switch year when running Smart Defaults
Smart Defaults tech debt
Improve the UX around liming and burning Smart Defaults sections. Currently, when the review the liming and burning preview table they will see an empty table. We are exploring different ways of handling this.
Fix a bug that is causing all prompts to say "tillage" in the preview description
Add support for crops that define no harvest events
Address overlapping planting/harvest dates for Smart Defaults as sending them off to COMET Farm for quantification in this way will result in an error.
Add support for perennial crops
Fix a bug that occurs when importing data from Smart Defaults for irrigation. Currently, the data is being imported with the wrong formatting applied that will cause errors when sending it off to COMET Farm
Currently, when users run Smart Defaults, they are given no chance to edit the data that we automatically detect. This task is to come up with a way to allow users to edit the detected data for all activity types before we import it into the data sheet.
We can detect tillage information-- but not to the degree of specificity we need for the COMET-Farm model run. As such, the growers need to tell us what their tillage practices were for all the years they didn't import / add records (which will vary year to year and field to field).
While Smart Defaults helps Growers + Data Managers get in something for all farm activities quickly, it doesn't allow flexibility in setting field practice defaults before and after a designated switch year (per field). Having the ability to set practice defaults for years since that switch year is important because when a switch year is known, the farmer likely (and should) know what the crop activities for years since that year are. However, currently, Smart Defaults only knows how to import all data up until the current year, even if the farmer knows that field practices changed at a given year.
The scope of this task is to find a way to allow the user to specify which years Smart Defaults will run for, or to allow the user to specify different defaults for field practices after a switch year.
Currently when running Smart Defaults we store intermediate step data in the browsers local storage. This is causing complex technical issues that are hard for us to debug. Additionally, storing data in the local storage of a browser means that that data cannot be drawn from when the user switches browsers or devices. As such, we will be moving the storage of this data from the local storage of a browser to a Nori database