Student Alternative 2019/20: Support guides

HESA collects data across a number of streams. These streams focus on different aspects of higher education.

The Student Alternative stream collects data about students studying at a subset of higher education providers. Historically, this collected data about students studying at private higher education providers whose students could access student loans. This now includes some higher education providers who are registered with the OfS and are not required to submit the full HESA Student return as well as providers on limited designation or teach out. Details of which students need to be returned to us are included in the Coverage document found in the coding manual.

The data we collect on behalf of the sector is provided to the government and the relevant funding council in order to support the regulation of higher education. We also make anonymised data available to the public to enhance understanding of UK higher education and to support its advancement.

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 and track the progress of the collection.

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:

• Details of who we are and what we do
• Information about data protection 
• Information for providers including the Code of practice for HE data collections, and information about subscription rates and the fixed database facility.

Our expert analysts have a thorough understanding of our records and processes. We are here to support you throughout the data submission process. 

Contact Liaison by email or on +44 (0)1242 388531 

Find out more about Liaison

C19054: Deadlines guidance 

As previously communicated to providers, the approach to deadlines will be different this year.

Return, commit and final commit deadlines – these deadlines are not statutory deadlines for this year and no written confirmation is required if they are not met. We strongly recommend that providers follow the normal timeline to progress through this year’s data collection as achieving these milestones ensures that providers and HESA are well placed to achieve signed off data by the sign-off deadline. HESA and Statutory Customers will still use these as progress points and contact you to check on your progress.

Sign-off deadline – this remains a statutory deadline. Providers are required to have committed a final file, resolved all data quality queries in the Issue Management System, and returned a completed sign-off form to [email protected] by 5pm on the day of the deadline. Please be aware that it can take up to five working days for HESA to check your file once committed and raise any necessary data quality queries. You should therefore aim to commit your final file in good time ahead of the sign-off deadline to ensure your file is checked and any quality queries resolved in time for the sign-off deadline.

Providers in England should notify the OfS via [email protected] if you foresee any issues with meeting the sign-off deadline. If the sign-off deadline is not met, a HESA Late Sign Off form will be required by HESA, signed by your Accountable Officer.

If you do foresee any issues, please get in touch as early as possible so that we can provide additional support and guidance as required.

Data collection schedule: Anticipated dates for deadlines

The data collection deadlines for the Student Alternative return are being moved earlier to bring them into line with the Student return, to ensure that all providers are being treated consistently. In order to assist with this change, we will be phasing the adjustments to the deadlines over the C19054, C20054 and C21054 collections. The anticipated deadlines can be seen in the table below.

New fields: Instance.FUNDCODE, Instance.FUNDCOMP and Instance.FUNDLEV

Only providers who are registered in the Approved (fee cap) category on the Office for Students register need to return these new fields.

Providers in the Approved category do not need to return this data.

For more information please see the C19054 Supplementary notification of changes and the coding manual guidance.

Our JISCMail groups allow you to discuss specific streams with colleagues from across the sector. We also use the lists to circulate news regarding data requirements and coding manual and validation kit releases.

Join the HESA-AP student JISCmail list

If you encounter any problems, contact Liaison

A high-level summary of the C19054 major component releases are highlighted below.

This is a guide to the proposed sequence of releases. Releases may occur before, or after, the month indicated depending on internal and external factors.

January

• Data entry tool
• HUSID lookup service
• Roll-on of collection
• Validation kit with rolled on business rules from the previous year

February/March

• Business rules to match coding manual schema and coverage updates
• First load of the OfS designation file

April

• XTPOINTs library update
• Continuity Register update
• Opening of the Data Collection System with rules and rule compare functionality
• Designation report

May/June/July

• Business rules to match coding manual schema and coverage updates
• Derived field development
• Exception rule updates following derived field implementation
• Entry Profile, Data Supply, Continuity (Expected Instances) population report
• Business rules to match coding manual schema and coverage updates
• Credibility and Exception rule updates using available external static data
• Frequency Counts report
• Revisions to XTPOINTs appendix
• Credibility reports (revised for Registered and Designated provider categories)
• IRIS reports

August

• NSS (National Student Survey) draft report, Unistats report
• Commit functionality and Sign-off form

A. Sending data

Send data by clicking on the 'send data' button in the data collection system. Note that actions not currently available will be greyed out.

Browse your computer to locate the file you wish to submit, and upload the file to the data collection system. 

Tips:

• 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 on the system.

B. Validation

Automated validation checks (quality rules) will now run.

Further details on the quality rules which apply to this collection can be found in 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.

You can run some of these validation checks through our validation kit before submitting data to the data collection system. The kit enables you to test your data locally against schema and business stage validation rules prior to submission. You are strongly encouraged to use the validation kit as part of your data preparations.

Remember that you need to process and pass the business-stage validation in order to meet the requirements of the return deadline.

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.

To proceed to the next stage in the submission process, a valid file needs to have been submitted. The data will then be classed as 'committable' and the option to process a COMMIT transaction will be made available through the data collection system.  

Prior to committing data, you should review all of the reports produced on the data collection system and make any necessary corrections to the data.

The COMMIT transaction sends a copy of your submission to our data quality assurance team and, where appropriate, to the relevant funding council. We analyse your return in parallel with your own analysis.

Decommitting

A passed commit transaction will lock the system to prevent the data from being amended. This is to allow our data quality assurance team to analyse the submission. To unlock the system you will need to request a DECOMMIT transaction.

Request a decommit by email or on +44 (0)1242 388531

Remember that you need to process and pass a COMMIT transaction in order to meet the requirements of the commit deadline.

Once we have analysed your committed return, data quality queries will be posted onto the Issue Management System data quality database. Relevant users will be notified by email when these queries are available to view. The Issue Management System user guide provides help on using the Issue Management System.

Access the Issue Management System data quality database

Once your data has passed all the stages of validation, and any issues highlighted during credibility checking have been addressed, we will set the return to CREDIBLE. This produces the sign-off form.