Student record 2015/16 - Course identifier
Student record 2015/16
Fields common to all countries
return to field list
|Applicable to||England Northern Ireland Scotland Wales|
Course identifiers will be allocated by the provider and should be unique for each course.
The term 'course' in this context relates to the combination of subject and qualification that defines what a student is aiming for and which are described in fields Course.COURSEAIM and CourseSubject.SBJCA.
The Course identifier links the course entity and the instance entity for the reporting period . There must be an entry in the course entity with a matching identifier in the instance entity to provide this link, and so give details about the student's study in the current year. Where a student changes course within an instance by changing either course aim (at the same level) or subject, the Course.COURSEID should be updated to reflect the course that is applicable at the end of the reporting period.
Where the student continues on the same course, the same COURSEID should be kept for all years of the course. It is intended that in the future for some onward uses data from the student record should be aggregated to allow publication at a Course level. For the Unistats (TQI) site, for example, information about entrants, continuation, outcomes and destinations will be published together. If the COURSEID is not consistent throughout the course it will not be possible to compile a complete set of statistics as relating to a single course. Course.CTITLE will not allow for this aggregation: it is a text field and not suitable for the necessary validation. HESA uses a validation warning when there is a UKPRN-HUSID-NUMHUS (UHN) link but COURSEID changes.
Year-on-year linking will continue by the UHN mechanism.
The valid characterset available for this field follows the Data Standards in the HESA student record.
The character set chosen will support Welsh and Gaelic languages as well as all European and most other languages using a Latin-based character set.
The Unicode charts that list each of the characters in this range can be found on the Unicode web site. The specific sets that are defined here are shown in the following PDF documents:
Files must be encoded with UTF-8 and schema validation will be in place to ensure this. Providers must specify the encoding used in their XML files in the first line of the file (i.e. <?xml version="1.0" encoding="UTF-8" ?>) and to ensure that their files are actually saved with that encoding. If XML files are edited with some text editors and the encoding is not specified or does not match the actual file encoding, there may be problems when submitting these files for validation.
Quality rules relating to this field are displayed here.
To facilitate linkage with the Instance entity.
Data type: COURSEIDType
Contact Liaison by email or on 01242 211144.