1 / 9

Waterloo LEARN Update

Waterloo LEARN Update. UCIST 20 January 2012. Performance Problems. Worst seems over, still some slow activities Causes (various) D2L database problems D2L DNS problems S ervice on another client installation (our 11 front end servers moved to own pool) Other performance related topics

kalyca
Download Presentation

Waterloo LEARN Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Waterloo LEARN Update UCIST 20 January 2012

  2. Performance Problems • Worst seems over, still some slow activities • Causes (various) • D2L database problems • D2L DNS problems • Service on another client installation (our 11 front end servers moved to own pool) • Other performance related topics • Plan network peering with ORION • Tools for tracing problems (e.g., fiddler)

  3. Winter 2012 activities • Learning Object Repository (Jan. 11th) • Data retention, activity tracking, etc. (with D2L, Jan. 18th) • Electronic marking (CEL & D2L demos, Jan. 18th) • Analytics (D2L demo, Jan. 31st, 1 – 4:30) • Guelph, WLU discussion (mid Feb.) • Devsystem for next version (mid Feb.) • Retreat (end Feb.) • Feedback to “fees not arranged” process • Feedback from students and instructors • Final report (75% done) • Upgrade end of April • ANGEL renewal to May 2013

  4. LOR update • Relatively low activity now • Instructional Repository to be set up (shared instructional resources from ANGEL) • Contact people requesting departmental repositories • Include Math for access to course materials • Determine how to use consulting time remaining with D2L

  5. Data Retention, Activity, etc. • Data retention policies to be same as ANGEL • Course with student data kept live 1 year after final marks, then deleted • Course content (not student data) kept for 3 years after term of offer, then deleted • Will be stored at uWaterloo • Next steps: • Policies need to be put into action

  6. Data Retention, Activity, etc. • Activity tracking • Issues: Limited built in reporting; no access to database for ad hoc queries; less rich logging data than ANGEL • E.g.s of use: • Student claims submitted dropbox item, but does not show. How to (dis)prove? • How many courses use quizzes, dropbox, etc. • Next steps: • D2L to give access to logs, check for more logging • Analytics demo (expensive product)

  7. Electronic Marking • CEL • Impetus: Timeliness of feedback, cost in mailing and time, lots of process to organize • Solutions: Digital ink (tablet), Microsoft Track Changes, PDF Annotator, macros • D2L comments • Next steps – pilot with D2L? Help roll out CEL solutions for campus?

  8. Retreat February 29th • Prep • Training on V9.4.1 (installed on dev Feb. 13th, training on 21st) • Integration consultation with D2L to discuss Maple TA, iClicker, eReserves, Turnitin feedback, etc. (date not set yet) • D2L strategic planning framework? • Consider how to involve D2L in process

  9. Over to you Questions?Comments on anything you’ve heard?

More Related