Unistats 2020/21: Support guides
This page provides an overview of the 2020/21 Unistats collection (C20061).
This should be used alongside the C20061 coding manual, which provides more detailed, technical information about the collection.
HESA collect data across a number of streams. These streams focus on different aspects of higher education.
The Unistats stream collects data about full-time and part-time undergraduate courses available for application for the next academic year. Details of what information needs to be returned are included in the Coverage document found in the coding manual.
The data we collect is currently published on the Discover Uni website (owned by the Office for Students and the higher education funding bodies in the other countries of the UK). The data is also available to the public and other information providers as an open dataset.
Our coding manuals provide you with all the necessary documentation to support your data return. The coding manual contains technical documents giving detailed information on the record's coverage, data specification and submission formats. Familiarising yourself with these documents will help you make an accurate and timely return.
Each collection has its own coding manual which can be found in the Data collection section of our site. By default, you will land on the open collection for each record; you can then select previous or future years.
The coding manuals will be updated throughout the data collection cycle and Record Contacts informed by email when new versions are made live. Be sure to check the manual's Revision history for a summary of changes.
You submit data via our Data Collection system. To access this, you will need to have an appropriate role in our Identity System (IDS). We publish an IDS user guide which includes information on creating and editing your account.
You will need to be given access to the Data Collection system by the relevant Record Contact at your provider.
Once you have access to the system you will be able to upload files, track the progress of your submission, view data quality issues and download reports. An overview of the submission and validation process is given below. Further details are provided in the Coding manual under the 'Submission process and quality assurance' section heading.
The coding manual homepage includes all the technical information you require, including:
- The data specification
- File format specifications
- A detailed collection schedule
- Our XML data entry tool (available for some streams)
- Quality rules.
This Support guides page collects together the following resources:
- User guide
- Data collection system: Known issues and release history.
In the Support area of the HESA website, you can find:
- User guides for our Identity System (IDS) and Issue Management System data quality database (HESA subscribers only).
- Support with using XML files
- Our XML amalgamator tool and Validation kits available for some collections.
Our Data innovation section includes information about:
- Open and recently completed record reviews, including information about changes we are implementing
- Our Data Futures programme which will transform the higher education information landscape.
In the About section, you can find:
Our expert analysts have a thorough understanding of our records and processes. We are here to support you throughout the data submission process.
Please note that from C20061 HESA are supporting English Further Education colleges with their Unistats submissions.
Data collection system: Release history and known issues
|Issue summary||Status||Date raised||Date resolved|
Issue ID: 96100 - Location.ACCOMURL.1 not triggering as expected
The QR.C20061.Location.ACCOMURL.1 rule is triggering incorrectly, as it is currently checking if any Location entity for a Location.ACCOMURL and only reporting the first it cannot find any. Additionally, it is not linking Location.LOCIDs to KISCourse entities, instead simply checking for the existence of Location.ACCOMURL and whether all courses in the file have a KISCourse.DISTANCE value of '1' ('Course is only available through distance learning'). The intention of the rule is to check the Location.LOCID against linked KISCourses, and check the KISCourse.DISTANCE values of those linked KISCourses, rather than all courses in the file.
|Open||22 June 2020|
|Release ID||Release date||Release summary|
|Month||Scheduled areas of work|
|No releases yet|
Stages of data submission
A. Sending data
Send data by clicking on ‘Send button' in the Data Collection system.
Browse your computer to locate the file you wish to submit, and upload the file to the Data Collection system.
- Files can have any name
- Files must be in XML and conform to the relevant XML Schema Definition (XSD) file
- Files can be compressed using PKZip/WinZip which will significantly reduce the upload time
- Only a single file can be held in the system.
B. Automated Validation
Automated validation checks will now run.
Further details on the quality rules applicable to this collection can be found on the coding manual
The Quality Rules report will contain the details of any rules triggered by the submission. Make any necessary amendments to the data and resubmit the file to the system. To pass validation the file must not trigger any validation errors.
*Note: Corrections cannot be made online to the file submitted to the Data Collection system and instead must be made to the file held locally, and the file then resubmitted.
Where possible the quality assurance report will be produced even where validation errors exist.
*Note that the NSS and Graduate Outcomes data will not be available until July and the Unistats output file will not be produced until then.
When all validation is complete the data is then considered as valid and this will be indicated in the Data Collection system
How to obtain a switch
When errors are triggered in the Data Collection system but the data has been checked and is genuine, you need to request a switch. This is because your file will not pass the validation requirements of the collection deadlines if there are any remaining errors.
Please email your switch request to Liaison, stating which rule is causing the error to be triggered and for how many records, together with an explanation as to why the data is genuine.
This will then be forwarded to your funding council/regulator for them to review. They may agree the switch, ask for more information or state how they wish the data to be returned so that an error is no longer triggered.
This request should be sent well in advance of any deadline, to allow sufficient time for a decision to be made.
When a switch has been agreed, it will be applied to your data for the count specified and the data will be reprocessed. This will resolve the error.
If the count increases, the rule will be triggered again, and you will need to request that the count on the switch be increased. This will be forwarded to your funding council/regulator for approval.
Once the file has passed all stages of validation and the Graduate Outcomes and NSS data is available, providers will have the option to 'approve the submission'. This will generate the sign-off form. A link to the sign-off form will automatically be emailed to the Accountable Officer/Head of Provider when available. The form should be completed and signed by the Accountable Officer (England and Wales) or Head of Provider (Scotland and Northern Ireland) and returned to HESA. This verification offers both the provider and HESA assurances regarding onward use of the data. Sign-off completes the data collection process.
The initial sign-off form can also be used (optionally) for the Accountable Officer/Head of Provider to nominate an individual with responsibility for signing off any updates made by the provider to the Unistats data after the submission deadline. Following publication of Unistats data in September only the Accountable Officer/Head of Provider or the authorised delegate can sign off further data submissions.