When I import a CSV file into the tokens table, using attribute_1, attribute_2, etc., is awkward, I'd much rather use company_name, website, etc., whatever my fields are.

Then conditions and defaults could use those same names, e.g. TOKEN:COMPANY_NAME

An auto-import function would be nice, something that could take a file like

email,website,company_name,year_founded,industry

and import it into the tokens table, automatically adding any new fields that weren't there.

If Lime Survey is installed in such a way that the root url for the survey is a long character string, the generated SURVEYURL may be longer than the line size of the email program.

This results in the email program splitting the survey link over multiple lines, and in many email programs, these split URL's no longer function (i.e. the portion of the URL that does not fit on the first line is visible, but no longer part of the actual URL). Clicking on such a broken link will lead to a failed attempt to access the survey, frustrating the invitee.

I just had a need to filter my tokens on a specifc attribute, but the search functionality seems only to adress tokens, names and email adress. But my custom attributes was not searched.
Fortunately I had uploaded my tokens in an orderly way, which made is possible to do what I wanted.

I run many surveys that use closed access and multiple token attributes for each user. I recycle several of these surveys over the course of an academic year, or from year to year.

In these surveys, there are several places where some text should change for each run of the survey, but should be consistent within the run. For example, one survey is used to collect vacation travel plans from students. The name of the vacation changes every time I run the survey, but it appears in several places within the survey and in the invitation emails. Similarly, I specify dates (used for input validation) that are the same for all students but change for each vacation.

Currently, I manage this by using a token attribute to specify the text, and refer to that attribute throughout the survey and email text as appropriate. This works, but it requires that I add the text as an attribute to the token for each student, even though it's the same for each student.

I would like to suggest a feature that would create a set of attributes for the survey, in addition to the attributes for each token.

there is only three Attribute must be filled:firstname lastname and email. so it limited much information for survey that the administrator want to know, it is very good for add one more Attribute, and it must be filled.

List-Unsubscribe is a mail message header used to provide machine readable unsubscribe instructions - an email address, a URL or both.

If List-Unsubscribe is present, some mail clients will offer a unsubscribe button and/or unsubscribe option if a user tries to flag the message as spam.

It is a recommended 'best practice' to improve message deliverability and do the right thing for the end user.

Documentation:
http://www.faqs.org/rfcs/rfc2369.html
http://www.list-unsubscribe.com/

Gmail support: https://mail.google.com/support/bin/answer.py?answer=81126#unsub
http://techcrunch.com/2009/07/23/gmail-tries-to-make-it-easier-to-unsubscribe-f rom-spam-newsletters-but-fails/

Microsoft support:
http://download.microsoft.com/download/e/3/3/e3397e7c-17a6-497d-9693-78f80be272 fb/enhance_deliver.pdf
(although may be broken?):
http://blog.deliverability.com/2011/04/has-hotmail-discarded-the-list-unsubscri be-functionality.html

[....]

USE CASE#1

I have a retail customer with an extensive customer database. The customer's Point of Sale (POS) system has the ability to build a URL to build a URL with the customers data.

At the end of each sale, the customers name, email address and perhaps a few user defined fields would be passed to lime survey. The API should return either a success or failed response, and limesurvey should automatically generate the token.

The user then receives the invitation to the survey automatically very soon after they have left the store.

This customers survey is very short NPS type survey. The NPS is most valid the sooner the user can take the survey.

---

USE CASE#2
Another user I have could also benefit. I could create a simple local file on her hard drive that when opened in a browser asks a few simple inputs, does a little bit of error checking on the fields, assembles the URL and POSTS its.

As above she would receive a success or fail return.

Currently she uses the admin interface several times a day to sadd a single new invitation. Again in this case the more timely the invitation to the survey is sent the more accurate the response will be.





[....]

In invitations, the keyword EXPIRY can be used to indicate the expiration date of the survey, but the tokens are usable from 'validfrom' until 'validuntil'.

Furthermore, it is not possible to send an invitation in advance, before the date of 'validfrom' is exceeded.

I would like to give a person who completed a survey a unique code, that they can use to redeem a free item. The code is in the token database, in my case in the Last Name field. So I would like to add, for example TOKEN:LASTNAME replacement field in my End Message text that you can define in Survey Settings. This would then work the same as in the Welcome screen or a question.
I can also seeing it used to display the full name, personalized message, or unique instructions based by token.

Dear LS-Team!

I am using the "Send invitations" with additional parameters and i am never sue, if they are incorporated in the email correctly. this can be quite a nerve wrecking situation, if doing this for a large number of invitations.
Whenever i do this with my testrecords, and have to reimport the token table, i am never quite sure, if i checked all the flds, if i installed all the correct additional attributes...

Currently, LS defaults to display 50 tokens, and it would be good to be able to easily change that setting without going into the PHP file.

I often have surveys with over 50 respondents, and it is inconvenient to always have to change the number of tokens displayed in order to see them all.

Limesurvey's email capabilities are great. One crucial thing is missing though: Email tracking.

If an email adress is wrong I recieve a bounce. Thats great. But what if my email is never recieved? On dedicated servers this shouldn't be a problem - but on shared hosts, were you share an IP adress with severel others, theres is a chance that the IP adress at some point will be blacklisted by some emailproviders.

It could also be that you design your email with lots of pictures and "false" from headings, thus increasing your risc of being caught in spam folders.

But basically there is no way to know if a low response rate is due to lack of interest, og because people never read your invite.

An iterate survey is dedicated to the case where one finds it convenient for the participant to see the survey prefilled with his previous answers when he participates for a t+1 time to the survey. Currently, all previous answers are conserved, without possibility to set some preserved and others eliminated.

Does anyone know if it is possible recover the code responded to a question previously answered? The Comen INSERTANS: SSSSXGIDXQID returns the text of selected item, is there any command that returns the code? This would be useful in a multilingual questionnaire, for each language in the text changes, but the code remained the same.

Currently the system can send out reminder emails, which is great. But the emails which people receive are identical regardless of whether they have already begun the survey (but not finished) or wether they have not begun the survey.

This is a problem because some people actually think that they have finished the surveye - or maybe forgot that the got interrupted. Some of theese people get annoyed when the recieve a confirmation mail.

It would be most wonderful, if one could provide the invitations with a date and/or timestamp in order to define the earliest date/time of posting them to the invited person.

Currently the data import isn't very flexible. The possibility to import data from a ldap data source is basically a good idea but does not fit my needs exactly.

In case of recurring surveys every week it would be a great help if LimeSurvey would provide the possibility of a full data management solution instead of just using tokens from a csv or ldap import.

By default, Limesurvey checks respondent emails so that each respondent can only have one email.
We find that allowing multiple emails, while still checking for their validity, would be a plus.

Having to create a anonymous survey that have to be done once by the user, I use the token management screen that you provide.

Even if the survey is anonymous, the administrator can deduct wich candidate has completed the survey.

First by having an email notification and looking into the token management screen to see wich one of the user has completed the survey.

It's a scretch (if you have a lot of user), but it a risk. (for me at least) but a real treath for the fisrt user who respond to the survey...

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.