Tailoring Moodle to Your Own Needs JALTCALL International Conference, Waseda University, Tokyo, 2 June 2007 Don Hinkelman, Sapporo Gakuin University Thomas Robb, Kyoto Sangyo University Paul Daniels, Kochi University of Technology Andy Johnson, Sapporo Gakuin University Gordon Bateson, Kanezawa University Peter Ruthven-Stuart, Hakodate Future University Version 5, Updated 2007.6.1
72
Embed
Tailoring Moodle to Your Own Needs JALTCALL International Conference, Waseda University, Tokyo, 2 June 2007 Don Hinkelman, Sapporo Gakuin University Thomas.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Tailoring Moodle to Your Own Needs
JALTCALL International Conference, Waseda University, Tokyo, 2 June 2007
Don Hinkelman, Sapporo Gakuin UniversityThomas Robb, Kyoto Sangyo University
Paul Daniels, Kochi University of TechnologyAndy Johnson, Sapporo Gakuin UniversityGordon Bateson, Kanezawa University
Peter Ruthven-Stuart, Hakodate Future University
Version 5, Updated 2007.6.1
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
2
Your LMS
Learning Management System (LMS)
Commercial or Open Source?
Moodle LMS >> My LMS
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
3
Types of “Tailoring”
Module Plug-in Block Modification
(tweak, hack, mod)
Customization Theme
Most difficult
Easiest
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
4
Outline of WorkshopModules Modules Plug-ins Blocks Tweaks Custom1. Hot Potatoes
2. Lecture Feedback
3. Project Module
4. Self-Study
Tom RobbDon HinkelmanPeter Ruthven-Stuart
5. Presentation
6. Media Blog
7. Seating Chart
8. FreeMail
Paul Daniels
9. Word Order Quiz Type
10. Split Screen Quiz Type
11. Content Choice Quiz Type
12. Seat Numbers & Nicknames
Tom Robb Andy Johnson
13. Lab Attendance
14. Blogger Links
15. Highest Quiz Scores
Tom RobbDon Hinkelman
16. Standard Romaji17. Cellphone Addresses18. Language Menu19. Multilang Filter20.Show/HideActivities21. Useful Links 22. Rotating Banners
Gordon Bateson
23. Roles
24. Themes
25. Language
Peter Ruthven-StuartDon Hinkelman
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
5
Basic Structure of Moodle
Moodle code directory (moodle) (See next slide)
Data directory (moodle_data) Contains all uploaded files including user pix
Numbered folders correspond to course IDs
Database (MySQL or PostgreSQL) MySQL is preferable since the user base is far greater
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
6
The Moodle Code Directory
Most common directories for tweaking Block Course
Many files herein can be tweaked to add/delete items that are displayed on the course page
Lang en_utf8 needs to include any new definitions
Lib code that is used in more than one place
Mod Themes
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
7
Adding new modules
Best to start by copying an existing module, renaming all elements within to a new name
A custom module that is not complete may wreak havoc with backups and restores, as well as cause “white screens” and other unpredictable behavior
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
8
Moodle Directory
Modules go here
Blocks go here
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
9
Moodle ‘mod’ folder
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
10
Moodle Database
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
11
Moodle Table
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
12
Module 1
Hot Potatoes Module Type: Module What it does:
Takes activities created in Hot Potatoes…Drap and dropMatchingxxx
Converts into a Moodle activityWhere to get it: now a standard moduleWhere to get help: moodle.org Using
Moodle forums
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
13
Module 2
Lecture Feedback Module Type: Module What it does:
Collects student questions and summaries of lecture-type classes
Semi-automatic coding of student feedbacks for printing (handout for next class)
Takes attendence with numbered, printed slips entered into a database (now separate module)
Mobile phone option (in class) or Desktop computer input option (after class)
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
14
Module 2
Lecture Feedback Module Screenshot
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
15
Module 2
Lecture Feedback Module Screenshot
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
16
Module 2
Lecture Feedback ModuleHow to install it:
Contact Don Hinkelman directly for package
Drop package into “mod” folder For mobile phone option:
Familiarize yourself with Moodle’s backend.database & directory structure
Read up on PHP and MySQL.freewebmasterhelp.com/tutorials/php/webmonkey.com/webmonkey/programming/php/tutorials/tutorial4.html
Find a programmer to work with long term.Scriptlance, Getafreelancer or RentACoder
Try out some easy jobs first.Project management skills are crucial.Set aside some extra funds for bug fixes.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
40
Plug-in
Ordering Question Type
Available: contact Tom Robb for latest download
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
41
Plug-in
Split Screen Mode
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
42
Plug-in
Content Choice Question Type
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
43
Plug-in/Hack
Seat Numbers & Nicknames
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
44
Plug-ins & Modifications
Advice
Working with Non-teacher Programmers Creating plug-in and “mod” proposals
Testing & debuggingOverall experience
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
45
Working with Non-teacher Programmers
Skills/experience recommended to work with non-teacher programmer (in order of useful to least useful)Software userExperience with computers in classroom
Basic skills with graphics programs Novice PHP/MySQL programming skills
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
46
Working with Non-teacher Programmers
It’s not enough to simply describe in general terms what you want your hack to do. You must explain in detail (better yet, visually show) what you want to happen on every stage.
<show Word HOs here>
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
47
Working with Non-teacher Programmers
Make sure you and programmer are using exact same version of Moodle.
Check in various browsers and in both Mac and Windows platforms.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
48
Working with Non-teacher Programmers
Don’t test/debug new modules in active Moodle (i.e. one with real students’ data)
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
49
Working with Non-teacher Programmers
Thoroughly check for bugs in every possible situationLog in as a student and test (i.e. just switching role to student is not enough); If you are an admin, also log in as a teacher and test.
You find different bugs testing as a single teacher than when you test a whole class full of students.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
50
Working with Non-teacher Programmers
Use movies to show bugs to programmer
QuickTime™ and aSorenson Video 3 decompressorare needed to see this picture.
QuickTime™ and aSorenson Video 3 decompressorare needed to see this picture.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
51
Working with Non-teacher Programmers
Nothing is ever 100% done; New bugs will always be found.
Make sure you have a programmer who offers “after-service care” and is willing to make minor modifications over time.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
52
Working with Non-teacher Programmers
You can’t rush it. Testing and debugging is a lengthy process.
The more time you spend at this stage, the easier actually implementing the new module into your active Moodle will be.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
53
Finding a Programmer
Qualifications: MySQL, PHP experience Moodle and open source Track record, and willing to give references Good communication (English, Japanese)
What it does:• Allow Moodle signup using (cell phone) email
addresses, which can contain “invalid” character combinations:• repeated full-stops, “..”• a full-stop just before the at-sign, “.@”• e.g. [email protected]
Small changes to your Moodle scripts are usually OK if you use CVS, changes are automatically merged otherwise you need to keep patching, manually or semi-automatically (e.g. WinMerge)
Offer code improvements on the forums or tracker small improvements that have been tested even then, the developers may be too busy to implement the changes.
A role is a set of permissions for a person in a specific context
Classic Roles:TeacherStudentAdmin
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
68
Roles New roles you might try to create: Moderator: a person who can edit or delete a forum post
Seminar Leader: a student who can make activities in a single course, but cannot view or change grades
Quiz-maker: students can make quizzes but no other teacher functions
Super Teacher: a teacher with limited admin functions, can add/edit users
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
69
Roles
How to Make a New Role Go to the Admin menu Click on Users >> Permissions >> Define Roles
Click button: Add a new role Assign the permissions you want, a little complex so read documentation in Moodle Docs
Then assign *people* to the role you create in the specific context (ie: course, not site) where they will use the role. The role will apply to them only in that context.
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
70
Themes
Simplest way to “tailor” your site Change themes
Go to Admin >>
Edit themes Themes: header.html, footer.html Get Firefox Web Developer Toolbar
2007.6.2 JALTCALL 2007, Waseda University, Tokyo
71
LanguageAnnoyed by a Moodle phrase on-screen?
Language: you can edit those strings Go to Admin>>Language>>Edit Language>>Edit Words
or Phrases Select the module and file you think it is in