Written by bverhaegh the 7 Oct 09 at 15:18.

the idea is to create a timer that creates tokens en send these customers the survey automaticly.

allso with big surveys, this can be used auto email the survey to groups 100 each time to avoid spam problems.

the idea is to create a timer that creates tokens en send these customers the survey automaticly. allso with big surveys, this can be used auto email the survey to groups 100 each time to avoid spam problems.

Written by freddekkers the 22 Apr 10 at 16:56.

I am no programming specialist, but i hear that there are java aps to perfom this task

I am no programming specialist, but i hear that there are java aps to perfom this task

Written by marcvangend the 5 Mar 10 at 12:20.

Some research needs to be done to decide what should be integrated and how that can be accomplished. I think the most important is to synchronize or share the users:
- from Limesurvey, Drupal users could be invited to fill out a survey;
- users of a Drupal site could fill out (and create?) surveys without logging in again (single sign on);
- a logged-in user could see in Drupal which surveys are available for him.

At least, a Drupal module would be needed. Depending on the architecture and API's of Limesurvey2, a module/mod/plugin/addon for Limesurvey might be needed as well.

Some research needs to be done to decide what should be integrated and how that can be accomplished. I think the most important is to synchronize or share the users: - from Limesurvey, Drupal users could be invited to fill out a survey; - users of a Drupal site could fill out (and create?) surveys without logging in again (single sign on); - a logged-in user could see in Drupal which surveys are available for him. At least, a Drupal module would be needed. Depending on the architecture and API's of Limesurvey2, a module/mod/plugin/addon for Limesurvey might be needed as well.

Written by hardzsi the 15 Mar 10 at 14:29.

In case of Typo3 CMS, an existing and published survey can be integrated into its frontend via iFrame technology (after installing an iFrame-enabler extension, eg. Flexform based IFrame (ffiframe)). Similar solution can exist on Drupal or other CMSs as well.

For the integration of admin part of LimeSurvey as a CMS module, i cant't see much benefit from.

In case of Typo3 CMS, an existing and published survey can be integrated into its frontend via iFrame technology (after installing an iFrame-enabler extension, eg. Flexform based IFrame (ffiframe)). Similar solution can exist on Drupal or other CMSs as well. For the integration of admin part of LimeSurvey as a CMS module, i cant't see much benefit from.

Written by onderzoekspraktijk the 19 Nov 09 at 23:49.

Of-course more importantly it needs some coding of the used software. I tried it but it is beyond me.

Of-course more importantly it needs some coding of the used software. I tried it but it is beyond me.

Written by c_schmitz the 19 Oct 10 at 11:59.

Create a new setting to hide the Welcome page.
The end page problem will be resolved by conditioned text blocks.

Create a new setting to hide the Welcome page. The end page problem will be resolved by conditioned text blocks.

Written by apps the 2 Feb 10 at 10:06.

show_tics = 0 (default). Just as it is.
show_tics = 1 : the slider shows tics under the bar, between the slider_min and the slider_max values.

show_tics = 0 (default). Just as it is. show_tics = 1 : the slider shows tics under the bar, between the slider_min and the slider_max values.

Written by tringate the 20 May 10 at 14:53.

Add a column in the survey list screen to give estimated survey table size.

The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color.

Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept.

...regarding survey size
Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.


•MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
•MySQL InnoDB: Maximum number of 1000 columns

Add a column in the survey list screen to give estimated survey table size. The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color. Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept. ...regarding survey size Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table. •MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB. •MySQL InnoDB: Maximum number of 1000 columns •MS SQL Server 2000: Maximum number of 1024 columns •Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See Installation FAQ and PostgreSQL FAQ. The mySQL ISAM engine is the most tricky one. As it allows only up to 65,535 bytes per row and utf8 characters can require up to three bytes per character the maximum may be only 21,844 characters (but this depends on your DB encoding). You can roughly calculate the size of your survey like this: •Every multiple numerical question: 20 chars for each answer •Every multiple choice & array question answers: 5 chars for each answer •Every other question type: 5 chars •Add 10% for the usual overhead

Written by evan the 28 Apr 10 at 05:04.

In the 'Edit survey settings' > 'Presentation & navigation' tab add a yes/no drop down titled "Display question codes" This would then be checked when populating the template then apply if 'yes'

In the 'Edit survey settings' > 'Presentation & navigation' tab add a yes/no drop down titled "Display question codes" This would then be checked when populating the template then apply if 'yes'

Written by fingerprn the 3 Feb 10 at 22:12.

Right next to the Export Survey Structure button, add a Copy Survey button. When you click on it, it asks for a new survey name. Click on that and it creates an exact duplicate (except the survey name) of the current survey structure and design. From there, you can open the new "inactive" survey and make any necessary changes.

