Differences

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

--- trackingandweighting [2023/05/08 12:43] – tom_reijnders
+++ trackingandweighting [2025/04/25 11:09] (current) – [Tracking and Weighting] admin
@@ Line 4: / Line 4: @@
   * the length of time the learner spends in the Xerte project
-  * the length of time the learners spends on an individual page
+  * the length of time the learners spends on an individual page (including videos)
   * the total score on all assessable interactive tasks in the Xerte project, according to weighting set by the author
   * the score on individual pages
@@ Line 33: / Line 33: @@
 These are the only pages which can produce automated scoring.
-To produce scores and data on time spent in a project or on specific pages, Xerte interacts with one or other of two technologies; SCORM or xAPI.
+To produce scores and data on time spent in a project or on specific pages, Xerte interacts with one or other of two technologies; SCORM or xAPI. In addition, there is a Results page that can be added to the learning object. The participant can (within the same session) see and download the results in a pdf.
@@ Line 44: / Line 44: @@
 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|Project Properties ]]page).
+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)
@@ Line 59: / Line 59: @@
 ===== 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.
+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.
-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}}