0.7.0
Sprint Weeks: 7/23/2020 - 8/4/2020

Plan Summary

  • Quantification updates
    • Error handling UX improvements
    • Ability to see partial quantification results
  • Data import updates
    • Open source validation module for input files
    • Latest data specification support
    • Managing the specification in version control for better collaboration
  • Marketplace updates
    • FIFO NRT sales
    • Checkout page changes
    • Supplier profile improvements
    • Verification report improvements
    • Certificate UI changes
  • NRT Issuance improvements
  • Admin page updates
  • Bug fixes

Quantification updates

Error handling UX improvements

A number of changes to the app's error handling UX will be making it's way to the app to make it easier to see and understand the various types of errors that a project might experience during quantification. Currently, the app reports errors using an obscure UI (see below).
Before
To make matters worse, a certain class of errors (COMET errors) don't even indicate which field is throwing the error. To remedy this, we are consolidating error handling into a new UI that iterates on our learning here. Check out the preview below!
After

Ability to see partial quantification results

One of the more frustrating parts of quantification is the fact that when a project runs quantification with a number of fields and a subset of those fields pass quantification whilst the remainder result in errors, the app has no way of allowing the user to see the results of the quantification for fields that did pass. To fix this, we will be enabling the ability to hide errors so that the underlying quantification can be seen.

Data import updates

Defining a specification for the data underlying a project has proved to be highly valuable for us. It allows the Nori product team to think about the data in a way that is more sustainable, maintainable and scalable than what currently exists in out intake sheet. As such, it is the foundation for two major milestones:
Creating a universal data specification allows us to:
  • Allow any partner or data manager to create projects from external data using a platform agnostic specification
  • Build a new foundation for projects and open a new pathway forward that will eventually allow us to remove the project spreadsheet dependency from the application\

Latest data specification support

The first data import milestone is to support the more recent version of the data specification that we have started sharing with partners and data platforms.

Open source validation module for input files

The second data import milestone is to create a module that third parties can use to validate data import files. Doing this allows partners to start creating import files prior to us having the full import flow finished and integrated in the app. This way, once the new specification is supported in the app, users will be confident that importing their files won't result in an error

Managing the specification in version control for better collaboration

For the past two iterations of the data specification, collaboration has been limited to a google doc shared with private parties. Going forward, the data specification and collaboration will be visible to all in our public GitHub repository.

Marketplace updates

Up until recently, Nori has only had to deal with a single issuer of NRTs. Soon, we will have multiple issuers of NRTs-- and because creating static artifacts like supplier profile pages and verification reports is not realistic or scalable, the Nori product team is implementing a bunch of changes.

FIFO NRT sales

Currently, all sales of NRTs come from an allocation of a specefic supplier's issuances. Going forward, additional issuances will be added to the end of a first-in-first-out (FIFO) queue. This means that additional issuances will be sold only once the previously added issuances have sold out.

Checkout page changes

Misc style and content changes will be made to the preview of the certificate.

Supplier profile improvements

Currently, supplier profiles pages are created statically. Going forward, any time a supplier creates an issuance, they will also create a public supplier profile.
A number of improvements are being made to the public supplier profile page (which is linked to every certificate that it a supplier issued NRTs for). This includes things like sale stats and project activity among other things. Check out the update preview below!
Supplier public profile improvements

Verification report improvements

Currently, since supplier profiles pages were created statically, verification reports for supplier projects were also static. Going forward, verification reports will be dynamically tied to the supplier project to which they belong.

Certificate UI changes

Misc style and content changes will be made to the certificate shown

Marketing site messaging changes

Currently the marketing site uses static messaging for certificate checkouts. We will be updating this so that it is dynamic enough to detect who the new supplier is that is issuing NRTs for their certificate purchase

NRT Issuance improvements

  • We are looking into ways to more strongly tie a specific quantification run to NRT issuance
  • Our first batch of issuances required us to statically set Issuance ISO locations. We will be implementing the ability to allow issuances to be created using different ISO locations for future batches.

Admin page updates

A few additional properties will be added to various orders pages in the admin UI to improve our ability to inventory useful metrics around sales

Bug fixes

  • fix a bug related to total fertilizer amount applied not being imported correctly
  • fix a bug that results in quantification always using tons/acre during quantification even when gals/acre was specified
Last modified 1yr ago