Student 2017/18 - REF dataREFData
Student 2017/18Fields required from institutions in All fieldsREF data | return to field list |
| Type | entity |
| Short name | REFData |
| Description |
A set of fields that describe the REF unit of assessment(s) relating to an Instance |
| Applicable to | England Northern Ireland Scotland Wales |
| Coverage | All instances where Course.COURSEAIM = L00, L80, L99, or D00, and Instance.REDUCEDI = 00, 01 or 04. |
| Notes |
Collaborative doctoral provisionIf there is a formal collaborative arrangement to provide doctoral research training for a student, then this should be reflected in the REF Data fields. Where there is concurrent collaboration or joint supervision the REFData.UOAPCNT, REFData.UOA2014, and REFData.COLPROV fields should be used to record appropriate details. Where there is a sequential collaboration (i.e. the student starts at one provider and reporting responsibilities are later transferred to another provider) the first provider should return code 12 'Transferred out due to collaborative supervision arrangements' in Instance.RSNEND, and complete Instance.COLTOPROV and Instance.COLTODATE; and the second provider should return Instance.NUMHUSPREV, Instance.COLFROMPROV and Instance.COLFROMDATE. For more details on collaborative provision, see the Further guidance on collaborative supervision arrangements. |
| Quality rules |
Quality rules relating to this entity are displayed here.
|
| Part of | |
| Minimum occurrences | 0 |
| Maximum occurrences | unbounded |
| Schema components |
Element: REFData |
| Has parts | |
| Owner | HESA |
| Version | 1.0 |
| Date modified | 2017-07-27 |
| Change management notes | The coverage has been updated to exclude Course.COURSEAIM valid entry D01 'New Route PhD that meets the criteria for a research-based higher degree'. |
Contact Liaison by email or on +44 (0)1242 388 531.