Quoting Jason Stephenson <[email protected]>:
Stepping down from my soapbox, I see absolutely no reason for a US library to store a patron's SSN. A drivers' license number, perhaps, but not the SSN. My suggestion is to delete the field, and if someone needs to track such an identifier then let them figure it out within the bounds of their local law.
Of course, after saying the above, I realize that their isn't a SSN field in the patron record, but the user ident_type and ident fields. I guess the SSN label should be removed or whatever.
Frankly, it shouldn't be a technical issue. It is a policy issue to be determined by each Evergreen user (and I use that term loosely). It's also not unique to Evergreen.
-- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium Chief Bug Wrangler, Evergreen ILS
