Learner XAPIStatement

Learner XAPIStatement

Introduction

A Learner XAPIStatement preserves the raw xAPI statement if your system ingests data following the xAPI protocol. This can be helpful for detailed analysis, auditing, or compliance purposes. While the platform typically extracts the relevant data into other LDM objects, storing the full statement ensures nothing is lost.

Key highlights:

• JSON Storage: You keep the entire statement, including the actor, verb, object, context, results, etc.

• Optional: Not all organizations need to store the full statements, but it’s there if you want full fidelity with xAPI logs.

• Traceable: Linked to the learner, so you can see exactly which statement came from which user.

Properties

Property Name	Description
ContactId	Identifies which learner the xAPI statement belongs to. You might parse out their interactions, completion data, or engagement metrics from the statement.
Statement	The raw JSON content of the xAPI statement. This can include object definitions, context extensions, result scores, timestamps, etc. Storing it here keeps all the original detail in case you need to re-process or debug any analytics.
CreatedDate	System-managed date/time when this record was created, likely matching the ingestion time.
ModifiedDate	System-updated if you edit or re-save the statement (which is rare if you keep statements immutable).

Example

You ingest an xAPI statement like:

{
  "actor": { "mbox": "mailto:[e-mail]" },
  "verb": { "id": "http://adlnet.gov/expapi/verbs/answered", "display": { "en-US": "answered" } },
  "object": { "id": "http://mysite.com/xapi/questions/question1" },
  "result": { "score": { "scaled": 0.8 } }
}