Project

General

Profile

Feature #5745

Add option to *not* interpret status from mastery_score in scorm

Added by Yannick Warnier almost 7 years ago. Updated almost 2 years ago.

Status:
Feature implemented
Priority:
High
Assignee:
Category:
Learning paths / Lecciones
Target version:
Start date:
20/11/2012
Due date:
29/09/2017
% Done:

100%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

In SCORM 1.2 RTE, the documentation says:
"1) If cmi.core.credit is set to “credit” and there is a mastery score in the manifest (adlcp:masteryscore), the LMS can change the status to either passed or failed depending on the student's score compared to the mastery score."

The subtelty is in "the LMS can change th status". (because the cmi.core.credit param depends on the "allow multiple attempts option" in Chamilo - allowed means "credit", unallow means "no-credit" from the second attempt. The first attempt is always in "credit").

There are cases where this is not desired.
Add a setting in the scorm edit page to allow the user to "unselect" a checkbox that says "Interpret status from score".

Depending on that option, comment this block in learnpathItem.class.php::set_score():

if ($master != -1 && $this->current_score >= $master && $current_status != $this->possible_status[2]) {
    $this->set_status($this->possible_status[3]);
} elseif ($master != -1 && $this->current_score < $master) {
    $this->set_status($this->possible_status[4]);
}

(just add a condition around it like if($this->guess_status) { ... } and make sure the guess_status is defined at the creation of the lpitem object).

Associated revisions

Revision 13edeb54 (diff)
Added by Julio Montoya almost 7 years ago

Adding temporal fix just for tests see #5745

Revision 6c6bdb60 (diff)
Added by Julio Montoya almost 7 years ago

Undo change see #5745

Revision b16193e0 (diff)
Added by Julio Montoya about 5 years ago

If the status was changed, then updated it. Don't need to set a score.

See #5745 and BT#8572

History

#1

Updated by Yannick Warnier almost 7 years ago

  • Description updated (diff)
#3

Updated by Yannick Warnier over 3 years ago

  • Target version changed from 2.0 to 3.0
#4

Updated by Noa Orizales Iglesias almost 2 years ago

  • Due date set to 29/09/2017
  • Status changed from Assigned to Feature implemented
  • % Done changed from 0 to 100

Also available in: Atom PDF