Difference between revisions of "Duplicates and Survey Logs"

Jump to: navigation, search
 
(28 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
<onlyinclude>Checking for duplicates makes sure that the answers of the survey respondent are not recorded twice. Matching field survey logs with server logs ensures that data has been fully transferred to the survey.</onlyinclude>
 +
 
== Read First ==
 
== Read First ==
* To complete that the survey data is complete, both these steps must be done. Skipping one might result in an incomplete data set.
+
* The data should be downloaded daily and checked for duplicates daily.It is much easier to solve the problem when the field team remembers the interview and is still close by that they can go back and re-interview the respondent. Other data quality checks depend on uniquely identifying ID variables.
 +
*Verifying survey logs with duplicates makes sure that data from the field has all been transferred over to the server. This should also be done daily which would make it easier to go back and re-interview respondents in cases where their survey might have been lost due to technical problems.  
  
== Data Duplicates==
+
== Types of Duplicates in SurveyCTO ==
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.
+
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. They need to be removed before starting other data quality checks as other quality checks depend on unique ID. There are three main types of duplicates in SurveyCTO which are:
 
 
* The data should be downloaded daily and checked for duplicates daily.
 
* This cannot be done later because it is much easier to solve the problem when the field team remembers the interview. Other quality checks depend on uniquely identifying ID variables.
 
  
 +
*Double Submissions of same observation and same data which happens when the first upload from the tablet to the server is interrupted due to bad internet. Few variables differ between the duplicates, and the differences are in the submission data.
 +
*Double submissions of same observation but with modified data(rare in SurveyCTO). This is due to answer being modified after submission of the original survey and the survey resubmitted. This is bad practice and it is more transparent to correct errors in the do-file instead. Some variables differ between the duplicates and some of them are in the observation data.
 +
*Incorrectly assigned ID i.e. two respondents with the same ID. This is due to a  typo in the field when the a respondent ID is being entered. Many variables differ between the duplicates and many of the differences are in the observation data.
  
 +
==Removing duplicates from a dataset==
  
 
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.
 
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.
  
 
<code>  
 
<code>  
ssc install ietoolkit </br>
+
ssc install ietoolkit       </br>
 
ieduplicates ''ID_varname'' </br>
 
ieduplicates ''ID_varname'' </br>
 
</code>
 
</code>
 +
 +
This identifies the duplicates in the ID variable and exports them to an Excel file which is also used to correct duplicates in Stata. Field supervisors without knowledge of Stata can make the corrections in the Excel file and the duplicates will be corrected the next time you run the code.
  
 
==Comparing Server Data to Field Logs ==
 
==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 in a few steps:
+
Comparing server data to field logs makes sure that all the data collected during the survey has made it to your server. Survey logs also serve the purpose of providing teams with a quick overview of the progress on the field, detecting enumerators who are not performing their tasks properly, and checking balance of the survey(i.e. gender, race, etc) in some cases.
  
*Gener
+
You can do this by creating a log for all the interviews done during the day on the field and matching that with the survey data on the server. This should be done only after the duplicates have been removed. This makes sure that all the survey data done during the day have been uploaded to the server.
  
 
== Back to Parent ==
 
== Back to Parent ==
This article is part of the topic [[Monitoring Data Quality]]
+
This article is part of the topic [[Data Management]]
  
 
== Additional Resources ==
 
== Additional Resources ==
* list here other articles related to this topic, with a brief description and link
+
*  
  
[[Category: Data Quality ]]
+
[[Category: Data Management]]

Latest revision as of 11:22, 5 April 2018

Checking for duplicates makes sure that the answers of the survey respondent are not recorded twice. Matching field survey logs with server logs ensures that data has been fully transferred to the survey.

Read First

  • The data should be downloaded daily and checked for duplicates daily.It is much easier to solve the problem when the field team remembers the interview and is still close by that they can go back and re-interview the respondent. Other data quality checks depend on uniquely identifying ID variables.
  • Verifying survey logs with duplicates makes sure that data from the field has all been transferred over to the server. This should also be done daily which would make it easier to go back and re-interview respondents in cases where their survey might have been lost due to technical problems.

Types of Duplicates in SurveyCTO

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. They need to be removed before starting other data quality checks as other quality checks depend on unique ID. There are three main types of duplicates in SurveyCTO which are:

  • Double Submissions of same observation and same data which happens when the first upload from the tablet to the server is interrupted due to bad internet. Few variables differ between the duplicates, and the differences are in the submission data.
  • Double submissions of same observation but with modified data(rare in SurveyCTO). This is due to answer being modified after submission of the original survey and the survey resubmitted. This is bad practice and it is more transparent to correct errors in the do-file instead. Some variables differ between the duplicates and some of them are in the observation data.
  • Incorrectly assigned ID i.e. two respondents with the same ID. This is due to a typo in the field when the a respondent ID is being entered. Many variables differ between the duplicates and many of the differences are in the observation data.

Removing duplicates from a dataset

To remove duplicates, you can use the DIME's Stata command ieduplicates which can be found in the ietoolkit Stata package.

ssc install ietoolkit
ieduplicates ID_varname

This identifies the duplicates in the ID variable and exports them to an Excel file which is also used to correct duplicates in Stata. Field supervisors without knowledge of Stata can make the corrections in the Excel file and the duplicates will be corrected the next time you run the code.

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. Survey logs also serve the purpose of providing teams with a quick overview of the progress on the field, detecting enumerators who are not performing their tasks properly, and checking balance of the survey(i.e. gender, race, etc) in some cases.

You can do this by creating a log for all the interviews done during the day on the field and matching that with the survey data on the server. This should be done only after the duplicates have been removed. This makes sure that all the survey data done during the day have been uploaded to the server.

Back to Parent

This article is part of the topic Data Management

Additional Resources