HESA Student Record 2008/09 - Course title
HESA Student Record 2008/09Fields required from institutions in ScotlandCourse title | return to field list |
Short name | CTITLE |
Type | field |
Description |
This field will be determined by the institution and in this context relates to the complete programme of study leading to the qualification aim referred to in fields Course.COURSEAIM and CourseSubject. |
Applicable to | England Northern Ireland Scotland Wales |
Coverage | All courses |
Base data type | TitleType |
Field length | 255 |
Part of | |
Minimum occurrences | 1 |
Maximum occurrences | 1 |
Related fields | |
Reason required |
To facilitate HESA cross-checking with institutions and to identify courses in onward analyses. |
Notes |
Although a compulsory field, this field will not be subject to specific checks regarding its validity. The only validation checks will be that the field contains at least one character. Feedback from users of the TQI site has indicated that they would want to see information at the course level. With the introduction of the course entity it is likely that the funding councils will want to explore this option further. Should users of the HESA data choose to publish course level information it is likely that the course title will form a critical part of this. Therefore institutions need to ensure that the CTITLE field contains course titles that would be meaningful to a wide range of stakeholders including potential students It is intended that this field can be used by the institution as a cross-check to fields Course.COURSEAIM and CourseSubject. The valid characterset available for this field has been defined by a specific study undertaken as a part of the MIAP Common Data Definitions (CDD) project. The conclusions of this study were:
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: XML files must be encoded with UTF-8 if they contain characters beyond the standard ASCII character set. Institutions are advised to specify the encoding used in their XML files (i.e. <?xml version="1.0" encoding="UTF-8" ?>) and to ensure that their files are actually saved with that encoding. Files with an explicit encoding declaration other than UTF-8 will be rejected. Files with undeclared encoding will be assumed to be UTF-8. If encoding is not specified or does not match the actual file encoding, institutions are warned that there is a risk that data contained in the files may be changed on submission to HESA. |
Owner | Managing Information Across Partners - Common Data Definitions |
Version | 1.1 |
Date modified | 2009-07-30 |
Change management notes | Further detail provided for file encoding |
Schema components |
Element: CTITLE
Data type: TitleType |
Contact Liaison by email or on +44 (0)1242 388 531.