 |
 |
I think it would be fairly easy to add a unique identifying number for each person (call it an account # if you must), that doesn't change. An account # could have a ZPID, APID and SSN associated with it, but keep the SSN on only the systems that really need it. Here's my question though. It seems that the APID could of easily have done this, so why complicate things with both an ZPID and APID? Have everyone move to APIDs and be done with using SSN numbers. Easy. Edward Glowacki wrote: > Paul Donahue wrote: > >> I share this view as I'm sure most people do. I am an example of a >> person who has both an APID and ZPID, I think my MSU Net ID would be >> a much better way to link these two pids rather than SSN. >> >> >> > Yeah, I have an APID and a ZPID too. Hardly ever use the ZPID for > anything though. > > As far as Netid's as a link between ZPID and APID, Netid's aren't static > over time, people change their Netid's when they get married, etc. SSN > is ultimately the one identifier that 1. everyone has and 2. doesn't > change. I agree that SSN shouldn't be used for as much stuff as it is, > but right now there isn't really a viable alternative that I know of. > SSN's have been used many, many places (not just the Library or MSU, but > all over the country) for many years, and are so far embedded into a lot > of things that to make a change away from SSN's everywhere they're used > would require a lot of work. Within MSU it might be possible to get > away from SSN's and replace them with some sort of equivalent unique ID > that each person only has one of, but that will take time. > > -ED