The draft recommendations for an approach to managing consistency and accuracy of HECoS are as follows.
Please comment on matters such as priority, relevance, clarity, and sufficiency. Please also comment on a desirable frequency of change, lead times, etc.
The NSCS Project recommends establishing a system that allows users to code their courses to an existing HECoS term, but also enables them to add a new proposed or candidate term.
In order to facilitate this change management process, the NSCS Project recommends setting up a candidate terms registry to gather new terms for inclusion in HECoS.
In order to strike a balance between flexibility and stability, it is recommended that the HECoS governing body should undertake an annual review of the coding scheme. The annual review should be undertaken by the Secretariat and should consider changes to definitions, scope notes and navigation structures, the impact of adopting new candidate terms and deprecating obsolete terms, and the overall level of change to the coding scheme. Any substantive changes to the coding scheme should have a one year lead time. Administrative changes to scope notes and navigation structures should be undertaken by the Secretariat. Substantive changes to definitions, and proposals for the adoption of candidate terms and the deprecation of obsolete terms, should be presented to the Board of Governors who must approve the changes and ensure that they are undertaken within an acceptable implementation timetable.
In order to balance a need to be agile in incorporating emerging new subjects with the need to provide stability, HECoS will use a new term request process. The essence of the process is that new terms can be recorded on a dedicated system quickly, and if they’re proven to be widely needed, they can be included in HECoS.
In detail, the new term request process works as follows:
- a coder needs to classify a new degree programme
- the coder finds that none of the current HECoS terms adequately covers the new degree programme
- on a registry website, the coder enters the title of the new degree programme, and the current HECoS term it is classified with
- the coder looks for a suitable term among those already suggested by others – if there is one, that gets saved as well.
- if there isn’t one, the coder can add a new term, and it will be saved alongside the degree programme title and the existing HECoS term that was used to classify the programme in data returns
- if there is enough evident need for a candidate term, and following a review by the HECoS governance body, it can be added to the vocabulary
From the perspective of a coder, the process looks like this:
Two questions arise.
Does the process outlined above satisfactorily meet the need for HECoS users to propose new terms?
The second question concerns the threshold which the HECoS governance process might use to signal candidacy as a new term, prior to assessment against the quality criteria indicated on our Subject Scheme page. How many independent HEps should have proposed a new term in order for that term to be evaluated for HECoS? One HEp, two HEps, three HEps, more than three?
This is one of a set of pages seeking comment on the draft Governance Model.