Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Just a little thought that came into my mind when reading your lines:
Quote: "We should discuss if every question should be mandatory in that way that the user has to click at least 'No answer' for a question."
I think it's not a very good solution to force the user to set a question to "no answer". In general every survey admin is happy about the least bit of information from his customers/users. Forcing the user to mark each question he doesn't want to think about it or simply doesn't want to answer for whatever reason will probably make him exit the survey when noticing that he always has to mark "no answer".
Von: limesurvey-developers-bounces@... [mailto:limesurvey-developers-bounces@...] Im Auftrag von Carsten Schmitz
Gesendet: Montag, 26. Mai 2008 11:48
Betreff: [limesurvey-developers] Not answered questions in LS2
I had a short talk to Michael on this subject last week and just wanted
to write down my thoughts on this.
In LimeSurvey 1 we have currently the problem that there is no flag for
This leads to the problem that the results of an unanswered question
does look exactly the same like a question that was not seen or touched
by the user.
So how do we handle different types of unanswered questions? Yes.. there
are different types, lets see:
1) Unanswered because it was not seen due to conditions
2) Unanswered because the user saw it but he/she did not click an option
3) Unanswered because the user marked it as 'No Answer'
None of these cases is easy to grab. Why?
to 1.) Unanswered because it was not seen due to conditions: This should
be marked in the result output as 'Not seen' because any 3rd party
program ( to where the results are exported to) does not know about the
conditions/branching. I propose to fill these database fields with
'NULL'. Not recording anything is an option when the export does handle
it accordingly but makes it alot harder to do SQL evaluations right on
the result tables.
to 2.)Unanswered because the user saw it but he/she did not click an
option: Does sound easy? Yes.. you could just fill the databse field
with an empty string.. But what about single option radiobuttons? You
cannot un-check them in case you have accidentally clicked an answer
option. This is strongly connected to option 3:
to 3.) Unanswered because the user marked it as 'No Answer': So do we
force the user to mark a no answer then? Letting the 'no answer' option
be a normal choice and record it accordingly may bite with the
Some solution proposals:
Case1: NULL on export/database
Case2: Some kind of 'not-touched' flag on DB save/export to indicate the
user did ignore the question?? Especially with default question this is
a problem. Remember that the non-touched flag will also be important in
the future to catch 'survey racers' who run through a survey and don't
click anything or just click anything to get through with it. We should
discuss if every question should be mandatory in that way that the user
has to click at least 'No answer' for a question.
Case3: Non-Mandatory question should always have an "No Answer"
Any thought, opinions on this? It would be great if we can design this
from the start as future-proof as possible
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
limesurvey-developers mailing list