STEP ONE: Determine if Your eLearning Content is Compatible

STEP TWO: Prepare SCORM-conformant content file for upload

• Chrome
• Firefox
• IE/Edge

• There are several places which must not include any special characters (e.g. @, $, &, etc.) Note: Allowable characters are alphanumeric (A-Z and 0-9), hyphen (-), and underscore (_).
  • The course code in the LMS
  • The filename of the SCORM output .ZIP file
  • On rarer occasions, some areas within the authored content itself, including the titles and identifiers that may be part of the publishing settings. Depending on how the content is authored, it could pose a potential problem if they exist in quiz titles, question titles, answer choices, or any place where interactional and navigational data in the SCORM/XML files could be suspect.
• The eLearning authoring tool you use for zipping content can impact the folder structure and therefore the location of the SCORM XML manifest file. After your content is zipped, ensure that the "imsmanifest.xml" file is located in the root of the zipped file, not within any of the file's folders. The figure below shows an example of correct and incorrect placement of the manifest file.
  
  
  
  
• There is a SCORM file size limit of 180 MB. For files exceeding that size, you can contact Latitude ClientCare for an cost estimate to  have a developer upload one or more oversized courses.

STEP THREE: Course Catalog Entry and Content Deployment

1. Do NOT include any special characters (e.g. @, $, &, etc.) in the Course Code or Course Name fields. Use only alphanumeric, hyphen, or underscore characters.
2. In the Delivery Method field, select eLearning.
3. The Can Relaunch setting determines whether or not students can relaunch course content after achieving a completed status.
4. When the Add Course form is complete, click Add Course.
5. In the confirmation pop-up window, determine your next step from the following options:
   
   • Are Finished: Keeps you on the Details page of the new course and lets you continue editing. The “SCORM” tab will become available so that you can upload content.
   • Want to deploy content for this eLearning course: Directs you to the  “SCORM” tab.
   • Want to add another course: Directs you to a new Add Course form.
6. Navigate to the SCORM tab when you are ready to deploy content.
   
   
   
   
7. Click Choose File to upload the zipped SCORM file (size limit is 180 MB).
   
   • Note: When uploading files, be sure that the path name of the source file is less than 255 characters. File names exceeding that will be truncated and will fail to launch properly. To shorten a filename and path, save it to a folder higher in your directory structure. For instance, place it on your C:\ drive root directory, or create a C:\UPLOAD directory to which you can move the file.
8. Deployment Options
   
   • Full Package: Select this option if deploying content for the first time. You should also use this option when uploading content revisions that have fundamentally changed the nature of the course (e.g. addition/deletion of slide/video content, navigation, user interactions, scoring). Full Package is recommended even for updated content if there is any doubt about how the new information will overlay the old.
   • Partial Package: Select only if you are re-deploying content with minor changes that do not alter the overall course structure (e.g. static texts, colors, images). If after using Partial Package, you find that the course is not loading properly or is not behaving or scoring activities as expected, try reloading it as a Full Package.
   • Validate Sequencing: This field is provided for use when there are issues with course launch caused by lack of or incomplete sequencing produced in some authoring tools. By default, you do do not need to check this box. If you load the course and find that it launches with a blank course window, you can reload the SCORM package for the course and check this box, then see if it makes a difference. If there are still issues after validating sequencing, you can then contact Latitude ClientCare for further assistance.
9. Click Deploy and wait for the on-page notification that your content has been queued for deployment. This means that your file was successfully loaded to the LMS SCORM content server and is being processed.
   
   
   
   If the file fails to upload, it is usually because a) the ZIP file was larger than the allowed 180 MB size limit, b) special characters were found in the file name or key locations in the content, or c) the placement of the imsmanifest.xlm file in the zipped content is incorrect. Try loading a file at least twice before contacting the ClientCare team with questions.
