XPSR01_2.8.1
| Field description | Field abbreviation | Field version | Field length | Field type |
|---|---|---|---|---|
| Standard registration population | XPSR01 | 2.8.1 | 1 | Char |
Valid entries
Dependent fields
- None
Depend upon fields
- XPSES01
- MODE
- ENDDATE
- COMDATE
- TYPEYR
- NOTACT
- UNITLGTH
- SPLENGTH
- PERIODENDDATE
Additional information
Summary
To generate a population for a 'whole year' count of active student instances, which counts each instance once and once only for each year of programme of study.
Standard definition
The HESA standard registration population is derived from the HESA Student or Student Alternative records and ensures that similar activity is counted in a similar way irrespective of when it occurs.
The population splits the student experience into 'years of programme of study'; the first year of which is deemed to start on the commencement date of the programme with second, and subsequent years, starting on, or near, the anniversary of that date.
Registrations are counted once for each 'year of programme of study'. Students who leave within two weeks of their start date, or anniversary of their start date, and are on a course of more than two weeks duration, are not included in the standard registration population. Students who have suspended study (e.g. dormant students), incoming visiting and exchange students from overseas, writing-up students and students on sabbatical are also excluded from this population.
Note that the starting point of the standard registration population is the session population, and so will exclude (where applicable):
1. dormant student instances (those who have suspended studying but have not formally de-registered)
2. incoming visiting and exchange student instances
3. postdoctoral student instances, and students primarily studying outside the UK
4. instances where the whole of the programme of study is outside of the UK
5. National College for Teaching and Leadership (NCTL) Subject Knowledge Enhancement (SKE) student instances
6. students on sabbatical
This derived field is created in both the Student record (Cyy051) and the Student Alternative record (Cyy054). The Student Alternative record makes use of the PERIODENDDATE field from the last active instance period, where there is one. NOTACT, STULOAD and ENDDATE are used to determine whether or not an instance period is active. If there are multiple active instance periods with the same PERIODSTART, take the one with the latest PERIODEND, or if these are the same, the one with the highest InstancePeriodKEY. Where there are no active instance period returned, the student is excluded from the standard registration population.
The Anniversary date identifies the anniversary of the commencement date of the study programme which falls within the current reporting period. For example, if Instance.COMDATE is 10 September 2018, Anniversary dates would be 10 September 2018 in 2018/19 dataset, 10 September 2019 in the 2019/20 dataset, etc. and Anniversary Instance.COMDATE + 14 days would be 24 September 2018 in 2018/19, 24 September 2019 in 2019/20, etc. When Instance.COMDATE is close to the end of the standard academic year and the anniversary of the commencement date plus 14 days may fall within the following standard academic year. For example, if Instance.COMDATE is 26 July 2018, the anniversary date would be 26 July 2019 in 2019/20 and anniversary Instance.COMDATE + 14 days would be 9 August 2020.
Where a programme of study is entirely within the current reporting period, Instance.COMDATE is used as the anniversary date.
Y1 is obtained by concatenating the first two digits from year in the system date with the first two digits of Institution.RECID (in Cyy51) or Provider.RECID (in Cyy54), e.g. Y1 = 19 for 2019/20.
To compare Instance.ENDDATE and Instance.COMDATE account must be taken of the month in Instance.COMDATE. For example:
• if Instance.COMDATE is 1 March 2019, for comparison purposes anniversary Instance.COMDATE in reporting period 2019/20 would be 1 March 2020 (Y1+1) and anniversary Instance.Comdate + 14 days would be 15 March 2020;
• if Instance.COMDATE is 1 October 2019, for comparison purposes anniversary Instance.COMDATE in reporting period 2019/20 would be 1 October 2019 (Y1) and anniversary Instance.Comdate + 14 days would be 15 October 2019;
• if Instance.COMDATE is 26 July 2019, for comparison purposes anniversary Instance.COMDATE in reporting period 2019/20 would be 26 July 2020 (Y1+1) and anniversary Instance.Comdate + 14 days would be 9 August 2020.
This population refers to the student's mode of study to exclude sabbatical, writing-up and dormant students where relevant to the collection. Modes 73 and 74, if available, are treated as active modes.
Technical Specification
In the Cyy051 Student record:
| XPSES01 | Instance. MODE | Instance. ENDDATE | Instance. TYPEYR | Instance. NOTACT | Instance. UNITLGTH | Instance. SPLENGTH | XPSR01 |
|---|---|---|---|---|---|---|---|
| 1,2 | 01, 02, 12, 13, 14, 23, 24, 25, 31, 33, 34, 35, 36, 38, 39, 65, 73, 74 | Null | 1,3,4, null | XPSES01 | |||
| 2 | Null | XPSES01 | |||||
| 1,2 | 0 | ||||||
| 5 | 0 | ||||||
| If completed, Instance.ENDDATE > anniversary Instance.COMDATE + 14 days | XPSES01 | ||||||
| If completed, Instance.ENDDATE <= anniversary Instance.COMDATE + 14 days | 3 | 01,02 | XPSES01 | ||||
| Otherwise, including null | 0 | ||||||
| 4 | 01-14 | XPSES01 | |||||
| Otherwise, including null | 0 | ||||||
| 5 | 01-42 | XPSES01 | |||||
| Otherwise, including null | 0 | ||||||
| Otherwise, including null | 0 | ||||||
| 43, 44 | 0 | ||||||
| 0 | XPSES01 |
Note: Instance.MODE 51, 63 and 64 in the Student record can only derive to an XPSES01 output of zero and hence an XPSR01 output of zero.
In the Cyy054 Student Alternative record:
To be considered inactive for the entirety of an instance period, the reporting period must be recorded as having no activity (InstancePeriod.STULOAD = 0), although it is not sufficient, to assess inactivity of an instance period on the basis of STULOAD alone.
Incoming visiting and exchange students, and those students who are studying abroad but spend more than 8 weeks in the UK, are permitted to return zero in the STULOAD field and consequently InstancePeriod.NOTACT must be also be considered.
Students who have no activity in the InstancePeriod in which their instance ends (usually due to the provider ending an instance retrospectively) will have a STULOAD of zero, but no NOTACT value. These are accommodated by using the presence of an ENDDATE to set their value to 'inactive', as otherwise they would be considered to be active in the absence of a NOTACT value stating otherwise.
Please note: in the following specification, the date reference '(Y1)' refers to a year-specific reference derived from the reporting year. For 2019/20, Y1 is 2019, thus for 2019/20 the year reference would be in the form 2019-08-01.
For each InstancePeriod in the collection, create a TEMP value as follows:
| InstancePeriod. STULOAD | Instance. ENDDATE | InstancePeriod. NOTACT | TEMP |
|---|---|---|---|
| 0, null | Not null, and < (Y1)-08-01 | 1 | |
| Null, or not null and >= (Y1)-08-01 | 1, 2 | 1 | |
| Null | 0 | ||
| > 0 | 0 |
For each instance, let Instance_Period_Active.PERIODEND be the date of the last active Instance_Period (latest PERIODSTART for which TEMP is 0):
Where there are no active Instance_Periods, set XPSR01 = 0.
Where two or more Instance_Period have the same PERIODSTART, take the one with the latest PERIODEND.
Where two or more Instance_Period have the same PERIODEND, take the one with the highest InstancePeriodKEY.
| XPSES01 | Instance. MODE | Instance. ENDDATE | Instance_Period_Active. PERIODEND | Instance. UNITLGTH | Instance. SPLENGTH | XPSR01 |
|---|---|---|---|---|---|---|
| 1 | 01, 02, 23, 24, 25, 31 | Null | Null | XPSES01 | ||
| <= anniversary Instance.COMDATE + 14 days | 0 | |||||
| > anniversary Instance.COMDATE + 14 days | XPSES01 | |||||
| If completed, Instance.ENDDATE > anniversary Instance.COMDATE + 14 days | XPSES01 | |||||
| If completed, Instance.ENDDATE <= anniversary Instance.COMDATE + 14 days | 3 | 01,02 | XPSES01 | |||
| Otherwise, including null | 0 | |||||
| 4 | 01-14 | XPSES01 | ||||
| Otherwise, including null | 0 | |||||
| 5 | 01-42 | XPSES01 | ||||
| Otherwise, including null | 0 | |||||
| Otherwise, including null | 0 | |||||
| 43, 44 | 0 | |||||
| 0 | XPSES01 |
Note: Instance.COMDATE is mandatory for all instances enforced by a business rule, 'Instance.COMDATE must exist'. This is not, however, enforced in the schema as minimum occurrences 1. If a null Instance.COMDATE exists through the switching off of this rule this function will fail.
Revision history
Contact Liaison by email or on +44 (0)1242 388 531.