Now that I know what SCORM is and about its design and what the developer does, it is time to begin my journey into creating course content with this platform. While searching for tutorials, I found Rustici Software who hosts a SCORM Engine. I requested a demo and created an account for SCROM Cloud which is used to store courses created in SCORM. However, I still did not know how to create course content to put into the SCORM Cloud. I was getting very frustrated to say the least. When I created my account, I was sent an email with information on how to create invitations in SCORM, how to dispatch a SCORM course into an LMS, and how to track student’s learning in SCORM as well as information on Tin Can API. I had seen Tin Can API before but did not know anything about it. Below this list of links of information, there was another link labelled “Need help? Check out our Knowledge Base”. I clicked on the link as fast as I could. It took me to a page full of resources on how to use SCORM Cloud and I decided to start with “getting started”. I did more reading and more searching without anything good on how to create course content on SCORM. I was still lost. I decided to check out the Tin Can API to see if I could find something to help me get started. If I understand properly it, Tin Can API is a modernized version of SCORM. “The Tin Can API (sometimes known as the Experience API or xAPI) is a brand new specification for learning technology that makes it possible to collect data about the wide range of experiences a person has (online and offline). This API, which stands for Application Programming Interface, captures data in a consistent format about a person’s or group’s activities from many technologies.” So, since I haven’t found anything on how to create course content on SCORM so far; I will now focus my attention on the Tin Can API platform in hope that I can find some tutorials teaching me how to create course content with in it.
SCORM versus Tin Can API showed that what Tin Can API can do is almost endless. The pictures below show that it can collect data on real life performances, simulations, and games as well as interactive, blended, offline and team-based learning. The acronym LRS represents Learning Record Store or the heart of Tin Can. One major particularity of Tin Can API is that it does not require an LMS to collect data student’s learning.
Without an LMS With an LMS
Now, that I am focusing on Tin Can API, it is necessary that I familiarize myself with its terminology and design model. The acronym LRS represents Learning Record Store or the heart of Tin Can. This Tin Can API list of statements . “At the simplest level, Tin Can statement structure can be expressed in the form of “actor verb object”.
Here is what a simple Tin Can statement might look like:
The final step in my learning journey this week was to create an account for SCORM Cloud which will act as my LRS. It has limited capacity and basic functionality but this should be sufficient for my first Tin Can project. After learning more in details about Tin Can API, I hope that I am finally ready to learn about how to create course content on a platform compatible with all LMS.
Here is a screencast of my learning journey this week.