LimeSurvey Manual - User contributions [en]

Manage users

2017-02-20T19:25:59Z

RsmokeUM:

<languages />
<translate>

__TOC__

= User management= 

==Create users== 


To create a new user open the user management ("Configuration" -> "Manage survey administrators")ː


[[File:LimeSurveyBenuzerVerwaltung.jpg]]


[[File:LimeSurveyAddUser.jpg]]
* Enter the desired username into the textfield '''Username'''.
* Enter the email address into the textfield '''Email'''. Please note
** If you don't want the user to receive the confirmation email with a link to the LimeSurvey installation, username and password you can use your own email address to send the confirmation email to you. After that you can change the email address to the address of the user.
** LimeSurvey sends out a confirmation email to the address entered into '''Email'''. This email address will be used as standard contact email address for surveys created by this user.
* Enter the users full name into the textfield '''Full name''' . Please note
** The full name entered here will be used as standard contact person name for surveys created by this user.
* Click '''Add user'''


So you created a new user. You will find out more about setting user permissions if you continue reading further.

==Edit users== 


You can use the pen symbol to edit a userː


[[File:LimeSurveyBleistiftSymbol.jpg]]


You can set a new email address, full name and even change the password. If you have finished what you want to do click '''Save'''.

==Delete users== 


To delete a user account simply click the trash button in the line with the user account that should be deleted and hit '''OK'''.

=Global permissions= 


Global permissions apply to the whole LimeSurvey installation. If you want to set permissions only for a specific survey you can use the Survey permissions settings.

==Setting global permissions for a user== 


To set global permissions for a user just click the lock symbol.


[[File:User_global_permission.png]]


[[File:User_global_permission_complete.png]]


{{FeatureChange|2.05}}


The system use CRUD (Create, read, update and delete) like the Survey right setttings. Check the first input check all the line, you can give less or more right for each system.


You can now add or remove the following rights.


* '''SuperAdministrator''': This right can only be added or removed by the user called '''admin''' and grants full rights to the whole LimeSurvey installation. '''Please note:''' This right is very powerful and you should be very carfefully with granting this right.


* '''Surveys''': This give the access to all survey. To allow a user to create and manage his survey, you need only to let the user to create survey. The creator of a survey is the owner of this survey : this give him all access to this survey. Remind each survey can have specific permission, the global permission is read before survey specific permission.


* '''Settings & Plugins''': With this right a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings. This allow too to manage all plugins.


* '''Users''': Having this right a user can create new users and delete users created with this account. The newly created users cannot have higher permissions than the parent. If this has to be done a '''SuperAdministrator''' has to grant the rights.


* '''User groups'''


* '''Templates''': It allows the user to use all design templates and edit all non standard templates. A person with this right should have sufficient knowledge in terms of HTML/php, Javascript and CSS. If a user not familar with this things should use a specific design template it would be better to give him only acccess to read permission. Each template can have specific permission.


* '''Label sets''': This right grants rights regarding label sets (create, update , use (view/read) and delete). The label sets don't have specific righth.


* '''Participant panel''': see [[Central participants database]]

==Setting template permissions for a user== 


With template permissions you can set which design templates a user can select when creating or editing a survey. It might be a good idea to restrict the design templates a user can select in order to prevent unwanted use of design templates not suitable for a user/survey.


'''Please note:''' If you have a specific design template for a group of users or customers you might want to restrict the access for them to use only the template created for their purpose.


To set/edit the template permissions for a user simply click the pen-and-lock symbol for design templates


[[File:LimeSurveySetDesignTemplatesLS.jpg]]


You can now select the design templates this user can select. After you finished your selection/deselection just hit '''Save''' in the upper right corner:


[[File:Save_Close.jpg]]


The most important use cases for granting user rights are collected at the '''use cases''' part of this article.

=Setting permissions for a single survey= 


These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.


'''Please note:''' An existing user account is required to set permissions for a single survey. If the account doesn't exist you have to create it first and then change the survey permissions. You don't have to apply any global rights to the user, it is just necessary that the user account itself exists.

==Setting user permissions for a single survey== 


To change the survey permissions you have to select '''Survey permissions''' from the '''Survey properties''' menu.


[[File:LimeSurveySurveyPermissions.jpg]]


In the next step you select the user you want to change the survey rights and click '''Add user'''.


[[File:LimeSurveyAddSurveyPermission.jpg]]


After you click '''Set survey permissions''' the survey permissions matrix for the survey and user will be shown.


[[File:LimeSurveyUserPermissionMatrix.jpg]]


In this matrix you can set the rights for the different features and parts. You simply click a checkbox if you want to add or remove this right. If you click a checkbox in the first column all rights for this line will be selected/removed.


In the other columns you can choose whether a user can do a single actions from this feature/part.


After you finished editing the survey permissions click '''Save''' or '''Save and close''' in the upper right corner.


[[File:Save-SaveAndClose-Close.jpg]]


The most important use cases for granting user rights are collected at the '''use cases''' part of this article.

=Use cases= 


In this part of the article we'll provide a few ideas which use cases may exist and how and which rights would be a good choice.

==A new person in charge for administrating LimeSurvey will be added== 
* login as '''admin'''
* Create a new user account
* Set global permissions for user to '''SuperAdministrator'''
* not necessary: Setting the template permissions ('''SuperAdministrator''' has all permissions for all templates)
* not necessary: Setting the survey permissions ('''SuperAdministrator''' has all permissions for all surveys)

