HESA Student record 2012/13
Timescales for data collection - stages of data submission
Version 1.0 Produced 2013-04-30
The document below is designed to guide institutions through the stages of data submission for the Student Record.
At a glance
|August 2012 to March 2013||Institutions' local preparations|
|April 2013||Validate data locally using validation kit|
|June to July 2013||C12051 Pre-collection validation system|
|June/July 2013||C12051 preparation guide released|
|August 2013||C12051 data collection opens|
|15 September 2013||Return date|
|24 September 2013||Commit date|
|24 September to 31 October 2013||Data quality checking period|
|31 October 2013||Last submission|
|1 November 2013||Sign-off|
The graph above details the expected curve of sector activity during the data submission period of August to the end of October 2013.
Institutions should read the C12051 Student record coding manual and associated documentation for details of the requirements for the return.
During these months institutions will need to load and maintain local student record systems including: registration, enrolments, qualifications and, if applicable, the UCAS data for HESA (formerly *J transaction).
If you have any queries with the requirements for C12051 please contact Institutional Liaison.
HESA's data quality assurance processes are outlined in the Validation overview.
The C12051 validation kit is made available to download from: Validation kits.
The kit enables institutions to test their data locally against the insert-stage validation ahead of the main collection opening in the summer. Institutions are strongly encouraged to use the validation kit as part of their data preparations.
The Student Pre-Collection Validation Systems (PCVS) provide an opportunity for institutions to expose their data to a wide range of validation checks before the data collection system opens.
Further details on the checks included in INSERT-stage validation can be found in the Validation overview.
The PCVS system provides the following functionality:
|INSERT-stage validation||These reports detail any validation errors or warnings triggered by the submission.|
|Entry Profile match report||This report lists any incoming instances submitted without Entry Profile data do not link to instances returned in previous collections. The Entry Profile entity must exist where the corresponding Instance has not been previously reported (i.e. cannot be found on the HIN/EntryProfile register).|
|Exception Report||A simplified COMMIT transaction running a wide range of exception stage validation checks.
Note that the full range of COMMIT checks and reports will not be implemented until the main data collection system opens in August.
|Frequency Counts||These counts detail the data submitted for all records listed by field and valid entry.|
HESA does not monitor or store data submitted by institutions to the PCVS system.
Access and PIN codes for this system will be distributed to Student record contacts when the system opens.
In advance of the main collection opening HESA releases a preparation guide. This provides further guidance of the requirements for the collection year, with particular reference to any areas HESA's statutory customers wish institutions to pay particular attention to during coding and submission.
Notification of the publication of this guide will be sent to Student record contacts, and is also circulated on sector mailgroups such as the Admin-HESA JISC mailgroup. If you would like to join Admin-HESA please contact Institutional Liaison.
The C12051 collection database opens on the submit site around 4-6 weeks ahead of the return date providing institutions with the opportunity to further test files against the full range of validation and exception checks ahead of the return date deadline.
For a user guide for the submission of C12051 Student record data please visit the Student collection.
Access and PIN codes for this system will be distributed to Student record contacts when the system opens.
HESA monitors all transactions on the system to ensure institutions are progressing reasonably and not encountering difficulties. However, if you require assistance with the submission process, please contact Institutional Liaison.
Institutions are required to send complete data that has passed insert-stage validation to HESA by 15 September 2013.
A single validation failure will result in no data being imported into the system.
Insert-stage business validation rules are listed within the Business rules summary document, or individually in each field within the C12051 coding manual. The insert transaction diagram illustrates the validation process that data files will be subjected to.
Data which fails validation will not be considered to have been returned to the Agency.
Institutions are advised to send complete data that has passed COMMIT-stage validation to HESA by 24 September 2013. This schedule allows the maximum amount of available time for data quality checking.
Commit-stage validation rules can be viewed at COMMIT-Stage validation. Data which fails validation will not be considered to have been returned to the Agency.
To be counted as having met this deadline one of the following submission statuses needs to have been met:
|Commit passed but HIN fail||Commit passed but HIN fail|
Note that failing the HIN checks does not prevent an institution from passing commit, and therefore meeting the commit deadline. Where HIN errors are encountered these should be resolved by the institution during the data quality checking period.
The TEST_COMMIT facility is available for the majority of the data collection period. This facility allows institutions to process a transaction, which, if successful will generate commit stage reports for scrutiny. These reports are for institutions' purposes only and will not be checked by HESA. Details of these reports are provided below.
Institutions are strongly encouraged to make use of the TEST_COMMIT facility as part of their data preparations. TEST_COMMIT serves as a useful interim facility in the data collection process. The facility enables institutions to view the commit reports and assess submitted data for anomalies before processing a full COMMIT to be scrutinised by HESA.
A successful COMMIT transaction will generate several reports containing management information that institutions will need to review to assess data quality. These reports for review are:
This Excel workbook contains a series of tables presenting much of the submitted data to enable institutions to check that their submission represents their institution as expected. Included within these tables is a cross-comparisons of the use of cost centres between the Student record, Staff record and Finance Statistics Return. Institutions are encouraged to liaise with colleagues responsible for these other returns to ensure commonality in use of cost centres.
|Check documentation compare facility||
This icon is available against every recommit made by the institution. This icon highlights changes between the two most recently processed test_commit/commit transactions. Cells highlighted in colour denote a change, by hovering the mouse over this cell the plus/minus difference between the two figures can be viewed.
These counts detail the data submitted for all records listed by field and valid entry.
This report details any COMMIT-stage validation errors/warnings triggered by the submission.
HIN checks are made to ensure that instance-specific information remains consistent year-on-year. Further information on HIN can be found at: Year-on-year linkage (HIN).
|HIN Target List||
The HIN target list is a list of students for whom a record is expected in the 2013/14 return. The list consists of records that have been returned as 'live' in 2012/13.
|National Student Survey (NSS)||
The National Student Survey (NSS) report identifies undergraduate students expected to be in the final year of their course in the academic year 2012/13 and therefore eligible to be included in the NSS census.
|DLHE population (POPDLHE)||
This report identifies students included within the 2012/13 DLHE target population The report includes both students with Instance.ENDDATE between 1 August 2012 and 31 December 2012 inclusive will have been surveyed in April 2013, and students with Instance.ENDDATE between 1 January 2013 and 31 July 2013 will be surveyed in January 2014. Coverage details for the 2012/13 DLHE record can be viewed at: C12018 Coverage of the record.
Record contacts should liaise with colleagues in the Careers Service to ensure that the right graduates are included in this report that will be required for the 2012/13 DLHE record (C12018), as the POPDLHE cannot be rectified once the Student record has closed.
This icon provides institutions with the derived field populations used by HESA to populate the items displayed within the check documentation. These derived fields can be used by institutions to re-create these items.
|Information Reporting Interface Service (IRIS)||
Following a successful COMMIT an automatic data feed will be sent to the relevant funding council to conduct reconciliation calculations. The results of these calculations will then be fed back onto the HESA Data Collection System for the institution to download. Note that this system runs alongside the HESA Data Collection System and will not impact on its data processing.
Institutions are required to review the reports and to resubmit data in order to resolve data quality issues. Institutions can contact Institutional Liaison throughout this period to request their data is decommitted in order to make adjustments to the submission. The data quality checking period is an iterative process during which institutions may need to submit, commit, review and decommit their data several times to ensure the final submission is credible. The commit transaction diagram illustrates this iterative process.
Institutions may also wish to decommit their return during this period in order to include results from late examination or re-sit boards.
During this period Data Quality Analysts at HESA will also examine data committed by all institutions. If any anomalies are found queries will be raised through the Minerva DQ database. Nevertheless institutions are in a better position to recognise more detailed anomalies within their data, using local knowledge of the intricacies of their own institution. As a consequence institutions are required to either resubmit their data to amend these anomalies, or provide an explanation through Minerva as to why these apparent anomalies are genuine.
Upon satisfactory completion of this process data will be set to credible.
In order to meet obligations for hand-over of data to its customers, HESA needs to receive all data files by 31 October 2013.
As part of the data quality assurance procedures, HESA requires the return to be signed-off by the head or acting head of your institution. This verification offers both the institutions and HESA assurances regarding onward use of the data. Sign-off completes the data collection process.
||On the system your institution's data will be set to credible and a new icon will be made available from where the sign-off form can be downloaded and completed. Once completed, the form should be posted back to HESA. Please note that the transaction number on the sign-off form must correspond to that of the data being signed-off.|
Note: Institutions should download and keep copies of all relevant reports that they are likely to need during the year. This will be necessary as access to the site will be restricted after the collection has closed.
Data is also used by HESA in the following ways:
Student Qualifiers and Enrolments Statistical First Release
HESA Students in Higher Education publication
Performance Indicators in Higher Education
General data enquiries
Contact Liaison by email or on +44 (0)1242 388 531.