< Previous | Contents | Next >
5.3. Processing Navigation Requests
When the learner or content triggers a navigation event through any mechanism, the LMS processes the corresponding navigation request by invoking the sequencing system. The result of processing the navigation request will always be one of the following:
1. If the effect of the navigation request is to end the current attempt on the activity tree, the LMS will process an Exit All navigation request, which ends the attempt and returns control to the LMS.
2. After evaluating the current tracking status and the applicable sequencing information on the activity tree, the LMS determines that processing the intended navigation request should not be honored. In that case, the LMS ignores the navigation request. The LMS takes no sequencing action until another navigation request is triggered.
For example:
Figure 5.3a: Choosing a Cluster Activity with Flow Disabled
Consider a part of an activity tree shown in Figure 5.3a and the situation where the learner is currently experiencing Activity A (not shown). If a choice navigation request for Activity C is triggered, the LMS may evaluate (validate) that request and determine no activity would be identified for delivery. Using this information, the LMS may ignore the request and allow the learner to continue experiencing Activity A.
3. After evaluating the current tracking status and the applicable information on the activity tree, the LMS determines that processing the intended navigation request should be honored. The LMS invokes the Overall Sequencing Process (refer to
Section 4.3) with the intended navigation request. The result of the Overall Sequencing Process will be one of the following:
a. A learning activity is identified for delivery: The LMS shall prepare and launch the identified learning activity’s associated content object (refer to the SCORM RTE book [4]).
b. No learning activity is identified for delivery: In this case, SCORM does not place any requirements on LMS behavior. However, it is recommended that the LMS provide minimal distraction to the learner.
For example, as described in the example above, if the LMS honored the choice navigation request for Activity C, no activity would be identified for delivery. The current learner session on Activity A would end, but the subsequent LMS behavior is undefined.
c. An exception occurs during one of the sequencing processes: In this case, SCORM does not place any requirements on LMS behavior. However, it is recommended that the LMS gracefully handle the exception and provide minimal distraction to the learner.