Two process updates for my high maintenance moodle customer

Enrollment statuses in moodle

My customer introduced a new process this fall for enrollments for his students.  He is using an external system called Genius.  This system allows his customers to create their own accounts and self enroll into courses offered.  This is a good system.  But, it does not do everything it should.  For example.  The integration with moodle is handled by another DB that we created on the moodle side, called geniusIntegration (GI).  It consists of only two tables, users and enrollments.  Genius pushes data into the GI DB when new accounts and enrollments are made.  Nice.  Then moodle consumes from the GI DB - for new accounts and enrollments.  Great.  Except - when my customer changes the status of an enrollment in Genius to completed or dropped,  the information does not make its way to the GI DB.   This probably would not matter too much if we did not have a concept of the enrollment status in moodle.  I introduced this concept a couple years ago along with a report that showed the enrollments in moodle as either active, completed or dropped.  My customer is still in the habit of going into moodle and changing the status of the enrollments.  My customer likes this process because it allows teachers in moodle to see the status of students enrolled in their courses.  A snapshot of the custom Enrollment report I build in moodle that shows some enrollment data.

These students are all active 'A' - which is a link to a simple form that allows the update to the status.

Snapshot of update form

I tweaked the standard moodle grade user report - adding the enrollment status and a dropdown menu so the teachers could see the grades of any student in the course.

Notice the letter to the left of the student names.

BOTTOM line for me - If I keep this report around - and the concept of an enrollment status in moodle - then I have to MANUALLY remove enrollments from the GI.enrollments table.  Mike will send me an email titled "UPDATED enrollments in Genius - REMOVE from GI.enrollments.

That is a conceptual mouth full.  Maybe I will simply remove the report and its concept, since they are now in Genius.  Makes me a little sad, as it is some programming that I had done and would then be retired.

NON student accounts must be manually created in moodle

SECOND issue - When new teachers are added to Genius - they do not push into moodle the way student accounts do.  Student accounts are automatically pushed into the GI.user table - where moodle consumes from and creates new accounts.  Genius does not push teacher or coach data into the GI.user table, only students.  As a result - we still have to manually create teacher accounts in moodle.

BOTTOM line for me - Mike will send me an email titled "New teachers added to Genius - Need to create in moodle.  Details from the Genius teacher account are 1) username, 2) password, 3) email.  They are used in the creation of the new account in moodle.  The account is also created with authentication type of manual - this allows the sign on from Genius to moodle.