|Page tools: Print Page Print All RSS Search this Product|
USING MICRODATA RESPONSIBLY
The ABS reserves the right to seek additional information from applicants regarding their statistical purpose for the use of microdata.
WHEN CAN MICRODATA BE SHARED?
Access to microdata can only be granted by the ABS. Microdata must not be shared with other individuals as this is a breach of the Undertaking signed by your organisation. Any person who needs access to microdata or uncleared DataLab output must apply and be approved by the ABS before accessing the data. This includes members of your research project team who will see, discuss or use microdata or uncleared DataLab output. Sanctions may be brought against organisations and individuals found to be sharing access to microdata with unapproved individuals or organisations.
Where researchers from different organisations are collaborating on a project, the ABS may provide permission to share specific microdata and uncleared DataLab output. See Collaborating on microdata research below.
WHEN CAN MICRODATA OUTPUT BE SHARED?
Output that can be shared
Cleared DataLab output: All DataLab output that has been cleared by the ABS may be shared or published.
Basic CURF output: Tables or other aggregated output (for example, averages and model parameters) may be disclosed, published or disseminated by the user.
Examples of basic CURF aggregate data that do not reveal microdata and are not required to remain in a secure environment include:
When disseminating aggregated output or reports, you must ensure that you correctly attribute ABS microdata as the source. See Microdata user obligations for Licence provisions, copyright and attribution.
Output that cannot be shared
Unit record data (microdata) cannot be shared unless the ABS has provided written permission to do so. It must not be disclosed or disseminated by the user, and must be securely stored. This includes:
Microdata collaboration can occur when consultants conduct work on behalf of an organisation, or when multiple organisations are working together on a research product.
When do collaborating researchers need to be approved to access microdata?
When can collaborating researchers work on a project without seeking approval to access microdata?
DataLab project workspaces
Researchers may work together on a project within the DataLab. In this case, the ABS may provide a shared workspace only accessible by the project researchers. People approved to participate in the project may share their uncleared DataLab research and results within the DataLab workspace, whether it is microdata or aggregate data. This is because all the researchers have been approved to access that microdata and access is within the secure DataLab environment.
MERGING OR MATCHING MICRODATA
You may merge microdata files where the data has been released as a multi-level or linked file, and identifiers have been provided for this purpose. You must not merge microdata files that have not been released in this way.
You must not match microdata files where identifiers have not been provided for that purpose. Different microdata releases may include information about the same record. For example a person may be selected in one survey and also be included in an administrative microdata file about people. In this case, identifiers will not be provided to facilitate matching that record across the two microdata files. You must not attempt to match that record based on their characteristics on the two files. This includes matching two ABS microdata files or matching ABS microdata with microdata from any other source.
An example of a multi-level microdata file is person data in one file and household data relating to those persons in another file. In this case, each record on the person file will include a person and household identifier. This enables you to group persons into households, and to undertake research about those people as a household group. Merging microdata files is only permitted where identifiers have been provided as part of the release.
ABS releases microdata files from many sources including surveys, censuses and administrative data provided by other organisations. In some cases the ABS may undertake a project to match or link records based on their characteristics. You must not attempt to match or link microdata records yourself. When the ABS links records to create a linked microdata file, it is assessed to ensure that the confidentiality of the records is protected before being released. Where the linked data is provided in multiple files that may be used together, record identifiers will be provided for that purpose.
Researchers may also want to add aggregate data characteristics to a microdata file. This may be appropriate, provided it is not undertaken in a way that assists identification of the record. For example, if median salary by sex and age was added to a person microdata file, this would not represent the actual income for each record but may benefit the research.
AGGREGATE DATA AND MICRODATA
Aggregate data is produced by grouping information into categories and combining values within these categories, for example, a count of the number of people of a particular age (obtained from the question ‘In what year were you born?’). Aggregate data examples include tables, means, medians, ranges and regressions.
Microdata is a dataset of unit records where each record contains information about a person, organisation or other record. This information can include individual responses to questions on surveys or administrative forms, which are characteristics of that record.
These documents will be presented in a new window.