- 1 - There is an external DB source for one of my moodle instances - it feeds a "external enrollment" DB that has an enrollment table with a SQL trigger. To push inserts in the table to a copy of the table. SQL trigger - smart - the right tool for the job. Analogous to using a power drill and precision bit for a job that requires it. I often say "get the right tool for the job. the right tool makes all the difference". A trigger that executes a SQL stored procedure is the right tool for this job.
- 2 - I went into a course from one of our 3rd party vendors and set some assignment properties. This course has alot of assignments, too many probably - but I am not removing things from the course without the understanding of the teacher - who can also do it, technically - her role has permissions. I should do this for her - as it is tedious and I could do en mass in the DB. I have a php scripting page that sets certain assignment properties in a course. I interpreted the teacher comments about the assignments - looked at the course and ran the script to set some things. Then I emailed the teacher and offered to remove some of the assignments from the course.
high level?
understand the problem
create a good solution
implement solution
notify concerned parties
- 3 - My customer asked me if he could take a look at a student who we had removed from the system about 3 months ago. I looked in the copy of the enrollment DB and saw the student in the table - then restored a copy of the DB from around the time he completed and there is was - the complete stats and work for that student - saved for perpetuity. I have a separate moodle instance that reads from the copy of the enrollments DB, naturally.
It was a day of 3 successes for common and important moodle tasks.
No comments:
Post a Comment