Course Versioning: What is the best practice?
Scenario: We have a SCORM course, “Cybersecurity Awareness”. We update the course annually so in our old LMS we would publish a “Cybersecurity Awareness 2017”, “Cybersecurity Awareness 2018”, “Cybersecurity Awareness 2019” and so on. This way on the report we would know what version of the course the learner completed.
Options
- Publish one SCORM course, “Cybersecurity Awareness” and annually update the SCORM package and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
- Publish one SCORM course and annually change the title to reflect version changes, “Cybersecurity Awareness 2018.1” and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
- Publish a new SCORM course for every version “Cybersecurity Awareness 2020”, “Cybersecurity Awareness 2021”, “Cybersecurity Awareness 2022”
- SOME OTHER SCHEME
Hi Will Baldwin,
We typically follow Option #3. For example, we have a quarterly course that's assigned out though ours is built natively in Bridge. I just duplicate the course, make any necessary edits, and then publish it as 2019 Q3 blah blah. This way a learner could be potentially enrolled in all three quarters of the course.
We use this method for several reasons.
We don't enroll new hires in previous versions of the course. I think this is important to note because you could have a learner be enrolled in all 3 versions at the same time. There is a supplementary course they receive that brings them up to speed and then the quarterly release everyone gets at the same time without a rolling enrollment. We use a CSV enrollment when we release it.
I hope this helps,
Heidi