Development Research in Practice

Page 140

completed, these variables may be removed from the data set. In fact, starting from a minimal set of variables and adding new ones as they are cleaned can make the data easier to handle. Using commands such as compress in Stata so that the data are always stored in the most efficient format helps to ensure that the cleaned data set file does not get too big to handle. Although all of these tasks are key to making the data easy to use, implementing them can be quite repetitive and create convoluted scripts. The iecodebook command suite, part of the iefieldkit Stata package, is designed to make some of the most tedious components of this process more efficient. It also creates a self-documenting workflow, so the data-cleaning documentation is created alongside the code, with no extra steps (see box 5.7 for a description of how iecodebook was used in the Demand for Safe Spaces project). In R, the Tidyverse (https://www.tidyverse.org) packages provide a consistent and useful grammar for performing the same tasks and can be used in a similar workflow.

BOX 5.7 RECODING AND ANNOTATING DATA: A CASE STUDY FROM THE DEMAND FOR SAFE SPACES PROJECT The Demand for Safe Spaces team relied mostly on the iecodebook command for this part of the

data-cleaning process. The screenshot below shows the iecodebook form used to clean the crowdsourced ride data. This process was carried out for each task.

Column B contains the corrected variable labels, column D indicates the value labels to be used for categorical variables, and column I recodes the underlying numbers in those variables. The differences between columns E and A indicate changes to variable names. Typically, it is strongly recommended not to rename variables at the cleaning stage, because it is important to maintain correspondence with the original data set. However, that was not possible in this case, because the same question had inconsistent variable names across multiple transfers of the data from the technology firm managing the mobile application. In fact, this is one of the two cleaning tasks that

(Box continues on next page) 120

DEVELOPMENT RESEARCH IN PRACTICE: THE DIME ANALYTICS DATA HANDBOOK


Turn static files into dynamic content formats.

Create a flipbook

Articles inside

Appendix C: Research design for impact evaluation

33min
pages 215-231

Appendix A: The DIME Analytics Coding Guide

24min
pages 195-210

Appendix B: DIME Analytics resource directory

3min
pages 211-214

8.1 Research data work outputs

6min
pages 190-194

Chapter 8: Conclusion

1min
page 189

7.4 Releasing a reproducibility package: A case study from the Demand for Safe Spaces project

3min
pages 184-186

7.1 Summary: Publishing reproducible research outputs

8min
pages 172-175

7.3 Publishing research data sets: A case study from the Demand for Safe Spaces project

10min
pages 180-183

7.2 Publishing research papers and reports: A case study from the Demand for Safe Spaces project

8min
pages 176-179

Chapter 7: Publishing reproducible research outputs

1min
page 171

6.1 Data analysis tasks and outputs

3min
pages 168-170

6.8 Managing outputs: A case study from the Demand for Safe Spaces project

10min
pages 163-167

6.7 Visualizing data: A case study from the Demand for Safe Spaces project

4min
pages 161-162

6.6 Organizing analysis code: A case study from the Demand for Safe Spaces project

4min
pages 159-160

6.5 Writing analysis code: A case study from the Demand for Safe Spaces project

3min
pages 157-158

6.4 Documenting variable construction: A case study from the Demand for Safe Spaces project

4min
pages 155-156

6.3 Creating analysis variables: A case study from the Demand for Safe Spaces project

1min
page 154

6.2 Integrating multiple data sources: A case study from the Demand for Safe Spaces project

9min
pages 150-153

6.1 Summary: Constructing and analyzing research data

10min
pages 146-149

Chapter 6: Constructing and analyzing research data

1min
page 145

5.7 Recoding and annotating data: A case study from the Demand for Safe Spaces project

3min
pages 140-141

5.6 Correcting data points: A case study from the Demand for Safe Spaces project

4min
pages 138-139

5.5 Implementing de-identification: A case study from the Demand for Safe Spaces project

9min
pages 134-137

5.1 Summary: Cleaning and processing research data

7min
pages 122-124

5.4 Assuring data quality: A case study from the Demand for Safe Spaces project

7min
pages 131-133

5.3 Tidying data: A case study from the Demand for Safe Spaces project

7min
pages 128-130

5.2 Establishing a unique identifier: A case study from the Demand for Safe Spaces project

7min
pages 125-127

Chapter 5: Cleaning and processing research data

1min
page 121

B4.4.1 A sample dashboard of indicators of progress

12min
pages 113-117

4.4 Checking data quality in real time: A case study from the Demand for Safe Spaces project

2min
page 112

4.3 Piloting survey instruments: A case study from the Demand for Safe Spaces project

14min
pages 106-111

4.2 Determining data ownership: A case study from the Demand for Safe Spaces project

16min
pages 100-105

B3.3.1 Flowchart of a project data map

37min
pages 81-96

B2.3.1 Folder structure of the Demand for Safe Spaces data work

36min
pages 55-72

Chapter 4: Acquiring development data

5min
pages 97-99

Chapter 3: Establishing a measurement framework

18min
pages 73-80

Chapter 1: Conducting reproducible, transparent, and credible research

35min
pages 31-46

Chapter 2: Setting the stage for effective and efficient collaboration

18min
pages 47-54

I.1 Overview of the tasks involved in development research data work

18min
pages 22-30

Introduction

2min
page 21
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.
Development Research in Practice by World Bank Publications - Issuu