trackingandweighting

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
trackingandweighting [2023/09/13 15:36] – [Tracking: xAPI] jsmithtrackingandweighting [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 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 total score on all assessable interactive tasks in the Xerte project, according to weighting set by the author
   * the score on individual pages   * the score on individual pages
Line 33: Line 33:
 These are the only pages which can produce automated scoring. 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 59: Line 59:
 ===== Completion ===== ===== 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}}
  
  
trackingandweighting.1694619375.txt.gz · Last modified: by jsmith