We're looking into using MNet as a possible architecture solution for allowing our centrally provided LMS to be broken down into multiple instances. The reason we're looking at this is to allow more granular administrative control over certain groups of courses. For instance to allow Faculty X to be able to limit or add plug-ins or different system-wide defaults to only those courses. Also this would allow us to connect and integrate currently running Moodle systems on campus.
I'm wondering if anyone has any experience with this type of setup? What were the benefits and/or drawbacks?
Just a couple quick thoughts so far (perhaps there are easy ways around some of these?):
- Only a single role can be set for remote enrolment. (eg. either Teachers or Students can be remotely enrolled in a course but not both)
- MNet doesn't allow creation of courses on remote systems, so a centralized course creation system could be problematic unless that system has integration with each and every instance. (
- By default theme ''home'' buttons return to the home of the local instance where only the local courses are listed. So it seems, short of having a single/few custom themes which force the home to return to the 'central' instance, where all enrolled courses are listed this could be a problem.
- No cascading permission/defaults/settings to other instances. So if there were a large number of instances a single global change would need to be made separately on all of them.
What are your thoughts?