2018-06-19 Daily Standup

Date

19 Jun 2018

We should restrict the email addresses from which the system should accept and process CSV/Excel files. Because our users rely on free Yahoo and gmail mailboxes, we can't specify such restrictions by domain (such as @villagereach.org or @MozMoH). Instead, we should plan to use a list of individual users' email addresses. The downside is that updating the list when employees come and go will require a support ticket to either VillageReach or Ona. Relying on domain names would have alleviated this need, but would also provide a meaningless degree of protection. (cc: Antonate Maritim (Unlicensed).)
As the requirements mention, it would be ideal if users can drill down into the DHIS-2 visualizations (cc: Clay Crosby (Unlicensed)). Antonate Maritim (Unlicensed) plans to retrieve all the requisite data from DHIS-2, and Timoteo Chaluco (Unlicensed) will send her district codes to make it easier.
DHIS-2 includes a population value for 2017. Its 2017 data is thus complete and therefore ideal for designing the related dashboards. (cc: Clay Crosby (Unlicensed)).

In descending level of priority...

Timoteo Chaluco (Unlicensed) will provide the district codes used by DHIS-2
Timoteo Chaluco (Unlicensed) will try to provide historical data which resides in systems other than SELV and DHIS-2.
Timoteo Chaluco (Unlicensed) will provide a list of users (and accompanying email addresses) whom should have access to dashboards, access to sensitive HSS info, the ability to edit dashboards, and the ability to submit data via email.