Forum Discussion
How to Chunk a Loooong Rise Course
Hi Everyone,
Question...we do an Annual Education push for all our staff; and as it contains the yearly compliance courses, etc., it is a very long course. We have already broken it into chunks using Rise, but it still runs as one long course.
The issue we are having is in our LMS - which has never been known to do bookmarks right when users need to stop and start. And users are finding when they need to leave the course and then return, they need to go thru the entire course again, as the LMS didn't bookmark. In addition, the course has just one place where it has users branch off based on their job titles.
Our LMS will let us know larger courses (we use Oracle, so they're called Specializations) where several courses make up the Specialization, but again, with that branching scenario, it makes it touch to create separate courses to fit neatly into a Specialization.
Anyone else do courses that branch and would otherwise be very long if you didn't use the approach you've learned to use? If so, can you share? Thanks so much!
4 Replies
Are you using SCORM 1.2 in your LMS for this? It has a 4096 character limit for suspend data so for a very long course that is the likely cause...
YES!!! We did use 1.2 when we saved it. Would you suggest we use 2004 instead?
The suspend data cap for 2004 is 64000 so if your LMS supports it that might be a fix that works for you
We run an annual compliance push the same way, and the thing that finally killed our bookmarking headaches was exactly what you're circling: stop shipping it as one big course.
We split the push into one short module per topic (most run 10-15 minutes), each with its own completion, and bundle them as a learning path in the LMS. When a module is short enough to finish in one sitting, resume stops mattering - nobody needs a bookmark for a 12-minute course.
For the job-title branch: we pulled that logic out of the course entirely. One tiny "start here" module tells each role which modules to complete, and the LMS assigns the right set per role. The branching lives in the LMS, not the course, so every module stays clean and standalone.
It's a bit more publishing overhead up front, but the tracking gets way more honest - you can see exactly which topic people stall on instead of one giant "in progress" bucket.
