Skip to main content

HESA Student Record 2008/09 - Module identifier

Back to C08051

HESA Student Record 2008/09

All fields

Module identifier

return to field list
Short nameMODID

This field is the primary key for the Module entity and exists as a foreign key on StudentOnModule.

Applicable toEngland Northern Ireland Scotland Wales

All student on module records

Base data typeMODIDType
Field length30
Part of
Minimum occurrences1
Maximum occurrences1
Reason required

To facilitate linkage with the Instance entity.


Any MODID returned on the StudentOnModule element must exist on the Module entity. Modules that have not been taken up in the reporting year can be included on the Module entity if this is easier.

Valid characters

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 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+007F and U+00A0 to U+024F.
  • 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:

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.

Date modified2009-07-30
Change management notesFurther detail provided for file encoding
Business rules

StudentOnModule.MODID must exist on Module.MODID


More than 2 occurrences of identical StudentOnModule.MODID for a single instance

Schema components
Element: MODID
Data type: MODIDType

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