May an LMS change moveOn for a person taking it "during" a registration?

[fugu13]

Specifically:

An LMS is allowed to override the moveOn value in course structure. Changing this when someone already has a registration with some statements to NotApplicable or a status previously gained (perhaps from CompletedAndPassed to just Completed, and the person has already completed the AU) seems like it should trigger, at some unspecified interval, satisfied statements. Is this allowed? Are there any restrictions on when the satisfied statements could happen?

[brianjmiller]

And this is why I fought against course structure "editing" :-). I think the answer is, this isn't addressed in the spec. We addressed that it is possible to pass a different value at "runtime" (effectively launch) to the AU and that the AU should act accordingly. We did not address (explicitly) changing post registration initialization. See #424 and #378 for some discussion around these sorts of things.

FWIW, to me, if it is allowed (which could only be when there are no active sessions or at least it triggers abandonment of them) then it should happen immediately. Having said that there is no allowance or more importantly forbiddance of it in the spec, so it seems like it is allowed and undefined.

[fugu13]

which could only be when there are no active sessions or at least it triggers abandonment of them

Why would that be true? Waiving (and associated satisfied statements) is allowed any time and it only triggers abandonment if it is for a different AU (at least, per the current text, dunno about intent) than the one a person is in (which actually seems pretty strange already; kicking someone out of a course while they're in it in adds a lot of high touch browser-server coordination to avoid horrible user experiences).

[fugu13]

(In other words, why would it do so for extraneous satisfieds for the same AU; abandoned seems to be required if it is different AU)

[brianjmiller]

Hence the word "could". It could be also that we don't want that.

[fugu13]

Ah, I see; I took the "if it is allowed (which could only be" as being under the current spec, not future looking.

[cawerkenthin]

From my reading, it is allowed during a registration because it is not prohibited. During a session, however, it would seem to be blocked by the practicality that the State document includes the moveOn. We should probably develop a best practice around this issue at a minimum.

[MrBillMcDonald]

Per the June 16th, meeting. This scenario is not addressed in the the cmi5 spec.
We will draft proposed language for the next version of the cmi5 spec to address this issue.

[MrBillMcDonald]

Per Feb 23, Meeting......

Modifying the course structure during an active registration should be avoided as it would cause unexpected results.

Scenarios for course structure changes:

1. Change a course structure after import (before registration)
2. Change a course structure after Registration (before launch/session)
3. Change a course structure after during a Session

Best Practice
Modifying the course structure during an active registration should be avoided as it would cause unexpected results.

Spec Change Option 1:
Course modification during an active registration and/or AU session is outside the scope of this specification.

Spec Change Option 2:
Course modification during an active registration is not allowed.

Spec Change Option 3:
Course modification during an active registration is not allowed when the AU has been previously marked Satisfied

---

Further discussion on this topic is needed