[CC] PIDM as ID in PPRD
David Rigg
drigg at sbc.edu
Wed Mar 26 09:54:56 EDT 2008
Indhu cloned PPRD from PROD last night.
I've made several changes to the data in PPRD.
The first involved changing each SPRIDEN_ID that was the same as the
SPBPERS_SSN to be the same as the SPRIDEN_PIDM (left zero filled). This was
easy to do and went cleanly.
The next change involved replacing SPRIDEN_IDs of the form @nnnnnnnn with
the SPRIDEN_PIDM (left zero filled). This was not as clean since it the
result could duplicate another record if the @nnnnnnnn ID had been
previously replaced by the SSN.
Another change involved making the PIDM ID the current ID. This was also
messy. Some IDs where SPRIDEN_CHANGE_IND is null had otherwise identical
entries where SPRIDEN_CHANGE_IND = 'I', so one of those IDs had to be
deleted in order to proceed. Some PIDMs had no current ID and for those
PIDMs a current ID needed to be created without replacing another one.
In the process I noticed several things in the data that I might not have
anticipated:
SPBPERS_SSN entries that were not valid SSNs. (I treated them as valid
anyway. See for example P00137961, P00071753, P00026739, or P00118730)
SPRIDEN_IDs that look like SSNs but that don't match the SPBPERS_SSN (see
for example P00174730)
ID or name change entries in SPRIDEN that do not appear to change the name
or ID (see for example P00174730 in PROD)
PIDMs with no current ID (see for example P00159210 in PROD)
PPRD is ready for you to look at to see/test the impact of the above
changes.
http://gandhi.noc.sbc.edu:7575 <http://gandhi.noc.sbc.edu:7575/>
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.sbc.edu/pipermail/banner-coordinating-committee/attachments/20080326/7ff1a230/attachment.html
More information about the Banner-coordinating-committee
mailing list