Content Collection updates
This release includes enhancements to improve the performance and usability of the Content Collection.
Files uploaded as part of a SCORM package are now saved in a Content Collection folder (/internal/courses/<courseID>/content/<contentID>) rather than the Local/Shared File System. When a client system upgrades to this release, server startup invokes a background migration task to move all existing SCORM files from Local/Shared File System to Content Collection. Several optimizations have been added to minimize the performance impact and memory usage for this task and it should be virtually transparent for users.
When versioned files are imported/restored as part of course import/restore, the version number (of the file in the source course) is appended at the end of the file name so that users can differentiate which version it is. For example, if version 1 and 2 of a file named "geography.html" are imported, the new files will be named "geography_v1.html" and "geography_v2.html", respectively.