==A new user wants to create own surveys== 
* login as '''admin''' or user with '''SuperAdministrator''' permission.
* Create a new user account
* Set global permissions for user to '''Create survey'''
* Set template permissions for user to the template/s that should be used by the user/user-group
* not necessary: Setting the survey permissions (The creator of a survey has all permissions for his/her surveys)

==The creator of a survey needs another person to edit his/her survey== 
* login as '''admin''' or user with '''SuperAdministrator''' permission.
* Create a new user account
* Set '''no global permissions''' for user
* Set '''no template permissions''' for user
* Set the survey permissions the way you want. It depends on what the new user should do and how much permissions he/she needs. If he/she should have all permissions for the survey you can select the first checkboxes in the first column with checkboxes (the one with the '''<<''' or '''>>''' button as header).

==A person responsible for the survey wants to see the results of the survey and export them== 
* login as '''admin''' or user with '''SuperAdministrator''' permission.
* Create a new user account
* Set '''no global permissions''' for user
* Set '''no template permissions''' for user
* Set survey permissions to: '''Responses''': '''View/read''' and '''export''' , '''Statistics''': '''View/read'''


[[File:LimeSurveyCusomerOwnStatistics.jpg]]


----


To be moved somewhere else once better defined:


There are several classes of possible people who access a LimeSurvey installation. But only one set of people is actually termed a '''user''' in the code and documentation. So lets understand what these classes of people are so we can better understand the terminology of the program.


{|
! Class !! Description
|-
|Installation Administrator || Those people who create login user accounts to allow others to create, edit, activate and/or view surveys and their results. Often can be given access to edit the templates, labelsets and other key features independent of any particular survey stored.
|-
|Survey Administrator || A person with a login account that is given some management access to a particular survey. Each survey can have its own set of users with specific rights to manipulate the survey. These rights can be as broad as to activate a survey and possibly edit its question base. They can be as minimum as simply able to review the results to date.
|-
|Participant || Those people who simply respond or participate in taking a survey. They may or may not have token access. They do not need a login account to the administrative interface and thus are not termed users.
|-
|Installer || A special class of person who has access to the MySQL (or similar) database server and possibly the command line interface of the computers operating system in order to install and configure the survey software. This person is asked to setup the initial SuperAdmin user account from which other user login accounts can be created.
|-
|Developer || An very special class of person who has access to the source code and can manipulate it to change the programs behavior. Generally only done with versions of the survey that are not available for live, active surveys.
|}

=Use one-time passwords= 


Since version 1.81 a user can call the limesurvey login at /limesurvey/admin and pass username and a one time password which was previously written into the users table (column one_time_pw) by an external application.


