So, you've created your project, checked it using Gomo's preview feature, and are ready to upload it to your SCORM-compliant Learning Management System for delivery to your learners. How do you do that from Gomo?  The good news is that it's really easy:

Either: 

• Right-click on the project you want to publish in the main projects view and select Publish project:

Or:

Open the project you want to publish, click on the Actions button at the top right of the Project structure view and select Publish project:

You can now select the type of tracking assigned to the SCORM file. gomo can produce SCORM 1.2 or 2004 compliant files.

• Track via SCORM 1.2 - publish a file with SCORM 1.2 tracking ability
• Track via SCORM 2004 3rd Edition - publish a file with SCORM 2004 3rd Edition tracking ability
• Track via SCORM 2004 4th Edition - publish a file with SCORM 2004 4th Edition tracking ability
• Track via xAPI (defined endpoint) - specify an additional LRS to send tracking data to
• Track via xAPI (undefined endpoint) - send the SCORM file to an LMS that has integrated LRS functionality
• Tracking not required - publish SCORM package with no tracking ability
• Google analytics - use Google Analytics to provide real-time data on User access to your projects
• Connectivity checker - alert users when the internet connection is lost. (If network/internet connection is lost then the Learner will need to exit & re-launch the course for progress to be recorded)

Once you've made your selections click Publish. Gomo will now take the content of your project, apply the theme you've selected for it, and create a multi-device HTML package with all the wrapper code needed to communicate with a SCORM compliant Learning Management System.

Go back to the main projects page and you'll see the progress of the publishing of your project:

When it's completed it will be ready for downloading from the Gomo cloud:

Click the Download button and a zip file will be transferred from the Gomo servers to the Downloads folder of the browser on your computer. This zip file will have a file name based on the Gomo project number and today's date, but you can rename it to whatever you want, as long as you keep the .zip file extension.

There's nothing else you need to do to the published project, so it can now be uploaded to your SCORM compliant LMS. For example, in Moodle, it can be uploaded as a SCORM activity.

The SCORM 1.2 API methods called by the gomo player are as follows:

• LMSInitialize()
• LMSGetValue()
• LMSSetValue()
• LMSCommit()
• LMSFinish()
• LMSGetLastError()
• LMSGetErrorString()
• LMSGetDiagnostic()

Note that, in the normal running of things, the last three should never be called.

The CMI data used to store state information is:

• cmi.core.lesson_location - Bookmarking / Last page visited popup
• cmi.core.lesson_status - Completion status, set to one of the following:
  • incomplete
  • completed
• cmi.core.score.raw - Assessment score (if assessment results asset has the "Is tracked assessment" flag set)
• cmi.core.exit - Helps some LMSs exit correctly
• cmi.suspend_data - Used to store any state information like tracking states
• cmi.core.session_time - Automatically appended during exit process