Dimewiki

Difference between revisions of "Monitoring Data Quality"

Jump to: navigation, search
Line 17: Line 17:


--Something about being close to the survey location and redoing the survey if absolutely necessary.  
--Something about being close to the survey location and redoing the survey if absolutely necessary.  
===Verifying that all survey data is on the server===
====Removing Duplicates====
Before analyzing the outcomes of quality checks or sometimes even before running real time quality checks, we need to check for duplicates in the data. Duplicates are common in ODK/SurveyCTO and need to be removed before starting other data quality checks.
To remove duplicates, you can use the DIME's Stata command <code> '''ieduplicates''' </code> which can be found in the <code> '''ietoolkit''' </code> Stata package.
====Comparing Server Data to Field Logs ====
Comparing server data to field logs makes sure that all the data collected during the survey has made it to your server. This can be done by writing code that generates a survey log which counts the number of surveys on the server and matching that log with the field logs.


=== Data Quality Checks===
=== Data Quality Checks===

Revision as of 20:06, 25 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

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.

  • Test for duplicates
  • Test that all data from the field is on the server.
  • 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
  • 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.

Data Quality Checks

Comparing back checks with the main data

Back to Parent

This article is part of the topic Monitoring data quality

Additional Resources

  • list here other articles related to this topic, with a brief description and link
Retrieved from "https://dimewiki.worldbank.org/index.php?title=Monitoring_Data_Quality&oldid=881"