Student record 2007/08
Back to C07051
Contact Institutional Liaison: liaison@hesa.ac.uk, tel 01242 211144
All FieldsForenames | 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: 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. 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. | |||||||||
| Owner | Managing Information Across Partners - Common Data Definitions | |||||||||
| Version | 1.2 | |||||||||
| Date modified | 2008-06-30 | |||||||||
| Change management notes | Note added to highlight the need to specify file encoding | |||||||||
| Business rules |
| |||||||||
| Schema components |
Element: FNAMES
Data type: NameWithNullStructure |
