27.10.2014 Views

Russel-Research-Method-in-Anthropology

Russel-Research-Method-in-Anthropology

Russel-Research-Method-in-Anthropology

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

550 Chapter 19<br />

<strong>in</strong>dependent variables. That’s the bivariate part. F<strong>in</strong>ally, you’d look at the<br />

simultaneous effect of the <strong>in</strong>dependent variables on the dependent variable or<br />

variables. That’s the multivariate part.<br />

Each part helps us answer questions about how th<strong>in</strong>gs work.<br />

Cod<strong>in</strong>g and Codebooks for Quantitative Data<br />

Quantitative data process<strong>in</strong>g depends crucially on hav<strong>in</strong>g a useful codebook.<br />

A codebook for quantitative data spells out exactly how to transform<br />

observations <strong>in</strong>to numbers that can be manipulated statistically and searched<br />

for patterns.<br />

A good codebook is worth a lot <strong>in</strong> data analysis and it’s worth more every<br />

year. It tells you (and others) what you have <strong>in</strong> your data—what variables<br />

you’ve studied, what you’ve called those variables, and how you’ve stored<br />

<strong>in</strong>formation about them. You simply can’t analyze quantitative data without a<br />

good, clear codebook.<br />

Just as important, neither can anyone else. You can’t share your data with<br />

other researchers unless you give them a codebook they can use. Six months<br />

after you f<strong>in</strong>ish anyth<strong>in</strong>g but the simplest projects (those with only half a<br />

dozen or fewer variables), even you won’t recognize your own data without a<br />

codebook. And if you want to reanalyze your data several years after a project<br />

has ended, or compare data from 2002 with current data, you won’t be able to<br />

do so unless you have built and filed away a good codebook.<br />

Cod<strong>in</strong>g<br />

The first rule for cod<strong>in</strong>g quantitative data is: Don’t analyze while you’re<br />

cod<strong>in</strong>g. This rule is the exact opposite of the rule that applies to cod<strong>in</strong>g qualitative<br />

data. Cod<strong>in</strong>g text is analysis—th<strong>in</strong>k<strong>in</strong>g about what each piece of text<br />

means, develop<strong>in</strong>g hypotheses about the people who are described, boil<strong>in</strong>g the<br />

text down to a series of mnemonics.<br />

It’s different with a set of numbers. Suppose you ask 400 randomly selected<br />

people, aged 20–70, how old they are. You could get as many as 51 different<br />

ages, and you’ll probably get at least 20 different ages.<br />

I’ve seen many researchers code this k<strong>in</strong>d of data <strong>in</strong>to four or five categories—such<br />

as 20–29, 30–39, 40–49, 50 and older—before see<strong>in</strong>g what<br />

they’ve got. Recall from chapter 2 that this just throws away the <strong>in</strong>terval-level<br />

power of data about age. You can always tell the computer to package data<br />

about age (or <strong>in</strong>come, or any <strong>in</strong>terval variable) <strong>in</strong>to a set of ord<strong>in</strong>al chunks.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!