1. Enhanced Electronic Gradebook Gillian Donagher DIT Gwen Kerdiles SungardHE

2. DIT Banner Environment Approx 200 custom forms & reports 95% vanilla for exams Currently Banner Student 7.3 – DB Oracle 10.2.0.2 on TRU64, App Server Oracle 10.1.2.0.2 on Windows Moving to Banner Student 7.4 with enhanced EGB – DB Oracle 10.2.0.3, App Server – Oracle 10.1.2.3

3. Background to DIT 20,000 students across 6 major sites Went live with Banner in 2002 primarily for admissions and registrations Pilot of EGB and Academic History in one school in 2005 EGB rolled out to entire Institute in 2006

4. Success...but… EGB did not meet all DIT’s requirements Other colleges had a similar view

5. Collaboration February 2007 – Collaboration group of 7 colleges formed – First meeting held in Salford – Common priorities identified – Reassessment, the ability to change marks in Academic History, navigation in EGB, controlling dates of publication of results to students and the ability to enter grade comments in EGB were the main issues – Group agreed to approach SGHE with requirements

6. Support from SungardHe November 2007 – First draft of requirements document January 2008 – First face-to-face meeting – Formation of a development project focus-group – Start of the build phase, use of experienced resources – Weekly conference calls

7. Support from SungardHE February 2008 – Durham workshop – Demo of the work-in-progress development – Reconfirmation of the goals and choices made

8. Support from SungardHe March 2008 – UAT in Dublin April 2008 – Release of enhanced EGB, including change requests and bug fixes for all items found in the UAT November 2008 – Release of change requests and bug fixes after new test phases at different Universities

9. The SGHE development project approach “Omnipresence” of the focus-group Validation – Weekly – Any time there is a doubt during the implementation – Final UAT, together, in one room  No implementation without full agreement on the requirement and way to implement Active post-release support

10. The Changes….

11. Main new features Enhanced processes – Reassessment = modification of the marks after the roll to Academic History – Roll-back from Academic History Enhanced data-structures – Comments – Fine-grain auditing Rule based Access Control – Property of being eligible for assessment/reassessment – Property of being eligible to view marks and grades Rule based Display Control – Institution/User control on the page layout – Anonymous marking – Name format control

12. Improved EGB Layout & navigation Full description of CRNs in drop down list Order of CRN drop down list configurable Up/Down arrows for marks entry Student names on recordsets # records per page Javascript calendar Restrict grade codes visible in EGB Improved validation & error processing

13. Ordered by part of term

14. Arrows can be used to navigate between student records

16. Staff PIDM GTVSDAX Setup

18. Grades restricted as per STVGCHG

19. Codes with SSB Ind are available in EGB Assessment If Reasess Ind & SSB Ind is checked then code is available in EGB Reassessment

20. Error appears beside problem record

21. Proposed Decision Composite comment can be entered in EGB for assessment and reassessment DIT is using this to allow a lecturer to propose a decision to the module board in assessment Comments based on STVGCMT

25. Changing Marks Post-Roll Reasons to change marks post-roll – Exam Board decisions – Data entry errors – Reassessment Grade change codes need to be setup on STVGCHG with Academic History/Reassessment checks

30. SHRCMRK

31. Data Entry Errors Unrolling from Academic History Functionality is provided via new form SKAEGBC Cannot be accessed directly on form, must be accessed via options menu on baseline form Unroll is available from the following forms: – SFASLST – SFAALST – SHATCKN

36. Reassessment Process Rules Engine used to define which students are eligible for reassessment DIT rule is based on the grade code on the latest record in Academic History Grade codes for AH and EGB need to be configured on STVGCHG Dates setup on SKAEGBC

44. Self Service Engine SSEN can be used to configure new EGB pages Hiding columns, changing text can now be performed by non technical staff

48. Other changes used by DIT Additional auditing on EGB Pidm not WWW_USER Composite grade listing shows all students Warning on SHAGCOM when components > 100

49. Questions