- To prevent this from happening, the CANVAS LMS (automatically) sandboxes each SCORM module outside of the course in a separate repository. When a course is copied from one shell to another, the SCORM modules are not copied.
- This means that after a course copy, such as during the CANVAS migration, SCORM modules would need to be (manually) re-deployed to the new copy.
My institution is concerned about the time this process will require for faculty. Is this problem (SCORM modules need to be manually copied to the CANVAS course copy)... still actually a problem? if yes, does anybody have a work around?