Relaxing identifier constraints for SCORM packages
We have relaxed the constraints for SCORM packages, which previously were required to have unique identifiers and versions. Administrators can now:
- Upload multiple SCORM packages with the same identifier
- Replace SCORM packages with replacement packages with different identifiers and version numbers
NOTE: Administrators are responsible for ensuring that they do not duplicate courses, or replace the wrong course by mistake. If an administrator were to make a mistake, Agylia will not be able to assist with rolling back to a previous version.
To reduce the risks associated with replacing the wrong course, we recommend that administrators download a copy of the existing item before performing a replace operation. In the event that the wrong course is used as a replacement, the administrator will then be able to immediately perform a further replace operation, using the downloaded package.
We continue to recommend that replace operations are only performed for minor updates to course packages. This is to ensure that users who have already started the course, do not end up in a corrupt state, if the existing suspend state information does not function correctly with the updated course.
No changes are planned to the handling of TinCan courses, which will continue to require a unique identifier.
Various bug fixes.
Please sign in to leave a comment.