Forum Discussion
Publish to Cmi5 in Storyline 360 and Rise 360
We’re pleased to share a new publishing option for your Storyline 360 and Rise 360 courses: cmi5. Cmi5 is the newest output standard for Learning Management Systems (LMSs). The cmi5 output option is...
So do they only partially support CMI5? A big advantage of CMI is that the content can live separate from the CMI package but still be delivered via the CMI5 package. Much like AICC does.
Thank You,
Mike
Sent from my iPad
Hello Michael,
I can confirm that only publishing to cmi5 is supported in Storyline 360. Could you tell me more about how 'content living separately from its published package' is supposed to function so I can check if we have other solutions available that we can share with you?
One of the features of CMI5 is that the package you load into an LMS does not need to contain the learning content within the CMI5 zip file. The content can be stored on a separate server (not an LMS). The benefit of this is that you can distribute the CMI5 file to many customers. When edits to the content need to be made it can be updated in one place. New CMI5 files don’t need to be sent out to all of your customers and they would have to republish in their LMS.
Thank You,
MikeSent from my iPad
Hi Michael, I think what you're referring to is a 'thin package', which isn't so much a feature of a CMI5 package, but rather a publishing function of an authoring platform. For instance, my company uses Xyleme CCMS to create and publish content to its own LRS. One of the options after publishing to the LRS is to download the course as a thin package. Inside the zip package is the typical index.html file and xml.manifest file which contains links to the content which is stored in the CMS, externally from the zip package.
You can give this package to another LMS to host and the LMS sees it as a normal scorm package. The benefit here is that you can update content remotely as you mentioned, but in addition, the LMS will get normal scorm reporting on its end, and the CCMS will also get xAPI reporting back on its end.
I don't know if thin packages can be created out of Articulate, but I don't 'think' it's unique to CMI5.
Rise 360 also shows that it can publish as CMI5.
Thank You,
MikeSent from my iPad
