Differences

This shows you the differences between two versions of the page.

--- trackingandweighting [2022/12/07 13:56] – [Tracking: SCORM] jsmith
+++ trackingandweighting [2023/09/26 08:15] (current) – [Completion] jsmith
@@ Line 9: / Line 9: @@
   * whether or not a learner has attempted a task.
-Xerte will only track performance on projects which include one or more of the following **Interactivity** pages;
+Xerte will only track answers and/or score on projects which include one or more of the following **Interactivity** pages;
   * Answer X of Y
   * Categories
+  * Dictation
+  * Drag and Drop Label
   * Gap Fill
+  * Hotspot Question
+  * Interactive Text
+  * Interactive Video
   * Matching Texts
-  * Model Answer
+  * Media Lesson
+  * Model Answer (answer only)
+  * Modify Answer
   * Multiple Choice Question
   * Opinion
   * Quiz
   * Sortable Grid
+  * Text Highlight
   * Text Correction
   * Timeline/Matching Pairs
@@ Line 35: / Line 43: @@
 ===== Tracking: xAPI =====
-xAPI ....
+xAPI allows for the tracking of individual performance with the data being reported to a dashboard that is generated within the Xerte interface.  This reporting feature is only available if you, or your IT team, have set up a Learning Record Store (LRS) and connected it to your Xerte installation.
+To track individual results that are related to a specific person, the project needs to be added to an LMS using LTI. When the project is started from the LMS, the LTI launch contains the details about the current user that Xerte uses to identify the learner (see LTI/xAPI on the [[project_properties#LTI/xAPI|Project Properties ]]page).
+The project can also be tracked anonymously by placing the xapi_launch.php URL in the LMS. See xAPI in Project details (the middle panel of the Workspace)
 ===== Weighting =====
@@ Line 44: / Line 55: @@
 If you don't want a page to be scored, set the Tracking Score Weight at 0.
+===== Completion =====
+Often it is as important to track completion as it is to track the score. By default all pages have to be visited or answered before a project is marked as complete. That is not always the case. Using the optional property 'Completion Not Required' (see [[op_completion_not_required|Optional Property: Completion not required]]) to indicate that a certain page does not need to be visited. For example, it would make sense to do this for all standalone pages. Sometimes you want text pages to be visited for a certain amount of time. Although we do not recommend using that unless you make it very clear to your learners that they really need to look at each page for a certain amount of time. You can enable that feature by changing the value of 'Page timeout for completion' in the optional property 'Tracking...' of the project.
+{{tag>pagetype some_pages}}