Difference between revisions of "Monitoring Data Quality"
Mrijanrimal (talk | contribs) |
Mrijanrimal (talk | contribs) |
||
| Line 4: | Line 4: | ||
== Steps important in the quality checks == | == Steps important in the quality checks == | ||
===Duplicates and Survey Logs === | |||
It is very important to do quality checks on data during the survey as it is difficult to fix the problem/recollect the data if the error is found after the completion of the survey. | It is very important to do quality checks on data during the survey as it is difficult to fix the problem/recollect the data if the error is found after the completion of the survey. | ||
*Testing for Duplicates - Since SurveyCTO/ODK data has a number of duplicates, the first thing you need to do is check for duplicates and remove the duplicates. | *Testing for Duplicates - Since SurveyCTO/ODK data has a number of duplicates, the first thing you need to do is check for duplicates and remove the duplicates. | ||
| Line 11: | Line 12: | ||
To see how to remove duplicates and check that all the field data is on servers, please see the main article at '''[[Duplicates and Survey Logs]].''' | To see how to remove duplicates and check that all the field data is on servers, please see the main article at '''[[Duplicates and Survey Logs]].''' | ||
===High Frequency Checks=== | |||
After you have verified that all the data is on the server, the following steps should be undertaken: | After you have verified that all the data is on the server, the following steps should be undertaken: | ||
*High frequency tests of data quality | *High frequency tests of data quality | ||
Revision as of 16:10, 30 January 2017
Read First
- Data quality checks should be done before and during the survey, as there is little that we can do after a survey if the data contains errors.
- Lots of preparation should be made before the survey and steps should be followed during the survey so any error that is caught can be changed quickly before it is too late.
Steps important in the quality checks
Duplicates and Survey Logs
It is very important to do quality checks on data during the survey as it is difficult to fix the problem/recollect the data if the error is found after the completion of the survey.
- Testing for Duplicates - Since SurveyCTO/ODK data has a number of duplicates, the first thing you need to do is check for duplicates and remove the duplicates.
- Test that all data from the field is on the server - Survey data logs from the field can then be matched with the logs from the survey data logs on the server to see if the all the data from the field has been transferred to the server.
Tip: Verifying that the data is complete should be done the day of or the day after the survey. Since, the interviewer is most likely close by, it would be easy to re-interview and get missing data if significant chunks of data were missing.
To see how to remove duplicates and check that all the field data is on servers, please see the main article at Duplicates and Survey Logs.
High Frequency Checks
After you have verified that all the data is on the server, the following steps should be undertaken:
- High frequency tests of data quality
- IPA Template only (Template assumes SurvyCTO)
- if not written in SurveyCTO -possible to adapt data to template, or template to data, but might be easier to write your own tests in Stata
- IPA Template + additional tests in Stata
- Test written in Stata only
- Option if data is not collected with SurveyCTO
- IPA Template only (Template assumes SurvyCTO)
- Follow up using the Data Explorer in SurveyCTO
- Back Checks
--Something about being close to the survey location and redoing the survey if absolutely necessary.
Additional Resources
- list here other articles related to this topic, with a brief description and link