Convert e-Learning to LTI

Jan 19, 2023

Hi all, 

I developed an e-learning for a customer and delivered it to them in SCORM 1.2 format, because last year it was also delivered in this format.

Now, their LMS provider comes back and says that they can't upload it to their LMS since they need LTI format. Is there anything we can do so that they can still use it in their LMS in LTI format?

Fingers crossed...

Best, Joanne 

11 Replies
Jose Tansengco

Hello Joanne, 

Thanks for reaching out! 

There isn't a way to convert the published output of your course from SCORM 1.2 to LTI format.

Storyline 360 currently does not support publishing courses in LTI format as an option, but I've added this thread to a feature request for adding support for LTI. We'll be sure to let you know as soon as we have any updates! 

Joseph Francis

SCORM vs. LTI: What’s the Difference?

"To put it simply, the main difference between LTI and SCORM is that LTI is focused on connecting learning systems, whereas SCORM is focused on launching training content and tracking interactions. LTI tends to be used by higher education and academia, whereas SCORM is used primarily by government and corporations..."

What learning management solution is your customer using? Are they an academic institution?

Joseph Francis

I see what Defacto is doing. They are leveraging LTI to get around the "same domain" issue which has plagued SCORM since its inception (essentially, course content must be housed on the same domain as the LMS application). Defacto's Certified Integration page explains it.

Rustici Dispatch give you the ability to host SCORM content on a different domain than the LMS application. We used that solution at my last employer to maintain control over our hosted courses for multiple clients.

Steven Benassi

Hi Annemarie!

Thanks for checking in on this!

Our development team is tracking an open feature request to allow Rise 360's support for LTI integration. I don't have any updates to share as other feature requests have been prioritized, but I've included you in the feature report.

We'll update this discussion if it makes it onto our Feature Roadmap.