Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Popular ideas Here are this month's most popular ideas about 1.x all.

Individual CSS for each survey  
Written by mdekker the 1 Mar 10 at 10:42. New
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.
1
votes
up equal down
Solution #1: Include a surveyid.css
Written by mdekker the 1 Mar 10 at 10:42.
Have the template check if a .css exists and include it when it does. (could be generated for a new survey but left blank initially)

Add an edit survey css button to the survey toolbar where one can jump to a special template editor screen where you can edit this sid.css
Would be nice if there were links in the screen to point people to the appropriate item in the wiki for help.

Add a comment or propose a solution >>

Email throttling like PhpList  
Written by GregB the 28 Feb 10 at 23:59. New
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.
1
votes
up equal down
Solution #1: Email throttling similar to PHPList
Written by GregB the 28 Feb 10 at 23:59.
PHPList is an open source newsletter package that I use to keep in touch with my subscribers.

It has an email queue that automatically works through batches of emails until it has sent all them all. The email queue can process automatically using cron jobs.

Since PhPList is open source and LimeSurvey is open source, maybe PHPList would share some lessons learned and allow sharing of some of theri current code?

Add a comment or propose a solution >>

How to visualize questions, logic & conditions  
Written by GregB the 16 Feb 10 at 23:28. New
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.
-2
votes
up equal down
Solution #1: Visual Question Tree using MindMap structure
Written by GregB the 16 Feb 10 at 23:28.
It would seem to me that someone very smart person could make some script to convert survey data into mindmap data.

This would be a straight export from LimeSurvey to the mindmap data structure.

Branches can be colorcoded to denote conditions.
1
votes
up equal down
Solution #2: Solution #2: Use a normal "folder visualisation"
Written by holch the 5 Mar 10 at 18:59.
I agree that the MindMap Structure wouldn't really work.

But I know some survey tools, that use a kind of "folder structure" as we know it from file explorers, etc.

I think this can display filters and so on pretty well. At the moment Quotas, Filters, and questions are somehow displayed very seperate and it difficult to get a good overview of the survey (I do agree with the GregB here).

But with the folder tree, you can show loops, filters, pages/groups and questions, which can be especially helpful for long and complicated surveys.

See the 1 comments or propose a solution >>

Totals fields for Array (Multi Flexi) (Text) (numbers only)  
Written by evan the 25 Feb 10 at 01:42. New
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.
0
votes
up equal down
Solution #1: Add three additional attributes for Array (Multi Flexi) (Text) (numbers only)
Written by evan the 25 Feb 10 at 01:42.
1 it might be worth making the question Array (Multi Flexi) (Text) (attribute: numbers only) into it's own question type

2 add the following attributes:
Show totals
* row = total for each row (an additional column)
* col = total for each column (an additional row)
* both = totals for both columns and rows (an additional row and column)

store totals in results
* 1 = store column/row totals in results

Grand total
* 1 = show grand total only
* 2 = store grand total in results (do not display)
* 3 = show grand total and store in results

Java script would calculate totals for columns/rows and would be able to hand negative numbers and floating point numbers.

for visual example see
http://apps.acu.edu.au/~evanw/LimeSurvey_custom-q-type_array-mulit-flexi-text-n umbers-only.html

Please ignore styling as this should be done with CSS.

I can help with the HTML side but can't help with JS, DB LS admin stuff.

Add a comment or propose a solution >>

Guide a respondent towards his/her saved questionnaire  
Written by leonievanrijn the 15 Feb 10 at 09:25. New
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.

0
votes
up equal down
Solution #1: Cookie placed when saving a form
Written by leonievanrijn the 15 Feb 10 at 09:25.
The proposed change: place a cookie when saving a form. The cookie blocks the possibility to open a second form and informs the respondent that he/she should open the link in the received email.

Ofcourse cookies can be removed if you really want to fill in a second form, but at least it will bring awareness to those who forgot they saved the form.

Redirecting a respondent to the saved form is also important because it makes the tool appear more reliable.

Add a comment or propose a solution >>