Skip to main content

Glossary

Welcome to the Data Futures Glossary. Please use this alongside the Coding manual (Data Futures) to clarify unfamiliar terms. 

A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z

All

To find out more about some of the key concepts and processes defined below please click through to the following sections:

Key concepts   Data Futures resources   Frequently asked questions

All definitions

Approval: The action of a defined role (for example a student returns officer) approving an in-Reference period data delivery to a HESA data customer, on behalf of the HE provider e.g. ITT return to NCTL.

Approved: A state of data that has undergone approval and is still open to amendment during the Reference period.

Business event: An event at an HE provider that might trigger a requirement for data to be submitted to HESA.

Coding frame: Table of values and labels that specifies the valid entries for a particular field.

Coding manual: The suite of material that supports HE providers and stakeholders in their submission and understanding of HESA data collections.

Data dictionary: A specification of fields, entities, and quality rules.

Derived entity: An entity created by HESA to aid either collection or analytical activities.

Derived field: A field created by HESA to aid either collection or analytical activities.

Dissemination point: The specified date, following the end of a Reference period, by which signed-off data will be extracted and supplied to HESA's data customers. Data disseminated at the Dissemination point will be used for official accounts of the higher education provider’s activity for statistical, regulatory, and public information purposes.

DLSG: Data Landscape Steering Group. The data landscape governance body charged with maintaining the HE sector’s data language and supporting logical model, and with promoting good practice for data collections.

Enrolment: The act of a student committing to undertake a course session at a provider.

Exception processing: A mechanism for handling historical amendments to provider data.

Historical amendment: Data submitted after the in-scope period has passed.

In-scope period: The duration for which each entity is relevant for sign-off by an HE provider. Data submitted prior to the in-scope period will not require sign-off until it becomes in-scope. Submission after this period will be subject to exception processing.

Logical model: A data model which displays the logical structure of how various elements of HE data are associated and interact in the real world.

Processing fields: A type of derived field to allow the collection process to occur. It does not appear in dissemination output.

Provider data: Data relating to a specific provider.

QA peer: An individual or organisation involved in the QA process.

Record: The set of data that accumulates over time as each Reference period is signed-off.

Reference period: A fixed period of time, the end of which, aligns to when HESA’s statutory and public purpose customers require sector-wide data and information.

Reference period data: Data relating to a specific Reference period.

Registration: A student registration is a binding agreement between a student and an organisation for the delivery of educational services, within the meaning of "Stage 3: enrolment stage" in the Competition and Markets Authority's advice for HE providers on consumer protection law.

Sector data: The data from more than one provider.

Signed off: A state of data that has undergone sign-off and may therefore be used in public purpose/statutory and analytical output.

Sign-off: The process of a defined role (for example Vice Chancellor) making a formal declaration that the in-scope data submitted to HESA represents an honest, impartial, and rigorous account of the HE provider’s events up to the end of the Reference period.

Submission: Process of supplying data to HESA.

Submitted: A state of data that has undergone submission but has not been signed-off.

Tolerance: Represents the permissible quality threshold for a rule.

Back to top

A: Approval, Approved...

Approval: The action of a defined role (for example a student returns officer) approving an in-Reference period data delivery to a HESA data customer, on behalf of the HE provider e.g. ITT return to NCTL.

Approved: A state of data that has undergone approval and is still open to amendment during the Reference period.

Back to top

B: Business event...

Business event: An event at an HE provider that might trigger a requirement for data to be submitted to HESA.

Back to top

C: Coding frame, Coding manual...

Coding frame: Table of values and labels that specifies the valid entries for a particular field.

Coding manual: The suite of material that supports HE providers and stakeholders in their submission and understanding of HESA data collections.

Back to top

D: Data dictionary, Derived entry...

Data dictionary: A specification of fields, entities, and quality rules.

Derived entity: An entity created by HESA to aid either collection or analytical activities. 

Derived field: A field created by HESA to aid either collection or analytical activities.

Dissemination point: The specified date, following the end of a Reference period, by which signed-off data will be extracted and supplied to HESA's data customers. Data disseminated at the Dissemination point will be used for official accounts of the higher education provider’s activity for statistical, regulatory, and public information purposes.

DLSG: Data Landscape Steering Group. The data landscape governance body charged with maintaining the HE sector’s data language and supporting logical model, and with promoting good practice for data collections.

Back to top

E: Enrolment, Exception processing...

Enrolment: The act of a student committing to undertake a course session at a provider.

Exception processing: A mechanism for handling historical amendments to provider data.

Back to top

F: Fragment...

Fragment: A file of data submitted to HESA by an HE provider.

Back to top

H: Historical amendment...

Historical amendment: Data submitted after the in-scope period has passed.

Back to top

I: In-scope period...

In-scope period: The duration for which each entity is relevant for sign-off by an HE provider. Data submitted prior to the in-scope period will not require sign-off until it becomes in scope. Submission after this period will be subject to exception processing.

Back to top

L: Logical model...

Logical model: A data model which displays the logical structure of how various elements of HE data are associated and interact in the real world.

Back to top

P: Processing fields, Provider data...

Processing fields: A type of derived field to allow the collection process to occur. It does not appear in dissemination output.

Provider data: Data relating to a specific provider.

Back to top

Q: QA peer...

QA peer: An individual or organisation involved in the QA process.

Back to top

R: Record, Reference period...

Record: The set of data that accumulates over time as each Reference period is signed-off.

Reference period: A fixed period of time, the end of which, aligns to when HESA’s statutory and public purpose customers require sector-wide data and information.

Reference period data: Data relating to a specific Reference period.

Registration: A student registration is a binding agreement between a student and an organisation for the delivery of educational services, within the meaning of "Stage 3: enrolment stage" in the Competition and Markets Authority's advice for HE providers on consumer protection law.

Back to top

S: Sector data, Signed off...

Sector data: The data from more than one provider.

Signed off: A state of data that has undergone sign-off and may therefore be used in public purpose/statutory and analytical output.

Sign-off: The process of a defined role (for example Vice Chancellor) making a formal declaration that the in scope data submitted to HESA represents an honest, impartial, and rigorous account of the HE provider’s events up to the end of the Reference period. 

Submission: Process of supplying data to HESA.

Submitted: A state of data that has undergone submission but has not been signed-off.

Back to top

T: Tolerance...

Tolerance: Represents the permissible quality threshold for a rule.

Back to top