1 / 32

Adventures in Open Source - Moodle, Mahara, Drupal et. al. at Purchase College

Adventures in Open Source - Moodle, Mahara, Drupal et. al. at Purchase College. Keith Landa SUNY Wizard Conference 18 November 2010 http://www.slideshare.net/keith.landa. Student Information System. Academic Analytics. Library Information Systems. Campus Repository.

rowa
Download Presentation

Adventures in Open Source - Moodle, Mahara, Drupal et. al. at Purchase College

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. Adventures in Open Source - Moodle, Mahara, Drupal et. al. at Purchase College Keith Landa SUNY Wizard Conference 18 November 2010 http://www.slideshare.net/keith.landa

  2. Student Information System Academic Analytics Library Information Systems Campus Repository The View from 30,000 Feet

  3. Why @ Purchase? http://moodle.org Criteria -Functionality -Support -Architecture/integration -Total cost of ownership -Risk management

  4. Background – Purchase – 2008 Liberal Arts and Sciences plus Arts Conservatories ~4200 FTE ERes electronic reserves Web enhancement of F2F courses Online programs in the works

  5. The LMS Landscape What is Moodle? The world’s most widely used open source LMS • 49,000 Registered Moodle Sites • 35,000,000 Registered Users http://www.moodle.org/stats

  6. Faculty Blackboard uses LMS desired features Distribute materials Library services Integration with SIS Course communications Links to external web sites One stop shopping for students Discussion forum Gradebook New media (blogs, wikis, podcasts) Drop boxes Student collaboration tools Course reports Self-directed lessons Online quizzing Real-time tools (chat, etc) Clickers No “killer app” tying us to Blackboard

  7. Student Survey Responses

  8. Implementation – course migration • Blackboard - ~1000 courses; ERes – substantially more • ERes – document download, upload to Moodle • Blackboard – Moodle can import Blackboard course archives (zip files), but…. (problems with the Bb archives) • Temp services staff - ~300 hours from May to Aug 2009, primarily ERes migration • Bb course migration on request during 2009/2010 year

  9. Implementation – faculty development • Spring 2009 workshops: hour long sessions, various topics; early adopters; 28 faculty • 2009 Summer Faculty Workshop Series: new programming, not just Moodle; half- and full-day workshops; stipends; 36 faculty at Moodle sessions • Fall 2009: Moodle Kickoff workshops; Getting Started, Gradebook, Learning Activity; 98 faculty

  10. Cost comparisons Switch to Moodle saves us over $50K each year (Blackboard and ERes licensing costs) Risk management: -dislocations in the commercial space -self-host vs vendor host: http://goo.gl/tQ5uX

  11. Community contributed modules Lightbox Gallery resource Map activity Community Modules and Plugins page http://moodle.org/mod/data/view.php?id=6009

  12. Bringing the cloud into the course

  13. Open advantages Enrollment automation Student Information System Academic Analytics Library Information Systems • Library integration • Reserve requests • Electronic resources Campus Repository Senior projects

  14. Focus on teaching & learning - Robust set of activities & resources - Add-on modules from the community - Moodle development pathway Integration - Other systems - Web 2.0 world Why @ Purchase? Costs - No licensing costs - Similar support costs Flexible open architecture Risk management - Risks of open source - Commercial products have different risks

  15. Campus lessons - Moodle • LMS focus should be learning • Faculty AND student perspectives • Change is hard, and exhilarating • Stewardship of campus resources • Choose the risk you’re comfortable with • Importance of community critical mass for open source apps • Clear roadmap for product development

  16. http://mahara.org • “Mahoodle” • Single sign-on • Mahara assignment in Moodle • Adoption process for Mahara • Why e-portfolios? • Tool to showcase student/faculty work? • Tool to support student learning? • Tool to collect institutional data?

  17. Mahara overview “Collect, select, reflect” and share (access control) Resume building Social networking

  18. Building and sharing a portfolio • Assembling artifacts • File uploads • Blog reflections • External materials (web video, RSS feeds, etc) • Creating a view • Determining the layout • Assembling and arranging portfolio components • Determining access controls • Share with individual user (e.g., instructor) • Make public, generate unique URL • Share with group (e.g., course group) • Submit to a course group (freezes portfolio view) • Creating templates

  19. Campus lessons - Mahara • Adoption slower than with Moodle • Less faculty interest • Stealth adoption • Stronger tie to Moodle 2.0 • Repositories • Focus on tool for student learning • Constraints on student showcase uses • Constraints on harvesting institutional data

  20. Importance of video at Purchase College • Film and media studies; cinema studies; journalism • Class projects • Student organizations • Training materials • Existing use of cloud video • Journalism & YouTube • TLTC Vimeo channel • http://vimeo.com/channels/97810 • Five Minute Moodling • Need for a campus solution? • Kaltura open source video • kaltura.comvskaltura.org • Use by serious players • Plugins already available Campus Repository

  21. Campus lessons - Kaltura • Too early to tell, hopeful • SaaS and community source model is interesting • Developer community appears vibrant • Baseline integrations with apps on campus

  22. WordPress, Drupal, OpenScholar WordPress -Implemented on campus before Moodle -http://blogs.purchase.edu -Some active individual blogs -Departmental use instead of homegrown CMS -e.g.: http://tltc.blogs.purchase.edu Drupal -Replacement for our home-grown CMS? -CampusEAI portal – includes CMS -Drupal for special projects -http://drupalsites.purchase.edu OpenScholar -Faculty scholarly web pages -Customized Drupal application

  23. Why were we so interested? -Legacy faculty web page service -Faculty desire for self-service -Information reuse possibilities -External faculty profile pages

  24. Ease of faculty updates -Editing existing content -Adding new items -Default layouts, widgets

  25. Faculty choice of -features -themes/appearance Ability to add others Central content access However….

  26. Campus lessons - OpenScholar • Make sure application is ready for primetime • Default authentication, site creation • Server constraints • Be prepared for community growing pains • Persistence Recent progress

  27. WordPress Drupal

  28. Campus lessons – WordPress, Drupal • WordPress – plug-in proliferation • Plug-in and version upgrades • Initial decisions can be critical – WP config • WordPress is easy for most users • Drupal is powerful, can be daunting • Need for turn-key Drupal set-ups

  29. Student Information System Academic Analytics Library Information Systems Campus Repository The View from 30,000 Feet

  30. Questions? Keith Landa Purchase College SUNY 914-251-6450 keith.landa@purchase.edu

More Related