Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a "cleaned spreadsheet" #174

Open
mikeymckay opened this issue Jan 25, 2016 · 1 comment
Open

Create a "cleaned spreadsheet" #174

mikeymckay opened this issue Jan 25, 2016 · 1 comment

Comments

@mikeymckay
Copy link
Owner

Invalid Shehia names are a problem when raw data is used for analysis. Particularly when looking at USSD or Case Notification data that has not had to pass validation to be saved. Shehia data, in particular, tends to become more accurate with each step of the case investigation. For instance, a shehia will be known definitively once the DMSO is at the household.

In the past, I have tried to encourage the team to use the built-in reports when possible. However, there has always been a tendency to generate reports manually in excel based on spreadsheet data that has been downloaded. Indeed, I expect there will always be a question that can only be answered by analysing the raw data. The problem is that the raw data doesn't include automated cleaning, data selection, etc, that the built-in reports do. For instance, in the absence of a 'Date of Positive Result' we use the creation date of the Case Notification as the 'Date of Positive Result'.

A solution is to provide a “cleaned” spreadsheet that includes these sort of automated data manipulations.

This will not fix all of the incorrect shehias in the system. Instead, we will create a list of invalid shehias and their case IDs from this new “cleaned” spreadsheet and then we will manually fix them where possible.

@mikeymckay
Copy link
Owner Author

Done and pushed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant