-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Dutch BSN in numeric columns #31
Comments
I would strongly advise against storing a BSN in a numeric column. It may cause the same impracticalities as storing a bank account number in a numeric column, which caused interesting problems in some systems when IBAN was introduced. Just because something has digits, does not make it a scalar number. There is no "bigger" or "smaller" BSN, and they can not be added or subtracted. In that sense, it is not a number. Particularly if it is an identifier for which the syntax rules are external to your system. Nothing against making this technically possible, but it makes me wonder... why? |
Point taken and yes, I agree with all the statements above. The point is that more than a few legacy systems have been implemented this way, i.e. by storing social security numbers in a numeric column. |
True. I've seen systems like that. I usually push a bit to get that fixed. But technically speaking, yes it should be possible to anonymize number-like data based on numeric fields in a database. |
That's exactly my point, because I believe it's not the responsibility of the anonymisation tool to determine what column definition is used to store BSN in an application's database. |
Merged into develop, part of next release. |
Anonimatron version: 1.9.3
Currently anonimatron generates an Exception if a Dutch BSN is configured for a numeric column in a database table, like so:
It would be nice to support numeric columns as well, because a Dutch BSN is a valid number.
The text was updated successfully, but these errors were encountered: