XPSR01_2.5.1
Field description | Field abbreviation | Field version | Field length | Field type |
---|---|---|---|---|
Standard registration population | XPSR01 | 2.5.1 | 1 | Char |
Valid entries
Dependent fields
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 AP student 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, and
7. the 'wrapper' programme aim of Apprenticeship Standards students.
This derived field is created in both the Student record (Cyy051) and the AP student record (Cyy054). The AP student record makes use of the PERIODENDDATE field from a rolled-up Instance_End analysis table, which reflects the position of the student in the last active instance period.
The Anniversary date identifies the anniversary of the commencement date of the study programme within the current reporting period. For example, if Instance.COMDATE is 10 September 2009, Anniversary dates would be 10 September 2010 in 2010/11 dataset, 10 September 2011 in the 2011/12 dataset, etc. and Anniversary Instance.COMDATE + 14 days would be 24 September 2010 in 2010/11, 24 September 2011 in 2011/12, etc.
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 = 11 for 2011/12.
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 2009, for comparison purposes Anniversary Instance.COMDATE in reporting period 2010/11 would be 1 March 2011 (Y1+1) and Anniversary Instance.COMDATE + 14 would be 15 March 2011;
• if Instance.COMDATE is 1 October 2009, for comparison purposes Anniversary Instance.COMDATE in reporting period 2010/11 would be 1 October 2010 (Y1) and Anniversary Instance.COMDATE + 14 would be 15 October 2010.
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, 99 | 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, 64 and 98 in the Student record can only derive to an XPSES01 output of zero and hence an XPSR01 output of zero.
In the Cyy054 AP student record:
XPSES01 | Instance. MODE | Instance. ENDDATE | Instance_End. PERIODENDDATE | 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.