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 support deleting any attempts.
For the users that did complete a module, the checkbox "Start a new attempt" appeared and if he checked that box, they could then access the module.
I am terrified of updating content if this is what I will need to do for any update.
FYI - I am downloading the modules as LMS SCORM 1.2 and then uploading them to Moodle. Should I be doing some differently?
Thank you for any insight you can provide.
Catia
When you update a Rise module the resume function will no longer work. This is the same for Storyline, but Storyline seems to be able to handle the wrong resume data better and doesn't hang.
thanks for your quick reply Phil. But do I understand it correctly that this is not due to the SCORM version.
Should we look at the option that Jürgen Schoenemeyer has given in his previous post?
Hi Catia,
Thanks for reaching out about this! I see you've opened a support case regarding the two issues you are having with your updated modules and are working with Fannie May. You are in good hands! If you have any questions about the case, please respond within the case via email.
if you create a new scorm package - or publish to web - storyline creates a new "resume id"
with this new package (new ID) the learner cannot resume the course (old ID)
-> update installed courses only if it's really needed
there are some tricks to work with this behavior
https://community.articulate.com/discussions/articulate-storyline/change-navigation-status-from-restricted-to-free-in-a-published-file-for-a-specific-userWe are working with Moodle through a third party and have updated the Rise modules. But our third party helpdesk answered that this is caused due to the use of SCORM 2004 and not SCORM 1.2. As Moodle does not support SCORM2004. Can you confirm that this is right?
Otherwise we have to advise our previous users to finish the old version. Add a new activity in Moodle with the new RISE module and some Users have to start all over.SCORM 2004 is not supported in Moodle. Parts of the API have been implemented, but others such as Navigation and Sequencing have not. Development on native SCORM 2004 support in Moodle has stopped. If you require a fully certified SCORM 2004 Player in Moodle, Rustici Software have a Moodle plugin which connects to their commercial SCORM Cloud service turning Moodle into a fully compliant SCORM 2004 LMS.
Good afternoon,
I have exactly the same problem as Catia, we are working on a fairly large project which works by modules (with many slides and audiovisual content) uploaded to an LMS platform. When any of the packages is updated, the progress of the same is erased having to start from scratch. In addition when the student or students make many attempts it crashes and remains in white screen, being the deletion of attempts the only option to solve it.
Is there any way to publish it or any option that we are not carrying out to be able to solve the error and not to happen again?
We have tried to change the package file imsmanifest.x.ml for the previous package but without any positive result.Thank you very much,
Best regards,
Hello Paz,
Happy to help out!
When you update existing course files in your LMS or web server, learners who previously started the course won't be able to resume where they left off. This is the expected behavior. See this article for more information.
As for the loading issue, can I ask how are you updating the package in your LMS? Does your LMS have a dedicated update button similar to the ones in the screenshot, or do you manually replace the files with the latest version yourself?
If you are using the update feature of your LMS, and your course is still not loading properly, open a case with our support team here so we can take a closer look at what's happening.
No we update the SCORM package RIse through the FTP server. The old package is then automatically deleted.
At building the course in Moodle, we use the activity SCORM, we upload the package through ftp server and then have to select link to file. After which we have to fill in some other settings, like appearance, availability, marks, attemps, etc. The other option make a copy, we should not use.
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)
> This is the expected behavior.
that means - never use Navigation "Locked", if it can happen to change the course later
Thanks for your feedback, I will share this with my colleagues
