The first time you submit data, there’ll be a little bit of ‘wrangling’ to correct errors and map your local data codes to the framework’s standard labels. Once done, the framework ‘remembers’ the corrections so that subsequent submissions cause much less fuss.
Stage 1 – submitting the data
Follow the ‘how-to-submit…’ guide below to submit your applications data.
Stage 2 – Updating and correcting field names
If there are any errors, you’ll get an email indicating that there there are field names * missing * and/or * ignored*. Here’s what it means, and what to do:
*missing* fields will indicate a whole column of data is missing. If you don’t have any data for a particular column e.g. ‘linked_appref’ then include the column and the field name but leave the data blank.
*ignored* fields indicate that the field name is incorrect (e.g. wrong spelling, wrong name, or even a stray ‘space’ in the correct spelling). An incorrectly spelled field name will appear as both *missing* and *ignored* – just correct the field name.
Once you’ve made the corrections (the ‘how-to-submit…’ guide contains the correct field names if you’re not sure), re-submit the spreadsheet of data to firstname.lastname@example.org and make sure you give the file exactly the same name as the first submission e.g. (council shortname).xlsx
Stage 3 – mapping data to the framework standard labels
Once the data columns and field names are correct, we’ll email you and ask you to help us ‘map’ all of the local names you have for things (e.g. application type ‘HOUS’) to a standard set of framework labels.
The screen cast embedded below explains what to do:
Click the icon at the bottom right to watch in full screen.