scribe for 79 links

[wibeasley]

Start the pipeline that takes the results in the database to eventually the rds for NlsyLinks.

[wibeasley]

this is mostly done now. For some reason, there ar a few ExtendedIDs and SubjectIDs that are null, in the really early algorithm versions (eg, 25 through 39)

  SELECT
    --a.ID
    a.AlgorithmVersion
    ,rs.ExtendedID
    ,a.SubjectTag_S1
    ,a.SubjectTag_S2
    --,s1.SubjectID             AS SubjectID_S1
    --,s2.SubjectID             AS SubjectID_S2
    ,a.MultipleBirthIfSameSex
    ,a.IsMz
    ,a.SameGeneration
    ,a.RosterAssignmentID
    ,a.RRoster
    ,a.LastSurvey_S1
    ,a.LastSurvey_S2
    ,a.RImplicitPass1
    ,a.RImplicit
    ,a.RImplicitSubject
    ,a.RImplicitMother
    ,a.RExplicitOldestSibVersion         AS RExplicitOlderSibVersion
    ,a.RExplicitYoungestSibVersion       AS RExplicitYoungerSibVersion
    ,a.RExplicitPass1
    ,a.RExplicit
    ,a.RPass1
    ,a.R
    ,a.RFull
    ,a.RPeek
  FROM [Archive].[tblRelatedValuesArchive]  a
    LEFT JOIN Process.tblRelatedStructure rs          ON (a.SubjectTag_S1=rs.SubjectTag_S1 AND a.SubjectTag_S2=rs.SubjectTag_S2)
    --LEFT JOIN Process.tblSubject          s1          ON (rs.SubjectTag_S1 = s1.SubjectTag AND rs.ExtendedID=s1.ExtendedID)
    --LEFT JOIN Process.tblSubject          s2          ON (rs.SubjectTag_S2 = s2.SubjectTag AND rs.ExtendedID=s2.ExtendedID)
where a.SubjectTag_S1= 864901 and a.SubjectTag_S2=864903
  ORDER BY a.AlgorithmVersion, rs.ExtendedID, a.SubjectTag_S1, a.SubjectTag_S2