Quiz development ideas

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by westwesterson on December 1, 2007 at 7:26am
Last updated by renu_mughal on Tue, 2008-04-15 08:52

This is a list of features that it would be nice if quiz had. These have no time-frame on them and are purely speculative, but simply a listing of what might help quiz along for future development. Note that the nature of this stuff is to change over time, and these are speculation, and may never be actual modules.

Extensible and robust question type api.

should account for different possible question types. Some question types might be:

matching
reg expression matching
math problem with randomly generated numbers
math problem utilizing advanced syntax functionality
fill in the blanks (I have already finished this and working fine on my website)
essay/short answer which is to be graded by humans.
  • +1 to all of that! [webchick]


adding question types often seen in e-learning development tools:

Questions:
- true/false
- multiple choice (radiobuttons)
- multiple response (checkboxes)
- Fill in the blank ( I have already finished that and working fine on my website, want to know more of it then just mail me.)
- Matching via drag & drop
- Matching via dropdowns
- Sequence (sorting) via drag and drop
- Sequence via dropdowns

Survey questions:
- Likert scale (-- | - | +/- | + | ++)
- Pick one…
- Pick Multiple…
- Which word
- Short answer
- Essay
- Ranking with drag & drop
- Ranking with dropdowns
- How many…
[yoroy]

What quiz api should be able to handle (examples not extensive):

So the api should be able to handle if the question is ready for grading on quiz submit, and it should have some way for the question type to tell the quiz module if the question was correct or if it failed. If a certain question has a higher point value than another this should be handled in quiz. But if a particular answer is only worth half credit, then this should be allowed for in the api. Multichoice should also be moved to the api. And this api should be documented. A bonus would be to finish the long unfinished matching.module a bonus to that bonus would be to integrate the matching module with jquery. Other possibilities with a robust api are integration with cck.

Separating the api/framework from quiz specifics:

The api could be abstracted into it's own module with basic quiz framework, and then you could install either quiz or trivia, and use the same framework, but you could choose whether you wanted to use the full quiz module.

Areas of great usefulness

cck question types

these little suckers would bring a million times the flexability of the current framework.
  • Agreed. I've sometimes thought that quiz question types should just be CCK fields so that there's no new APIs for developers to learn, but I'm not sure how well that would work in practice. One of the initial specs in this module was the ability to community-review questions, and you can't tag/comment on/author/etc. a CCK field. [webchick]

better developer documentation for question type modules.

Added developer documentation means that creating a new question type module will be a lot easier.

jquery based timer

an often requested feature, this timer would automatically close the quiz after the time limit has been reached.

workflow/workflow-ng

Implementation of one of these modules, and also triggers/actions with drupal 6.0 this adds a lot more functionality to the quiz module.

Human Grading Interface

We need a system for humans to go in and grade questions, maybe they noticed a typo on a quiz, which means certain answers marked as wrong are actually right, maybe they took an essay question, which needs to be graded by a human. This should be a part of the quiz api. where question modules can specify how to grade questions. And it should set a flag either requiring human grading, or allowing the user to select human or computer grading. Also an optional default grading type in the api.

blocks

maybe a block with the user's latest quiz scores, or the overall highest scores on all quizzes. This is now possible with quiz views, but we could add defaults which do these things, or create code versions which don't require the views module.

  • I prefer the default Views option, personally. Whatever we guess people are going to want out of the box, it's probably going to be wrong. :) [webchick]

  • I agree, i think this can be handled by views. If you want interesting ways to display data from the quiz module, views will be a prerequisite, but if you just want an easy to use quiz interface and don't care much about how your data is organized, don't enable views. I just might make a GHOP task out of this one. [westwesterson]

drupal 6.0 upgrade

This should probably be done sooner rather than later. The increased functionality with views makes the quiz module more attractive already, but being one of the first modules released will hopefully get quiz more exposure and more developers.

  • We're somewhat stalled in this area on the Views 6.x port... see http://groups.drupal.org/node/7206 for more details. However, we could always port without Views integration at first. [webchick]

  • Depending on how long views takes we may upgrade without it. The goal is to start work on a drupal 6 upgrade after we launch 2.0 [westwesterson]

Quiz

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: