21.06.2014 Views

Questionnaire Dwelling Unit-Level and Person Pair-Level Sampling ...

Questionnaire Dwelling Unit-Level and Person Pair-Level Sampling ...

Questionnaire Dwelling Unit-Level and Person Pair-Level Sampling ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix O: Rules for Determining <strong>Pair</strong> Relationships<br />

O.1 Rules for Determining Matching <strong>Pair</strong>s, in Priority Order<br />

The following rules are used to determine the roster member in a respondent's household<br />

roster that corresponds to the other pair member. In these rules, an "age match" occurs if the<br />

questionnaire age of one pair member matches a roster age in the other pair member's roster, <strong>and</strong><br />

a "gender match" occurs if the questionnaire gender of one of the pair members matches a roster<br />

gender in the other pair member's roster. In the table below, if the rules for <strong>Pair</strong> Member A <strong>and</strong><br />

<strong>Pair</strong> Member B in a single row differ, then the count for that row includes the rules as listed, <strong>and</strong><br />

the rules with <strong>Pair</strong> Member A <strong>and</strong> <strong>Pair</strong> Member B are reversed. If the age <strong>and</strong>/or gender are off<br />

when finding these matches, the age <strong>and</strong>/or gender are defined by the questionnaire age <strong>and</strong><br />

gender of the selected pair member when determining the pair domain. The rules, called priority<br />

conditions because of their hierarchical nature, are listed in priority order in Table O.1, along<br />

with the number of pairs to which each rule was applied. Since the 2001 survey, it was<br />

technically impossible to identify more than one roster member as the "other pair member<br />

selected," resulting in either 0 or 1 MBRSEL for each responding pair. Rules involving situations<br />

where more than one MBRSEL existed are therefore not included in this table. Some other<br />

conditions that were not evident in 2006 also are excluded from this table, provided the<br />

distribution of counts would have been unaffected by their exclusion from the code.<br />

Table O.1 Rules for Determining Matching <strong>Pair</strong>s, in Priority Order<br />

Priority<br />

Rule<br />

Condition <strong>Pair</strong> Member A <strong>Pair</strong> Member B Count<br />

1 Age <strong>and</strong> gender match exactly,<br />

exactly one MBRSEL in right place<br />

2 Age <strong>and</strong> gender match exactly,<br />

exactly one MBRSEL in right place<br />

3 Age within one, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

4 Age <strong>and</strong> gender match exactly,<br />

exactly one MBRSEL in right place<br />

5 Age within one, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

6 Age within two, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

Age <strong>and</strong> gender match exactly,<br />

exactly one MBRSEL in right place<br />

Age within one, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

Age within one, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

Age within two, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

Age within two, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

Age within two, gender matches<br />

exactly, exactly one MBRSEL in<br />

right place<br />

16,590<br />

2,160<br />

131<br />

276<br />

34<br />

10<br />

O-3

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

Saved successfully!

Ooh no, something went wrong!