>>>>> "Tim" == Tim Kirby <[email protected]> writes:
Tim> On 5/3/11 3:21 PM, "John Stoffel" <[email protected]> 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. Tim> I missed the SSN requirement... it's not obvious to me why SSN Tim> would appear anywhere in this. If it's being used as a unique Tim> handle, generate an arbitrary unique ID. You absolutely *don't* Tim> want to have people critical information like SSN's stored Tim> anywhere that is not required (e.g. in payroll databases or Tim> other repositories where there is an otherwise unavoidable Tim> legal requirement to have it). That's a great comment, and I actually agree on it. I was trying to think with the $$$$ hat, which needs to have a reliable (ha!) key to use for tracking where the money comes/goes to. So yes, using non-SSN based unique ID is key here. The Handle will obviously change over time. The Key shouldn't since people don't change over time. Famous last words... :] Tim> You really don't want to be held responsible for someone Tim> being the victim of identity theft. Tim> Just sayin' I agree 100%, I miswrote in my musings as I was composing the reply. John _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
