HESA Student Record 2008/09 - Forenames
HESA Student Record 2008/09Fields required from institutions in ScotlandForenames | return to field list |
Short name | FNAMES | ||||||||||||
Type | field | ||||||||||||
Description |
This field records the forenames of the student. | ||||||||||||
Applicable to | England Northern Ireland Scotland Wales | ||||||||||||
Coverage | All students where any Instance.REDUCEDI = 00, 01 or 04 | ||||||||||||
Base data type | NameWithNullStructure | ||||||||||||
Field length | 35 | ||||||||||||
Part of | |||||||||||||
Minimum occurrences | 0 | ||||||||||||
Maximum occurrences | 1 | ||||||||||||
Reason required |
To facilitate HESA checking data with institutions and for Statutory Customers to link student records collected by HESA for statistical purposes. | ||||||||||||
Notes |
In cases where the student does not split their name between family and forenames, the whole name should be entered in Student.SURNAME and an empty element should be returned with the ReasonForNull attribute set to 9 (not applicable), i.e: <FNAMES ReasonForNull="9"></FNAMES> For students entering through UCAS this information will be available from UCAS via the *J transaction. The field length has been set to 35 characters to align this field with MIAP definitions. Valid characters The question of valid characters is significant in this field since many names include characters with accents and other diacritics that are not supported by the standard ASCII characterset. 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.2 | ||||||||||||
Date modified | 2009-07-30 | ||||||||||||
Change management notes | Further detail provided for file encoding | ||||||||||||
Business rules |
| ||||||||||||
Schema components |
Element: FNAMES
Data type: NameWithNullStructure |
Contact Liaison by email or on +44 (0)1242 388 531.