Experience in Adopting Tin Can API

Experience in adopting Tin Can API

Experience in Adopting Tin Can API

I have discussed about the importance of making eLearning courses compatible to SCORM standards in my earlier blogs. I also discussed how these standards allow courses to communicate with the LMS to support the tracking of learning activities. In this blog, I want to talk about how tracking can be taken to the next level – across devices and platforms.

Gone are the days when learners acquired knowledge by logging into the LMS and taking the assigned courses. Today’s learners want to get trained at their own pace, anytime, anywhere and by using the device of their choice, irrespective of whether the training is formal or informal.  In fact, corporate learning has become more informal as a result of sharing of experiences, peer interactions etc. Would it not be in the interest of the organization to track these learning efforts across different media?

This is why experts tried to develop a specification, which can track eLearning in all its forms and that is how Tin Can API has come into the picture. Here, I will share  some information on Tin Can API, formally termed as Experience API, with you all.

Basics of Tin Can

Tin Can API is the successor to SCORM.  It tracks and records learning experiences that occur anywhere, through any device. It can recognize and track a wide range of learning activities including:

  • Mobile learning
  • Gamified learning
  • Offline learning
  • Collaborative learning
  • Experiential learning
  • Simulations
  • Mobile Applications or Apps
  • Responsive Learning

How does Tin Can API track?

Tin Can allows us to track both formal and informal learning events of employees. These can be then recorded into a Learning Record Store (LRS) using the below syntax:

Noun – Verb – Object. ‘I – took – This’.

Tin Can allows you to store training programs as statements inside an LRS. For example, statements such as “Team 3 successfully took the course” can be recorded and stored in the LRS, thereby facilitating tracking. The LRS acts as a server that can either be used as a stand-alone system or integrated with the LMS.

LMS to LRS- It allows tracking of

  • Quizzes
  • Courses
  • Forum posts
  • Classroom Training

So what can we track?

Everything! SCORM allows us to track only these aspects of an online course.

  • Pass/Fail status
  • Completion of the course
  • Time taken by users to complete the course
  • The final scores

But, Tin Can allows us to track everything – detailed data about the activities of a person a group , while taking the course.  The training can take place through any device. Yet, you can track the training activities using very simple action statements.

Tin Can allows us to do things which were not possible using SCORM. For instance, users can launch a course outside the LMS or access the course from the LMS and continue to take it using their devices.  Tin Can supports the management of course delivery and tracks learning that takes place.  Tin Can allows you to record complete data of trainings and evaluate what is working and what is not.

Even though the final or official version of Tin Can API is still not released and it is being adopted on an experimental basis, Tin Can standards have overcome the restrictions associated with SCORM, allowing us to record informal and formal learning experiences as and when users access courses.

With constant changes in the training needs of organizations and rapid developments in technology , it has become important for organizations to adopt and be up to date with the trends of the industry.

So, why don’t you adopt Tin Can API? We’d love to hear your views.

View Presentation on Generating Reports in an LMS to Review Training