Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.8, 1.8.1, 1.8.2
    • Fix Version/s: 2.0
    • Component/s: Course, SCORM
    • Labels:
      None
    • Environment:
      N/A
    • Affected Branches:
      MOODLE_18_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE
    • Rank:
      24686

      Description

      When i create a new course, that course has one Adobe Captivate 3 quiz/training session, exporting with SCORM 1.2. All of our quizzes are going to allow for unlimited attempts, but I really think the Mode, Start new Attempt, and enter course button could be vastly improved.

      I think that every time the user clicks the enter course button, it should always start a new attempt if available or prompt me asking if i want to start a new attempt. I think my users will miss the start a new attempt check box and get frustrated and just stop trying. I think the whole mode thing with the radio buttons toggling between Preview and Normal mode should just be removed alltogether as well as removing the start a new attempt checkbox.

      So ideally all you would see below that scorm content is:

      1) If it is your first attempt at the scorm content you only see an enter course button.
      2) If it is your second attempt or greater you see a Review button which reviews your highest scoring attempt or your last attempt and an Enter Course button that starts a new attempt.
      3) If you have made a perfect score you should only see the review button, and not the Enter Course button.
      4) If you have exhausted all of your attempts you should only see the review button as well.

      Would this improvement be possible?

        Issue Links

          Activity

          Hide
          Piers Harding added a comment -

          To help with player behaviour issues, and interaction with SCORM packages, I am making a series of changes that will allow a course administrator to influence the player/package interation.
          There are 5 new switches configurable for a SCORM package:

          • display attempt status - show the status of current attempts and the grading passed into the grade book
          • display course structure - display/supress the course structure on the (mod/scorm) course outline page
          • force completed - for SCORM 1.2 package, force the status to be completed if a score has been issued, this will be useful for buggy legacy packages.
          • force new attempt - make every revisit to a package a new attempt, this will inhibit attempt revisiting to improve scoring.
          • last attempt locked - lock out the package when all attempts have bee consumed.

          Additional to this there is the suppression of the start new attempt (point 1 and 2 above).

          Show
          Piers Harding added a comment - To help with player behaviour issues, and interaction with SCORM packages, I am making a series of changes that will allow a course administrator to influence the player/package interation. There are 5 new switches configurable for a SCORM package: display attempt status - show the status of current attempts and the grading passed into the grade book display course structure - display/supress the course structure on the (mod/scorm) course outline page force completed - for SCORM 1.2 package, force the status to be completed if a score has been issued, this will be useful for buggy legacy packages. force new attempt - make every revisit to a package a new attempt, this will inhibit attempt revisiting to improve scoring. last attempt locked - lock out the package when all attempts have bee consumed. Additional to this there is the suppression of the start new attempt (point 1 and 2 above).
          Hide
          tim rhymer added a comment -

          This is great news! Will this be effective in new builds of Moodle or which version should I expect to see this change?

          Show
          tim rhymer added a comment - This is great news! Will this be effective in new builds of Moodle or which version should I expect to see this change?
          Hide
          Piers Harding added a comment -

          Hi - this was commited into 2.0 (HEAD), and because it requires schema changes it is usually held back to the next major release (which is 2.0 as far as I'm aware).

          I'll see what Dan thinks.

          Cheers.

          Show
          Piers Harding added a comment - Hi - this was commited into 2.0 (HEAD), and because it requires schema changes it is usually held back to the next major release (which is 2.0 as far as I'm aware). I'll see what Dan thinks. Cheers.
          Hide
          Dan Marsden added a comment -

          Yeah - Piers is right, this can't go into the 1.9stable build due to the schema changes. but it would be nice if we could provide a patch for people to be able to use that would add the fields to the db and the changes to the mod_form.php page.... especially as Reporting is a big issue for a lot of people.

          but I don't really like the fact that a patch touches so many files, and it will be difficult for us to maintain/support if lots of people install it, and then want to update to newer versions.

          looking at locallib.php - a lot of that could be committed to stable couldn't it (would need a few checks to isset() before checking some vars as they won't normally exist) - Piers can we commit "some" of this patch to stable to limit the patch we would provide to add the functionality to a 19stable install? - if you get a chance could you post a potential "partial" patch to 1.9stable here for review?

          Show
          Dan Marsden added a comment - Yeah - Piers is right, this can't go into the 1.9stable build due to the schema changes. but it would be nice if we could provide a patch for people to be able to use that would add the fields to the db and the changes to the mod_form.php page.... especially as Reporting is a big issue for a lot of people. but I don't really like the fact that a patch touches so many files, and it will be difficult for us to maintain/support if lots of people install it, and then want to update to newer versions. looking at locallib.php - a lot of that could be committed to stable couldn't it (would need a few checks to isset() before checking some vars as they won't normally exist) - Piers can we commit "some" of this patch to stable to limit the patch we would provide to add the functionality to a 19stable install? - if you get a chance could you post a potential "partial" patch to 1.9stable here for review?
          Hide
          Dan Marsden added a comment -

          I'm flagging this as fixed - Piers has committed fixes to 2.0 that provide greater flexibility over SCORM packages, and allows changing the behavior dictated by the SCORM object by the authoring package. Anything not covered by these changes to 2.0 should be added in a new Tracker issue.

          NOTE: - these changes will not be in 1.9stable as they require db schema changes.

          thanks!

          Show
          Dan Marsden added a comment - I'm flagging this as fixed - Piers has committed fixes to 2.0 that provide greater flexibility over SCORM packages, and allows changing the behavior dictated by the SCORM object by the authoring package. Anything not covered by these changes to 2.0 should be added in a new Tracker issue. NOTE: - these changes will not be in 1.9stable as they require db schema changes. thanks!

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: