It's a ZClasses thingy to make multi-page surveys or quizzes. Use this only if you really need to get a multi-page survey up online quickly. If you want lots of customization, use Formulator.

QSurvey automatically creates a "RESULTS" folder and saves the results of submission in the ZODB.

Version 0.31 requires Zope-2.5+

V0.31 currently breaks existing QSurveys. You have been warned.

New with version 0.30

• Uses Zope-2.5's Session Tracking and commits save at the last page. To make this happen, create a final QPage, and on the Button_Text tab, set submittext to "", i.e., nothing. This is a good place to say "thanks for completing the survey."
• Guesses IP address, particularly will use http-x-forwarded-for if available.
• Still saves only to the ZODB, but should be easy to modify to save elsewhere by changing the filethedatapersistent method of QSurvey:QSurveyClass
• More of the logic is in Python Scripts; easier to figure out what is going on.
• By popular request, style sheet is localized to the instance rather than the class.
• More things are allowed within QPages/QSurveys for flexibility. Particularly, you may put a QSurvey within a QSurvey. We used this for rudimentary managing of a bilingual survey.

There is a wiki page about QSurvey in the zope-edu Wiki. Zope.org members may now give me persistent! feedback about QSurvey.

The product is designed to make on-line surveys easy to write. Instead of having first to develop the backend for the storage, then adapt the questions to the storage available, this product allows you to concentrate on the survey and its questions. Zope takes care of the storage.

The page-centric model with optional branching determines at run-time which page to display next.

If you need more than simply questions, you may include DTML Document material interspersed with your questions. This means that Images and other content are allowed inside a QPage.

QSurvey features:

• A page-oriented model, with the QSurvey holding QPages, and QPages holding DTML Documents and Questions.
• Multi-page interaction is possible with branching dependent on the values of a multiple-choice question.
• All Multiple-Choice are a single type. Select listbox, radio, checkbox, formatting from a single "options" tab.
• Ordering of things within a page from a management tab in the QPage object.
• Uses css instead of tables. Looks very nice in IE4+, Mozilla. Acceptable on NS4. Degrades nicely for Lynx. Deliberately ugly default css provided to encourage customization.
• Pays attention to AUTHENTICATED_USER for results ID creation
• Still does no validation.
• Some hooks do nothing yet
• RESULTS available in various tab-delimited formats.
• Still too much global Add-list pollution (2 items: QSurvey, QPage, TextQuestion, MultipleChoiceQuestion)
• Each survey writes only what is actually submitted to the ZODB.