It's very usual to find users submitting the form with mandatory questions unanswered. Then the page gets reloaded again with a change of css to point out the such questions. The problem is when a survey page is too long with more number of questions then the user needs to scroll all along to find out what he missed. This is fine but a better alternative can be thought of.

Every now and then we find incomplete surveys.
The user might get bored in the middle (happens usually for long surveys) and/or close his browser window (can be sometimes unexpectedly ) which results in incomplete survey.

I use the same survey, except for a few small changes, with different groups of people. I'd like the ability to just click a button and copy a survey, including questions, layout, etc., without needing to use the import/export feature.

Drupal is one of the most popular open source CMS'es, but it's not geared towards complex surveys. I think that both Drupal and Limesurvey would benefit from a Drupal-Limesurvey integration module.

When you want to style question for an individual survey you have to manually include a css file or edit the overall template. It would be nice to have additional, surveyspecific CSS in a separate CSS file that can be edited from the survey screen instead of from the template editor.

Many shared hosting providers have an hourly limit on how many emails you can send out.

To manage this limit, you have to babysit LimeSurvey and press the button in batches.

If you exceed the hourly limit, bunches of emails will not go out and often you will receive bounced email messages. It is a mess to determine who did get your invitation / reminder and who did not.

I was thinking about this quite a while already. It is not always possible to do a interview online (CAWI) or via telephone (CATI). When programming is necessary CAPI comes into the game.

However, most CAPI-Tools are old and boring and additionally you have to have still another program.

However, wouldn't it be greate to be able to use Limesurvey for all those purposes. However, even with UMTS/3G it is not always possible or reliable enough to do it with a online survey tool.

We have a survey that requires participants to fill in a time sheet. We would like to show them the total hours for each task. We also need to record these totals in the survey results.

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.

In many surveys in organisations, it's considered important that each respondent only replies once. Therefor, you use a token in order to allow each respondent to fill in a survey only once. However, it is now possible for a respondent who has saved his/her form, to start a second. The record created by the first, unfinished form is not removed from the database. As it is an anonymous survey, it's not possible to identify this record. If you want to guarantee the uniqueness of each respondent, there is no other option but to throw away all unfinished records, in which case you also remove records of respondents who had other reasons for not finishing the survey.

A new use case:
the client wants to validate and approve all questions textes before giving GO/NOGO to the launch. This includes also: question help text.

Rationale:
This is a likely checkpoint in a project. Since the questions are to be delivered to users, the client requests a final REVIEW/APPROVE to validate the textes before the launch.

The same applyes to groups. This time, the to-be-approved textes are: group title, group description.

Being able to edit the textes on-the-fly is considered a plus.

I have a preview for a single question which is really helpful.

I would like to have as well a preview of a Question Group. This would help me to get an idea about the order and being lost in details. Would help especially for those questions at the end of a survey.

Survey settings is composed of 2 pages:
1 Survey configs, with tuples (name-value) .e.g. Allow Saves Y/N
2 Survey textes, with survey title, welcome, endmsg.

The first part of settings are set at start of your work with a survey, and rarely fixed later.
The behaviour of a survey is technical choice, with a tendency of no change over time.

The second part is very frequently used, I believe it stays at the same level of questions and aswer, often modified for the same aesthetic or pratic reasons.

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.

SAS is a powerful statistics application that's pretty broadly used. LimeSurvey already supports exporting results to R and SPSS, which are good packages, but many of our users prefer to use SAS.

We'd like to see support for exporting LimeSurvey data into a format SAS can use, as has been done for SPSS and R.

In older version of Limesurvey, it was possible for the author of a survey to manage the results (delete and modify the results).

In the 1.87 version, it's now impossible. The user have to be super-administrator to do this.

Tics (aka tic marks) should be visible under the slider bar.

See this sketch: http://img38.imageshack.us/img38/5295/10403feb10095848.gif

benefits: easy read, make it clear it's a slider with discrete values, catch where the handle is in respect to left and right limits.

Details:
type = multiple numerical input
options:
use slider layout = 1
slider min = 0
slider max = 10
slider accurancy = 1

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.

Limesurvey tokens already have a field named token status that takes the "OK" default value. When this field is updated withj any other value, the token email can be automatically bypassed by LimeSurvey invitation/reminder process.

The goal of this idea is to design a new process that would make it possible to an external probe script, to send a failed-email-address notification to LimeSurvey so that the token status is automatically updated (right now this is only a manual update).

The probe script is external to limesurvey since its operation depends on the mail-server system used by the Administrator Bounce address.

Special care must be take to prevent anyone on the internet from sending a specially crafted fake bounced email that would disable valid tokens.

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.)