-
Notifications
You must be signed in to change notification settings - Fork 7
/
labelled_spss_survey.Rmd
169 lines (126 loc) · 6.59 KB
/
labelled_spss_survey.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
---
title: "The labelled_spss_survey class"
output: rmarkdown::html_vignette
vignette: >
%\VignetteIndexEntry{The labelled_spss_survey class}
%\VignetteEngine{knitr::rmarkdown}
%\VignetteEncoding{UTF-8}
---
```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>"
)
```
Large international survey programs that provide data access to their data, such as the aforementioned Eurobarometer, Afrobarometer and Arab Barometer, or the European Values Survey, or Lationbarometro usually give access to the data in SPSS files. In some cases, Stata files are available, too. Our examples always start with SPSS files.
In R, the [haven](https://haven.tidyverse.org/) package provides functions to import and export data to and from IBM's proprietary SPSS files. We had to realize that while [haven::read_spss](https://haven.tidyverse.org/reference/read_spss.html) works perfectly with importing the data and metadata of a single survey, it is not always suitable for multiple survey files, for two important reasons. SPSS files contain the survey data in a coded form, with the coding (labelling) metadata optionally included to each variable.
1. Variables imported with inconsistent labelling cannot always be concatenated. For example, unlabelled age variables are imported to an R numeric vector, whilst when the age 18 is labelled *18 years* or *18 éves*, it is imported to a labelled class.
2. The SPSS variables do not handle various missing cases in a complete and unambiguous form. In an age variable, *998* and *999* may be labelled as *not asked* and *declined to answer*, or simply the numerical range between 120-999 may be marked as a range of numeric values representing missing cases.
One practical problem in the Eurobarometer surveys, which targets the population of at least 15 years old Europeans is that in some standard questions, such as the age of finishing full-time education, 10 represents a special missing value, whilst in other surveys it may be a perfectly valid numerical answer. The real coding problem is that SPSS users can freely chose to use explicit labelling of missing cases, using a numerical range for missing cases, or not providing any missing case metadata at all.
Our importing functions rely on two new S3 classes. A single survey is imported into a `survey()` class, which inherits all the properties of a modern data frame, i.e., it is a `tibble` or `tbl_df` from [tibble](https://tibble.tidyverse.org/) in the tidyverse, but it includes as much metadata from the original SPSS file as possible. These metadata attributes are handled in a way that they can facilitate proper documentation and a reproducible workflow. Furthermore, it converts labelled variables into the *retroharmonize_labelled_spss* class inherited from [haven::labelled_spss](https://haven.tidyverse.org/reference/labelled_spss.html) with more consistent handling of missing value ranges and labels. See `?labelled_spss_survey`.
Working with our new *retroharmonize_labelled_spss class* can be very cumbersome, particularly with simple harmonization tasks. In the case of harmonizing a single question from two surveys, this may not be practical, and a simple crosswalk table can help with spotting and correcting inconsistent codes.
Our survey objects or retroharmonize_labelled_spss vectors can be converted to base R classes with the `as_numeric()`, `as_factor(`) or `as_character()` methods. When computing a numerical average, the special age value of 10 is converted to `NA_real`_ as a numeric. In other statistical applications, missing and special values are best represented as categories---this calls for the factor representation. The character representation is often more useful for visualizing the data then the factor representation.
## Create A labelled_spss_survey Vector
```{r setup}
library(retroharmonize)
```
Use the `labelled_spss_survey()` helper function to create vectors of class *retroharmonize_labelled_spss_survey*.
```{r}
sl1 <- labelled_spss_survey (
x = c(1,1,0,8,8,8),
labels = c("yes" =1,
"no" = 0,
"declined" = 8),
label = "Do you agree?",
na_values = 8,
id = "survey1")
print(sl1)
```
You can check the type:
```{r}
is.labelled_spss_survey (sl1)
```
The `labelled_spss_survey()` class inherits some properties from `haven::labelled()`, which can be manipulated by the `labelled` package (See particularly the vignette *Introduction to labelled* by Joseph Larmarange.)
```{r}
haven::is.labelled(sl1)
```
```{r}
labelled::val_labels(sl1)
```
```{r}
labelled::na_values(sl1)
```
It can also be subsetted:
```{r}
sl1[3:4]
```
When used within the modernized version of *data.frame*, `tibble::tibble()`, the summary of the variable content prints in an informative way.
```{r}
df <- tibble::tibble (v1 = sl1)
## Use tibble instead of data.frame(v1=sl1) ...
print(df)
## ... which inherits the methods of a data.frame
subset(df, v1 == 1)
```
## Coercion rules and type casting
To avoid any confusion with mis-labelled surveys, coercion with double or integer vectors will result in a double or integer vector. The use of `vctrs::vec_c` is generally safer than base R `c()`.
```{r}
#double
c(sl1, 1/7)
vctrs::vec_c(sl1, 1/7)
```
```{r integer}
c(sl1, 1:3)
```
Conversion to character works as expected:
```{r character}
as.character(sl1)
```
The base `as.factor` converts to integer and uses the integers as levels, because base R factors are integers with a `levels` attribute.
```{r as.factor}
as.factor(sl1)
```
Conversion to factor with `as_factor` converts the value labels to factor levels:
```{r as_factor}
as_factor(sl1)
```
Similarly, when converting to numeric types, we have to convert the user-defined missing values to `NA` values used in the R language. For numerical analysis, convert with `as_numeric`.
```{r numerics}
as.numeric(sl1)
as_numeric(sl1)
```
## Arithmetics
The median value is correctly displayed, because user-defined missing values are removed from the calculation. Only a few arithmetic methods are implemented, such as
* median()
```{r}
median (as.numeric(sl1))
median (sl1)
```
* quantile()
```{r}
quantile (as.numeric(sl1), 0.9)
quantile (sl1, 0.9)
```
* mean()
```{r}
mean (as.numeric(sl1))
mean (sl1)
mean (sl1, na.rm=TRUE)
```
* weighted.mean() - always removes NA values.
```{r}
weights1 <- runif (n = 6, min = 0, max = 1)
weighted.mean(as.numeric(sl1), weights1)
weighted.mean(sl1, weights1)
```
* sum()
```{r}
sum (as.numeric(sl1))
sum (sl1, na.rm=TRUE)
```
The result of the conversion to numeric can be used for other mathematical / statistical function.
```{r}
as_numeric(sl1)
min ( as_numeric(sl1))
min ( as_numeric(sl1), na.rm=TRUE)
```