Skip to main content

XPGO01_1.1.1

Back to C17051

Field description Field abbreviation Field version Field length Field type
Graduate Outcomes population XPGO01 1.1.1 1 Char

Valid entries

Code Label
0 The instance is NOT counted within the Graduate Outcomes target population
1 The instance is counted within the Graduate Outcomes target population
2 The instance is not counted within the Graduate Outcomes target population but this instance refers to a further qualifying awarded in the same census period

Dependent fields

  • XPUBPOPG01

Depend upon fields

  • INTERCALATE
  • LOCSDY
  • EXCHANGE
  • RSNEND
  • MODE
  • XOBTNG01
  • ENDDATE
  • QUAL
  • HUSID
  • XINSTID01
  • APRJAN
  • EXCHIND
  • NOTACT

Additional information

Standard definition

Students identified in the HESA Graduate Outcomes target population are those submitted to HESA within the reporting period 1 August Y1 to 31 July Y2 who have obtained relevant qualifications and whose study was full-time or part-time (including sandwich students and those writing-up theses). Awards from dormant status are not included in the target population, except for postgraduate research qualifications. Graduate Outcomes target population also includes students who were domiciled from outside the EU.

There are, however, a number of exceptions to this total-coverage population, with the following exclusions (where applicable to the record):

(1) Students obtaining the following higher education qualifications:
• Awards for Visiting students (on the grounds that most will go back to another higher education provider);
• Post-registration health and social care awards (on the assumption that these are likely to be currently-employed students);
• Professional qualifications for serving schoolteachers (on the assumption that these are likely to be currently-employed students);
• Awards of credit.

(2) All further education level qualifications.

(3) Students studying on an intercalated course.

(4) Students studying mainly overseas.

(5) Incoming exchange students.

(6) Deceased students.

(7) Qualifications awarded from dormant (suspended study) status, except Postgraduate Research qualifications.

(8) Students who have been transferred out of the provider to another as part of collaborative supervision arrangements.

This derived field is used to identify the Graduate Outcomes Survey population supplied back to higher education providers following their Student or AP student record submission.

A student instance will be assigned to code 1 (The instance is counted within the Graduate Outcomes target population) in each census period (rather than one in each reporting period). The census periods are for students gaining a relevant award/qualification between August to October and/or November to January and/or February to April and/or May to July, so that for the majority of students completing a programme in one of the survey cohorts they are surveyed fifteen months after completion. The list of QualificationsAwarded.QUAL codes was also been updated.

Code 2 (The instance is not counted within the Graduate Outcomes target population but this instance refers to a further qualifying award) has been assigned to identify those records where a student holds more than one qualifying award in the same cohort period. Only one record for a student will qualify for inclusion in the population but additional records which meet the criteria for inclusion in the target population for each census period are identified. This allows linking the Graduate Outcomes records back to all relevant student records.

Technical Specification

TECHNICAL SPECIFICATION IN THE CYY051 STUDENT RECORD

Step 1: Initial exclusions (Table 1)

First, ineligible instances are removed (i.e. LOCSDY ‘S’, incoming exchange students, students with a null, '05' or '12' RSNEND and dormant mode students (unless PGR students)). These are set as an XPGO01 value of '0'.

Table 1
Instance. INTERCALATE Instance. LOCSDY Instance. EXCHANGE Instance. RSNEND Instance. MODE First character of XOBTNG01 XPGO01
01 0
Null S 0
6, 9, C, D, E, H, J, K, T, U, Z, null 4, G 0
N, Y, Z, null 05, 12, null 0
Otherwise 63,64, 98 E, M, H, I, J, C, $, _ 0
D,L Go to Table 2
Otherwise Go to Table 2

Step 2: Identifying qualifying instances and assigning a value of XPGO01 (Table 2):

Instances with only excluded QualificationsAwarded.QUALs, and/or non-excluded QUALs that occur outside the census periods (that is, August-October 'December census', November-January 'March census', February-April 'June census' and May-July 'September census'), are set to a XPGO01 value of '0'.

(1) If there is only a single qualifying instance within a census period, this instance is assigned an XPGO01 value of ‘1’.

