Your SlideShare is downloading. ×
ULCC Moodle User Group (HE) - 03.07.13
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ULCC Moodle User Group (HE) - 03.07.13


Published on

The ULCC slides from the ULCC Moodle User Group (HE) meeting which occurred on Wednesday 3rd July 2013

The ULCC slides from the ULCC Moodle User Group (HE) meeting which occurred on Wednesday 3rd July 2013

Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • First of, if you are not already aware, the matrix and policy can be found on the ULCC customer demo site which is available here. It will eventually move to our customer portal but in the mean time it is available here. In line with our new plugins policy from September 2013, plugins will be request able twice a year: in September to be installed by January, and in January to be installed alongside any upgrade. This includes plugins that are within our plugins matrix and new ones that need evaluating. This has been done so that ULCC can stay committed to evaluating and installing the plugins. Until September any plugins can be requested ad-hoc to be evaluated by ULCC to see if they meet the criteria to be installed.
  • So what's the criteria that ULCC evaluate plugins to…Well, a plugin must add sufficient value to Moodle and do what it claims. There are a number of plugins which suggest that they do one thing and don’t or are a minor improvement on existing Moodle functionality which should really be looked at as a change of Moodle core functionality through adding an improvement request on Moodle's core functionality tracker website tracker.moodle.orgIt must be unique in the sense that it cannot duplicate existing Moodle functionality or a existing contributed Moodle plugin which ULCC have already approved unless there is a large enough case otherwise. This is so that we can deliver a reasonable list that means your needs. The plugins must be secure in that they provide minimal security risk to being installed on your site. There are several plugins that have been rejected for reasons including storing user data on a third party service without a reasonable privacy policy. The plugin should be written by a developer or company who is committed to maintaining the plugin. There are several plugins which get made which then are no longer maintained by its authors. Of course there will be plugins which upon re-evaluation are no longer maintained but there should be sufficient evidence that the author is committed to maintaining the plugin such as recent discussion about changes, a statement from the author or the plugin being recently updated. The plugin must meet a risk assessment to see whether it would likely cause issues in future upgrades. For example, there are some plugins that rely on other functionality and therefore release notes for future supported releases would need to be assessed to make sure that a change in their functionality isn’t likely to affect it for example, the Moodle Mahara Assignment type is reliant on the Moodle 2.2 assignment functionality which still exists in 2.4 but will disappear eventually. The plugin must have sufficient documentation available to make it easier to use the plugin. There are several plugins with little or no documentation that just expects you to understand how to use it when sometimes it is unclear on the best use. The plugin must be written to have best efforts to meet Moodle coding standards and be well developed. This is to ensure that that plugin has minimal impact on the performance or stability of your site as there are several plugins that are deemed “beta” or some plugins have an impact on a Moodle site when used extensively so they need to be carefully thought about.
  • Transcript

    • 1. ULCC Moodle User Group (HE)
    • 2. WiFi & Hashtag Eduroam Use your institutional login credentials WiFi WiFi - UoL Conferences Password - fthofo @ulcc #ULCCMUGHE
    • 3. Agenda • Introductions • Feedback from last meeting • Current work and developments • Future developments and plans • Q&A session @ulcc #ULCCMUGHE
    • 4. Introductions Dave Kenworthy Head of Software Services Mick Kahn Head of Learning Technology Services Sarah Sherman BLE Service Manager ULCCMUGHE Chair @ulcc #ULCCMUGHE
    • 5. Introductions Mike Dearing Senior Solutions Consultant Richard Havinga Learning Technologist Richard Thompson Service Desk Manager @ulcc #ULCCMUGHE
    • 6. Feedback from last ULCCMUGHE • Approved list of plugins • Joint funding for developments • Be a megaphone to Turnitin • Access to support ticket status • Sharing best practice @ulcc #ULCCMUGHE
    • 7. Current work and developments Demo of Customer Portal Richard Thompson
    • 8. Current work and developments How MMU approached load testing Mark Stubbs
    • 9. Current work and developments Reporting/analytics framework Dave Kenworthy
    • 10. Reporting/analytics framework • What is it? – Reports from Moodle DB (including logs) – Data source separated from production DB with time delay – On-screen reports through Moodle – Web Services for integrations – Remote MySQL for integrations – Ability to add many more reports @ulcc #ULCCMUGHE
    • 11. Reporting/analytics framework @ulcc #ULCCMUGHE
    • 12. Reporting/analytics framework • £8,500 p.a. for – Reporting Server (4CPU, 50GB) – Reporting Framework Moodle plug-in – 13 reports (see handout) – Remote MySQL access to reporting DB • 2-4 days initial setup (£1300 – £2600) – 2 days for server + framework – 2 (optional) days for remote MySQL @ulcc #ULCCMUGHE
    • 13. Current work and developments Moodle Plugins Richard Havinga
    • 14. Plugin Policy & Matrix • Matrix and policy – • September changes @ulcc #ULCCMUGHE
    • 15. Plugin Policy & Matrix What are the criteria? • Add Value • Unique • Secure • Sustainable • Upgradable • Documentation • Stability @ulcc #ULCCMUGHE
    • 16. Future developments and plans Annual cycle of implementations and service roll outs
    • 17. Development cycle User requirements Implementation Test Pilot Deploy Detailed specification @ulcc #ULCCMUGHE
    • 18. Current developments • Reporting (pilot v1) • E-assessment (user requirements – but also prior developments) • Course backup/restore (deploy v1) • Test servers (deploy, options) • Individual Learning Plans (deploy v2, implementation v2.4, user requirements: reporting) • New service definitions (detailed specification) @ulcc #ULCCMUGHE
    • 19. Future developments and plans HE Assessment Solution Mike Dearing
    • 20. Q&A Session Questions Next session planning
    • 21. Thank you @ulcc #ULCCMUGHE User Group Chair Contact Information Sarah Sherman BLE Service Manager 07515 580 385