Tracking Data Record

A Tracking Data Record (TDR) represents the data generated from a single session of a given user interacting with a learning object. For example, the raw tracking data associated with the last AICC putParam for a given user or learning object session is what generates a TDR.

Tag Name	Type	Semantics
id	int	This ID is unique for all TDRs per content consumer system. This ID will be a monotonically increasing 32-bit integer that starts at 0.
timestamp	timestamp	The UTC timestamp of when the TDR is entered into the On-demand Communication system.
userid	string	Equivalent to the AICC core student_id provided by the content consumer.
assetid	string	The content publisher’s ID for the associated learning object. If data is received for an unknown asset then the content publisher may provide a capability to retrieve and install the metadata for the learning object on the fly.
reset	boolean	If the was previously sent to the content consumer but not acknowledged by the content consumer, then 1, otherwise 0.
format	string	The name of the format used in the data element. The currently supported format is “cmixml/1.0/ToLMS”. For more information about cmixml/1.0/ToLMS” format, see http://www.aicc.org/docs/tech/cmi013v1.pdf
data	string	The actual data in “cmixml/1.0/ToLMS” format. For more information about cmixml/1.0/ToLMS” format, see http://www.aicc.org/docs/tech/cmi013v1.pdf
context	string	The format for context is: `<context>` `<olsa_ai>`0 \|\| 1`</olsa_ai>` `<olsa_completable>`0 \|\| 1`</olsa_completable>` `</context>` The following values are available as of OLSA 1.2 SR3 Patch 1: olsa_completable - If an asset is completable, then the value is 1, if it is not completable then it is 0. If the tag is omitted then the default value is 1. Only Assets that are completable are trackable. If the tag is omitted then the default value is 1. olsa_ai - Asset is delivered through the Asset Synchronization Cycle, then the value = 1. Asset is not delivered through the Asset Synchronization Cycle, then the value = 0. Note: Do not assume order of these tags. Other tags may appear in this data element in the future. Table 1: Tracking Data Record elements

A TDR can be generated in the following ways:

Content consumer initiated launches – From the perspective of the consumer, also known as a direct launch. Learning objects launched in this manner are in the traditional model where the metadata, for example, AICC, SCORM, for the learning object is installed into the content-consumer system. At which point, such learning objects are then available to the end users of the content consumer system. An end user can now log into the content consumer system, navigate through its User Interface screens, and directly launch the learning object in question. Learning objects launched in this manner are initiated by the content consumer system.
Content publisher initiated launches – From the perspective of the consumer, also known as an indirect launch. Learning objects launched in this manner use a new model. In this model, the content-consumer is unaware that its end users are accessing the learning objects in question. A learning object launched from within a learning object would be one example of this model. Learning objects launched via a content publisher’s proprietary offline solution would be another example. Learning objects launched in this manner are initiated by the content publisher system.
In some cases, the learning object in question may be for content that is not natively yet installed or known in the content-consumer system. A content consumer must be prepared for this contingency. A content consumer can choose to ignore such TDRs. In the case of the Skillsoft OLSA implementation, the content consumer has access to the Selective Asset Metadata Retrieval (SAMR) functions. These functions allow the content consumer to get AICC or SCORM metadata so the missing learning object can be installed as needed, if such a step is necessary to properly process such TDRs.