Soil Health V1
Purpose
To augment the current soil amendment task in order to capture the data necessary for understanding the impacts of different types of soil amendments on soil health, biodiversity, carbon sequestration, and a reduction in greenhouse gases.
Stakeholders
Hannah Wittman
Sean Smukler
Grants involved
ScotiaBank
RBC
OSC4
Hannah’s new new frontiers
Release window
Spring
Scope
Epic | User story | Additional context |
---|---|---|
Augment the soil amendment task | As a user applying a soil amendment I want to be able to select multiple purposes to reflect the reality that many soil amendments have more than one purpose | Right now purpose is single selection.
|
Augment the soil amendment task | As a user applying a soil amendment I want to be able to document the important attributes and ingredients of that soil amendment so that I can understand how it will impact my soil over time | Attributes and ingredients TBD. See API - Version 1 (current) for some guidance. The ability to manage these at the product and product inventory level will be introduced with Soil Health V2. |
Updated scope after discussion between David, Loic and UBC research team available on LF-4213. | https://lite-farm.atlassian.net/browse/LF-4213 https://github.com/LiteFarmOrg/LiteFarm/releases/tag/v.3.6.5 | Dev note from Duncan: |
Things to be investigated
Question | Answer | Notes |
---|---|---|
Should we just patch this in before delivering Animals? | This could be a good candidate for Sprint 85 | @Lite Farm to follow-up with Hannah about attributes for the soil amendment task. |
Should the current values for “Purpose” be modified? |
|
|
Is it sufficient to say I’m applying soil amendments to an entire field or should there be more granular options - e.g. specifying a percentage, drawing a polygon, or selecting a particular point? |
|
|
Right now, you can select any number of fields to have soil amendments applied. However, you can only select one product and quantity. Should this be expanded to allow a different product and property per field (or per crop plan)? If we do support that, should more than one soil amendment task be generated? |
|
|
What attributes and ingredients should be documented in each soil amendment task? | Starter list (to be verified by Hannah):
| See API - Version 1 (current) (fertilisers, green_manure section). From the proposal:
|
Additional resources
API - Version 1 (current) (See fertilisers, green_manure sections)