When the LMSFinish is received by the LMS, there are several scenarios that may need to be taken into account. Some of these may be the product of errors in course development but are scenarios that have been experienced in interfacing with a SCORM compliant course:
1. The SCORM course may indicate the student has failed a lesson but the score passed from the SCO may be greater than the lesson passing grade that was installed from the manifest.
2. The SCORM course may indicate a lesson status for the user and pass the score of the lesson but there has been no passing grade defined for the lesson.
3. It would be advantageous for the Learning Management System to provide API message logging so that a communication history may be recreated for debugging or historical purposes. Consideration should be given to the following:
a). Method of storage, whether it is stored in a database or out to a file.
b). Is logging on all the time or is there a switch to turn logging on or off? (There will be some overhead when logging is switched on, as opposed to being off.)
c). If logging is to file, is there a log file for each course, each user, or one large SCORM log file?
d). How is log data purged? When logging is stored in the database, how often is the table purged? Can the data be deleted or does it need to be archived? If logging is to a file, does the file build in size until it is manually renewed or does the logging mechanism have a trigger that automatically generates a new file? (If the file is left to grow too big, it becomes very impractical to open it in a text editor.)
No comments:
Post a Comment