Status Report August 10, 2006

Here's a synopsis of the current status of the questionpool import code and some additional issues I'd like to resolve before release to collab:

• Import pool function works on the same asi design as import assessment
  I've imported 2 translated Respondus files, with 60 and 240 questions successfully. These files were translated to the simplest, compatible format, i.e., sans the quiz settings, but still Samigo-specific. The assessment name is assigned as the pool name and the section data is ignored. Both quizzes were all multiple-choice questions.
  I also exported a single-section, multiple choice assessment and successfully imported it as a question pool.
  An import with more than one section does not get imported at this time.

• Question pool imports are limited to a single section at this time
  The limit is based on the fact that decisions need to be made about a subpool import structure. From the xml samples I've received to date for Respondus and BlackBoard, their exports are single section, so this should not be a migration issue. I need more information/samples from outside systems to see if there are other precedents/strategies for QTI-compliant multi-section qpool imports. QTI documentation is not helpful here (until we add content packaging.)

• Better error handling is needed
  The current import process does not handle import failures well - the messages are cryptic. The most common failure is trying to import an xml file that is not well-formed. Other errors occur with odd characters which might just be a problem with my local system. I also need to add an error message if an import with multiple sections is attempted. I'll implement a minimum of messages for now with an eye to improving them as I go.

• GUI review with Marc needed
  I simply added a left-aligned import link after Add New Pool. The import link goes to an import pool screen like assessment. After import, the pool returns to the main Question Pools screen. I'll get screen shots to Marc and see how he wants to handle the design approval process.

• Code Delivery, Code Review and Testing
  I'm using a local svn 2.2 trunk to save my code changes. The files need to be merged with current trunk for testing on your end. I'd also like you to review the code since I'm a newbie. Please catch anything that's awfully bad!
  I need to merge with our local 2.1.x trunk for testing at Davis. Code testing needs to be done to validate that all the currently importable question types are imported currectly. Rigorous testing is needed - and the best source of importable xml files are existing assessments.
  Also, I need to get a test to Megan prior to collab QA testing and suggest to them how to get pools for import.

• Release Timing
  Most of the steps above must be completed before releasing to collab, so you can see it may be a few weeks yet.
  A major issue for releasing to 2.3+ would be the value of the release. I'm not sure how many faculty would want to import their quizzes into a question pool, although it does beat importing each question singly!
  The question would be whether to go ahead and release or wait until either question pool export or import from Respondus (or BlackBoard) is also completed. I guess I can bring this up in the assessment and dev lists an see what responses I get.

• Documentation
  Do you want me to start documenting my progress in confluence? I'll be noting this info in Davis' for our team, but it might be helpful to the community to see what's going on.
  Reviewing the code has brought up other issues like error handling, new question types, etc., which I'd like to document as I go so I don't lose track. I also need to do a jira review to see if there is anything I can fix while I'm working on import/export code.