Package: HighFrequencyChecks 0.5.0

Demo data | Pro-active actions - Enumerators rigorous work standards | Interview Duration | Interview Duration Outliers | Picked up less than a certain number of answers for select multiple questions | Are Interviews Completed? | Do Interviews include Consent? | Is there Missing Values in the reponse? | Number of distinct values (not missing) per fields | Other distinct values (not missing) per fields other with count | Response Outliers | Abnormally High Values | Abnormally Low Values | Enumerator Errors Summary | Pro-active actions - Enumerators productivity | Summary of daily average productivity | Daily number of filled forms per attempt output | Daily number of filled forms per time in the day | Percentage of non-completed interviews by enumerator | Interview Duration per Enumerator | Number of Interview by enumerator | Enumerators with very low or high productivity | Corrective actions - Correct set-up of data collection devices and encoding of the forms | How many Attempt for each SampleRespondant ID? | Are there unique respondantID Missing? | Is there any survey interview lasting on more than a day? | Is there any survey interview with end date time before start time? | Is there any survey interview with start date after today? | Corrective actions - Data collected according the plan | Is there any survey interview starting before official first day? | Are there interviews appearing too short? | Are there interviews appearing too short based on household Size? | Are interviews taking place in the expected site? | Are interviews taking place in the expected point? | Overall tracking sheet | run_app

Automating Data Quality Monitoring Report | Create a public github repo | Set up the manifest | Publish the report to Rstudio Connect from Github | Set up your kobotoolbox API key within Rstudio Connect | Set up report frequency generation and sending it to your email | Use power automate to forward automatically the email with the report to the data supervisor | Doing some of the available checks on the individual loops | Doing a check by enumerator or not | Periodic checks (daily for example) on the data collected | Changing the purpose of a function

Measuring data collection quality | Specific variables to be controlled | Setting up tablet | Process configuration | Loading survey dataset (microdata) | Configuring numeric questions | Configuring categoric questions | Configuring sampling plan | Configuring geodata for the surveyed area | Report Configuration | Corrective actions | Correct set-up of data collection devices and encoding of the forms | Respondent ID | Configuration of dates on device | Data collected according the plan | Completed interviews | Interviews made before the first day of data collection | Enumerators who made a survey below r minimumSurveyDuration minutes | Recorded site name for each interview matches the name of the location | Recorded locations for each interview within a r buffer meters buffer from a sample point | Tracking sheet per site | Pro-active actions | Enumerators rigorous work standards | Durations of Interviews | Responses with outliers | Numeric value above a certain threshold | Enumerators who pick up less than a predifined number of answers per specific questions: | Check percentage of “don’t know” and refusal responses by the enumerator. | Number of other distinct values (for the questions with a possibility of other) | Enumerator productivity | How many completed interview per day? | How many attempted interview per day and obtained consent? | Percentage of survey per consent status by enumerator | Average interview duration by enumerator | Number of surveys per day by enumerator | Enumerators with productivity significantly different from the average (low or high)