Update: The Output of Project Tin Can is Experience API.

next generation scorm evolution project tin can
 

Ready to really dive in?
View the full
Tin Can API spec.

View the Tin Can API
“quick start” guide.


User-Defined Variables

user defined variables scorm tin canAt its simplest, a user-defined variable is just a dynamic piece of information that lives inside content.

There are two ways to incorporate user-defined variables.

The first way is where external information is fed into the LRS to be used by an activity. Some examples of how this can be used:

  • A course on the stock market that pulls in real-time stock numbers
  • A flight simulator that uses real-world wind speeds from a weather feed
  • An “on-boarding” course for a company that brings in variable data (staff names, holiday schedule, etc.)
  • A sports course that uses real-time stats from a feed or database

The other way to use user-defined variables is by storing information about a learner or an activity as a variable that can be used later in reporting. These variables would be any arbitrary data that wouldn’t belong in a normal statement, such as stock market numbers or wind speed from the above examples. Another example would be an assessment that stores which areas a student needs help in, and then serves up a review course based on those variables.

The use cases for user-defined variables are many. We surely haven’t thought of all of them. Use the comments section below to see other use cases, talk about how you’d utilize user-defined variables, and discuss any concerns that you have with this feature.

SCORM 2.0 next generation project tin can

Did we achieve what you wanted with this feature?


  • Gem

    I guess I prematurely posted this in the previous page but it seems to be more pertinent to this one, so here it is again:

    Any parameters on troubleshooting with inaccurate reporting if the need arises? It seems proper syntax is crucial for tracking (typos, etc.)… how are these handled? Thanks.

  • bsc_scorm

    It’s up to activity provider creating the statements to use the correct identifiers. For specced properties, typos will result in rejected statements. For extensions, or vocabularies like verbs or extensions that take any URI, a typo will generally just result in storing a statement that doesn’t ‘make sense’.

    Reporting systems might try to detect this by keeping track of all verbs / extensions that are “known” and flag when “unknown” verbs/extensions are encountered, for an administrator to either mark as “known” or follow up with the owner of the activity provider.

    User defined variables are a power tool, and those using them need to exercise care.

  • Pingback: Tin Can API & the Future of E-Learning | Learnnovators - Bringing INNOVATION to LEARNING()

  • Pingback: TIN CAN API & THE FUTURE OF E-LEARNING | E-Learning Blog()