Generally, I would advise not to use Moodle for either content management or student administration.
Leaving the content management piece aside for now (as I’m sure that will produce some howls of protest…), let’s consider what a typical training or learning & development organisation needs to do.
Any organisation needs to know who their customers are and what they are buying or using. Clever analytics will help the organisation to match new &existing customers to new & existing products in order to grow further.
Administration is the process of ensuring the right people get the right information at the right time, with the minimal amount of wasted activity for all involved.
At the heart of any L&Dorganisation is the “delivery” of learning, whether that’s events, materials or activities.
People will often need support, especially when there are complex administration processes, assessments or technology involved. It’s important to ensure that those support requests are met efficiently and effectively, and then to learn from them to improve communication and processes in the future.
By pulling together data from across the different parts of the organisation it’s possible to provide up-to-date information to both the learner and the organisation’s teams – to help them make decisions and improvements.
When you look in more detail at how these building blocks work together, it shows some fairly complex process flows:
Moodle is great at the Learning Delivery part of the puzzle. But ask anyone who’s tried to use Moodle on its own to run an L&Dorganisation and they’ll tell you horror stories of multiple spreadsheets, CSV files and complex mail merges.
In schools and colleges there are a few, high-powered Student Information Systems, like Capita’s Unit-E, and Tribal’s SITS, but these will be overkill for many of the adult learning contexts where Moodle is found.
CourseCRM connects Moodle with its equivalent in the Customer Relationship Management world: SugarCRM (you might want to use SuiteCRM instead – which is SugarCRM with a lot of additional functionality, especially around reporting, in a neat, easily upgradeable package).
It pulls as much data as it can out of Moodle (using a clever web-service, with a built in queuing system – which is important to ensure no data is missed) and aggregates it into SugarCRM.
This allows the admin team to easily find out what is happening with their learners.
This data can then be used alongside SugarCRM’s ticketing and sales process systems in order to provide an all-round picture of your communications with your students.
From within the CRM, an administrator could:
Using data available in the CRM, the administrator can now build reports, such as:
The bit that’s missing, at the moment, is the administration piece, where you organise student into courses, manage joining instructions, sort out tutors etc, and then push all that data into Moodle. With small student numbers that’s not a problem. But once you start getting into complex scenarios or large student numbers, that can become quite a major headache.
In a recent project, where I had to organise dozens of students into groups within multiple courses, I ended up writing a Python script to merge the list of students with the list of groups to create a massive CSV file for importing into Moodle. This wasn’t ideal, especially as it needed to be done for every intake. And just moving a student from one group to another involved many operations – in multiple courses.
What CourseCRM does, it does extremely well. So, if you’re looking for a way to efficiently support and track students and their courses, then you should consider CourseCRM.
My hope is that they’ll extend the functionality so that SugarCRM can also be the place where the administration can happen.
Posted: 14 November 2014