Mobility scheme(MOBSCHEME)
Navigation: Index / Data Dictionary / OffVenueActivity / MOBSCHEME
Key | Value | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Mobility scheme | ||||||||||||||
Short Name | MOBSCHEME | ||||||||||||||
Parent Entity | |||||||||||||||
Type | Field | ||||||||||||||
Applicable To | England Northern Ireland Scotland Wales | ||||||||||||||
Coverage | All OffVenueActivity entities | ||||||||||||||
Description | This field records the scheme associated with the OffVenueActivity. | ||||||||||||||
Notes | Code 01 'Provider' includes anything organised as part of the provider's course (i.e. placements, field work etc.) Code 02 should be used for sandwich placements. This should exclude any placement that is part of an ERASMUS+ scheme or Turing Scheme, which should be coded 03. The definition of sandwich in this instance should be consistent with regulating and funding council definitions. Code 03 includes Erasmus Mundus, Comenius, Tempus and Erasmus for All. Code 04 should be used where the scheme is not captured by the other codes. Code 05 should be used where students on the Turing Scheme are in receipt of Turing Scheme funding. Students on the scheme not in receipt of Turing Scheme funding should be coded 01 or 04 as appropriate. Code 06 can only be used by providers in Wales. More information on Taith can be found here | ||||||||||||||
Reason Required | To monitor trends in mobility experiences and for use in further studies into the longer-term impact of participation in mobility schemes, for example employability. | ||||||||||||||
Field Length | 2 | ||||||||||||||
Quality Rules | Quality Rules to follow | ||||||||||||||
Minimum Occurrence | 1 | ||||||||||||||
Maximum Occurrence | 1 | ||||||||||||||
Primary Key? | False | ||||||||||||||
Valid Values |
| ||||||||||||||
Revision History | https://www.hesa.ac.uk/support/coding-manual-tools/revision-histories?Collection=22056 |