Forum Discussion
Current Version Indicator Published
Has there ever been thought given to visually displaying the Current Version (date) within the published course. This would be a Rise feature that you toggle on/off similar to "Author", for example. The published version would be display somewhere on the published course, very small print in a corner so that developers can easily and quickly identify which version was published and if its the correct one. This helps with addressing feedback, or simply to ensure that the loaded file in the LMS system is correct.
6 Replies
Versioning is always a good thing, definitely. I expect the challenge to be overcome would be less how to insert such text (which can be done manually of course with a block) and more how the course would know which version to apply. There's not a standard way to version best I know, and one person's 1.3.2 might be another person's 2.0. There's definitely an opportunity for teams to implement such a method themselves.
I am assuming that only one copy of the course is being updated at any given time, and not a duplicate copy. So, yes, the versioning would change in that scenario. We only work off of the original course and make updates to it. No duplicating.
There wouldn't need to be duplicates for there to be different ways to version. For a lot people, any updated version just gets the next whole number up, but many bigger projects (and indeed in a lot of software development), the periods are used to identify the kinds of changes. In version a.b.c., a is used to qualify major feature or updates such that may break backward compatibility, b is used for smaller features and upgrades, and c is used for patches or bug fixes. An entirely new Code of Conduct eLearning may go from version 2 to version 3, but if there was a problem with a slide transition and I fixed it so the course works normally, that might mean the version goes from 2 to 2.0.1.
This is why Rise can't assume how I and others want to version content. If it assumes and says something is version 3 when I don't want it to be, that's a problem.
We use Rise for some customer-facing content and we place it in the course description at the end (Version: 2026.02.05, or Last Revised: 2/5/2026 for example)
We do pretty much the same thing. We have two dates: date last edited, and the date last published.
