You are here:

Release Notes, July 27, 2023


This release features an improved MRV stratification service. The stratification service will no longer update the stratification record’s needed id when there is a failure. This was previously causing fields to get stuck in a loop and could never be properly stratified. The whole stratification process has been redone to allow the field to be re-queued for stratification. Some fields can run into problems from upstream connections/services the stratification uses. Instead of just automatically failing, the new service updates will resend the field a second time. This resend has vastly improved the stratification success rate. Another change to the service has been the ability to change a sampling density. The MRV will now allow the project to change to the desired sampling density. This change would affect all producers/fields in the project. Fields that already had existing stratification would need to be resent for the updated sampling density to apply. The full list of release notes has been included below.

Added Features

  • Updated stratification density ability. The MRV will now support projects changing their stratification density. This change would affect all producer fields in the project and would only apply to fields that need to be stratified. If the producer already had fields stratified, those would need to be re-stratified to reflect the project’s new stratification density. 

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.
  • The Fields and Practice Changes Review & Final Review and Submission modules require the user to save before the comments and markings are saved in the database. If the reviewer leaves the review before saving their progress, it will not be saved and the reviewer will need to start over.

Fixed Issues

  • The MRV’s stratification service has been updated. The stratification process has been enhanced to resolve failures from upstream data sources/connections. Fields sent to the stratification service will require and attempt a second time when there is a failure. Additionally, fields that have a failure will keep the same ID while being re-sent to avoid the previous “stuck in a loop” issue.
Table of Contents