Slide Converter Versioning - How are you tracking versions?

Outside of Docebo ;).

Unfortunately - (IMHO) the system is mediocre with this at best. You can have multiple versions of training materials when you are doing SCORM uploads….but you then need to do imports of those uploads and choose to always version up instead of overwriting….which may not be a perfect fit for a change moving into a production level of a system.

I am not sure about the other flavors of content/training material….but SCORM supports what I described.

​@dklinger thanks for your response. I was hoping I was missing a step and it was possible in the system!

We have to have a very clear version control for our content, so for each new version/updated we update using the annual year to indicate which rev the content is. So for example, we have a 2023 HIPAA & Privacy, 2024 HIPAA & Privacy, and now a 2025 HIPAA & Privacy. 

This way we also have record of training for each version as well. 

I would also love to see a version control feature available!

Hope this helps! 

We use a course additional field (free text) to track dates and changes made to content and other settings. Sort of a timeline of course changes. It comes in very handy.

For content changes, we opt, in some cases, to maintain the old version as an unpublished learning object (to maintain tracking history where it applies, like tests) and only have the newest version published and available to users.

​@mmoore and ​@lrnlab thank you both for your suggestions and I can see the value in both ways.