|Page tools: Print Page Print All RSS Search this Product|
What does ABS mean when it releases output as 'Keep Secure'
ABS sometimes release output to RADL users that needs to be kept secure. Output released as 'Keep Secure' must be very carefully managed by clients.
All RADL output that ABS releases with a 'Keep Secure' caveat can be used in further analysis. However, it cannot be published. 'Keep Secure' output includes all printouts of unit record information, as well as the results of analysis with any likelihood of breaching confidentiality.
How do clients ensure they are taking the appropriate steps to carefully manage their 'Keep Secure' output?
'Keep Secure' means that analytical results, whether they include unit information or not, must be retained in a secure environment. Printouts of this nature should be kept under lock and key, and electronic output must be stored in strongly protected systems.
RADL 'Keep Secure' printouts must be securely destroyed (ie shredded) when no longer needed, and analytical output (whether or not it includes unit record information) held in an intranet must be deleted. Deletion must happen in such a way that recovery is not possible by unauthorised people.
RADL 'Keep Secure' output cannot be shared between users who do not have access to the source CURF, nor with users in other organisations whether or not they do have access to the CURF.
Test whether your RADL code works with our test files
Sometimes the way RADL works can surprise users. Code that they might normally expect to run against an ABS CURF in their own environment doesn't fully work in RADL.
So how can users go about checking whether their code will run in RADL?
There's two ways: firstly, check out the restrictions on program statements in Chapter 2.3 of the Remote Access Data Laboratory (RADL) User Guide (Cat no. 1406.0.55.002).
Secondly, download a CURF test file and run your code against it.
MASS provides authorised RADL users with test files for each new CURF to which they have access. Test files are downloadable files with exactly the same structure as the CURF. The data in each test file however is synthetic and has been randomly generated.
Downloaded test files can be used to develop code to run against the actual CURF on RADL. RADL programs can be run locally against downloaded test files to check for coding errors prior to submitting the job through the RADL.
Test files are available for all CURFs released since 2005, and are being developed for all CURFs hosted on RADL. RADL users can locate test files for the CURFs to which they have authorised access in the 'CURF Documentation' pages accessed via the Help link in the RADL.
MASS continues to be available to help you with any queries that cannot be answered by your organisation's CURF Contact Officer, or from ABS CURF web pages. Our staff include Kim Farley-Lamour (Director), Grant Mitchell (Assistant Director), Simone Maconachie, Bob Osten, Damien Kennedy, Carolyne Henderson, Rachel Price and Liliana Rojas.
If you have a query for ABS about accessing CURFs, would like to request more microdata training for your organisation, or if you require more information about the ABS/AVCC CURF Agreement, please contact the Microdata Access and Strategies Section at:
These documents will be presented in a new window.