HESA Student Record 2013/14 - Term-time postcode
HESA Student Record 2013/14
return to field list
This field records a postcode for the student's term-time address at some point during the reporting year.
|Applicable to||England Northern Ireland Scotland Wales|
This field is required for all students except those studying by distance learning and those on placements.
This can be a postcode from any point during term-time, but should not be a correspondence or summer contact address. It is expected that in many cases the postcode will change between years. Where students spend all or part of the year in a hall of residence the institution will be able to insert a generic postcode for that that hall into all of the relevant records.
Although completion of the field will be compulsory for all students, 'Unknown' values will be acceptable. If no valid postcode (full or outward only) can be ascertained an empty element should be returned with the ReasonForNull attribute set to 1 (not known), i.e:
It will be possible to provide only the outward part of the postcode if this is all that is known, although that is not expected to arise commonly.
Postcodes returned must pass schema validation of format. Individual postcodes will be validated against the Royal Mail list but only a warning rather than an error will be generated if validation fails. This is intended to assist institutions that attach importance to the accuracy of their contact information but who may not be in a position to validate postcodes themselves.
British Forces Post Office (BFPO) postcodes
Where BFPO codes relate to UK locations, institutions will need to locate the Royal Mail equivalent postcode for the base. If this is not known, then an empty element must be returned with the ReasonForNull attribute set to 1 (not known), i.e:
There is further guidance on valid postcode formats at: http://webarchive.nationalarchives.gov.uk/+/http://www.cabinetoffice.gov.uk/govtalk/schemasstandards/e-gif/datastandards.aspx. The business rule structure validation will be slightly less strict than that described in UK Government Data Standards Catalogue, as not all parsers will support the full GDSC definition. All postcodes are validated against valid postcodes at exception.
A typical postcode such as GL50 3DA would be coded with a blank in the fifth character position. A postcode such as B1 6SR would have a blank in position 3. The part of the postcode before the space is known as the outward part of the postcode and can be 2, 3 or 4 characters long. The part of the postcode after the space is known as the inward part of the postcode and is a fixed length of 3 characters. The space between the outward and inward parts of the postcode must always be shown as part of the postcode.
There is further guidance on valid postcode formats at: http://webarchive.nationalarchives.gov.uk/+/http://www.cabinetoffice.gov.uk/govtalk/schemasstandards/e-gif/datastandards.aspx. The business rule structure validation is slightly less strict than that described in UK Government Data Standards Catalogue, as not all parsers will support the full GDSC definition. All postcodes are validated against valid postcodes at exception, using the Office for National Statistics Postcode Directory (ONSPD).
Quality rules relating to this field are displayed here.
To allow estimates to be made of local student populations for use in developing national statistics, monitoring migration and travel to study patterns.
Data type: PostCodeWithNullStructure
|Change management notes||Business rule 1 updated in line with the published change in coverage following the removal of Instance.LOCSDY code F from the coding frame and the addition of code T. Business rule 2 updated to include new Course.COURSEAIM M28 in the validation of term-time postcode in relation to postcode on entry.|
Contact Liaison by email or on +44 (0)1242 388 531.