Statistics Group Strategic Priorities - RAP Month
Alice Byers
Data Innovation Team, Data Division
14 February 2024
An overall approach to carrying out analysis
A set of principles that ensure analysis is:
In order to achieve the full benefits, at a minimum a RAP must:
Minimise manual steps
Be built using open-source software; e.g. R, Python
Be peer reviewed by colleagues
Be version controlled; e.g. Git
Be open to anyone; e.g. code published on GitHub
Follow good practice for quality assurance
Contain well-commented code and have documentation embedded
Routine ‘traditional’ publications
Shiny dashboards
Ministerial briefings
FOIs
One-off analysis
Data extraction
Data cleaning
Data analysis
Modelling
Data visualisation
Reporting
Currently in development
Four levels with criteria for each
Level 0 - Aspiring RAP
Level 1 - Fundamental RAP
Level 2 - Intermediate RAP
Level 3 - Advanced RAP
Data Innovation team provide RAP support
Gerry Scullion, Tom Wilson and Alice Byers
Lots of information on the Statistics Group Sharepoint
We can help with:
Reviewing project requirements and mapping out a process.
Deciding where to start when transitioning a process to a RAP.
Understanding what software is available and how to make best use of it.
Following best practices for structuring scripts, files and folders for your RAP.
Using Git and GitHub, ensuring your RAP project is setup within a repository.
Applying best practices to your code, for example “do not repeat yourself” and following coding conventions from a style guide.
Reviewing your code.
Long term support
The aim is to help you to develop your RAP skills, not to write all the code for you.
Agreement to work together for 4-6 months
Regular meetings to review progress
Get in touch to discuss your project
Blog: How we saved 3 analysts 6 weeks of copying and pasting
Email me – I’m always happy to talk about RAP!