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

Create successful ePaper yourself

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

Appendix R: Conditions Used for Reconciling Differing<br />

Multiplicity Counts between <strong>Pair</strong> Members<br />

R.1 Introduction<br />

In order to determine multiplicity counts, counts were obtained from each pair member.<br />

The count from the pair member who was the focus member of the domain was considered the<br />

direct count, <strong>and</strong> the count from the other pair member was considered the indirect count.<br />

Typically, these counts were in agreement, <strong>and</strong> the determination of the final multiplicity count<br />

was straightforward, provided both rosters did not have bad data codes. The strategy also was<br />

usually clear if one pair member had bad data in the household roster, or had a 0 count when the<br />

pair relationship precluded a value of 0. The count from the pair member with good, nonzero<br />

data was usually preferred in those cases. If the bad data was limited to bad relationship codes,<br />

then the member with good data was selected only if substituting the appropriate relationship<br />

codes for the bad data codes would have given a total that was equal to the count from the pair<br />

member with good data. There were instances where bad data codes existed in the roster, <strong>and</strong> this<br />

condition did not apply. There were other exceptions as well. Finally, there were instances where<br />

neither pair member had bad data in their rosters, yet their counts still disagreed. In this<br />

appendix, the rules that were used to reconcile these disagreeing counts are outlined.<br />

Note that the reconciliation of differing counts was necessary for parent-child <strong>and</strong><br />

sibling-sibling pairs but was not necessary for spouse-spouse pairs, since the multiplicity count<br />

for spouse-spouse pairs was always 1. As noted in Section 6.3, it was technically possible for a<br />

respondent to have multiple spouses, but these situations were not accounted for.<br />

R.2 Parent-Child Counts<br />

For parent-child counts, the screener <strong>and</strong> the FIPE3 variable were used to help reconcile<br />

disagreeing counts. The rules follow below, separated by the member of focus:<br />

Parent-child pairs, child focus. The multiplicity counts in this domain reflected the<br />

selected child's parents <strong>and</strong> in most cases had values of 1 or 2. If neither side had bad<br />

relationship codes <strong>and</strong> the direct count exceeded the indirect count, the following rules applied:<br />

1. The direct count might have exceeded the indirect count because one parent had left<br />

or entered the household between interviews. In this case, the ages in the rosters were<br />

matched to the screener roster to determine which count to believe. This was done in<br />

two ways. First, the total number of roster members between ages 30 <strong>and</strong> 39, 35 <strong>and</strong><br />

44, <strong>and</strong> 40 <strong>and</strong> 49 were compared between pair members <strong>and</strong> the screener. The pair<br />

member with age range counts closest to the screener was the one whose parent-child<br />

count was chosen for the final count. If neither side had age range counts equal to the<br />

screener, then the pair member with a parent-child count equal to the total number of<br />

screener roster members between ages 26 <strong>and</strong> 64 was chosen as the final count.<br />

2. The direct count might have exceeded the indirect count because the selected parent<br />

did not consider the other "parent" a spouse or live-in partner. If the pair relationship<br />

R-3

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

Saved successfully!

Ooh no, something went wrong!