How to handle versioning of a SCORM file-3 - Hiding the old, showing the new

Video Transcription

Video Summary

Updating a SCORM file without preserving progress resets user data, including reports. Changes may vary in compatibility impact, with minor edits often safe. To maintain previous data, create a new version while hiding the old one with an "eye" icon. This way, users won't lose progress, but admins can access both versions. Refreshing the learner site reveals the new SCORM file, keeping the previous version hidden from users. This method enables the retention of data while introducing new content for users and admins, achieving the best of both worlds.

Meta Tag

Creation Year 2024

Keywords

SCORM file

progress

user data

compatibility impact

version control

KGConcept: SCORM File (10)

KGConcept: Learner Progress (9)

KGConcept: Reporting (9)

KGConcept: Backward Compatibility (8)

KGConcept: Content Change (7)

KGConcept: Versioning (8)

KGConcept: SCORM Version (7)

KGConcept: Historical Completion Data (8)

KGConcept: Learner Report (8)

KGConcept: Admin access (6)