Gradebook Integration
Ultimately, Sosua will need to track interactions with a user on pages and sequences. However, in the short term, we can grade a page assigned based on view/no view, and a sequence on reaching the end or how far along.
IMS has done some design work to formalize the SCORM data persistance at:
http://www.imsglobal.org/ssp/sspv1p0/imsssp_prflv1p0.html
Sequence Tracking
When a user starts a sequence, an attempt record is created. This record tracks progress through the sequence. On reaching a defined end-point (there is only one in the current implementation), a grade is calculated for this sequence as an activity. This grade can be optionally posted to the Sakai gradebook. Tracking only happens if this activity is represented as an assignment.
Results Table
Field Name |
Type |
Notes |
---|---|---|
Assignment Id |
String |
Can be null. |
User Id |
String |
Must be non-null. |
Attempt Id |
Number |
This might be a time-stamp |
Completed |
Time |
Can be null. |
Grade |
Decimal |
Can be null. |
Results Tracking
Once interactive elements are added to a Sousa page or sequence, instructors may wish to grade them and weight them against the score for the whole sequence (or page). Further, there is likely a desire to preserve the responses of the student (including all attempts). Interactive elements can be broken down as follows:
- Questions or tasks
- Essay
- Short Text Answer
- Multiple Choice (including T/F, etc.)
- (many others)
- Pure interaction
- Simulation
- Game
Scoring can be done with rubrics. Saving results is more difficult. It may be possible to leverage an existing assessment engine, such as SAMigo or Mneme.
Perhaps an intermediate solution can be managed by recording a reference to the interaction element, a textual response, and a score. That could be easily saved in a database table and could even support multiple attempts. Separate out reporting from data capture.