Right next to the Export Survey Structure button, add a Copy Survey button. When you click on it, it asks for a new survey name. Click on that and it creates an exact duplicate (except the survey name) of the current survey structure and design. From there, you can open the new "inactive" survey and make any necessary changes.

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?

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?

Written by holch the 26 Feb 10 at 02:31.

In times of Google Gears and HTML5 I was wondering if it would be possible to use the survey offline?

Tine20.org for example is using Gears to make the application usable offline. Or Gmail, etc.

I am not sure if this is possible with a very complex and flexible tool like Limesurvey, but maybe it is?

In times of Google Gears and HTML5 I was wondering if it would be possible to use the survey offline? Tine20.org for example is using Gears to make the application usable offline. Or Gmail, etc. I am not sure if this is possible with a very complex and flexible tool like Limesurvey, but maybe it is?

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.

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.

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.

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.

Written by leolime the 6 Feb 10 at 19:09.

To have a button same as the Question Preview a Question Group Preview-Button.

To have a button same as the Question Preview a Question Group Preview-Button.

Written by oddible the 29 Sep 09 at 17:53.

1) Provide a mechanism to better codify and search for Label Sets

a) a field for number of answers so people can find the 13 point Likert scale that someone else created for instance (~cringe~)

b) a catalogue to explore labelsets and

c) a field for descriptive keywords for each labelset rather than relying on the labelset names.

d) a Labelset search

1) Provide a mechanism to better codify and search for Label Sets a) a field for number of answers so people can find the 13 point Likert scale that someone else created for instance (~cringe~) b) a catalogue to explore labelsets and c) a field for descriptive keywords for each labelset rather than relying on the labelset names. d) a Labelset search

Written by izahn the 16 Oct 09 at 07:11.

I agree that label sets tend to become a problem. One way to address this is to have a system where each user manages their own set of labels. This could work as follows:

1) Each user has their own list of label sets

2) Have a global list of label sets that consists of the combination of all the individual user's label sets

3) Users can copy label sets from the global list into their personal label set list.

This way each user is not overwhelmed by the clutter of label sets that tends to accumulate, but can access the master list if they want to.

I agree that label sets tend to become a problem. One way to address this is to have a system where each user manages their own set of labels. This could work as follows: 1) Each user has their own list of label sets 2) Have a global list of label sets that consists of the combination of all the individual user's label sets 3) Users can copy label sets from the global list into their personal label set list. This way each user is not overwhelmed by the clutter of label sets that tends to accumulate, but can access the master list if they want to.

Written by jumper51 the 12 Feb 11 at 20:38.

Allow the administrator to write his own conditions in either javascript or php! Maybe a security issue, but the admin could enable or disable this feature for certain users and groups! This would solve other familiar problems as well!

Allow the administrator to write his own conditions in either javascript or php! Maybe a security issue, but the admin could enable or disable this feature for certain users and groups! This would solve other familiar problems as well!

Written by izahn the 16 Oct 09 at 07:24.

I don't think time stamps are the way to go. Just calculate the actual time spent.

It's actually kind of complicated I think.

1) If presenting one-question-per-page, have a question attribute "record time".
2) If presenting one-group-per-page, have a question group attribute "record time".
3) Store the value in a field named "QUESTIONID_time" if survey is presented question-by-question or "QGROUP_time" if survey is presented group-by-group.

If you have these all turned on in question-by-question presentation mode then you've just doubled the number of fields in your data set. So I don't think this should be and option at the survey level, only at the group/question level.

A related request is to set time limits for questions/question groups. After the time limit has expired the survey moves on to the next question/question group.

I don't think time stamps are the way to go. Just calculate the actual time spent. It's actually kind of complicated I think. 1) If presenting one-question-per-page, have a question attribute "record time". 2) If presenting one-group-per-page, have a question group attribute "record time". 3) Store the value in a field named "QUESTIONID_time" if survey is presented question-by-question or "QGROUP_time" if survey is presented group-by-group. If you have these all turned on in question-by-question presentation mode then you've just doubled the number of fields in your data set. So I don't think this should be and option at the survey level, only at the group/question level. A related request is to set time limits for questions/question groups. After the time limit has expired the survey moves on to the next question/question group.

Written by hardzsi the 26 Sep 09 at 15:37.

Store at least TOTAL. If possible, PERC and ASSESSMENT_CURRENT_TOTAL too.

Store at least TOTAL. If possible, PERC and ASSESSMENT_CURRENT_TOTAL too.

Written by c_schmitz the 8 Aug 11 at 13:22.

I think it is not the best way to store a score that may be subject to changes when editing a response. Best would be to calc the values during export.

I think it is not the best way to store a score that may be subject to changes when editing a response. Best would be to calc the values during export.