(2) For the Student.HUSIDs where there are multiple qualifying instances within a census period, identify the highest ranked of the qualifications associated with any of the instances. Ranking is done in accordance with the ordering in derived field XOBTNG01, with the highest value considered to be the one first in the list. Where this highest ranked qualification is present in more than one instance, then assign the record with the lowest INSTANCEKEY to XPGO01 = ‘1’, and assign the remaining XPGO01 values for that census period to ‘2’.

(3) Where the highest ranked qualification is only present for one of the multiple instances within a census period, select that instance and assign XPGO01 = ‘1’. Assign remaining instances for that HUSID and census period to XPGO01 = ‘2’.

The listing in Table 2 below starts with the highest qualification appearing first and ends with the lowest (this listing is a subset of values in QualificationsAwarded.QUAL, with codes M22, M26 and M28 appearing immediately before H codes).

Y1 is obtained by concatenating the first two digits from year in the system date with the first two digits of RECID, e.g. 01 for 2001/02.

Table 2
XOBTNG01 (ordered by highest qualification first) Instance. ENDDATE Number of matching instances Associated QUAL(s) position in hierarchy INSTANCE XPGO01
D00, D01, E00, E43, L00, M00, M01, M02, M10, M11, M16, M50, M71, E40, L80, M40, M41, M42, M43, M44, M45, M70, M73, M78, M79, M80, M86, M88, M22, M26, M28, H00, H11, H12, H16, H18, H22, H23, H50, I00, I11, I12, I16, H41, H42, H43, H60, H61, H62, H70, H71, H78, H79, H80, H81, H88, I60, I61, I70, I71, I73, I74, I78, I79, I80, I81, J10, J16, J20, J26, J30, J41, J42, J43, J45, J80, C20, C30, C41, C42, C43, C77, C78, C80 > 01-AUG-Y1 and <= 31-OCT-Y1 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-NOV-Y1 and <= 31-JAN-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-FEB-Y2 and <= 30-APR-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-MAY-Y2 and <= 31-JUL-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
< 31-JUL-Y1 or > 31-JUL-Y2 or blank 0
D90, E90, L90, L91, M72, M76, M90, M91, H24, H72, H76, H90, H91, I72, I76, I90, I91, J76, J90, C90, $$$, ___ 0

TECHNICAL SPECIFICATION IN THE CYY054 AP STUDENT RECORD

Step 1: Initial exclusions (Table 1)

First, ineligible instances are removed (i.e. LOCSDY ‘S’, incoming exchange students, students with a null or ‘05’ RSNEND and suspended study ('dormant') students). These are set as an XPGO01 value of '0'. (Note that the AP student record makes use of fields from a rolled-up Instance_End analysis table which reflects the position of the student in the last active instance period.)

Table 1
Instance_End. LOCSDY Instance_End. EXCHIND Instance. RSNEND Instance. XINACT01 XPGO01
S 0
6, 9, D, E, T, U, Z 1 0
2, 3 05 or null 0
Otherwise 1 0
0 Go to Table 2

Step 2: Identifying qualifying instances and assigning a value of XPGO01 (Table 2):

In the AP student record an instance may have many associated instance periods, each with up to two qualifications awarded. An instance may therefore have a large number of associated qualifications. Each instance has derived field XOBTNG01 calculated to indicate the single highest-ranking qualification within all associated QualificationsAwarded.QUALs for that instance.

Instances with only excluded QualificationsAwarded.QUALs, and/or non-excluded QUALs that occur outside the census periods (that is, August-October 'December census', November-January 'March census', February-April 'June census' and May-July 'September census'), are set to a XPGO01 value of '0'.

(1) If there is only a single qualifying instance within a census period, this instance is assigned an XPGO01 value of ‘1’.

(2) For the Student.HUSIDs where there are multiple qualifying instances within a census period, identify the highest ranked of the qualifications associated with any of the instances. Ranking is done in accordance with the ordering in derived field XOBTNG01, with the highest value considered to be the one first in the list. Where this highest ranked qualification is present in more than one instance, then assign the record with the lowest INSTANCEKEY to XPGO01 = ‘1’, and assign the remaining XPGO01 values for that census period to ‘2’.

