How are you managing course versions/versioning in Docebo? Share your best practices and lessons learned here.
Sign up for Docebo Community
Already have an account? Login
Log in to Docebo Community
Enter your email address or username and password below to log in to Docebo Community. No account yet? Create an account
Docebo Employee Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Naming conventions help to differentiate (typically by adding a year or date to it) the date that it was released that it was relevant for. For example a compliance course for this year may be Annual Compliance Training 2022.
Lessons learned btw? You may want to develop a policy surrounding a publishing or curation cycle for courses. Stale content is a serious distractor to learners and reinforces tired LMS syndrome…so you express to your teams:
A = Audience
CT = Country code, two letter, international standards
1 = Generation, which we define as “significant, more than version, changes”
_ = Segment break
xxxx = Course number. Certain groups like “New Hire” begin with 1; other groups use different numbers. Course number actually remains the same thru different countries or languages if the content is largely the same, and thru generational changes too. This helps with sorting.
_ = Segment break
LN = Language, one or two characters, and try to use international standards.
We use the same schema for our catalogs and learning plans, with some minor modifications
The one drawback I’ve found with using codes is that they generally aren’t searchable by the learner. The only way I found for a learner to use a course number is to add it into the Title of the course. Unfortunately, this made the course tiles look very messy, so we’ve had to made course codes an “admin only” thing, which really really limits their usefulness.
I like the approaches from everyone. We follow a similar unique course code that is filtered mainly by admins and not our external users. Because of our current practices we are beginning to grow our courses at an alarming rate. I am curious how people are dealing with versioning of materials and test instead of creating a whole new course to be the versioning. As a company we are moving to a more aggressive delivery of product which will require us to offer updated training more regularly than we can sustain by duplicating courses with new codes to work as our versioning. Any ideas?
We use a similar course code classification structure for defining the category, course sequence, audience, and language. However, we don't number the version of each course. Versions of a course are limited to the audience or the language. If we are versioning the course content, we push the training material that is changing to the Central Repository and use the versioning there to track the update. This method keeps all the courses in our library evergreen and insures the learner always has the latest version.
I also described our process for pruning old courses in an earlier discussion: https://community.docebo.com/let-s-talk-shop-42/how-do-you-decide-what-to-prune-4169?postid=17966#post17966
Briefly, we divide training into "reference" courses that we always keep up to date and "current awareness" courses that cover what is new. The current awareness courses are never updated (unless there was an error in the original material) and are unpublished after about one year.
In addition, we created two course additional fields, Released and Updated, to keep track of when the course was first published and when it was last updated.
I am curious how people are dealing with versioning of materials and test instead of creating a whole new course to be the versioning.
There are two ways that I can understand your question
Here is some thing I DON’T do:
Some great ideas. When updating a course version, my understanding it that a user who is in-progress for that course will have to start over. Does anyone have experience with this? It seems like users would get upset at having to start a course over.