2018-06-11 Daily Standup

Date

11 Jun 2018

Attendees and/or Technical Stakeholders

• Craig Appl (Unlicensed)
• Clay Crosby (Unlicensed)
• Antonate Maritim (Unlicensed)
• Wambere (Unlicensed)
• Felimone Amone Junior
• Timoteo Chaluco (Unlicensed)
• Dércio Duvane
• Christine Lenihan

• Ben Leibert

Discussion items

NexLeaf

• The proof of concept Ben showed looks good. It should include a legend, though, explaining how to read the charts. If possible, it should also have its dropdowns float in place and therefore always be visible.
• In descending order of specificity, facilities belong to a Central Level -> Province -> District. The current proof of concept shows provinces like Gaza and Niassa, and this is sufficient for the Dashboard. If NexLeaf provides the requisite images, though, it would be nice if the Dashboard could show District data as well. However, it isn't crucial. If need be, we can simply refer users to NexLeaf's website for additional detail.
  
  

Reports

• The MoH is working to provide CSV files with historical data that we can load into the Dashboard. Dércio Duvane will follow up with them.
• The RED/REC report is the only one which includes a complete dataset related to all prior reports. It's unique in that it's data can thus override previous submissions. Every other report includes data just for the most current period. 
  
  

Projected Stockouts

• Stockout calculations are based partly on stock information housed in SELV which will be a month or two old by the time they appear in the SELV+ Dashboard. Nevertheless, calculating projected stockouts based on them is valuable. This is because facilities should always have at least three months of stock on-hand. A projected stockout value that's a month old should therefore still be somewhat actionable.
• Dercio confirmed that it would be helpful to keep historical records of the projected stockout values.
• It would be sufficient and appropriate to show the projected stockout values in months. (For example: stock is projected to run out in 0.5 months, or in 1.5 months.)

Translations

• Mozambique uses Continental Portuguese. It's so similar to Brazilian Portuguese, though, that use of the latter within the Dashboard is just fine.
• Superset offer in-build support for Brazilian Portuguese, and we'll plan to use it.
• Superset's Brazilian Portuguese translations aren't complete. Clay Crosby (Unlicensed) thus created SD-21. The tickets comments describe how to contribute translations to the project. As they suggest, Portuguese translations reside in the https://github.com/apache/incubator-superset/blob/master/superset/translations/pt_BR/LC_MESSAGES/messages.po file. 
• The messages.po file looks to have been mostly translated already. Dércio Duvane will review it, though, and estimate the level of effort necessary to translate the rest. We have budget to hire a translator if necessary. Very possibly, though, the level of necessary effort will be minimal and something to which Dércio Duvane can thus commit.
• In terms of prioritization:
  • If Dércio Duvane can provide translations within a day or two, it would be great to give the work the highest possible priority. In this case, we would wait for the translations to be done prior to fixing our broken Superset server. This, in turn, would save us from having to update the Superset server again at a later date after the translations become available. 
  • If it will take more than a day or two to produce the translations, it would be alright to de-prioritize the work. We probably won't wait more than a few days to fix the Superset server. We'd therefore have to incur the cost of upgrading it to incorporate the translations at a later time - and doing so this week as opposed to the next shouldn't make much of a difference.

Action items

• Ben Leibert will look into whether NexLeaf provides District-level imagery.
• Dércio Duvane will coordinate with the MoH to ensure they provide us with historical report data. 
• Dércio Duvane will estimate how long it will take to provide Portuguese translations, and potentially create them for the team.