New solution for viewing submitted student coursework for pertetuity

Thoughts around our newest model - solution for keeping submitted student work for perpetuity - which means forever....which is actually 5 more years - then I play to retire ;).

We are no longer relying on individual course backups.

We are instead relying on a complete DB restore with the following steps

Remote into the moodle server -

Drop the restored_student DB - then re-create it using UTF collation 8

Restore the DB from the F\dbbackups\archives folder

If I have to update the moodle code base - I will have to change the settings in the code (this should only need to be done once - not each time the DB is restored).

Check the restored_student external DB authentication parameters - it SHOULD BE CONSUMING from the DB on the server called perpetuity_geniusintegration.  This DB NEVER loses enrollments.  In fact enrollments are AUTOMATICALLY added to the  perpetuity_geniusintegration_enrollments table by a script that I will write that copy enrollments from the live geniusintegration table.  This is a must - since the enrollements must be in that table for our restored DB to show the student and their submitted work.  Logical.

Settings in moodle plugin external DB configuration

 

ALSO check the admin\ cron.php file in the restored_student code base, ensuring it is calling the correct windows .bat file that actually specifies the perpetuity_geniusintegration DB to consume from.