Flagging personal and sensitive data
Closed this issue · 1 comments
OpenCommunity introduced the new fields: personal_data and sensitive_data in the contact table.
iStandUK comments "this seemed to be the wrong place to put them, as you can have more than one contact entry for a service. As these are boolean, they could be applied as taxonomy terms, if at all." and "Does this need to apply to data other than this Contact information? Should this be applied to service/location?"
However, as Open Referral UK is an open data standard, there is an argument for excluding these fields altogether. Of course they may be held in a database to determine if records should be published or not in the open data set.
Considered an internal database property not one for data interchange. Only public, non-personal; data should be included.