Soil depth intervals - Part 1

[ltseng]

User Story

• When a project is created, the project should be set to use LandPKS soil depth intervals by default. The project manager can also select NRCS depth intervals, create custom ones, or set "None Specified." See spec for specific intervals
• As a site or project manager, if I select custom depth intervals at the project level, I can create and name up to 20 different custom default soil depth intervals between 0 and 200 cm in the US and international LandPKS apps.
  • Names must be unique
  • Names can use up to 10 characters
  • Depth intervals cannot overlap. One interval can end on the same integer value as another one begins (e.g. 0 -2 cm and 2 - 4 cm)
• These soil depth intervals should be common across all data input methods for the site or project
• As a site or project contributor, I can add another custom soil depth interval that does not overlap with the ones set by the site or project manager, if custom intervals have been specified.

### Design
- [ ] https://github.com/techmatters/terraso-product/issues/205
- [ ] https://github.com/techmatters/terraso-product/issues/206

### Front end
- [ ] https://github.com/techmatters/terraso-client-shared/issues/11
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/456
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/381
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/502
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/975

### Back end
- [ ] https://github.com/techmatters/terraso-backend/issues/622

Acceptance criteria

• I can only set custom depth intervals for sites or projects I manage.
• I can only add more custom depth intervals on a per-site basis for sites I have contributor access to
• Deleting a default custom soil depth interval should also delete all data collected at that depth.
• Corresponding audit log entries should be created for any create/edit/delete action taken by authenticated users in the site and project audit logs
• Analytics should be collected according to the spec document

Custom soil depth intervals Test cases

### Bugs
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/504
- [ ] https://github.com/techmatters/terraso-mobile-client/issues/943

### Out of Capri

[CourtneyLee333]

@ltseng I wonder - can the project manager decide whether or not the contributor can add more intervals? Or, does the contributor always have the option to add intervals that are outside of the required intervals?

And, don't we have a scenario where a contributor or manager can determine the intervals per site, and override presets, when they encounter soil horizons that are different than the presets?

[ltseng]

The contributor can always add more intervals on a per-site basis for sites that are unaffiliated or are part of projects. In both cases, the contributor can only add intervals that do not overlap with any other custom ones that have been defined, whether by the project manager or by another project/site contributor.

The scenario you mentioned is covered partially by the specified functionality. I say partially because it only works for the case where project managers have created custom depth intervals for part of the possible 0-200 cm range (say, 0-25 and 25-30), but the project contributor wants to record observations for the uncovered depths (30-200).

What is not covered is the scenario where the project contributor wants to modify the depth intervals set by the project manager, but only for their given site. So, in the previous example, they would not be able to change it to 0-10 cm and 10-30 cm, for example. I'm not entirely sure how to make that work. I'm also not sure how common this scenario would be.

If this is a common scenario, perhaps we need to propose a new requirement - if the project manager hasn't specified any depth intervals at the project level, the any project manager or contributor can choose to override the standard default depth intervals (i.e. LandPKS and NRCS) and use custom depth intervals per site. But that seems potentially tricky to design.

What are your thoughts, @CourtneyLee333?

[CourtneyLee333]

I also don't know how common or significant the scenario will be where the soil horizons are different from the pre-set intervals. I've included some questions about this in the notes for the next BLM meeting.

[ltseng]

@david-code and @ajabeckett -

@CourtneyLee333 and I conferred and made the following changes, which should be reflected in the user story above:

• Remove the toggle for "Soil Pit Required" -> When a project is created for the first time, it will default to using LandPKS depth intervals. The project manager can then go in and change the depth intervals to NRCS, Custom, or none required (i.e. per-site depth intervals).
• Independently, when a project is created for the first time, it will by default have slope, soil texture and rock fragments, and soil color required.
• When the project has either LandPKS, NRCS, or Custom depth intervals chosen, they will see a version of the screenshot below with the circle icon for required data inputs next to Slope, Texture, Rock Fragment, and Color

• When the project has depth intervals set to "None specified," they will see a version of the screenshot below, with the circle icon for required data inputs next to Slope only. Then, as the data collectors create depth intervals, each depth interval will automatically be populated with similar rows with circle icons for texture, rock fragment, and color

• The project manager will have the option to not require any data inputs, but that will be a change they have to intentionally make to the default project requirements. In the case where all data requirements have been toggled off:
  • If they have LandPKS, NRCS, or custom depth intervals specified at the project level, data collectors would simply see a list of the depth intervals, with the three dots/More icon next to each depth interval, from which data collectors could select data inputs on an ad hoc basis.
  • If project depth intervals are set to "None specified," data collectors would need to create depth intervals, and then interact with the tree dots/More icon in order to select data inputs on an ad hoc basis.