1 / 23

The Moodle Reader Module: A Progress Report

The Moodle Reader Module: A Progress Report. Thomas N. Robb Kyoto Sangyo University trobb@cc.kyoto-su.ac.jp http://moodlereader.org. Purpose of the Reader Module.

todd
Download Presentation

The Moodle Reader Module: A Progress Report

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. The Moodle Reader Module: A Progress Report Thomas N. Robb Kyoto Sangyo University trobb@cc.kyoto-su.ac.jp http://moodlereader.org

  2. Purpose of the Reader Module • To provide an efficient, easily manageable means of testing the comprehension of texts used for extensive reading (and thus the ability to assess whether students have read the books they claim to have read). • To ensure that students only select books at their own reading level in order to prevent frustration and overuse of the dictionary. • To encourage regular reading by pacing the quiz-taking times • To provide a mild sense of competition and an additional incentive to reading through the cover "stamp collection"

  3. Choosing a book from the library

  4. Comparison of AR Program and the Reader Module Approach

  5. Question Types • True/False • Multiple Choice • Matching questions • Who said this? • Ordering type

  6. Comparison of Student Accesses – AR vs MR

  7. Quizzes Taken Friday, June 6Passed: 243; Failed: 51; Total: 294

  8. Analysis of AR vs. Reader Module • More books read. 4.7 per students for AR, vs. 8.3 for the Reader Module for the same time period • A more even distribution of reading. (AR students could not take quizzes on weekends and tended to postpone their reading to the end of the reading period.) • Fewer quiz failures: Greater comprehension?

  9. Two Approaches to Implementation • 1. Install the MoodleReader Module on your own server • 2. Request a course on MoodleReader.Org

  10. Setting Up the Module (1) • Install the "Reader Module" in their Moodle course. • Import, from moodlereader.org, quizzes for the books that you have in their own ER collection. You may also create their own quizzes for any books for which quizzes are not available. • Determine which reading level the books should be set at (if they wish to depart from the recommended levels in the repository) and set the initial level for each student.

  11. Set-up (2) • Set parameters such as • target point goal • the time limit • where quizzes may be accessed • passing percentage, • how frequently quiz taking is to be permitted • Determine a policy for how points are gained, or how total points above and below the set target point value are to be integrated into the students’ final class evaluation.

  12. Procedure for Students • Students read a book and then take the quiz. • If students pass the quiz, they are awarded one point, none if they fail. • Books at any level that are considerably longer or shorter than the average graded reader at that level may have a higher or lower point value. • When students have passed a specific number of quizzes at their current level, they are promoted to the next level. They can still take a set number quizzes on books one level above or below.

  13. Color-Coded Levels

  14. New Admin Menu

  15. Student Summary Report

  16. Level Adjustment Page

  17. Implementation Challenges • Funding and coding • Obtaining cover images from publishers • Problem of multiple editions • Getting publishers to create quizzes • Quality control of teacher-made quizzes • Getting other schools to participate • Syncing authentication systems

  18. Another Lesson Learned Implementation of technology for student use across an entire curriculum Sidesteps the problem of requiring or expecting individual teachers to have the know-how, time and/or enthusiasm to implement a tech component But this requires:

  19. Curriculum-wide Implementation • The authority to require it • An adequate server and necessary software • The human resources (ideally tech-proficient teacher) to implement and support it, including system back-up • A mechanism for making the student grade reports available to the individual instructors so that they can incorporate the grades into their students’ final evaluation.

  20. Questions/Discussion? • Logins: user-low OR user-mid with same for the password • Email: tom@tomrobb.com • http://moodlereader.org

More Related