It's more productive to show and review all conditions in a admin page.
Mantain them from there (Edit, add, delete) is considered a plus.

As we know, there are may applications and games are become more and more popular with the integration with Facebook.

If we can make LimeSurvey become a widget, then it would make LimeSurvey become more easy to integrate with SNS or open source applications, such as Joomla, WordPress, etc.

I have tried many survey systems, but I didn't find any survey system with LimeSurvey powerful features is social media oriented.

What I mean is we need to leverage the user base from Facebook, Twitter, Gtalk, MSN, Yahoo or any other instant messengers or SNS.

For example, I have to conduct an academic or business research, it's easy to build up survey with the powerful LimeSurvey, but it's hard for me to distribute the survey to my friendlist on Facebook, Twitter, Gtalk, etc.

Therefore, if we have the invitation feature, and it would be easy for me to send an invitation to my friends on my friend list.

Since my friend take part in my survey, I do hope there is a reward feature to give them a certain market place points that they can use to exchange cash or coupon or voucher, so as to encourage their contributions.

And also it would be better if the reward feature has question level marketplace points and survey level market place points. For example, some questions worth 5 points, but some questions worth 30 points, or I can set the whole survey worth 300 points no matter how many questions in the survey.

If we have survey invitation and reward feature, then the survey system could be more social media oriented, it would attract many academic or business institutions to set up survey, invite friend from their friend list on SNS or IM, and reward contributors with marketplace points (such as eBay bucks) and get the survey results.

Looking forward for your reply!

Place all answers in confirmation E-Mails and produce no error, if a question wasn't answered.

I would like to see a tool that could toggle the "Mandatory" setting on all questions in the survey from "on" to "off" and vice versa.

This would make the Q/A process on long surveys much easier - one wouldn't need to answer every question just to check a fix on page 16 of a survey.

Nowadays, all research with human subjects require informed consent and authorization. The use of a program such as LimeSurvey in academic, government, or business environments require a mechanism of informed consent. In the specific case of academic environments, Institutional Review Boards WILL NOT APPROVE any type of research with human subjects without a mechanisms to verify the informed consent. Restrictions such as this are already found (or likely to be found in the near future) in government, medical and some business settings. Usage of LimeSurvey in academic--or other-- settings will be hindered by the absence of this kind of functionality.

For 'us psychologists' (researchers) it is often necessary to randomise participants over 'conditions' (in the research sense, not in the LimeSurvey sense). For example, we may want to present 50% with group 3 and 50% with group 4. To make matters a bit more, eh, challenging, it can sometimes be useful to make this randomisation dependent on earlier answers (i.e., only randomise participants with a certain profile; present all others with group 5), or to randomise different proportions of participants to different groups (i.e. 60% to group 3, 20% to group 4, 10% to group 5, and 10% to group 6).

So I thought it would be pretty cool if that could be implemented :-)

When creating / testing / editing a survey mandatory question are really annoying. I can think of these situations where making questions of a survey (temporary) non mandatory will be a great improvement:

1. (Developer) Testing possible bugs
When importing a survey for testing mandatory question can drive you nuts.

2. (User) Previewing a survey which is in development
You just want to take a look at the questions and survey design, having to answer all mandatory questions is a mess.

Some surveys can be very complex.

For my last survey, I had a committee deciding the groups and questions. We used FreeMind to come up with our structure.

I believe that all question types on a survey should allow for mandatory enforcement which this question type currently does not. Since it doesn't and people taking the survey might not answer a question of this type, either on purpose or by accident there is no way to ensure data integrity. At the very least, if the question cannot enforce the mandatory option that option box should not be available in design mode. It allows an unsuspecting survey designer to include what could be a key question and not realize it could be bypassed and save what I assume would be a "0" answer even though it was not a respondant's intention. In some ways, this question is similar to a simple Y/N question. If the respondant clicks the next button without ever clicking one of the two options on a Yes/No question, the mandatory test stops you from proceding and warns that the question was unanswered. I would think the (Multi Flexible) (Numbers) checkbox layout question type should behave in the same manner. I have had students take surveys and have missing, potentially incorrect answers because the (Multi Flexible) (Numbers) checkbox layout questions will proceed even though they did not select any of the options and clicked the next button. However, I did set the question's mandatory option equal to yes.

Currently responses are checked on the client. But HTTP can easily be tampered such that arbitrary values are sent to the server. (E.g. the value 5 when only 1 to 4 is allowed.)

I am developing a questionnaire in LS 1.86.
At certain points it requires a branch/jump to another point in the questionnaire, dependent on the answer to the current question.
It may have to jump back and redo a an earlier set of questions, or jump ahead and skip the next questions.

This is critical for my application!

I'll need as administrator of LS the ability to choose which languages will be available to use in LS. Since certain languages I'll never use so there is no need to let users choose.

Hi,

we are using Limesurvey since the beginning of this year and the number of surveys increased. For administration the list of surveys becomes more and more confused. It would be great if one could organize the surveys in folders to have them organized depending on what belongs together.

I would like to be able to create different categories for surveys.
Currently, the surveys are only split into two categories, Active and Inactive.
I would like to be able to put these in their own categories.

I think sometimes it is useful to have possibility to have "one questions, one page" for the first part of the survey; and "more questions, one page" for the sopio-demographic questions.

So it will be useful to display questions in these different ways, in differen section of the same survey. If questionnaire requires it.


Regards,
Arnaldo

Making conditions in LS are very time consuming. I hope the following standard condition actions could be implemented:

if condition is true/false then jump to
- next question
- selected question in group
- next group
- selected group
- finish

This is really useful when a lot of questions have to rely on answer on some previous one.

The existing condition rules are only useful when asking a very few additional questions, as the condition has to be entered as a rule to each question.
--
Pål Monstad

There are some survey results needed to be handle as soon as posible. For example, sales leads or dissatisfied customer feedback. If customers took the survey and willing to leave their personal information for sales contact, system should send the notification email to admin as soon as possible. Sometimes in customer satisfication survey need this alert also. If system can send alert email when customer click dissatisfied rating, agents can handle their complain immediately.

Create a system for designing and running conditions. These can be used for survey branching, conditionally hidden/generated questions, filtering records etc.