Disclosure Control is a necessary evil. We have an obligation to protect people’s information and if we didn’t they wouldn’t complete their Census forms. Applying disclosure control though means that we are always going to lose something - but there are choices and trade-offs to be made. The survey asked which SDC features users consider to be most important for example, maintaining additivity in tables, consistency across tables, counts that are as near as possible to true counts, a method that is easy to understand, being able to take account of the effects of the method in analysis and the relative importance of these features. Users from different communities may have different priorities and we will be reporting on this and giving feedback to the methodologists who are evaluating the short-listed SDC methods in terms of the protection they give and the effects on the data -a risk/utility continuum.
We are aware that users were very unhappy about the effects of the late addition of Small Cell Adjustment in the 2001 Census, particularly to tables with low counts such as the OA level Origin/destination tables which resulted in users reporting that such outputs were “unfit for purpose”. Whichever SDC method is applied the data quality of sparse tables are going to be disproportionately affected. For these types of tables we are considering the option of applying lower levels of SDC and making the output available to users only under special licence or accessed in data labs with outputs checked prior to removal. For example, some outputs from the Origin/Destination tables could be made available publicly at Super Output Area (SOA)/Data Zone level, made available under licence at Output Area (OA) level, and allow users interested in specific journeys access to detailed micro-data in a safe setting.
What would you feel about access arrangements such as this?