On 5/3/11 3:21 PM, "John Stoffel" <j...@stoffel.org> wrote: > >You'll need to problably have a mapping of: > > userid > First/Middle/Last > campus > ssn (scary!) > status (one of faculty,student,staff,other) > created date > disabled date > >Where the tuple of (userid,campus,status) is the unique key. I assume >a faculty at one campus can be a student elsewhere.
I missed the SSN requirement... it's not obvious to me why SSN would appear anywhere in this. If it's being used as a unique handle, generate an arbitrary unique ID. You absolutely *don't* want to have people critical information like SSN's stored anywhere that is not required (e.g. in payroll databases or other repositories where there is an otherwise unavoidable legal requirement to have it). You really don't want to be held responsible for someone being the victim of identity theft. Just sayin' Tim -- Tim Kirby t...@kirbys.org _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
