Forum Discussion
How do you handle content delivery?
Thanks for the reply. The admin access is interesting - a few clients have offered that too. My hesitation is practical more than anything - I'm now responsible for whatever happens in their LMS while I'm in there. And I'm still dependent on them setting it up, maintaining my access, all of that. Mostly though, even when I do get in and push the update, I keep coming up against the issue of learners who were mid-course potentially losing their progress and having to restart. That's the bit I can't seem to solve. Have you hit that one?
Hi Smitosco!
I understand. Updating a SCORM can be risky, so we keep the process simple. I have access to the Test and Production environments and I manage the SCORM uploads directly. Our process works like this:
-
One month before the update, we add a short notice to the course so staff know they must finish it before the set date, otherwise they will need to start again.
-
The new SCORM package is fully tested in the Test environment, and we use a clear naming convention for all SCORM files.
-
The course is temporarily removed from Production while the SCORM is replaced.
-
Once updated and tested, the course is returned to Production. Managers will receive an email.
I hope this helps.
Chela
To echo what ChelaPortugal said in point number 1 - I've had similar situations when I worked for a large corporation. A course assigned to hundreds of users with varying "due" dates (based on when they joined the company, when they were added to a curriculum etc) may need an update. In those cases, I would communicate 1 month, 2 weeks, and 1 week in advance of the update to everyone who had it assigned to them, warning them that it was going to be updated on X date, and if they didn't complete the current assignment before then, they may lose their progress.