(3) Where the highest ranked qualification is only present for one of the multiple instances within a census period, select that instance and assign XPGO01 = ‘1’. Assign remaining instances for that HUSID and census period to XPGO01 = ‘2’.

The listing in Table 2 below starts with the highest qualification appearing first and ends with the lowest (this listing is a subset of values in QualificationsAwarded.QUAL, with codes M22, M26 and M28 appearing immediately before H codes).

Y1 is obtained by concatenating the first two digits from year in the system date with the first two digits of RECID, e.g. 01 for 2001/02.

Table 2
XOBTNG01 (ordered by highest qualification first) Instance. ENDDATE Number of matching instances Associated QUAL(s) position in hierarchy INSTANCE XPGO01
M00, M01, M02, M10, M11, M16, M22, M26, M28, M41, M42, M44, M71, M73 H00, H11, H16, H18, H22, H23, H41, H42, H43, H50, H60, H61, H62, H70, H71, H78, H79, H80, H81, H88, I00, I11, I16, I60, I61, I70, I71, I74, I78 I79, I80, I81, J10, J16, J20, J26, J30, J41, J42, J43, J45, J80, C20, C30, C41, C42, C43, C77, C78, C80 > 01-AUG-Y1 and <= 31-OCT-Y1 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-NOV-Y1 and <= 31-JAN-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-FEB-Y2 and <= 30-APR-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
>= 01-MAY-Y2 and <= 31-JUL-Y2 More than 1 One or more equally high Lowest INSTANCEKEY value 1
Other instances 2
Otherwise Instance with highest ranked qualification 1
Other instances 2
1 1
< 01-AUG-Y1 or > 31-JUL-Y2 or blank 0
H72, H76, H90, H91, I72, I76, I90, I91, J76, J90, C90, $$$, ___ 0

TECHNICAL SPECIFICATION IN GRADUATE OUTCOMES RECORD

The value of XPGO01 in the Graduate Outcomes record is based on the value in the linked record(s) in the Student or AP student record, where one can be made. However, it contains additional values to account for Graduate Outcomes records submitted which either have no direct link to the Student or AP student record, or have a link to the Student or AP student record but there is incompatible information on survey dates. A provider will submit data in one of either the Student or AP student records, not both. Consequently, there is no need to account for matching data in the Graduate Outcomes record to both the Student and AP student records.

B: Dealing with multiple Graduate Outcomes survey reponses which link to the same Student or AP student record instance
Where more than one record exists in the Graduate Outcomes record for a HUSID + INSTID, and this can be linked to only one INSTANCEKEY in the Student or AP student record, set the XPGO01 value in the earliest submitted Graduate Outcomes record to that of the Student or AP student record XPGO01 value as applicable, and populate Graduate Outcomes INSTANCEKEY with the associated Student or AP student record INSTANCEKEY value. Set the XPGO01 value for the Graduate Outcomes record submitted second to ‘3’ and pad Graduate Outcomes INSTANCEKEY with underscores to the length of the field, to indicate that no link is possible.

THIS SECTION NEEDS TO BE DELETED AS THIS REFERS TO WHEN A PROVIDER SUBMIT MORE THAN ONE RECORD BUT ONLY ONE CAN BE LINK TO AN INSTANCEKEY.

C: Dealing with multiple Graduate Outcomes survey reponses which link to multiple Student or AP student record instances
THIS COULD BE SOLVE BY HAVING A UNIQUE KEY FOR EACH SURVEY? Where more than one record exists in the Graduate Outcomes record for a HUSID + INSTID, and there is more than one instance for that HUSID + UKPRN, it is necessary to further associate the Graduate Outcomes survey reponse with the correct instance using the survey period. Associating records is done by comparing the Student or AP student ENDDATE value with the Graduate Outcomes CENSUS value for records already matched on HUSID + INSTID (the 'candidate' instances). A CENSUS value of 'Dec' requires an ENDDATE between August 1st yr1 and October 31st yr1 (inclusive), a CENSUS value of 'Mar' requires an ENDDATE between November 1st yr1 and January 31st yr2 (inclusive), a CENSUS value of 'Jun' requires an ENDDATE between February 1st yr2 and April 30th yr2 (inclusive), a CENSUS value of 'Sep' requires an ENDDATE between May 1st yr2 and July 31st yr2 (inclusive).

