Knowledge Base
Search…
0.5.X
Sprint Weeks: 5/26/2020 - 6/9/2020 (0.5.0), Sprint Weeks: 6/9/2020 - 7/9/2020 (0.5.1)

Plan Summary

  • Quantification improvements
    • NRT Quantification for grandfathered years
    • Detecting overlapping planting/harvest dates
    • Misc improvements
  • Smart Defaults improvements
    • Allowing users to edit defaults from the preview table UI
    • Adding the ability to select a subset of years before importing defaults
    • Adding an FAQ
  • Giving users the ability to opt in to beta features
  • Project reporting and statistics UI πŸ“ˆ
    • Total acreage reports in the admin interface and in the app
  • Smart Defaults documentation πŸ“–
  • Smart Defaults public beta launch πŸš€
  • Quantification bug fixes 🐞

Quantification improvements

NRT Quantification for grandfathered years

Currently, the application is using an out of date quantification UI that does not give all of the relevant information surrounding NRT quantification. In addition there are a number of manual steps that we have to execute external of the product to finish quantification for any given project.
To address this, we will be making some adjustments to automate this manual steps we currently take as well as to implement some improvements to the UI so that additional information about a project's quantification run is made available (such as the number of eligible grandfathered NRTs).
Quantification UI updates (mock)

Detecting overlapping planting/harvest dates

For Smart Defaults and some data imports/entry, sometimes the typical planting and harvest dates overlap one another (i.e., a second crop was specified as being planted before the first crop was removed or harvested). Sometimes this happens when one crop is planted into the other before harvest or that the crops were planted or harvested at different times. In either case, COMET farm considers this invalid and as a result will throw an error.
Unfortunately, we see adjusting these dates behind the scenes to be too problematic and we are making the decision to not try to automatically resolve dates by adjusting them automatically when sending the data off to COMET farm.
That said, there is currently no feedback given to the user about if and when this issue exists in the user's sheet. As such, we will be implementing a detection step for this type of data overlap and will appropriately handle it as an error message that is collected and shown to the user when they try to run quantification.

Misc improvements

  • Verify the server-side field area matches the value found in the field tabs area named range when performing quantification
  • Provide visual feedback to the user if their project is still using spreadsheet versions that are lower than v3.1
  • Remove an existing requirement that requires users to have more than 10 years of data after the switch year

Smart Defaults improvements

Allowing users to edit defaults from the preview table UI

Currently, the Smart Defaults UX flow does not allow users to edit the automatically assigned defaults that we detect before they get imported into the project sheet. However, we want to get our customers a complete data set as quickly as possible whilst also giving them a good mechanism to correct some of the defaults before they get added to the sheet. This is important because it's usually better to make those changes prior to applying them to the sheet than trying to edit them after, which slows everything down.

Adding the ability to select a subset of years before importing defaults

We are working to allow customers the ability to select / deselect years to import into the sheet when setting up Smart Defaults. This would allow customers the specificity of different defaults for a subset of years.

Ability to specify multiple events for a given crop activity

Although the sheet already supports the ability to specify multiple events for a given crop activity, Smart Defaults does not currently have the ability to do this. However, we know many farmers will stagger multiple events under a single activity across a longer period of time and that differences might be more than just amount and date applied. As such, it is important to give users the ability to do such a thing when they run Smart Defaults.

FAQ content for Smart Defaults

We are currently working on collecting FAQ for Smart Defaults. When we have finished collecting and polishing the questions and answers for this section, they will be added to the application. Check out the preview below!
Smart Defaults FAQ preview

Giving users the ability to opt in to beta features

Currently, the only way to opt in to all beta features is to use an employee account. However, this is not ideal and we are working to allow users the ability to opt in to these features with non-employee accounts.

Project reporting and statistics UI πŸ“ˆ

Total acreage reports in the admin interface and in the app

Currently, the process of detecting how many acres are enrolled for a given field, project, user, or in total across all users is entirely manual. We are exploring ways to improve this reporting for both employees and for users and will implement a solution soon.

Smart Defaults documentation

We are working on creating more robust product documentation. A section of this relating to Smart Defaults will be worked on and made available in the near future.

Smart Defaults public beta launch

During this sprint, the product team is going through a launch readiness checklist. When we satisfy all of the constraints we will make Smart Defaults available to the public as a beta feature.

Quantification bug fixes

  • Fix a bug that could cause quantification to credit reduction in emissions
Last modified 1yr ago