[Building Sakai] Non-question page in the middle of an assessment

Karen Tsao ktsao at stanford.edu
Tue Jul 14 22:54:00 PDT 2009


Hi Carlos,

Please see below for my comments:


> My question is: Is it possible to create new question types? Or even a new
> assessment type?
>
You can create a new assessment type. Just go to assessment type page and
add a new one. However, creating a new question type needs to code changes
in couple of places.

This is because the test we have is as follows:
>
>   At the beginning the user goes to a test page, called pre-test, with
>   questions relevant to a particular matter.
>   After, we display some info pages with no questions at all, just text,
>   tables, graphics... about the particular matter. There can be some tests
>   in the middle, but we don't count the punctuation, is just for feedback.
>   At the end, we present that same test as at the beginning - called
>   post-test.
>   After submitting this test, we display a page comparing the answers
>   before and after, and giving feedback for every single question/answer
>   possible.
>   Only the answers from the last tests counts to decide if the user has
>   passed it or not.
>
The closest workaround I can think of is: Add empty parts (part without
questions) between the two sets of questions. Put your text, table, graphics
in these empty parts. For the pre-test questions, set the score to zero
because you don't want them to get graded. However, I don't think there is a
way to display the comparison.

Other problem I'm facing is that it seems that the text fields are limited
> to 4,000 characters,  which is not enough for the info pages and for some
> questions.


This limit is from Oracle's 4000 character limitation on VARCHAR2 fields. If
you use MySQL, you can just increase the length of that column and increase
the validateLength in JSF file. If you use Oracle, other than the JSF
modification, you need to do more work on database side (
http://confluence.atlassian.com/display/JIRA/Using+Oracle+10g+drivers+to+solve+the+4000+character+limitation).
The reason we use 4000 in all database is just to keep the behavior
consistent.

Thanks,
Karen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090714/ab4823ba/attachment.html 


More information about the sakai-dev mailing list