This scoping document defines the process for building placeholder events in place of missing events that were identified in Namibia in Q4 2019.

Links

January missing event details

Namibia Data Dictionary

Summary

There are a total of 946 missing events that need to be rebuilt with task business status of “Sprayed”, “Partially-Sprayed” or “Not Sprayed”. We need to build a process for creating “placeholder” events that can be posted to the OpenSRP server so that they show up in the Android client. Below is a summary of placeholder events that need to be generated based on operational area and business status:

Process

1. (We are here) Scope and create an excel spreadsheet that defines the fields that need to be captured for the missing events.

2. Akros will estimate the number of rooms to add for each operational area and share those with Ona

3. Ona will fill in the spreadsheet template and work with Akros to confirm that the estimated number of rooms will reflect correctly in the totals for each operational area

4. Convert each row of the spreadsheet to JSON so it can be posted

5. POST three events, one for each business status, to the Namibia production environment to test that they functions as expected in the Android app

6. Try to edit the three events in the Android app (offline) and confirm that it is able to save.

7. Track that event to confirm that the dashboard was updated in the Namibia Web UI

8. Once confirmed, POST all other events to the Namibia production server

9. Perform a spot check in the Android app in each operational area to confirm that events were applied correctly.

10. Review the Namibia dashboards to confirm the numbers are updated

11. Export the data from Superset and confirm that the events all show up

Expected Outcomes

We expect the following to be achieved through this process:

1. 946 events need to be generated and posted to the OpenSRP server, one for each missing event identified in the table above and linked document.

2. Users will be able to see these events in the Android app when they tap a location in the card pop up clearly marked as “Placeholder Event”

3. Users will be able to edit events to update that location in the plan if they ever visit that location again in the field.

Sample JSON from Namibia Production

This section contains sample code of each event extracted from Namibia’s production environment (identifying information removed).

Namibia Spray Form JSON

Sample Spray Event (THIS IS WHAT THE OUTPUT SHOULD LOOK LIKE)

This demonstrates a complete sample spray event. The subsequent samples show form data that has been processed after the ETL process and are available in the data warehouse. You can access this event by accessing https://reveal-na.smartregister.org/opensrp/rest/event/findById?id=8333c67a-8dba-4afb-8f20-75dddce31e6f You can access the task for this event at https://reveal-na.smartregister.org/opensrp/rest/task/58b5e8ca-3b72-4133-a9ee-080bbdc35445

Business Status: Sprayed Form Data

SQLLab Query:

SELECT form_data FROM events
WHERE form_data @> '{"business_status":["Sprayed"]}'
Limit 100;

Business Status: Partially Sprayed Form Data

SQLLab Query: SELECT form_data FROM events
WHERE form_data @> '{"business_status":["Partially Sprayed"]}' AND form_data @> '{"mopUpVisit":["no"]}'
Limit 100;

Business Status: Not Sprayed Form Data

SQLLab Query:

SELECT form_data FROM events

WHERE form_data @> '{"business_status":["Not Sprayed"]}'
Limit 100;

Assumptions

We make the following assumptions:

• Namibia dropped points when they created forms in the field. After they created a location the task was automatically generated. We will use the date information from the task to complete the event templates

Task/Event Field Mapping

This section defines the field mapping of the tasks and events.

Event Template and Google Sheet Formulas

Business Status: Not Sprayed

Sample template

Formula for the Google Sheet