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

Ideas in development Here are the implemented LimeSurvey ideas for the 1.91 release.

Automatic tracking of failed email addresses in tokens  
Written by lemeur the 3 Jan 10 at 14:33. Related project: 1.x all. Implemented
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.
5
votes
implemented
Selected solution (#1): SMTP tagging, Probe and SOAP solution
Written by lemeur the 3 Jan 10 at 14:33.
* First of all, email messages sent by LS must be tagged in some way with an message-dest-id
This message destination id is made up of: the SurveyID, the target email address, the token code, and a specific integrity code.
This integrity code is used to make sure the bounce email is not a fake so that we don't disable some valid tokens.
The integrity code would be an ASCII verison of a HMAC of the previous elmeents encrypted with a key containing the token ID (internal element inside LS, and a global value specific to this LS installation and set in config.php).

* the probe will decode the bounced email to read the error message and get the original message-dest-id, then it would send the two data to LS-remote-command (via SOAP)

* The LSRC API will provide a service that would check the integrity and authentication of the message-dest-id and then update the token status accordingly.

Some references:
* Tagging with VERP solution: http://en.wikipedia.org/wiki/Variable_envelope_return_path
* Tagging in SMTP header (my preferred way): http://www.php.net/manual/fr/function.mail.php#78934

See the 1 comments or propose a solution >>

Possibility to select separator for tokes imported from CSV  
Written by puohis the 7 May 10 at 14:47. Related project: 1.x all. Implemented
In Finland and in many other countries other than US use semicolon (;) as a list separator and LimeSurvey can only use comma (,) as list separator (US style) for CSV files.
Would be nice to be able to select which list separator to use, because Windows and Excel are so dummy that you can't select the separator when you are saving file from Excel to CSV. You can change the separator by setting it to Windows locale settings, but that affects all programs.

1
votes
implemented
Selected solution (#2): Configurable in import dialog
Written by c_schmitz the 24 Oct 10 at 02:35.
Easiest would be the option to choose the separator in the import dialog

See the 3 comments or propose a solution >>

bulk creation of dummy tokens  
Written by roB2009 the 2 Dec 10 at 15:47. Related project: 1.x all. Implemented
Idea comes up, thinking about an anonymous survey scenario

Imagine..

a survey should be anonymous, but you should have the advantages of a token based survey (like.. save or finish later on an other Computer).

For that you need to create tokens, export them and send a token to each participant
(it‘s like the TAN of online banking) by .. ok.. sounds funny, by mail! (not email! :-)).

In this scenario the participant would have a good feeling, that it‘s really anonymous.


1
votes
implemented
Selected solution (#1): bulk creation form for dummy tokens
Written by roB2009 the 2 Dec 10 at 15:47.
For that we would need a form in token area with:

„numbers of tokens“

„number of characters“

Press the „Create-Button“ and magic 700 dummy token are in the token table.

Export it, create a bulk letter.. stamps on it or inhouse mail...

Add a comment or propose a solution >>

Fine rules to manage the results  
Written by ludogre the 3 Feb 10 at 11:40. Related project: 1.x all. Implemented
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.
1
votes
implemented
Selected solution (#1): Add "modify results" in the rules option for a survey
Written by ludogre the 3 Feb 10 at 11:40.
If it's possible, add a "Modify/delete" option rule for the survey users.

Add a comment or propose a solution >>