Sakai la-ewsv2

392 views
318 views

Published on

EWS using Sakai

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
392
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sakai la-ewsv2

  1. 1. Early Warning System for Identifying students at risk of failing<br />Roger Brown<br />Center for Educational Technology<br />University of Cape Town<br />roger.brown@uct.ac.za<br />
  2. 2. Overview<br />PART 1<br />Why we started looking at EWS<br />The functional requirements of the system<br />Institutional fit<br />Matching Vula (Sakai) affordances to the functional requirements<br />Developments that would allow Sakai to act as an EWS (well some of them anyway!)<br />How UCT is moving forward<br />PART 2 - Discussion<br />Activity and course grade<br />Your ideas<br />12th Sakai Conference – Los Angeles, California – June 14-16<br />2<br />
  3. 3. Part1: Introduction<br />In 2009 Senate Re-admission Review Committee recommended that greater attention needed to be given to Faculty EWS. <br />The SRRC report recommended that:<br />the SRRC monitors data from the Faculty EWS with the aim of assessing and reporting on the impact mid-year exclusions have on throughput rates, and <br />Investigate the EWS issue to assess the most effective approach to adopt a single system thereby providing consistency across faculties.<br />
  4. 4. EWS – Functional requirements<br />The ability to record a standard number of “in course”results/performance/grade<br />The ability to create a current class list of all valid registered students in a course, populate this list with “in course results”, and load these to the students’ PeopleSoft record.<br />Specification of an “at risk” threshold value for these results<br />Recording of comments against a student<br />Generation of communication to identified students <br />Retentions of a permanent record of these communications<br />Specified reporting of student performance<br />For a student within a course across all courses<br />For a specified cohort of students<br />Access and authorisations to entry grades, viewing of grades and running of reports, course conveners and/or mentors and/or other “intervention” managers <br />
  5. 5. EWS – Institutional criteria<br />Technical Implementation<br />Technical Integration<br />Usability and User Support Requirements<br />Technical Support<br />Security and Authorisations<br />Student Access<br />Overall Reporting Capacity<br />Cost (of licensing, implementation and support)<br />Vendor and Product Sustainability<br />
  6. 6. EWS Functional requirements and Vula (Sakai 2.7) - Integration<br />PeopleSoft<br />HEDA - Higher Education Data Analyzer <br />Demographic and K12 data (currently used by IPD)<br />IDvault<br />
  7. 7. Vula: Affordances vs Requirements<br />Groups: Easily created and populated<br />Configurable Roles: <br />Access<br />and authority<br />Gradebook<br />
  8. 8. Vula: Affordances vs Requirements<br />Communication: <br />Email<br />Internal message<br />SMS<br /><ul><li> Secure
  9. 9. Familiar
  10. 10. Widely accepted by admin/academic staff (2474 staff used Vula in 2010)</li></li></ul><li>Vula: Affordances vs Requirements -Gradebook<br />1. Import marks from excel<br />3. Integrates with Vula testing tools<br />2. Weighting and Categories<br />
  11. 11. Assessing students at risk?<br />Back to My Workspace<br />Out of Gradebook<br />
  12. 12. Vula: Limitations (currently)<br />“At Risk” assessment would need to be done outside Vula<br />Not all lecturers/course convenors use Vula<br />Vula is not the authoritative source of marks<br />Vula does not “push” data to PS<br />Staffing<br />
  13. 13. Vula: R&D for EWS application<br />Automated Gradebook export to ETL platform or preferably an internal logic<br />Internal or external algorithm development for risk analysis<br />Auto grouping based on risk analysis<br />Reporting communications, display, etc <br />Predictive logic based on previous student performance<br />
  14. 14. How UCT is moving forward<br />The task team recommended in phase 1<br />EWS to utilise the functionality of PeopleSoft (some developments required)<br />Improve the integration of Sakai and PS <br />gradebook export to PS (it’s easier to get grades into GB than into PS )<br />Samigo& Asn => GB => PS<br />12th Sakai Conference – Los Angeles, California – June 14-16<br />13<br />
  15. 15. Part 2: Vula: Final grade vs all events (PSY1001W)<br />
  16. 16. Your Ideas <br />12th Sakai Conference – Los Angeles, California – June 14-16<br />15<br />Predictive modelling<br />GB in students’ “My workspace”<br />?<br />Using ETL<br />Communicating “failure”<br />Learning analytics<br />A “read only” SU role in Sakai <br />Data mining – automating and exposing<br />More than grades only? – is attendance a predictor?<br />

×