I would like to update an already existing (as a SCORM) exported Articulate module in our Learning Management System (ILIAS). I also want to keep the current learning-progresses of the Users on the earlier mentioned ILIAS-System. According to ILIAS (https://docu.ilias.de/goto_docu_pg_45448_3052.html) the structure of the new edited learning module has have the same structure, than the original SCORM-file. Because of this we think, the imsmanifest.xml has to be identical to the old one. Is there any other possibility to modify and edit things in a storyline file (for example adding PNGs) without getting a conflict with imsmanifest.xml when uploading the new scorm module?
My experience is that even the smallest changes (although some small text changes will be possible) will make the resume data unreadable, all users who have completed should be retained by your LMS but most of those in progress will need to start again.
Phil's spot on about the resume data - when you update (overwrite) 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. They'll start over at the first slide in the updated course.
Folks in the community may have ideas on how to edit that published output to ensure it's the same course for learners to access, but keep the resume/progress piece in mind too!
We are experiencing the same issue with the ILIAS LMS. We wanted to insert the permanent link leading direcly to the module in one of the slides so the learner can share it with others.
We uploaded the module to the LMS, generated the link, copied and pasted onto the slide, then published the SCORM file again. However, an error message popped up when we clicked the button “Upload a new version”, which read “Incompatible module! Please make sure imsmmanifest.xml is not changed.”
We haven’t found the soulution yet. I guess we will insert the link to the platform instead.
The new output will be treated as a new copy or version of the course, and it will have a new identifier. We recommend connecting with the ILIAS team for any tips on overwriting content.
Did anyone manage to resolve this? We also use Ilias - and the ability to update SCORM modules without having to upload new ones (and hide the old ones to keep the user data) would be useful
7 Replies
My experience is that even the smallest changes (although some small text changes will be possible) will make the resume data unreadable, all users who have completed should be retained by your LMS but most of those in progress will need to start again.
Hi Ulla,
Phil's spot on about the resume data - when you update (overwrite) 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. They'll start over at the first slide in the updated course.
Folks in the community may have ideas on how to edit that published output to ensure it's the same course for learners to access, but keep the resume/progress piece in mind too!
Following.
We are experiencing the same issue with the ILIAS LMS. We wanted to insert the permanent link leading direcly to the module in one of the slides so the learner can share it with others.
We uploaded the module to the LMS, generated the link, copied and pasted onto the slide, then published the SCORM file again. However, an error message popped up when we clicked the button “Upload a new version”, which read “Incompatible module! Please make sure imsmmanifest.xml is not changed.”
We haven’t found the soulution yet. I guess we will insert the link to the platform instead.
Hello there, Monica!
The new output will be treated as a new copy or version of the course, and it will have a new identifier. We recommend connecting with the ILIAS team for any tips on overwriting content.
Note: Keep the disclaimer Ashley shared above in mind when overwriting existing course files.
Our Engineers can also step in! Click here to open a private case, where they'll share the next step.
Did anyone manage to resolve this? We also use Ilias - and the ability to update SCORM modules without having to upload new ones (and hide the old ones to keep the user data) would be useful
- when I said useful - for our new strategy, it will be essential to be able to upload new versions of SCORM files to ilias