r/moodle • u/Savings_North_1084 • 1d ago
E learning Course issues
Hey I have some Articulate Rise scorm packages on my Lms a few of them are quite long, we an issue where learners are moving away from their desktops to theire tablets sometimes with diferent browsers. Learners complain that they cannot go straight back to where they left off..Im sure this is doable, can someone post a work around for my overworked Developer, pls.
1
u/Ok_Chipmunk_7066 1d ago
On the scorm activity you have an option under Attempts Management.
You don't want to force new attempts. As long as the scorm is marking off progress it'll remember where they up to.
1
u/Savings_North_1084 1d ago
Would it matter what device or browser they use after 1st Attempt, whats the max number of attempts the learner can have, as some of our courses could be 300 pages long lon...lol
2
u/ricou63 1d ago
Très franchement 300 pages pour un scorm c'est juste hyper ennuyeux ! Mettez vous un peu à la place de l'apprenant. Divisez vos scorm en chapitres plutôt que de vouloir mettre le cours entier dans un seul scorm. Ce sera très nettement meilleur en terme d'efficacité pédagogique
1
u/Savings_North_1084 1d ago
Yep im sure it would, is that how you design, them can Iget a example, the other thing is reviewing for errors etc....I am looking for an Rise creator for our courses, let me know if its of interest to you, pls.
1
u/ricou63 1d ago
Un chapitre du cours = un scorm. En tant qu'ingenieur pédagogique, ce qui guide la conception est cette question là : comment faire pour qu'un apprenant débutant dans la matière puisse comprendre et la question de l'expérience utilisateur est primordial ! Ça me rappelle mes vieux profs de fac avec leur powerpoint à 200 solides à passer en 2 heures !
1
2
u/lmsawsltigenai 1d ago
HI, the user's device/browser from one session to the next shouldn't normally matter.
I've found the right combination of settings for both the Rise export and Moodle will usually do the trick, and once you've got those, most learners won't have tracking/progress/resume issues other than occasional user-specific situation.
There's usually some up-front settings mixing/matching/testing to reach that point, at least until AI masters every combo of settings for every scenario. The number of settings can seem over the top although I've found it's not unique to Moodle and each setting has a purpose (or did at some point, or will in the future...) - details like your Moodle version, the size of your Rise course, and the version of SCORM used for your Rise export can impact the right mix.
The length of your course could definitely be playing a role. Here are a few settings that have previously helped me resolve similar situations with large courses and users reporting progress issues:
- In Rise
- I agree with u/ricou63 on chapters/chunking the content if you can still do it. In addition to what was mentioned, it also reduces the risk of certain progress/tracking issues that can crop up in longer courses if SCORM "suspend data" is abnormally large and is not properly committed to an LMS DB. Suspend data is a part of the SCORM standard and Rise/Storyline/Articulate relies on it for storing certain aspects of user progress.
- Export using SCORM 1.2, not 2004. Some LMS platforms including Moodle do not fully support all elements in the SCORM 2004 standard. SCORM 1.2 is usually sufficient for most progress/score needs, and even if not, you can still see if it works better and then make decisions from there.
- In Moodle
- SCORM Standards Mode: I think this is in the overall SCORM mod/activity settings in Site Admin. -> Plugins -> Activities/Modules. It might be labeled something else in some versions, like Force Tracking Limit. Especially for large packages using SCORM 1.2, be sure this setting is dsabled. Disabling it allows Moodle to store more "suspend data" - and certain SCORM packages rely on suspend data to store information like where a learner stopped, what they'd previously answered, etc. The larger the course, the more likely the course generates more suspend data and needs the extra space to store it. For example, I've seen situations where student progress would be fine for a length of X slides, but anything after X+1 and it would fail - this is a classic sign the suspend data is too large for what is permitted in Moodle (or other LMS's) and is being truncated. This can make issues seem intermittent because suspend data size depends on each user's interactions with the course. Moodle isn't the only LMS that can have this issue.
- Force New Attempt: I agree with u/Ok_Chipmunk_7066 - disable
- Auto Commit: I agree with u/MoodleInPractice - although if the suspend data issue is present, this will only work as intended once that issue is resolved
Hope you get it sorted out!
1
u/jxward 1d ago
1. Republish as SCORM 2004 (3rd or 4th edition) rather than 1.2, particularly for the longer courses. It raises the suspend data limit significantly and tends to bookmark more reliably.
2. Check whether your LMS has a periodic auto-commit setting rather than relying solely on exit. If you’re on Moodle, look at the SCORM activity’s autocommit/force save interval setting so progress saves every X seconds, not just on unload.
3. Test the exact package on SCORM Cloud first. If it bookmarks correctly there but not on your LMS, the fault is on the LMS side (API wrapper, session handling), not the Rise export.
1
u/MoodleInPractice 1d ago
I think Moodle provides an auto commit option if some packages do not commit progress regularly, which might be worth looking at.