Riverina Institute VLE- a journey of integration with Moodle
• 1. VLE - Integration with Moodle
• 2. My Journey to MEDMOOT13
• 3. Using Education to grow opportunities Gundagai
• 4. TAFENSW Riverina Institute
• 5. Dealing with the challenges of distance and population
• 6. Integration – An elusive pot of GOLD
• 7. Brainstorming!
• 8. Brainstorming!
• 9. An integrated Virtual Learning Environment (VLE)
• 10. Moodle as an integration tool
• 11. TAFE NSW Riverina Institute Learning Environment
• 12. > Autonomy - Individualism > Creativity > Brilliance > Genius > CHAOS!
• 13. CREATIVE HARMONY!
• 14. Systemic development
• 15. LMS Structural Models – Finding Balance
• 16. Structure & Templates
• 17. Unit Based Model 1:Many Many:Many Modular design
• 18. Unit Based Model - Effective clustering
• 19. Cohort – Unit Model
• 20. Faculty Landing Pages
• 21. Cohort Landing Pages
• 22. STAFF ROLES AND FUNCTIONS
• 23. CAPABILITY DEVELOPMENT
• 24. Automation
• 25. Bulk course upload •Import groups -
• 26. Import groups
• 27. Course Application Process
• 28. Moodle Backups
• 29. • Templates • Clustering • Cohorts • Groups •
• 30. > Don’t oversimplify! Kaizen could be small steps in the wrong direction!
31. Course Application Process
> Landing Page(s)
> Cohort Site
> Units of competence or clusters of units
> Course Metadata to link to
– Learner Analytics
– Business Metrics
LandingPageSiteApplication-RiverinaInstituteShouldthisbe atextfield?Oromitted
*Application
Completedby
*LandingPage Full
Name
*Summary ProgramArea Campus *LandingPage Type orTemplate *LandingPage Site
Coordinator
*QualityAssurer Teacher(s) NonEditingTeachers *StartDate *EndDate *EstimatedArchive Date *Linkingto? Comments
Emailofperson
completingthis form
egICTTeachingDept Providea short1-2linesummaryofsitepurpose.
This informationis viewablebyusers browsingthe
Moodleserver
selecttherelevantprogramarea for
this site
ifapplicable eg.Business Line,METline,programarea,domain
area (sub-program)
DECusernameofwhois goingto
editormanagethis sitespace-can
bemorethanoneteacher
DECusernameofstaff
memberthatwillbe
responsibleforQA
checkofthis siteprior
toreleasetostudents
DECusername (comma
separated)ofstaffwho need
"teacher" role and therefore
rightsto editsite content
addtheDECusername(comma
separated)ofstafftobeadded
tothesiteinthenon-editing
teacherrole
pleasespecify
expecteddatesitewill
needtogoliveor
acceptenrolments
mm/dd/yyyy
entertheknownorestimated
enddatemm/dd/yyyyOR
enterrolling-enrollments
enddatewhensitecanbe
backedupforarchivingand
thendeleted
Whatotherlandingpageor
cohortsites willthis landing
pagelinkto? Insertsite
shortnameorURLforeachsite
tobelinkedtoseparatedby
commas
Ifyouhaveused'other'inanyfieldorwouldliketoadd
relevantnotes pleaseenterthemhere
32. Moodle Backups
> Summary
> ==================================================
> Courses: 914
> OK: 79
> Skipped: 540
> Error: 295
> Unfinished: 0
> Warning: 0
>
> Some of your courses weren't saved!!
>
> Please take a look at your backup logs:
>
> We need partial Moodle site resets
> Structure and clustering matters!
Error: 295!
33. • Templates
• Clustering
• Cohorts
• Groups
• User
Engagement
Scope and
Design• Planning
• Resources
Enrolments• Courses
• Skills sets
Roll books
• Class Groups
The missing link?
Import
groups
Bulk
Course
Upload
Learner
Analytics
34. > Don’t oversimplify! Kaizen could be small steps
in the wrong direction!
> Virtual Learning Environments VLE
> ADVANCED MOODLE SKILLS
– Automate creation of courses
– Automate addition of students
into cohorts, groups, groupings
> SYSTEMS
– Systems to talk together (Advertising,
enrolment, Moodle and ePortfolio’s)
> PLANNING
– Start planning earlier and in more detail
> Team based development
> CULTURE
– Sharing, planning and delegation for
accountability
THE CHALLENGES
Notas del editor
Re: Automatic Moodle Back ups failingby Glen BYRAM - Monday, 16 September 2013, 12:32 PMI did some testing, and can confirm that Moodle 2.x (up to 2.4) is very slack with its housekeeping. Uploaded files (e.g. for assignments) STAY in the course and are included in the backup even when the students who uploaded them are un-enrolled. AND if the student is un-enrolled, the uploads don't show when viewing/grading assignments. (They appear again if the students are re-enrolled). So, a course can be left full of debris from past students, with no clear way of finding the uploaded files once the uploaders are un-enrolled.Maybe I could cook up a plugin that runs a partial "reset": delete all data in a course that belonged to students that are no longer enrolled. But it seems that without supplementing Moodle's base code, any course with "continual enrolments" that accepts student uploads (and maybe forum posts, adding to a database activity, etc.) will continue to grow in size ad infinitum. The only way I can see to avoid this with out-of-the-box Moodle is: a) don't have continual enrolments in the same course, i.e. clone a new course every so often, b) don't allow uploads into Moodle, i.e. use an external repository like Mahara (although this will still have continually accruing links to the external site, so course data size will still grow, but slower.)BTW, when I delete a whole course the student files stay in the "Moodledata" folder until the scheduled "cron job" runs. But files I uploaded as resources stay there. So this is another weakness in Moodle's housekeeping. (Moodle v2.4.3).Show parent | ReplySee this post in context