1. The New Subject Coding Scheme project Alan Paull (APS Ltd, working with CETIS)

2.  The New Subject Coding Scheme (NSCS) project  Motivation of the project  Methodology  Areas of conflict  Features of the Higher Education Classification of Subjects (HECoS) scheme  Next steps Overview

3.  Reasons that prompted a new approach to subject coding:  the limit of the existing coding framework has been reached;  changes and growth in JACS' range of functions mean it is no longer consistently applied;  it does not meet the needs of all of the key sector stakeholders;  incomplete and misunderstood JACS terminology and definitions have led to poor quality data in some instances. Motivation

4. Workshops Phone interviews Meetings Comment web site Core sector bodies such as UCAS √√√ Other sector bodies such as the QAA √ √ Professional, Statutory and Regulatory Bodies such as the GMC √ √ Higher Education providers (HEps) including Universities √ √ Other interested parties √ √ Methodology

5. Straw Man Prototypes

6.  44 requirements  15 design principles:  Support policy implementation  A unified approach to support a wide group of stakeholders  A means of linking to data classified in other frameworks.  The NSCS should be simple to understand  Be robust  Be stable  Backwards compatibility with legacy data  An appropriate level of granularity (in relation to usability and meaningful data)  Provide comprehensive coverage of the range of subjects of study available in HE at an appropriate level of detail for its target users  Increased consistency of application across institutions  Be clearly separate conceptually from the JACS system.  A framework with scope for evolution  Have a broadly consistent level of detail.  Address the perceived need for a discipline-based system.  Address the specific recommendations in the 'roadmap' about disciplines, levels and structure. Results

7.  Comprehensive detail for data analysts versus minimal coding effort for data providers  Agility versus stability  Supporting different purposes in a single scheme Areas of conflict

8.  What are we mainly classifying?  Subjects of study in …Programmes …Modules  Includes  UG  PGT  PGR  others Features of HECoS

9.  First cut criteria for inclusion:  Initially - is the term in JACS?  is there evidence of use of the term in HESA returns?  is the term’s definition and scope sufficiently clear and comprehensive to allow relatively easy classification?  is the term reliably distinguishable from other terms? Features of HECoS

10.  Data model:  Title  Status  Category number (classification code)  Permanent URI  Scope  Definition  History  Relationships. These define the default navigation groupings, related terms, and synonyms. Any formally controlled aggregation or specialisation hierarchies linked to the scheme will be displayed alongside HECoS, but not defined by it.  Date of creation  Date of approval Features of HECoS

11.  Dealing with different purposes Features of HECoS

12.  Consult the sector on the new scheme: http://ovod.net/tematres/ Subjectcoding.wordpress.com  Develop a governance model that is supported by an appropriate selection of stakeholders, with sufficient authority and resources to manage its evolution.  Develop an adoption plan to support the widest possible implementation of HECoS across the sector. Next steps

13.  http://www.ovod.net/tematres/vocab/ http://www.ovod.net/tematres/vocab/ HECoS – a quick look at the scheme

14.  Developing the vocabulary Features of HECoS Develop new programmeIs there a good HECoS code? Is there a good candidate HECoS code in the registry? Register program, old HECoS code and candidate HECoS code Register program, old HECoS code, new candidate HECoS code HECoS governance body accepts or rejects new candidate terms Done Yes No Yes