Understanding the Tincan (XAPI) published files

Hey there Darren.  First I wanted to offer this article on how Articulate works with the Tin Can API.

It sounds like you wanted to host your course on a web server and then link it to your LMS so that the actual content of the course is not hosted directly in the LMS.  Is that right?  If so, this article on how to publish your content for Tin Can API addresses where to host your content (2nd section).

I hope that helps!

Hi,

thanks for the reply, however I am familiar with that document already, and actually followed it.

My question was more about why do I place the Storyline Content on my external server, and also have to upload the zipped file (which also includes the Storyline Course Content) onto the LMS? I did not think that the actual course had to also be uploaded to the LMS?

I am asking this because the plan was that we would be able to edit and update any Course source content on the external server, without the need to get the LMS team involved whenever we need to update Course content. But if we also need to upload the Storyline Content into the LMS I see a problem?

Ah, I see.  The LMS needs to reference the zipped contents of the course to verify the content on the external server.  Additionally, the external link created when publishing the project for LMS becomes a part of the published output, and that published output needs to be hosted in the LMS so that the LMS knows where to point to the external server.  There is no way to break off some of the published output to lighten the load on the LMS side.

I understand that it presents a hassle for you if you have to deal with both the external server and then your LMS team when updates need to be made.

The points Crystal makes, plus the LMS is reading information from the Story file including the settings up established in Publish To LMS