The HECoS archive comprises background information regarding the development of the HECoS framework.
HECoS was the main output of the Higher Education Data and Information Improvement Programme (HEDIIP) New Subject Coding System Project (NSCS) which ran between 2014 and 2015.
HECoS Archive Contents
The objectives of the NCSC project were:
- To define the HE sector requirements for a new subject coding system to replace JACS.
- To develop a standard coding structure that meets the HE sector requirements.
- To prepare an adoption plan and gain the agreement of the project's key stakeholders.
- With reference to Project 2.3 (Data language), define a governance model for the on-going maintenance and development of the New Subject Coding System.
- To develop and execute a communication plan that: raises awareness of the new system and its benefits; enables appropriate stakeholders to participate in the project; and enables stakeholders to prepare their organisations for implementation.
- To recommend a standard approach to subject based analysis using the new subject coding system.
The desired project outcome was for a coding system that meets the design principles described below:
- a coding framework that corresponds to recognised good practice;
- a framework with scope for evolution;
- a framework at an appropriate level of granularity (in relation to usability and meaningful data);
- an easy transition path;
- increased consistency of application across institutions;
- a means of furthering the open data agenda;
- a unified approach to supporting a much wider group of stakeholders;
- a means of linking to data classified in other frameworks;
- backwards compatibility with legacy data.
Work began on the development of a new subject coding system in 2013 led by the former Higher Education Data and Information Improvement Programme (HEDIIP) and in consultation with the HE sector. The project was borne out of a need to replace the JACS system to meet the needs of a broader group of stakeholders and to reflect the diverse and dynamic nature of Higher Education in the twenty-first century, and culminated in July 2016 with the publication of the subject code system now known as HECoS.
The HECoS and CAH management guide (published as a .pdf download) explains the process for managing the HECoS standard. In particular it:
- Delineates the parameters within which the HECoS standard can be adapted over time.
- Provides guidance to users who seek to update or improve HECoS.
Version 1.3 of the Common Aggregation Hierachy (CAH)
CAH groupings CSV File (VERSION 1.3)
CAH groupings (No Labels) CSV File (VERSION 1.3)
HECoS to CAH mapping CSV File (VERSION 1.3)
HECoS to CAH mapping (No Labels) CSV File (VERSION 1.3)
Version 1.2 of the Common Aggregation Hierachy (CAH)
CAH groupings CSV File (VERSION 1.2)
CAH groupings (No Labels) CSV File (VERSION 1.2)
HECoS to CAH mapping CSV File (VERSION 1.2)
Mapping document archive
An extensive archive of the HEDIIP programme is maintained at HESA. Selected NSCS project documents are reproduced here in unredacted form (including some notes that were absent from the versions previously available on the former HEDIIP website). Taken together, these documents offer an overview of the way the project objectives were defined, how the project was conducted, the considerations that were taken into account, and the outcomes and outputs of the work.
HESA supports the Foreign, Commonwealth and Development Office (FCDO) in their adoption of HECoS and CAH for the Academic Technology Approval Scheme (ATAS). This was implemented from 2019/20, to align with UCAS and HESA processes. HESA convened a meeting with the Foreign and Commonwealth Office (FCO, the FCDO's predecessor organisation) and volunteer HE providers to help determine an appropriate approach. Minutes from that meeting are available in the PDF below:
This document was last updated on 15 April 2019.
For JACS 3.0 (valid from 2012/13 datasets onwards) we have produced a single mapping document to cover subject area/principal and 4 digit splits. We have included all currently available subject mappings and will update this document as other mappings are confirmed.
Upon opening this document the JACS subject shown and cross tabulated where possible in columns A-C of the first tab. The remaining columns relate to each individual league table, data enquiries or subject groupings.
In each of columns D onwards, the subject code relating to that particular classification is listed. Where no subject group information has been provided for a JACS subject then ‘no allocation’ has been stated in blue text. There are also a series of tabs within the document, one relating to each column. Within those tabs are a list of all the subject group codes and labels for each.
Please note, subject mappings may change year on year so we will endeavour to keep this document up to date with any alterations in mappings.
These documents were last updated as of 8th March 2013.
Subject Area to Principal Subject:
Principal Subject to 4 Digit JACS:
The subject classification used is JACS version 2.0 (applicable from 2007/08 onwards). Due to the size of subject classifications, we have produced two documents – the first maps subject area with principal subject, whilst the second maps principal subject with 4 Digit JACS.
Upon opening each of these documents the JACS subject shown and cross tabulated where possible in columns A and B of the first tab. The remaining columns relate to each individual league table, data enquiries or subject groupings.
In each of columns C onwards, the subject code relating to that particular classification is listed. Where no subject group information has been provided for a JACS subject then ‘no allocation’ has been stated in blue text. There are also a series of tabs within the document, one relating to each column. Within those tabs are a list of all the subject group codes and labels for each.
In some instances, one 4 Digit JACS code may be in one subject group but the other codes may be within another subject group, this is therefore not easily identifiable when only subject area and principal subject are shown. To make it clear where this has occurred (using B1 for the Times subject grouping as an example), we have included the text: ‘EXCLUDE B16. B16 is in group 49’. This method of flagging issues has been used throughout the remainder of the document where such an issue has occurred.
The Guardian subject mapping shown is their default mapping. HEPs may, however, alter this mapping to correspond to their own subject mix and therefore in some cases, this mapping will differ from that used for the Guardian University guide league table. The majority of the codes are not altered so will follow the standard Guardian subject mapping.