techmatters / terraso-product

Non-engineering tasks or tasks that have significance across repos in Terraso.
0 stars 0 forks source link

Effervescence data input #167

Open ltseng opened 1 year ago

ltseng commented 1 year ago

While not (yet) relevant for the Soil ID algorithm, some soil scientists can interpret effervescence/carbonates to help determine soil.

Effervescence is the measurement, and is an indicator of carbonates in the soil.

References

Spec

Design

Post-Capri Figma section

### Tasks
- [ ] https://github.com/techmatters/terraso-product/issues/301
- [ ] https://github.com/techmatters/terraso-client-shared/issues/10
- [ ] https://github.com/techmatters/terraso-backend/issues/623
- [ ] https://github.com/techmatters/terraso-product/issues/992
- [ ] https://github.com/techmatters/terraso-product/issues/1005
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/475

Acceptance criteria

ltseng commented 1 year ago

Note: we are still trying to figure out whether or not this top-level Carbonates data input method should be synced with the carbonates submethod within Soil Limitations, and if so, how.

ltseng commented 1 year ago

Update: there is no need for any level of syncing, full steam ahead!

CourtneyLee333 commented 3 months ago

@DerekCaelin Do you want to include the following in this issue, or are there separate ones?

CourtneyLee333 commented 3 months ago

Oh, I see the list above that encompasses those things. I'll update the verbiage to make it more clear, and update the Figma references.

CourtneyLee333 commented 3 months ago

@DerekCaelin do we also need to add Effervescence to Soil ID screens - Site Data soil properties chart, Soil Info Sheet chart? I think yes.

DerekCaelin commented 2 months ago

Carissa: estimate 3 for front end, 3 for back end