Friday, February 18, 2005

IERI Utility

Created some screen shots for KM. Eight shots total of five different screens.


Made a modification to the utility so that multiple instances of a teacher/activity sequence could be made. KM needs this so that multiple testers can timecode the same enacted activity sequence (EAS) . The changes were fairly simple:
  • I modified the database to add a new field to store the instance number. The instance number is stored in the enSequence table in the field instance.
  • I modified the processing script (process.asp) so that when a new activity is added it no longer checks for a previous instance. Now it counts the number of previous instances and adds a new one with an incremented instance value.
  • I added a new column to the EAS timecoding listing table. The column displays the value of the instance field. An additional sort is done on this field so that the instances are displayed in order (1, 2, ...).
I think this might also be a good addition for instances where a teacher teaches the same lesson to multiple classes. I don't know that IERI will ever need this capability. But as a utility function it may be something useful. I doubt we'll ever release the utility publicly, but I would like to at least plan for such an eventuality. It would be a bit of a waste to just ditch the utility once we're done with it. We should at least consider releasing it as an open-source project (though I have pretty big doubts that it would find much of an audience).


One final change ... I added a teacher filter to the EAS timecoding list. Previously, when an administrator accessed this list every available EAS was shown. The list could grow to unmanagable size quickly. The full list is still shown initially, but now the user has the ability to limit the list to the EASes for a specific teacher.

This feature is also available to less-priveledged users. However, the reason for the change does not have as serious an affect on these users.