Skip to main content

Student 2016/17 - Provider's own identifier for student

Back to C16051

Student 2016/17

Fields required from institutions in England

Provider's own identifier for student

return to field list
Short nameOWNSTU

This field records the provider's own internal identifier for the student.

Applicable toEngland Northern Ireland Scotland Wales

All students (optional)


This field is designed to be used to aid in linking records. Due to the nature of this requirement, and consequent visibility of the field when manipulating data, it is not advised that protected characteristics such as student names or dates of birth should be used in the population of this field.

Valid characters

The valid characterset available for this field follows the Data Standards in the HESA student record.

  • The general policy is to support all Latin-based characters for names, addresses and general text fields, but not non-Latin characters.
  • All Unicode code charts for Latin characters are supported. These are Basic Latin (excluding the C0 control characters), Latin-1 (excluding the C1 control characters), Latin Extended A, Latin Extended B and Latin Extended Additional. This set corresponds to Unicode code points U+0020 to U+007E, U+00A0 to U+024F and U+1E00 to U+1EFF.
  • Schemas are built in such a way that an individual project can further restrict the set if required.

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
Quality rules to follow
Reason required

To facilitate HESA checking data with providers, for example, validation reports, etc.

Part of
Field length20
Minimum occurrences0
Maximum occurrences1
Schema components
Element: OWNSTU
Data type: OWNSTUType

Contact Liaison by email or on +44 (0)1242 388 531.