How Can We Help?
Release Notes, February 27, 2023
Highlights
This release contains a couple of new features and fixes but mainly changes how the MRV’s behind the scenes process works. The MRV’s development process has been updated to allow easier tracking between pushed changes. Migration scripts can no longer alter existing database views or functions. The MRV will now have its views and functions in a source file. Going forwards, the migration can only be used to update the table, type, enum and data operations. Another change to the process was the ability to spin up individual Hasura instances for each branch of the MRV’s development. This release includes additional validation for fields marked with the “conversion of cropland to grassland” practice change. The additional validation will prevent the user from continuing in later years with the same field not marked as continuing the conversion practice.
One of the fixes included in this release fixed an issue with fields using the “pending enrollment” practice change. Fields with the marking in earlier years did not update correctly when the field was officially enrolled in later years. When the field is enrolled in a later year, the field’s initial year will be updated to be the year of the enrollment. The full list of release notes has been included below.
Added Features
- Additional validation has been added to the MRV for handling fields marked with the “conversion of cropland to grassland”. This additional validation will ensure fields that are marked with the conversion practice continue that marking in the following collection years.
- The project administrator and staff roles are now able to remove soil sampler users from the project(s) to which they have been assigned. This does not disable the soil sampler from the MRV since they might be tied to different projects.
- The MRV’s build and development process has been modified for cleaner development and deployment capabilities. Migration scripts will no longer alter views and functions and will be edited like other source files. This allows for better tracking when investigating issues. In addition to other changes, the deployment process now sets up a Hasura environment for each development branch of the MRV.
Known Issues
- Producers that have self-registered on the registration page will show a status of N/A on the MRV’s admin pages. Once the producer’s enrollment request is approved or denied, the producer’s status will be updated.
Fixed Issues
- Fields that were previously marked as “pending enrollment” in earlier collection/enrollment years will now have their initial enrollment value updated to the correct year. This was previously remaining the same and causing issues in both reporting and other MRV workflow areas.
- The map drawing icons were updated to the correct MRV icons. All map drawing functionality uses the same buttons to keep the user familiar with what the button/functionality does.