Sequencing
Along with Data Validation and Versioning, probably the most +
Sequencing
+Along with Data Validation and Versioning, probably the most vexing problem confronting the Assessment package is how to handle conditional navigation through an Assessment guided by user input. Simple branching has already been accomplished in the "complex @@ -15,7 +14,8 @@ branching/skipping depends not merely on what combination of "correct" or "in range" data the user submits, but also on combinations of "incorrect" or "out of range" data, how the heck do -we do this?
One basic conceptual question is whether Data Validation is a +we do this?
+One basic conceptual question is whether Data Validation is a distinct process from Navigation Control or not. Initially we thought it was and that there should be a datamodel and set of procedures for checking user input, the output of which would pipe @@ -28,16 +28,21 @@ step we'll refer to here as Sequencing. (Note: we reviewed several alternatives in the archived prior discussions here.
+ So here is our current approach. We note that there are two scopes over which Sequencing needs to be handled:- intra-item: checks pertaining to user responses to a single item
- inter-item : checks pertaining to user responses to more than one item; checks among multiple items will be built up pairwise -
So how might we implement this in our datamodel? Consider the + +
So how might we implement this in our datamodel? Consider the
"sequencing" subsystem of the Assessment package:
-
Specific Entities
-
+
+
- Item-checks (as_item_checks) define 1..n ordered evaluations of a user's response to a single Item. These can occur either via client-side Javascript when the user moves focus from the Item, or @@ -106,4 +111,3 @@