/
2018-06-27 Weekly Check-in

2018-06-27 Weekly Check-in

Owned by Ben Leibert
Jun 27, 2018

Date

Attendees and/or Technical Stakeholders

Discussion items

Status Update

The last week has been a rollercoaster. Our progress and outlook looked good at other times, and the opposite at others. Throughout it, Timoteo Chaluco (Unlicensed)'s ability and willingness to answer questions whenever they arose has been critically important and quite appreciated. It's hard to understate the importance of Craig Appl (Unlicensed)'s contributions as well. He's singlehandedly unblocked our team more than once this week.

At the moment, we're unblocked and agreed that showing the system in use this Friday is necessary and attainable.

ColdTrace

The NexLeaf team finished the planned public-facing changes to their endpoints today. I incorporated the changes into our system and will know tomorrow whether the related process scheduled to run late tonight will succeed. Our public-facing UI remains unaffected by these changes and is something we reviewed as a team several weeks ago.

Null Stockout Entries

Q: Given that SELV contains a number of NULL stockout fields, how do we calculate and present the percentage of facilities which have incurred stockout events?

A: We should display the raw numbers, which are the number of facilities which have:

  1. Not reported stockout data.
  2. Reported stockout data (regardless of whether or not it denotes an stockout event).
  3. Reported stockout data which indicates they incurred a stockout.
  4. Reported stockout data which indicates they have not suffered a stockout

Additionally, because raw values aren't user friendly, we should display a simple percentage as follows:

(Facilities which have reported a stockout)   /  (Facilities which have reported non-null stockout related information)

Schedule

It's important that we demo this Friday - we can't slip again. We can incorporate feedback, however, even into next week. Additionally, there are some areas we know will need work even beyond this week. They are:

  • Setting up server monitoring courtesy of Scalyr. (This was intentionally postponed so that the SELV+ project can benefit from the related work being done for the Gap project.)  
  • Updating the server's hardware and configuration settings as we get a better feel for its runtime characteristics and performance. (Having Scalyr in place will help with this.)
  • Improving user interaction. The data validation performed by the server (NiFi) is currently somewhat crude. We're also limited at the moment in terms of how we can accept eSISATFE files via email. In general, the ways in which users submit data via email and the error responses they receive in kind may need improvement.