Advantages of using a live dataset
You can think of live datasets as a more flexible version of Tag hierarchies:
- With a Tag hierarchy, you specify a fixed ordering of Tag types, and all your reports must present the same drill down order.
- With a live dataset, you specify a pool of Tag types, and each learning outcomes report can display whichever ordering you like from within that pool. Each report can use any of the Tag types from that pool to create a hierarchical drill down, in any order.
Figure 1: Tag hierarchies compared to live datasets in the Learning Outcomes Report
When using a live dataset, you can create multiple versions of the learning outcomes report. As in the diagram above, you could create the following:
- A version with drill down for: Cluster > Standard > Difficulty,
- Another version with drill down for: Cluster > Difficulty, and
- Another version with a drill down for: Difficulty > Standard.
All these different versions can be powered by a single live dataset, which would have to include the Cluster, Standard and Difficulty Tag types. As in the example, these reports can have different drill-down depths as well. Each report's hierarchy can contain up to 5 levels, drawn from any of Tag types in the live dataset.
Note that only the learning outcomes report uses live datasets. If you want to use any of the other Tag based reports, such as Last Score by Tag by User, or Sessions Summary by Tag, those will still require you to set up a Tag hierarchy.
You can adjust the scope of the report to only include Item content related to one or more Tags. For example, in a live dataset containing curriculum content, your hierarchy might include Domains, Clusters and Standards. You could choose to constrain the scope to only display the Standards from within one Cluster.
You can also filter which sessions go into a live dataset, based on parameters of the session, e.g. Activity IDs or other metadata from the session.
Storing a record of attempts
By default, Learnosity will only store the most recent attempt of an Item. It is possible to store more information than this if needed. For example, all attempts per Item could be stored.