Understanding Society User Support

Hi Chris,
the note is from quite a while back and did not get updated as 'the code' developed. There are two distinct aspects to the code: identifying cases that are inconsistent on relationship hence were inspected for editing, and code to identify cross-wave inconsistent relationships (relationship_dv).

To identify cross-wave inconsistencies, you can adapt the code below. It lists natural child relationships that changed at least once throughout the observation period. You can list other inconsistencies by adjusting the line: bys ID: gen _natch=sum(L.relationship_dv==4 & !inlist(relationship_dv,4,.).

• Start code
  local w=1
  foreach x in a b c d e f g h i {
  use pidp apidp `x'_relationship_dv using ${inpath}/`x'_egoalt, clear
  rename `x'_relationship_dv relationship_dv
  gen wave=`w'
  save M:/egoalt_`x', replace
  local w=`w'+1
  }
  foreach x in a b c d e f g h {
  append using ${outpath}/egoalt_`x'
  }
  sort pidp apidp wave
  egen long ID=group(pidp apidp)
  bysort ID (wave): gen index=_n
  xtset ID index
  replace relationship_dv=. if relationship_dv<1
  bys ID: gen _natch=sum(L.relationship_dv==4 & !inlist(relationship_dv,4,.)
  bys ID: egen Dnatch=max(_natch)
  recode Dnatch (0=0) (else=1)
  lab var Dnatch "Nat child relationshp changes to something else"
  li ID index pidp apidp relationship if Dnatch==1, sepby(ID)
• end code

The code to identify cases that are inconsistent within a wave now requires quite a bit of editing and commenting before we could share it meaningfully. If this is the aspect of 'the code' that you are interested in we can look into how it might be done. In principle, we are looking into sharing do-files but this particular set is a bit of a beast and it may take a bit longer. Do let us know.

Hope this helps,
Gundi

Chris confirmed this solved the query.