The primary purpose of the LXP Data Model is to aggregate, personalise and recommend learning content from multiple sources, with the core focus being on content curation and learner engagement. Whereas the xAPI Data Model is to track and store learning experiences in a standardised format, focusing on the tracking of learning activity data from multiple sources.
We will use the example below of displaying object completion to demonstrate how we can build the same query using either data models, and how we can expand the data depending on the focus.
Object Completion with the LXP Data Model:
When using the LXP Data Model for Object completion, it is possible to output the total number of objects associated with a Learning Experience and then surface how many of those objects a user has completed. (However, please note it is not possible to surface the date on which each of the objects was completed.)
Using the example object completions per user, this can be done, as shown below;
First, surface the user's name; in this example, we will pull in the User Full Name field.
Next, we want to add the Course Name, also referred to as a Learning Experience.
Now you will be able to see both the user's full name and course name visible within the widget.
Next, add in the field Number of Objects to capture the overall total within that course, as shown below ;
Next, add in the field Object Completed as shown below;
Once you have added your fields, your widget will show you a comparison of how many objects each user enrolled onto the course has completed:
Object Completion within the xAPI Data Model:
Using the xAPI data model, you can now start to pull in more granular detail, unlike the LXP data model you will have access to surface more information. The reason we can do this is because the xAPI Data Model is designed to work together with your Learning Record Store (LRS). Your xAPI data defines the data format and your LRS is the storage system. Analytics will allow you surface this granular data using the xAPI data model.
Sticking to the example of object completion we will expand our widget to incorporate completion dates which is only surfaced if you are using the xAPI Data Model.
This time to surface the user's name we will search for persona_name;
Next, we will pull in the course_name which relates to the Learning Experience name within your LXP;
Next, we will pull in the object_name. This will show only those objects that have been completed;
Next, you can surface a users object completion date pulling in Timestamp;
The xAPI data model will present you with all possible verbs which are being stored in your LRS. For our example we want to display users who have completed an object.
So you would add your verb_name and filter it to display completed.
Next, pull in the column for object_name;
Helpful tip, if you are seeing any Object Names displaying as N\A, you will be able to filter these out by setting the rule Is not equal to N/A.
Another useful point to note is you may see more than 1 timestamp against a users object completion;
This does not necessarily mean that there is a mistake in the data being displayed. The xAPI data for that user will capture if a user has completed an object multiple times.
You can verify this theory by taking the users information and compiling a query within the LRS to verify the findings: