I've added a page summarising (and signposting) standards that will be a requirement (above and beyond the base EES standards) for data sets being uploaded for use with the API.
Why are these changes being made?
We want a much more coherent data ecosystem when it comes to the API and we'll be manually checking data files against this. So we need a framework laying out clearly both for analysts intending to make data their data available via the API, and for us when reviewing a data set for acceptance on to the system.
Detailed description of changes
I've added a specific API data standards page which is linked from the statistics production menu.
This covers four key elements:
tidy data
standardised filter names and items
standardised indicator names
character constraints on column names, labels and filter items
Issue ticket number/s and link
Checklist before requesting a review
[ ] I have checked the contributing guidelines
[ ] I have checked for and linked any relevant issues that this may resolve
[ ] I have checked that these changes build locally
[ ] I understand that if merged into main, these changes will be publicly available
rmbielby
commented
2 months ago 
Overview of changes
I've added a page summarising (and signposting) standards that will be a requirement (above and beyond the base EES standards) for data sets being uploaded for use with the API.
Why are these changes being made?
We want a much more coherent data ecosystem when it comes to the API and we'll be manually checking data files against this. So we need a framework laying out clearly both for analysts intending to make data their data available via the API, and for us when reviewing a data set for acceptance on to the system.
Detailed description of changes
I've added a specific API data standards page which is linked from the statistics production menu.
This covers four key elements:
Issue ticket number/s and link
Checklist before requesting a review