Where a Graduate Outcomes survey reponse has a CENSUS value compatible with the ENDDATE of a single candidate Student/AP student instance, set the Graduate Outcomes XPGO02 and INSTANCEKEY values to that of the single instance.

Where the Graduate Outcomes survey response can be associated with more than one candidate Student/AP student instance which is within the survey dates, it is necessary to then further associate the Graduate Outcomes survey reponse with the target population status of the candidate instances.

Where a Graduate Outcomes survey reponse has a CENSUS value compatible with the ENDDATE of more than one candidate Student/AP student instance within the target population, set the Graduate Outcomes XPGO02 and INSTANCEKEY value to that of the candidate instance with the lowest INSTANCEKEY.

D: Dealing with single Graduate Outcomes survey reponses that link to a single Student or AP student record instance
Where a record exists in the Graduate Outcomes record for a HUSID + INSTID, and this can be linked to one INSTANCEKEY in the Student or AP student record, set Graduate Outcomes XPGO02 to the value held by the Student or AP student record instance as applicable and populate Graduate Outcomes INSTANCEKEY with that associated student or AP student record INSTANCEKEY value.

E: Dealing with single Graduate Outcomes survey reponses with links to multiple Student or AP student record instances
Where a record exists in the Graduate Outcomes record for a HUSID + INSTID, and this can be linked to multiple instances in the Student or AP student record, it is necessary to associate the Graduate Outcomes survey reponse with the target population of the records already matched on HUSID + INSTID (the 'candidate' instances).

Where only one candidate student instance is within the target population (Student or AP student XPGO02 of '1'), set the Graduate Outcomes XPGO02 and INSTANCEKEY values to that of the single instance.

Where the Graduate Outcomes survey response can be associated with more than one candidate Student/AP studentudent instance which is within the target population, it is necessary to then further associate the Graduate Outcomes survey reponse with the correct instance using the survey period. Associating records is done by comparing the Student or AP student ENDDATE value with the Graduate Outcomes CENSUS value for the candidate instances. A CENSUS value of 'Dec' requires an ENDDATE between August 1st yr1 and October 31st yr1 (inclusive), a CENSUS value of 'Mar' requires an ENDDATE between November 1st yr1 and January 31st yr2 (inclusive), a CENSUS value of 'Jun' requires an ENDDATE between February 1st yr2 and April 30th yr2 (inclusive), a CENSUS value of 'Sep' requires an ENDDATE between May 1st yr2 and July 31st yr2 (inclusive).

Where a Graduate Outcomes survey reponse has a CENSUS value compatible with the ENDDATE of more than one candidate Student/AP student instance within the target population, set the Graduate outcomes XPGO02 and INSTANCEKEY values to that of the candidate instance within the target population with the lowest INSTANCEKEY.

Where a Graduate Outcomes survey reponse does not have a CENSUS value compatible with the ENDDATE of any candidate Student/AP student instance within the target population, set the Graduate Outcomes XPGO02 and INSTANCEKEY values to that of the candidate instance outside of the target population with the lowest INSTANCEKEY.

This approach ensures that where a one-to-one relationship between Graduate Outcomes response and Student or AP student instance does not exist, linking is done in an order designed to prioiritise the likely qualification against which the response was sought.

HUSID+INSTID match in Student/AP student record Number of Graduate Outcomes records for HUSID+INSTID Number of matching instances in Student/AP student records Graduate Outcomes XPGO02
C HUSID+INSTID found in Student/AP student >1 >1 Set the XPGO02 value of each Graduate Outcomes record to that held in a linked Student/AP student instance XPGO02 as per text
D 1 1 Set the XPGO02 value of the Graduate Outcomes record to that held in linked Student/AP student instance XPGO02
E >1 Set the XPGO02 value of the Graduate Outcomes record to that held in a linked Student/AP student instance XPGO02 as per text

Revision history

Date Version Notes
2018-04-05 1.1.1 Field Created.

Contact Liaison by email or on 01242 211144.