Harnessing the power of Moodle roles
- 1. Harnessing the Power of Moodle roles Deborah Kearney / Rex Lorenzo / UCLA
- 2. Who are we? Deborah Kearney CCLE Support Coordinator dkearney@oid.ucla.edu Rex Lorenzo CCLE Lead Developer rex@oid.ucla.edu
- 3. Outline 1. Why customize standard roles? 2. What do you need to succeed? 3. How can role customization drive development?
- 4. Why customize standard roles? ! ! ! When standard roles fail or just wont scale ! ! !
- 5. UCLA / CCLE Campus-wide LMS De-centralized support
- 6. UCLA / CCLE Term! Fall 2012 Fall 2011 Fall 2010 Fall 2009 Fall 2008 Total Users 46,717 41,881 27,664 26,868 17,445
- 7. Case study: 1.9 Admin role Problem Category-level: too limited Site-level: too powerful Solution Create new limited site-administrator role
- 8. By trimming site-admin permissions standard admin view limited admin view
- 9. Possible intersection points Site con鍖g settings Contexts Capability! a/b:c Role overrides Other capabilities
- 11. Remove Add in Create sites manually; place in any Category Add/remove/change any CCLE user role in any site Change the settings on any existing site Add content to any site Copy to/restore from any site Import to/from any site Check the Profile of any user Create a special-case login on CCLE Approve Moodle course requestor sites
- 12. Customizing is hard ! Everything is connected Roles & capabilities dont live in a vacuum
- 13. Con鍖guration settings trump permissions No
- 14. Vicious cycle Change Rollback For 3 Years! Report problem
- 15. Case study (contd): Manager role in Moodle 2.0 Role between site admin and editing teacher Something we can assign at category level and site level
- 16. Manager role imperfections Still need site-level role for access to site reports and tools Manager limited Needed to be locked down when assigned at site level New capabilities needed
- 17. Scaling manager role Site con鍖gs tied to abilities Grades => Site con鍖g Backup/Restore/Import => Site con鍖g Course settings => Frontpage settings Disallow dangerous actions Bulk user actions
- 18. New tools and reports 1. Roles capabilities https://github.com/danielneis/moodle-reportrolescapabilities 2. Edit roles by capability https://github.com/moodleou/moodletool_editrolesbycap 3. Roles migration https://github.com/ncsu-delta/moodlereport_rolesmigration
- 24. What do you need to succeed? 1. Experience in role management 2. Ability and willingness to make code modi鍖cations to scale roles 3. Tools to support roles
- 25. How can role customization drive development? Solve complex problems with elegant tools
- 26. Case study: Editing teacher Problem! Teacher is in charge of enrollments Access to entire user DB Solution! Delegate enrollment to local support Enrollment key
- 27. Wouldnt scale Delegating enrollment to local support Tenure faculty found process frustrating and absurd New units joining system also frustrated Enrollment key limitations No control over who uses it Burden on faculty to set it up
- 28. Invitation enrollment Track who uses invitation Granular role assignment Make it easier to choose proper role
- 36. Invitation Enrollment Open source version: https://github.com/ucla/moodle-enrol_invitation
- 37. Conclusion 1. Why customize standard roles? To scale or 鍖t unique use cases 2. What do you need to succeed? Tools, reports, and developers 3. How can role customization drive development? Solve complex problems with elegant tools
- 38. Q&A / Contact Deborah Kearney CCLE Support Coordinator dkearney@oid.ucla.edu Rex Lorenzo CCLE Lead Developer rex@oid.ucla.edu 際際滷s: http://www.slideshare.net/rexlorenzo