10. Once this activity is confirmed, you can monitor the status of your deployment process via email, or from your LMS “Messages” page. A notification is sent once the content deployment process is complete, informing whether the attempt succeeded or failed.
11. Course Shell Configuration settings allow you to enable/disable tools that enhance presentation of each e-Learning course. Apply changes in real time by clicking Update Shell Configuration button, without the need to re-deploy your SCORM content. Set default configuration or brand these features from your Site Management > LMS Information page. Learn more: LMS Information and Portal Configuration.
    
    • Enable Navigation: Disabled by default. When enabled, this responsive menu opens collapsed by default and  provides one-click navigation between each SCO (shareable content object) within the course, with the option to expand to full screen. Note: We strongly recommend leaving this unchecked, as it is by default. It is only relevant for some clients using specifically-developed Multi-SCO courses, Most instructional designers include navigation menus or buttons directly in the course.
      
      
      
      
    • Enable System Checker: Disabled by default. When enabled, this tool allows LMS Administrators to define system requirements for their eLearning content, such as supported devices, operating systems, browsers, cookies, JavaScript. On course launch, the LMS will check the accessing device and inform students whether or not the device and its configuration meets defined requirements. Either way, students are able to click “Continue” and launch SCORM content.
      
      
      
      

STEP FOUR: Test Launch the Course and Debug Issues

Once eLearning content has been deployed, return to the course SCORM tab to view the SCO list, which indicates contents and manifest information of the SCORM content currently deployed. Click Test Launch to preview your content and better understand how it will present to LMS users.



If you are able to upload/deploy content to the LMS successfully, but still encounter issues launching, navigating, scoring, or completing the course, we also provide a debugging tool on the SCORM tab. Test launch again with the Show Debug Info box checked, and try troubleshooting errors with your course content support team before submitting a request to Latitude Support.

Note: If you have re-deployed a SCORM package, overwriting old content with a Full Package or Partial Package, you must clear your browser cache and cookies before test launching to see new course content. Failure to do so may cause cached content from the old version’s browser cookies to display old information, even though new content is deployed.

If you have ever launched a previous version of the same course, the system will have stored CMI bookmark data that may affect the launch experience. Click Clear My Local Data to ensure that all of your CMI data related to the old SCORM file is cleared from the database. Then test launch the new content.

THE USER EXPERIENCE: Uploading New Content to an Existing Course

• Users who have never enrolled in the course or have enrolled but never launched will get the new content with no issues.
• Users who have launched the course with the older content may have bookmarking and SCORM CMI data associated with the original launch. It is possible that relaunching the course with new content may lead to launch issues, including 102 Sequencing errors. This is because the LMS is unable to match where they left off in the original content now that new content is in place. LatitudeLearning ClientCare can clear CMI data associated with 102 Sequencing errors if provided the username and course code. Canceling the enrollment and re-enrolling will also fix the issue.
• If concerns exist about those in-progress being impacted, consider creating a new course and retiring the old course. This would allow you to use Course Visibility and Open Enrollment Dates to drive student behavior and retain course version information in student training history records.

CONTENT SUPPORT: When to contact Latitude Learning

• Thoroughly reviewed our training materials
• Reached out to your authoring tool’s Support team for guidance
• Verified that your course is behaving correctly in SCORM Cloud or Articulate Test Suite. Success there does not always ensure success in the LMS, but it can help identify major issues that are in the course before getting it to the LMS.

• The LMS window and the course content "launch" window/tab must be open concurrently. If a student closes the LMS window, the SCORM engine cannot properly update score and status.
• Any interruption in network connectivity while a student is taking the course can interrupt or disconnect communication of status between the LMS and the course.
• Course configuration in the authoring tool may be problematic:
  
  1. Success/completion factors are not being fully met by the student. Making them aware of the success factors or helping create navigation and workflows that guide them toward full completion can help.
  2. The student does not navigate or exit the course in a way that triggers submission of final status or score to the LMS. For instance, if a final "Finish" button submits scores to the LMS but the user simply closes the course window.
  3. Publishing settings such as "Report status to LMS as" can cause issues with the LMS and may need to be altered if initial attempts fail. These are the settings that tell the system to report as "Passed/Incomplete", "Passed/Failed", "Complete/Incomplete", etc. Using "Passed/Incomplete" is usually successful.