Your SlideShare is downloading. ×
Electronic submission marking feedback moodle moot 2012
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

Electronic submission marking feedback moodle moot 2012

1,421

Published on

Electronic Submission, Marking and Feedback via Moodle 2. …

Electronic Submission, Marking and Feedback via Moodle 2.
Bob Ridge-Stearn
Newman University College, Birmingham

Published in: Education, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,421
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. EXPECT TO ACHIEVEElectronic Submission, Markingand Feedback via Moodle 2.Bob Ridge-Stearn(contact details on last slide)MoodleMoot 2012 Dublin
  • 2. EXPECT TO ACHIEVEMoodleMoot 2011Implementing electronic submission and markingwith Turnitin’s Moodle Direct pluginMoodleMoot 2012Electronic Submission, Marking and Feedbackvia Moodle 2.
  • 3. EXPECT TO ACHIEVEBackground to eSMF at Newman• Drivers• Feedback turnaround times• Quality / richness of feedback• Amount of paper stored in Exams & Assessments• Student Expectations• Flexibility• Uniformity of experience• Electronic Submission Working Group• Academics• Student Union• Quality Office• Exams & Assessments• E-learning• Inclusion/Disability
  • 4. EXPECT TO ACHIEVEElectronic Submission Working Group• Rejected the Moodle – Turnitin integration. • Liked submission process • Disliked marking process (GradeMark)• Asked for further trials – • Moodle Advanced Uploading of Files Assignment Activity • Feedback via Word.• Asked for more information about • current practices across the University College • Opinions and experiences of staff and students
  • 5. EXPECT TO ACHIEVE Report.External Consultant(Andy Birch)commissioned toproduce a report.Bought to ourattention the greatvariety of assessmenttypes in use, thatmany tutors alreadyused electronicassessments andsubmission and alsothat some tutors wereapprehensive of theidea of marking online.
  • 6. EXPECT TO ACHIEVESome of the Report Recommendations.1. After a system is devised, this is clearly disseminated and training materials produced.2. A daytime submission deadline is adopted.3. Moodle Advanced Assignment tool is adopted as the submission method4. Change Management approach is adopted.
  • 7. EXPECT TO ACHIEVELearning & Teaching Committee Nov 2011.• Proposal • Introduce ES in Sept 2012 - not include marking and feedback• Concerns • Who would print off the assignments? • Who would cover the cost of this? • Would this have an impact on turnaround times? • Would resources be available in Exams & Assessments? • Use of home PCs • Health & Safety • Training • Cannot separate submission from marking/feedback• Rejected
  • 8. EXPECT TO ACHIEVELearning & Teaching Committee Jan 2012.• New Proposal • A phased approach - Introduce ES in Sept 2012 in only certain level 4 modules • Submission AND electronic feedback/marking included • Not a roll out – a further pilot.• Agreed.• New working group formed - eSMF Implementation Group • Added IT Services and Health & Safety to existing members of Working Group. (Does not replace Working Group) Implementation Group is focussed on delivering the goods within a timescale.
  • 9. EXPECT TO ACHIEVENew technical procedures mean… New policies and procedures.• Stakeholders • Processes affected. affected• Quality Office • Submission• Exams & Assessments • Marking• IT Services • Feedback• Academics • Disputes• Students • Lateness• External Examiners • Moderation• Senior Academic Support Tutors • Second Marking
  • 10. EXPECT TO ACHIEVE Example screenshot from the project task list.
  • 11. EXPECT TO ACHIEVEMoodle.• Sometimes we had to adapt the VLE to our existing policies and procedures.• Sometimes we had to adapt policies and procedures to the technology.• Each time any adaptation (i.e. compromise) was required it involved explanations and negotiations with stakeholders. Sometimes apparently minor decisions took longer to resolve than anticipated as the context as seen by different stakeholders was more complex.
  • 12. EXPECT TO ACHIEVEExamples of adapting Moodle to fit withpolicies/procedures.• Blind Marking / Anonymous marking.• Create all assignments automatically with set defaults• Standardization of experience – just one Assignment type• Enable email receipt for students• Provide students with uniform assessment information across all courses/modules
  • 13. EXPECT TO ACHIEVEMoodle – Blind / anon marking. We achieved this by changing the Moodle code in the Assignment Module. We didn’t need to modify the database as we just populated the ID # field , which previously contained the student name with the student ID number. Strictly speaking this isn’t 100% anonymous but we can live with it.
  • 14. EXPECT TO ACHIEVEMoodle – Blind / anon marking.
  • 15. EXPECT TO ACHIEVEMoodle – Blind / anon marking.Anonymizing the Reports part wastricky so we simply removed thereports that were difficult toanonymize and left only the GraderReport. This shouldn’t cause too muchinconvenience as this function isn’twidely used at Newman as grades aremore often analyzed in SITS.
  • 16. EXPECT TO ACHIEVEMoodle - Standardized Assignments To standardize the way assignments are set up we now set them up1. Limit types of assignment automatically by having an SQL script2. Create all assignments that takes parameters for things like the same assignment name, deadline etc from SITS where that info is already stored and creates the assignment and inserts it into the top section of each course. Because not all courses are the same – some need to allow multiple files to be uploaded – module leaders complete a form asking how the Assignments should be set up – we’ll look at that in a minute – and Exams & Assessments staff are trained to EDIT the assignments once created.
  • 17. EXPECT TO ACHIEVEMoodle - Standardized Assignments These are the sort of things we wanted to standardize because without standardization we have students who can delete submitted files on one module but not on another, who have to press ‘send for marking’ on one, but not etc.
  • 18. EXPECT TO ACHIEVEMoodle – email submission notifications In our trials of Moodle 2.0 in Semester 1 2011/12 we had a big problem with providing a date stamp for students . This arose for two reasons. 1. A date stamp is produced even if the submission process is incomplete. 2. Students thought they had uploaded because they had chosen and uploaded a file but the file is not actually uploaded until a Save Changes button is pressed.
  • 19. EXPECT TO ACHIEVEMoodle – email submission notifications So our solution was to change the code to send emails to students as well as tutors when this setting was changed. The circled area is non- standard. Normally only teachers receive emails. We will deal with tutors’ displeasure by educating them about creating email rules to filter their inbox.
  • 20. EXPECT TO ACHIEVEMoodle – uniform information required acrosscoursesFrom next semester all our Moodle courses will carry Module, Course andInstitutional Information on them. This change was made for two reasons.1. Last year (March 2011) we completed a QAA institutional audit. One of therecommendations was that we should ensure a complete, consistent and synchronizedpublication of programme specifications and handbooks.2. By September 2012 all HEIs have a legal obligation under new Public Informationrequirements to publish Key Information Sets (KIS) for every “course” they offer (this isoverseen by HESA (Higher Education Statistics Agency)).This information will also be available off Moodle – on mynewman (?) and available toprospective students and existing students who need information to choose futuremodules.
  • 21. EXPECT TO ACHIEVEMoodle – uniform information in iframeData is on SITS andpublished to a statichtml file in a virtualdirectory on theMoodle server.Formatted by CSSEditable by Staff inQuality Office only
  • 22. EXPECT TO ACHIEVE Moodle – uniform information in iframeWe couldn’t have Module Data Sets inevery course as we have courses thatdo not relate to academic modules,e.g. Subject Areas have their ownMoodle pages.Also meta courses that takeenrolment from multiple SITS coursesdo not have their own module DataSets so we named all meta courseswith – META after their name and allother non-SITS courses we namedwith NO MDS and these Moodlecourses receive different info at thetop of their pages.
  • 23. EXPECT TO ACHIEVEMoodle - uniform information - Assignment Brief To provide consistent information about assessment we will upload an assignment brief to every Moodle course. These will present the information in a uniform way and in the same place on each Moodle course. This is different to information in the MDS as it is specific to the instance of the module – for example the deadlines will change each time the module runs. To collect this information we ask all module leaders to provide it and this process has involved a lot of negotiation and explanations as to why it is necessary but we have now got a form (see left) that is being trailed this semester. This is used whether the module uses ES or not.
  • 24. EXPECT TO ACHIEVEMoodle Assignment info. If, when completing the Assignment Brief form , the module leader says Electronic Submission is used, he/she completes this Moodle Assignment form to inform the creation of the Moodle Assignment. All assignments are created automatically with defaults so this info is only used to edit the assignments once created and then only if a default is not to be used.
  • 25. EXPECT TO ACHIEVEExamples of adapting policies andprocedures to the technology• Text box feedback. (Tutors must provide comments and a grade for students to see response files.)• Separate Late assignments (because Moodle doesn’t allow 2 deadlines nor can you restrict access by the hour/minute in Restrict Access feature)• Audio feedback process altered in Moodle 2.0 (you cannot upload a file to a folder and embed a player. You need to attach audio file as a response file. SoundCloud may be a solution for others who do not need feedback file on their own server).• 12 hr clock (cannot be altered to 24h – issue with noon/midnight)• Moderators and External examiners now access all submissions• External Examiners needed login ID (we have single sign-on)• Opportunity to redesign the exisiting A4 paper feedback form.
  • 26. EXPECT TO ACHIEVEMoodle – test on each upgrade The submission process is a critical process. Be careful when upgrading Moodle to ensure that it all works after the upgrade. Recently we upgraded to 2.2.2 and saw this issue. ‘No attempts’ is recorded even with a submission. It affects students and tutors. A patch is available but it reminds one to test it.
  • 27. EXPECT TO ACHIEVEMoodle – MaharaIn MoodleMoot 2012 I had notime to talk about Mahoodlebut we are also introducingthis integration from Sept2012.
  • 28. EXPECT TO ACHIEVEBob Ridge-Stearn = @BobRidgeStearn = Bob.Ridge-Stearn@Newman.ac.uk

×