To enable this login method [[Optional settings#Use_one_time_passwords |a setting has to be turned on]] ($use_one_time_passwords = true;) in config.php.


The URL has to contain the following variables:
* '''user:''' The username normally used to login into LimeSurvey. This username has to exist in the 'users' table of the database.
* '''onepass:''' The plain text password which is then compared to the password in the 'users' table


A valid URL to login using a one-time password will look like this...


... for 1.81 to 1.92:


<div class="simplebox">http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&onepass;=secretpassword</div>


...for 2.0 or later:


<div class="simplebox">http://www.yourdomain.org/limesurvey/index.php/admin/authentication/login?user=myusername&onepass;=secretpassword</div>


'''Things to watch out for:'''
* One time passwords have to be enabled by setting "$use_one_time_passwords = true;" (for 1.92), respective "use_one_time_passwords => true" (for 2.0 in config section) in config.php.
* The passed username has to exist in LimeSurvey's ''users'' table
* The one time password, which can be set by an external application, has to be stored as [http://www.php.net/md5 MD5 hash] in column ''one_time_pw'' of table ''users''
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column ''one_time_pw'' of table ''users''. Both passwords have to match.
* After the first login with the one time password this password is deleted from the database. The user won't be able to login with this password a second time.
</translate>

Using regular expressions

2017-02-15T16:43:41Z

RsmokeUM: /* Age validation */

<languages /> <translate>


__TOC__


Regular Expressions must start and finish with a forward slash ("/"). You can find a good library of regular expressions at http://www.regexlib.net/. These patterns will almost all work if surrounded with the forward slash.


To test your regex you can [https://regex101.com/ use this regex tester].


''Please add successfully tested regular expressions!''


Examples (note that these are all one line):

=Important: Regular Expressions in conditions= 


Note that when using regular expressions in the condition editor, do NOT include the beginning and ending slash.

=Email validation= 


<source>
/^(\w[-._+\w]*\w@\w[-._\w]*\w\.\w{2,3})$/
</source>

=Postcodes= 

==Australian postcodes:== 


<source>/^[0-9]{4}/</source>

==Brazilian postcodes== 


<source>/^[0-9]{2}\.[0-9]{3}-[0-9]{3}$/</source>

==Canadian postcodes== 


<source>/^[a-zA-Z]\d{1}[a-zA-Z](\-| |)\d{1}[a-zA-Z]\d{1}$/</source>

==US postal codes== 


<source>/^[0-9]{5}([- /]?[0-9]{4})?$/</source>

==UK postcodes== 


<source>/^[A-Z][A-Z]?[0-9][A-Z0-9]? ?[0-9][ABDEFGHJLNPQRSTUWXYZ]{2}$/i</source>


Note that this is not very exact, and a more exact validation is much more complex. For example, see [http://stackoverflow.com/questions/164979/uk-postcode-regex-comprehensive StackOverflow answer] and [http://en.wikipedia.org/wiki/Talk:Postcodes_in_the_United_Kingdom#Regular_Expressions Wikipedia] for more information.

=Phone numbers= 

==US phone numbers== 


<source>/^(?:$[2-9]\d{2}$\ ?|[2-9]\d{2}(?:\-?|\ ?))[2-9]\d{2}[- ]?\d{4}$/</source>


or


<source>/^[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{4}[\.\- ]{0,}$/</source>


This second option will match all phone Canadian and US phone numbers that include non-digit symbols including


<source> . ( ) - (space)</source>


This will allow you to match phone numbers which resemble below.
*(555)555 5555
*555.555.5555
*555 555 5555
*(555)-555-5555
*555-555-5555
*555555555

==Australian phone numbers== 


The following patterns match all various Australian mobile and landline phone numbers including with "+61" country prefix eg:
*(02) 9123 6535
*03 1234-5345
*0412 345 678
*+61 2 3456 789


But not:
* 234 3450 234
*a234 534 3432
*134567
*123456789013


Brackets, white space and hypens are ignored.


The 'Very precise:' versions listed here match against the first four or five digits in a number to ensure that they are valid Australian numbers.


The 'Not very precise:' only match against the first and second digit so may allow invaid numbers.

===All Australian phone numbers (mobile and landline - area code required)=== 


Very precise:


<source>/^$?(?:\+?61|0)(?:(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}|4\)?[ -]?(?:(?:[01][ -]?[0-9]|2[ -]?[0-57-9]|3[ -]?[1-9]|4[ -]?[7-9]|5[ -]?[018])[ -]?[0-9]|3[ -]?0[ -]?[0-5])(?:[ -]?[0-9]){5})$/
</source>


Not very precise:


<source>/^(?:\+?61|0)[2-478](?:[ -]?[0-9]){8}$/</source>

===All Australian phone numbers (landlines only - area code required)=== 


Very precise:


<source>/^$?(?:\+?61|0)(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source>/^(?:\+?61|$?0)[2378]$?(?:[ -]?[0-9]){8}$/</source>

===New South Wales landline phone numbers (area code optional)=== 


Very precise:


<source>/^(?:$?(?:\+?61|0)2$?[ -]?)?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source>/^(?:$?(?:\+?61|0)2$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Victorian and Tasmanian landline phone numbers (area code optional)=== 


Very precise:


<source>/^(?:$?(?:\+?61|0)3$?[ -]?)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source>/^(?:$?(?:\+?61|0)3$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Queensland landline phone numbers (area code optional)=== 


Very precise:


<source>/^(?:$?(?:\+?61|0)7$?[ -]?)?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)(?:[ -]?[0-9]){6}$/</source>


Not very precise:


<source>/^(?:$?(?:\+?61|0)7$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===South Australia, Northern Territory, Western Australia landline phone numbers (area code optional)=== 


Very precise:


<source>/^(?:$?(?:\+?61|0)8$?[ -]?)?(?:5[1-4]|6[0-8]|[7-9][0-9])$/</source>


Not very precise:


<source>/^(?:$?(?:\+?61|0)8$?(?:[ -]?[0-9]){7}[0-9]$/</source>

===Australian mobile phone numbers only=== 


Very precise:


<source>/^(?:\+?61|0)4 ?(?:(?:[01] ?[0-9]|2 ?[0-57-9]|3 ?[1-9]|4 ?[7-9]|5 ?[018]) ?[0-9]|3 ?0 ?[0-5])(?: ?[0-9]){5}$/</source>


Not very precise:


<source>/^(?:$?(?:\+?61|0)4$?(?:[ -]?[0-9]){7}[0-9]$/</source>

==Belgian phone number== 
<source>/^((\+|00)32\s?|0)(\d\s?\d{3}|\d{2}\s?\d{2})(\s?\d{2}){2}$/</source>
==Belgian mobile phone number==
<source>/^((\+|00)32\s?|0)4(60|[789]\d)(\s?\d{2}){3}$/</source>
==French phone number==
<source>/^((\+|00)33\s?|0)[1-5](\s?\d{2}){4}$/</source>
==French mobile phone number==
<source>/^((\+|00)33\s?|0)[679](\s?\d{2}){4}$/</source>
==Luxemburg phone number==
<source>/^((\+|00\s?)352)?(\s?\d{2}){3,4}$/</source>
==Luxemburg mobile phone number==
<source>/^((\+|00\s?)352)?\s?6[269]1(\s?\d{3}){2}$/</source>
=German marks (with optional plus or minus)=
<source>/^[1-6]{1}[\+|\-]?$/</source>
=Age validation=
Example: Age 20-99
<source>/([2-9][0-9])/</source>


Example: Age 18-35
<source>/(1[8-9]|2[0-9]|3[0-5])/</source>


Example: Age 19-65
<source>/^(1[8-9]|[2-5][0-9]|6[0-5])$/</source>

=Number validation= 
==Numbers from 1 to 99999==
<source>/^([1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1-9][0-9][0-9][0-9][0-9])$/</source>
<source>/^[1-9][0-9]{0,4}$/ does the same as above but should run a little faster</source>
==Numbers from 1 to 999, 1.000 to 999.999 to 999.999.999==
<source>/^[1-9][0-9]{0,2}(?:\.[0-9]{3}){0,2}$/</source>
Accepts numbers from 1 to 999, 1.000 to 999.999 to 999.999.999 but
rejects numbers like 999.1.1 , 94.22.22, 999.1.22, 999.11.1, 999.1.333

==Number validation with optional decimal (for price)== 
Accepts numbers from 0 to 199, with 2 decimal optional:
<source>/^([1][0-9][0-9]|[1-9][0-9]|[0-9])((\.)[0-9][0-9])?$/</source>


Forces two decimal points and accepts numbers from 1.00 to 999,999,999.00 with an optional comma delimiting thousands/millions
including all of the following: 1.00, 1,000.00, 12,345.67, 12345,02, 123,456,468.00, 1234566.00, 123456789.00
but not 1,23.00, 12,3.4 or 1234,43.04
<source>/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}\.[0-9]{2}$/</source>


Same as above but the two decimal points are optional:
<source>/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}(?:\.[0-9]{2})?$/ </source>

==Month (1-12)== 


If you want to ask for the month a person was born you can validate the input as follows:


<source>/^[0]*[1-9]$|^[0]*1[0-2]$/</source>

=Minimum width (set to 3 in this example)= 


<source>/^.{3,}$/</source>

=Currency= 

==US currency (dollar sign and cents optional)== 


<source>/^\$?\d+(\.(\d{2}]]?$/</source>

==Swiss price== 


A number with two decimal numbers after the decimal point of which the last one is either a 5 or a 0:


<source>/^(\d+)(\.\d(05)?)?$/</source>

=Validate score= 

==1-10== 


<source>/^[1-9]{1}$|^10$/</source>

==1-100== 


<source>/^[1-9]?[0-9]{1}$|^100$/</source>

=Text validation= 


currently multiple short text doesn't support minimum or maximum answers. One way around this is to use a long free text type question with a regular expression.


The following test for at least one word per line for at least 3 lines and no more than 10 lines.


<source>/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)){2,10}/is</source>


If you wanted, say five words per line you could change the first and last star/asterisk to {4,} e.g.


<source>/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+){4,})(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+){4,})){2,10}/is</source>


If you wanted one or more words per line on between 1 and 5 lines, you can change the content of the last curley braces to '''0,4''' (note you use 0 because you're already matching the first line).


<source>/(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[^,.;:?!& \n\r]+(?: [^,.;:?!& \n\r]+)*)){0,4}/is</source>

==Word count== 


<source>The following restricts the number of words allowed to a minimum of 1 and a maximum of 200


/^[-\w]+(?:\W+[-\w]+){0,199}\W*$/</source>


<source>To increase the minimum change the zero part of {0,199}


To increase or decrease the maximum change the "199" part of {0,199}</source>

=Time validation= 


There are a number of ways of writing time formats. Some of the possible options are 12 hour or 24 hour, with seconds or without. Although it is an option to use the date question type (it can also capture time) you can use "short free text" with one of the validation regular expressions below:


The following three validation strings test for 24 hour time (in order of appearences) without seconds, with optional seconds lastly with seconds required.


<source>/^(?:[01][0-9]|2[0-3]):[0-5][0-9]$/</source>


<source>/^(?:[01][0-9]|2[0-3]):[0-5][0-9](?::[0-5][0-9])?$/</source>


<source>/^(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]$/</source>


The following three match 12 hour time, as above with seconds, optional seconds and with seconds required


<source>/^(?">00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))$/</source>


<source>/^(?:00:[0-5][0-9](?::[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?::[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?::[0-5][0-9])? (?:pm|PM))$/</source>


<source>/^(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))$/</source>


The following three match either 12 or 24 hour time as above with seconds, optional seconds and with seconds required


<source>/^(?:(?:00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9])$/</source>


<source>/^(?:(?:00:[0-5][0-9](?[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?[0-5][0-9])? (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9](?[0-5][0-9])?)$/</source>


<source>/^(?:(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9])$/</source>

=US states= 


To validate for one state use the following (example is Texas):
*TX uppercase only = <source>/^(TX)$/</source>
*tx lowercase only = <source>/^(tx)$/</source>
*TX upper or lowercase = <source>/^([T|t][X|x])$/</source>

=Profanity Filter= 


To filter profanity words from an answer:


<source>/^(?i)((?!\bENTERPROFANITYHERE\b).)*$(?-i)/</source>


Replace "ENTERPROFANITYHERE" with your bad word.


The \b will allow passing of words such as "assassination" & "hello" if you enter "ass" or "hell" as your profanity word. This also works if you are trying to omit other words, names etc. from answers.

</translate>

Browsing survey results

2017-02-15T15:57:38Z

RsmokeUM:

<languages /> <translate>

__TOC__

=General= 


Once a survey has been activated, and survey responses have been submitted, you will want to be able to view those responses, maybe edit some of them (or possibly delete some), export them, get some information about the responses received so far, and so on. All of this is done through the "Browse responses" function.

=How to get there= 


When your survey is active, make sure your survey is selected. Then click on the 'Responses & statistics' icon [[File:Responses.png]] and in the appearing dropdown menu the 'Browse responses' menu entry [[File:browse.png]] in the survey tool bar. This will take you to the "Responses & statistics" main screen.

=Functionality= 


The main screen (Response Summary), which is the entry screen for this section, will show you the following information:
*The number of full responses
*The number of incomplete responses
*The total number of responses (which is a total of full and incomplete responses)


If your survey is also using tokens to restrict survey access then some information for the tokens is shown here too:
*Total invitations sent
*Total surveys completed
*Total with no unique token
*Total records in the token table


<div class="simplebox">''Incomplete answers are response records with no ''submission date'': such a record can occur when a participant uses the 'saved so far but do not submit survey' function, or when an operator uses the data entry facility to fill out a survey without 'Finalizing the submit', or even when a participant fails to complete the survey because he/she just left.''</div>


The other options in this screen are described below:
*Return to survey administration: Return to the main admin screen for this survey
*Show summary information: The responses main screen
*Display responses: Display all the results to the survey. The browse shows full descriptive question names, but only abbreviated answers. See section below (editing and deleting responses).
*Display last 50: Display the last 50 responses to the survey, ordered from most recent to least recent.


*[[Data entry]]: Go to the data entry screen to add a new response (this option is also available from the admin screen)
*[[Statistics]]: A simple method for filtering and getting summaries of responses.
*[[Exporting results|Export results]]: Export all the responses to this survey to different formats like Word, Excel, CSV, SPSS, R and more.

=View survey results by participant= 


When you are browsing responses (by clicking either the ''Display responses'' or ''Display last 50 responses'') the first row shows you a number of small icons for each link. Clicking on the ''View response details'' icon [[File:Token viewanswer.png]] allows you to view that specific response on an individual basis. From here you can also edit, delete or export that specific response. See section below (editing and deleting responses).


Participants can be identified either by token, name, or IP address.

=Editing and deleting responses= 


When viewing your responses, you will be able to view a specific response by clicking on the id number. From this point you can choose to "Edit" or "Delete" this response.

==Editing a response== 


Editing the response is also fairly self-explanatory. It will take you to a 'data-entry' screen with the responses provided, and allow you to make and save any modifications. Again, in a survey you generally don't want to make changes to the responses made by the participants - but hey - it's your survey. Do what you want!

==Deleting a response== 


Deleting the responses is, of course, fairly self-explanatory - and as anyone who regularly runs surveys would know, is not recommended, unless you've got a pretty good reason (ie: a doubled up entry, or some sufficiently serious reason as to why it should be deleted). Don't click on this button thinking it will give you a second chance. If you click "Delete", the entry will be deleted with no second guessing or second checks.

==Exporting a response== 


At the "Browse responses for this survey" section you can click on "Display responses" and the id number you want to export in the left column. Then you can click on "Export this survey" above the data.
</translate>

Exporting results

2017-02-15T15:16:30Z

RsmokeUM:

<languages /> <translate>

__TOC__


Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...


[[File:browse_results.png]]

=Export to application (Excel/.csv)= 


On top of the browse responses page several export options are listed, beginning with ''export to CSV/application''.


[[File:export2.png]]


When exporting results to an application there are several filter options which are separated into:
*'''General'''
** Set a range like export records X to Y
** Set to export all records OR completed records only OR incomplete records only
*'''Questions'''
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes
** Convert spaces in question text to underscores
*'''Answers'''
** You can either export full answers or convert answer codes Y and N to a defined variable
*'''Format'''
** Microsoft Word (latin charset)
** Microsoft Excel (all charsets)
** CSV File (all charsets)
** PDF
*'''Column Control'''
** Set which answers should be exported. All answers in this list are represented by their [[SGQA identifier|SGQA identifier]]
** Set which '''''token''''' data should be exported. This option is only available if your survey is '''''not anonymous'''''!


[[File:export_tokens.png]]

=SPSS Export= 

==General== 


SPSS Statistics is a software package used for logical batched and non-batched statistical analysis. You can use official SPSS package or use [https://www.gnu.org/software/pspp/ GNU PSPP] replacement for the proprietary program SPSS.


To export your response data to SPSS go to Responses & Statistics section and click the icon to export to SPSS.


[[File:spss_toolbar.png]]

==Export and filter data== 


When exporting data to SPSS there are two filter options. You can select '''which data''' should be selected (''all records/completed records only/incompleted records only'') and for '''which SPSS version''' the export files will be used (''prior version 16/16 or up'').


SPSS export includes two files:
# a syntax file (''survey_xxxx_SPSS_syntax_file.sps'')
# and a data file (''survey_xxxx_SPSS_data_file.dat'').


After having downloaded these files you can open them using a raw text editor like notepad to take a look how the exported data looks like. The syntax file holds the commands that should be run to import the data. It is like a programming language inside SPSS. The data file contains a comma separated file with all data. If you just import this data as csv via a wizard you loose information about questions, labelsets etc. so we don't do that.

==Import data in SPSS== 


Place the two files in the same folder on your drive (example: ''c:\data\survey_xxxx_SPSS_syntax_file.sps'' and ''c:\data\survey_xxxx_SPSS_data_file.dat'')


We have two options now:


1. When using Windows use the explorer to browse to the folder used above. If SPSS is connected to the .sps file extension you can just open the file by double clicking it:


[[File:spss_explorer-screenshot.jpg]]


Now you can just choose Run->All from the opened window and after some time have your output dataset that you can save as a normal .sav file.


2. Sometimes the easy solution above does not work. Then you can proceed as follows:
* Open SPSS
* Choose File->Open->Syntax
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps
* Now the syntax opens.
* Change the line that reads ''/FILE='survey_xxxx_SPSS_data_file.dat' '' to include the path where the files are: ''/FILE='c:\data\survey_xxxx_SPSS_data_file.dat' '', for mac user : ''/FILE='HD/Users/username/survey_xxxx_SPSS_data_file.dat' ''
* Now mark the whole command text and choose Run->All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.

=R Export= 


Feel free to add more information if you have some!


The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is an export to an application export in Limesurvey.


Instructions on how to import your dataset in R:
#Download both the syntax file and the data file.
#Store both files in R working directory (use ''getwd()'' and ''setwd()'' in a R command window to get and set).
# In your code enter ''source("Surveydata_syntax.R", encoding = "UTF-8")'' in R command window which will import the data in the correct format to a data frame called "data".


Responses with limited options will be factored with the levels matching the code of the question and the labels matching the options.


Questions with other as an option will have the question field with _Other appended as a new column for the other data.


NB: R-export is a plugin in Limesurvey. If you cannot find the R-export options (''R (syntax file)'', ''R (data file)'') under ''Export results to application'', make sure the R-export plugin is enabled in the plugin menu.

=STATA-xml Export= 


<div class="simplebox">This option is available from version 2.05</div>


STATA is a commercial data analysis and statistical software package.


This export routine was created to facilitate rapid analysis of data collected with LimeSurvey. It creates an XML-file in STATAs proprietary format, which can be imported independent of the platform STATA is run on. Using this format offeres several advantages over importing plain CSV files:
*Data sets are fully labelled including variable labels (question, subquestion) and value labels (answers, if applicable).
*Dates are already transformed to STATAs internal date format and thus can directly be used to calculate difference between days etc.
*Variable names are, if necessary, converted to a STATA compatible format.
*Data formats of variables (string, integer, float, etc.) are already set according to the underlying data. (No more numbers encoded as strings!).


'''Howto load the file in STATA:
In STATA's menu, click on File, Import, xml-data. Choose browse to navigate to your exported file and click 'OK'. That should be it.
If you prefer STATA's binary .dta files, you can just save your data again in this format.
'''


'''Be aware:'''
*Due to a limitation in STATA's data format, the length of string (text) variables have a maximum of 244 characters (Stata versions 8-12) and 2045 characters (Stata version 13 and above). Please indicate your Stata version in the settings of the export plugin.
*STATA only supports attaching value labels to numerical values. So to achieve short answers (usually one or two digits) and have these properly labelled, one should use numerical answer-codes in LimeSurvey (1=Totally agree).cIf non-numerical answer codes are used (A=Totally agree), then the complete answer text will be used as answer (eg.: 'Totally agree').

=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])= 


{{FeatureChange|v=2.05}}


Once you've begun collecting responses, there may be occasions where you need to be able to directly edit and modify large quantities of data from your responses table, where a spreadsheet tool may be more useful.


VVExport (the "VV" stands for vertical verification) allows you to export your responses table into a .csv file. So long as the general structure of the file remains intact, you can then edit values within it, and then import the file again into your responses table using the "VVImport" feature.


Things you should be aware of:
* If you want to import responses using "VVImport" make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.
* If you are trying to import responses from a different yet identical (e.g. identical questions/answers from another survey) make sure you are using the correct vv file and that the first two lines of the .csv-file are correct.
* If you import a survey to your LimeSurvey installation the SID will (if possible) not change. The group id and question id however might change. So you might have to adjust the first two heading lines to match the new group id/question id. See '''Adjusting vv file headings'''

== VVExport file version 2 {{NewIn|2.05}} == 
This new feature allows different column names than the database. If your question code are unique, then the new version is selected. In the new version each column name uses the [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]]. For example this allows to update an existing survey in different installation more easily.

==Exporting a VV survey file== 


[[File:limesurveyExportVVen.jpg]]


When you choose to export responses using VVExport you will be given the option to choose which survey to be exported, whether you want to export all responses or complete responses only or incomplete responses only. The file extension allows you to choose which extension the exported file will have. For easy use .csv should be chosen.


A 'vv survey file' allows you to import the responses to a survey when the question/answer combinations have changed. Effectively this allows you to add or remove questions in an active survey.


Clicking on "Export a VV survey file" will then produce a tab delimited file that can be opened by Excel or similar style spreadsheet program. The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.


You should not modify the first two rows of this spreadsheet if you want to be able to "import" the data back into LimeSurvey at a later point.

===Exporting a VV survey file {{NewIn|v=2.05}}=== 


{{FeatureStarting|v=2.05}}


[[File:VV2-export-en.png|center]]


* '''Export survey''' : The survey ID to be exported (read-only)
* '''Export''' : The completion state of the responses to be exported
* '''File extension''' : The file extension. The file is a TSV ([[wikipedia:Tab-separated_values|Tab-separated values]]) file. For easy opening in MS-Excel set the extension to .txt, with LibreOffice, OpenOffice or other spreadsheet program you can leave it to .csv.
* '''VV export version''' : The 1.0 version uses database column headers, version 2.0 uses [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]]. Version 2.0 is selected by default if all of your question code are unique.


The first two rows of the spreadsheet are the column labels. The first row is a "human readable" column heading that details the name of the question. The second row is the real column name (Internal DB- or Qcode-name) for that response.

==Editing a VV survey file== 


When a .vv file has been successfully exported you can use a spreadsheet tool to open and edit the file. If you have to choose a column separator when opening the file please use the "Tab" character. If you are using non-ASCII characters make sure you set "UTF-8" as character set.


{{Alert|If you are using Microsoft Excel to edit the exported vv file, you should know that excel destroys the original data structure of the file. This causes an error when you try to re-import the edited .vv file.}}


By default the first two rows of the .vv file are headers. If needed you can remove the first line to have a real TSV file. There are different use cases for importing a .vv file so we will differentiate between adding new responses to a survey and overwriting all responses of the survey.


Example structure of a .vv file:

===VV version 1 TSV file=== 


<syntaxhighlight lang="text" enclose="div">
Response ID Date submitted Last page Start language Token please vote from 1 to 6 (1 - super, 6 - worst)
id submitdate lastpage startlanguage token 46492X40X1991
183 09.11.11 11:44 3 de jsfhusdgqfygqsy 4
184 09.11.11 11:53 3 de sdfhsifgsyergze 2
190 09.11.11 11:44 3 de qsdqshkfhkdsjhj 1
</syntaxhighlight>

===VV version 2 TSV file=== 


<syntaxhighlight lang="text" enclose="div">
Response ID Date submitted Last page Start language Token please vote from 1 to 6 (1 - super, 6 - worst)
id submitdate lastpage startlanguage token QCODE
183 09.11.11 11:44 3 de jsfhusdgqfygqsy 4
184 09.11.11 11:53 3 de sdfhsifgsyergze 2
190 09.11.11 11:44 3 de qsdqshkfhkdsjhj 1
</syntaxhighlight>


Here SQGA identifier are not used - instead Qcode variable naming <code>QCODE</code> is used in the second line.

===Reserved names=== 


.VV file uses left and right brackets for reserved names, when importing this string is replaced by :
* <code>{question_not_shown}</code> : NULL value in database. LimeSurvey use [empty string] for not answered question, and NULL value for question not shown (by Expression manager or max step in survey).
* <code>{quote}</code> : " (a double quote)
* <code>{cr}</code> : Carriage return
* <code>{newline}</code> : A new line
* <code>{lbrace}</code> : Left bracket (for example, if you want to have {cr} in response : use <code>{lbrace}cr}</code> )

===VV Version 1 editing=== 

====Adding new responses to the existing responses of a survey==== 
This is not supported for version 1 of the format as it easily can lead to various problems including data being imported into the wrong columns. The version 1 of the .vv file was always meant for vertical verification of data in an external tool like Excel, not as a mean to pull together data from different source (like the same survey running on another server).

====Modify all responses of a survey==== 


If you want to modify responses of survey you can just add the edit the file.


'''Example:'''


Step 1: Open the file


<syntaxhighlight lang="text" enclose="div">
Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)
id submitdate lastpage startlanguage 46492X40X1991
183 09.11.11 11:44 3 de 4
184 09.11.11 11:53 3 de 2
190 09.11.11 11:44 3 de 1
</syntaxhighlight>


Step 2: Modify responses


<syntaxhighlight lang="text" enclose="div">
Response ID Date submitted Last page Start language please vote from 1 to 6 (1 - super, 6 - worst)
id submitdate lastpage startlanguage 46492X40X1991
1000 09.11.11 11:44 3 de 3
1001 09.11.11 11:53 3 de 3
1002 09.11.11 11:44 3 de 3
</syntaxhighlight>


You can then import the survey, make sure to override the existing responses (see "Importing a VV survey file").

==Importing a VV survey file== 


[[File:LimeSurveyImportVVen.jpg]]


As long as the first two lines are intact, you can then import the data in your vv survey file back into an active LimeSurvey survey.


If you used Microsoft Excel to edit the exported vv file, the data structure of this file may be corrupted, so LimeSurvey is not able to import the edited file. You can try the following workaround to get the import working without an error:
*Open your exported vv file in Excel and do your changes (I guess you already did that)
*Save it as tab-separated text file (It creates a new file with the extension .txt)
*Do another "clean" vv export from LimeSurvey
*Open this new exported vv file with a texteditor like notepad or something else (I used textwrangler on mac)
*Press CTRL + A to mark all of the content and delete it
*Open the Excel edited vv file (the tab separated .txt file) with a texteditor and press CTRL + A to mark all of the content
*Press CTRL + C to copy the content and paste it into the new (now empty) vv file
*Press CTRL + S to save the file as it is (as .csv)
*Now try to import this file


Then, from the browse screen, choose the "Import a VV Survey file" icon.


The "Import a VV Survey File" screen needs you to choose the "vvexport" file you are importing. If you choose to "Exclude Record IDs" the records will be imported and brand new Record ID's will be generated for them (use this option for the use case "Adding new responses to the existing responses of a survey"). If you un-check this box, then the original record id's will be imported (use this option for the use case "Overwriting all responses of the survey").


There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.
*Report an error (and skip the new record).
*Renumber the new record
*Replace the existing record (uses this for the use case "Overwriting all responses of the survey")

===Importing a VV survey file {{NewIn|2.05}}=== 


[[File:VV2-import-en.png|center]]


* '''File''' : Select the file to be uploaded. The file must be a [[wikipedia:Tab-separated_values|TSV file]]: A text file with each column separated by TAB.
* '''Exclude record IDs?''' : If 'id' column exist in the file you can exclude this line or not. If this setting is checked then a new record is added for each line of the .vv file. If unchecked you can choose:
* '''When an imported record matches an existing record ID''':
** ''skip'' : Report and skip the new record. After upload you will see if the record already existed - if it existed it's not imported.
** ''renumber'' : Renumber the new record. A new record is added to the response table with answer of the VV file.
** ''replace'' : Replace the existing record. The old record is deleted and completely replaced by the record from the VV file
** ''replaceanswer'' : Replace response details from the file in the existing record. The old record is updated with the new response from the VV file. This allow to replace only one question in the response table.
* '''Import as not finalized response?''' : If checked the submitdate is set to NULL, so the response is set to not completed.
* '''Character set of the file''' : You can choose the character set of the file - the default and recommended value is UTF-8 but some spreadsheet program don't allow to choose a character set.
* '''First line contains question codes''' : By default VV file first line contain human readable question, the real column names are in the second line. This allow to use the first line as the real column names.
* '''Force import''' : If the question codes are not found in the database name or in [[Expression_Manager#Qcode_Variable_Naming|Qcode Variable Naming]] then columns are assigned depending of order. This can be used to import VV file from different LimeSurvey instance but each survey must be exactly the same. We strongly recommend to use this only if you know what you are doing. It can be very dangerous and lead to results ending up in the wrong column.

=Other export options= 

==Export a single response== 


If you want to export an individual response, you can do it in 3 ways:


1. Login to limesurvey admin backend, choose your survey, goto "Edit survey settings" -> "Notification and data management" and make sure you receive basic email notifications.


Every time someone has completed a survey, you will receive an email with a link: "Click the following link to see the individual response"


This will take you to a page with a button above the data saying "Export this response"


2. Login to limesurvey admin backend, choose your survey and "Browse responses for this survey". Click on "Display responses" and the id number you want to export in the left column. Then you can click on "Export this survey" above the data.


3. Login to limesurvey admin backend, choose your survey and "Export results to application". In the last field above "Export data" you can choose which entry you want to export.

==Match responses from different surveys== 


If you want to track survey responses for particular individuals over time, LimeSurvey can help you do that. A possible use case is to track group responses before and after the group takes a particular seminar.


The steps to implementing this are as follows:


1. Create the survey


2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:


a - Click on the icon General settings.


b - Then under the Tokens tab select "No" for Anonymized responses.


3. Activate the survey.


When you activate the survey, click on the "switch to closed-access mode" button to create the token table:


[[File:switch_to_closed.png]]


4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).


5. Export the survey results and make sure you include the token information.


To export click ''browse results''...


[[File:browse_results.png]]


...and then ''export'':


[[File:export2.png]]


Remember to choose one or more elements from the token table to associate with the survey responses:


[[File:export_tokens.png]]


6. When you run the survey again, which can easily be done by copying the survey and tokens table using export/import, just repeat the steps, and make sure the same query is used to build the csv token import file.

=Problems & Solutions= 

==Excel== 

===Modifying responses in Excel prior to Import=== 


In order to make multiple changes to responses, you may choose to Export and open a file in Excel. Make changes to the data (other than the top lines) and then save as a .txt file. If you save as .csv, Excel uses comma-delimits which will not import into LimeSurvey. By saving as a .txt file, Excel saves as a tab-delimited file which imports back into LimeSurvey.

===Edit .csv with Excel=== 


In general '''''we do not recommend to use Excel to edit the exported .csv files''''' because Excel does some changes to the internal data structure which results in a failing import. If you nevertheless want to use Excel you have to set the seperator for Excel to a comma in System Control (Windows Systems):


System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,

===Workaround to edit .csv files with Excel=== 


Using Excel for editing questions can prevent you from being able to re-import them. But editing is the way to go if you have more than 5 or so options or ranking options, want to use Excel capabilities like sorting, etc.


This is a partial workaround that seems to work in 1.82-essentially, only use Excel on the part of the file that is the data:
* Export a question similar to what you would like to reuse as .csv file
* Open the CSV file in a rawtext editor
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish
* Save the file as Excel CSV, which will likely have no quotes.
* Open this file in the editor, and Select All, Copy
* Go back to the file you opened with the rawtext editor
* Paste over the answers there
* Save AS, with a different name, maybe one that you can remember for reuse
* Import this file.

===Excel - export limited to 255 columns=== 


Due to limitations in Excel (versions lower and equal to 2003), LimeSurvey can export only 255 columns at the same time. Microsoft has proposed a [http://support.microsoft.com/kb/272729/en-us workaround as a VB macro].


Although newer spreadsheets (Excel >= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can't export more than 255 columns.


Two workarounds are however possible, use one of the following solutions:
* Either export to CSV and import in your spreadsheet
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results

===Excel/.csv - export fails=== 


If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.

==CSV== 

===CSV defaults to 255 columns=== 


When exporting large surveys the GUI by default limits the export to the first 255 columns. To work around this, simply mark all data sets for export.

==SPSS export== 

===General steps=== 


To import the LimeSurvey response data please use the following steps:
#Click on the 'Export to SPSS' icon.
#From the select boxes select which responses you want to export and your SPSS version.
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)
#Open the .sps file with SPSS by opening SPSS, then select 'Choose another type of file' and select the downloaded .sps file.
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with '/FILE=...'
#Edit that line and adjust the path so it points to your .dat file. Example: Your *.dat file is in c:\temp so set this line to /FILE='c:\temp\survey_(xxxx)_SPSS_data_file.dat'
#Now select all commands inside the editor by pressing CTRL-A.
#From the SPSS menu select Run/All.
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.
#Done!

===Possible error messages in SPSS=== 

====ERROR. command name:Get Data==== 


If you receive the error message ''ERROR. command name:Get Data. 2267 Unexpected Token missing.'' please edit the forth line of your syntax file so it points to the absolute path of the data file like


<div class="simplebox">C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat</div>

====Error: "Text value unmappable in the current server locale"==== 


This error can happen if you try to open an exported syntax file in SPSS 16. The solution is to force SPSS to interpret the syntax file as unicode.


<div class="simplebox">Open SPSS. Go to Edit > Options > Character encoding for data and syntax. Change the option to "unicode".</div>


LimeSurvey data can now be exported to SPSS 16 without any problem.

===Define the scale to use for your variable=== 


It is possible to override the default scale used for a variable by setting the question attribute [[Advanced question settings#scale_export|scale_export]] to the appropriate value.

==VV Export/Import== 

===VV - Problems with vv import=== 


If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.

==Other problems and solutions== 

===Copying responses into a different survey (using tokens)=== 
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.
# Export the responses from the old survey, including tokens, open in Excel.
# Use this data to create an Excel worksheet for the standard token file import (eg. Firstname, Lastname, Token, Email address, Email status (OK), Language (En)). Save as .csv and import tokens to the new survey in LimeSurvey.
# In Excel, copy the response fields from the old survey responses that you want in the new survey (including token) into the appropriate Excel column of the new survey format.
# Save as .txt file.
# Use VVImport to import the new data into the new survey.
# Possible import errors include date format - some system date fields do not allow a NULL value, some do. If the date looks okay but gives an error, use the Excel cell format "2009-12-01".
</translate>