160 likes | 337 Views
HESA 2007/08. Michael Davies. Introduction. Phase I Data capture Phase II Production Timescales Delivery Discussion Points Some problem areas (?) Some questions. Phase I. Amendments to existing tables HESA Module Details (STCSTHMO) Additional fields
E N D
HESA 2007/08 Michael Davies
Introduction • Phase I • Data capture • Phase II • Production • Timescales • Delivery • Discussion Points • Some problem areas (?) • Some questions
Phase I • Amendments to existing tables • HESA Module Details (STCSTHMO) • Additional fields • Curriculum Static > HESA Module Details • HESA Programme Details (STCSTHPR) • Additional fields • Curriculum Static > HESA Programme Details • Student AOS Details (STMAOS) • Additional fields • Workspace > HESA AOS Details
Phase I (cont.) • Amendments to existing tables (cont.) • Student AOS Destination Details (STMAOSDN) • Additional fields • Workspace > AOS Destination • Student Biographical Details (STMBIOGR) • Additional fields • Workspace > Student Biographical • Student HESA Details (STMHESA1) • Additional fields • Workspace > HESA Student Details
Phase I (cont.) • Amendments to existing tables (cont.) • Student HESA AOS Details (STMHESA2) • Additional fields • Workspace > HESA AOS Details • Student HESA Qualifications (STMHESA3) • Additional fields • Workspace > Student Qualifications on Entry • HESA Workbench Parameters (STMNHPRM) • Additional fields • HESA Workbench > Parameters
Phase I (cont.) • Amendments to existing tables (cont.) • UCAS IDs (STMQUSTU) • Additional fields • Workspace > HESA Student Details
Phase I (cont.) • New Tables • Sessional Module Details (STCSTHMOS) • Existing submission fields from STCSTHMO • Additional fields • Curriculum Sessional > HESA Details • Student Annual Values (STMHESA1A) • Biographical fields with change potential • Workspace > Student Annual Values
Phase I (cont.) • Coded Fields • Initialise values to 2007/08 code set • Level playing field • Code mappings for new coding frames • Where new coding frames replaces an existing ones map the values from the ‘old’ coding frame to the ‘new’ coding frame on production • UCAS mappings • Map to ‘old’ coding frame where applicable
Phase I (cont.) • Research Students Data Capture • Captured in new STMHESA2 fields • Change of mode date • PhD submission date • Research council student identifier • Research council student • RAE unit of assessment 1-3 • Unit of assessment percentage 1-3 • Auto update for RDB customers
Phase I (cont.) • Student Annual Values • Student Annual Values table is updated when changes are detected in Biographical and/or Enrolment details
Phase II • Workbench • The workbench design philosophy to be retained • Tabbed approach to the presentation of data • Rules and defaults to be expanded across datasets • XML and CSV outputs
Phase II (cont.) • Entry Profile Dataset • Record Entry Profiles in the workbench • Provide mechanism for resending
Timescales • Phase 0 • 01.08 (Late April) • Database changes • Phase I • 01.08 HF? (July) • Data capture • Phase II • 01.09 HF? (?) • Production
Discussion Points • Course Identifier • Static or Sessional? • New Course Id? • Module Identifier • Static or Sessional? • New Module Id?
Discussion Points • FTE Calculation • Appropriate time for consensus? • Cross-Year Students • How reported?
Discussion Points • Some questions … • Unit level data - any plans to draw it from program level for Workbench or DSL offering any solutions to help transfer data to unit level? • Can we edit XML output in or off-system? • When will user testing of Workbench begin? • Can Error Code be included as a filter in the Workbench?