Forum Discussion
Updating SCORM packages in Moodle
Hello,
We just updated all nine modules of one of our courses and any student who had started an attempt but did not finish he module could no longer access that module. The work-around was admin...
in storyline are updates of existing courses with preservation of learner status (out of the box) not possible
what happens in storyline
- publish a course - an internal resume ID is generated (e.g. abcde192)
- course is upladed and set up in the lms
- learner A starts the course -> resume info is send to the LMS with the id "abcde192"
- learner A stops the course
- learner A starts the course again, the LMS sends the old resume infos (with the id "abcde192")
- resume is working
now modify the original course (e.g. change one comma):
- publish the course again -> a new ID is generated (eg. efgh456)
- course is upladed as update to lms (all learner data - with the original iD - is preserved)
- learner A start the course, the LMS sends the old resume infos (with the id "abcde192")
- now the IDs of the course variantes are not matching anymore (abcde192 <-> efgh456)
- storyline decides that it will not use the old resume values and starts the course from beginning without any old data
- learner A interrupts his new try, the data wit id efgh456 is send to the lms
- resume is possible (until the next updated upload of the course)
result: don't update a course, if it is not really necessary
(same happens with publish to web - data are not stored in lms, but in the local browser)
