<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.limesurvey.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Steve</id>
	<title>LimeSurvey Manual - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.limesurvey.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Steve"/>
	<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/Special:Contributions/Steve"/>
	<updated>2026-08-13T01:11:23Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Question_groups_-_introduction&amp;diff=4130</id>
		<title>Question groups - introduction</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Question_groups_-_introduction&amp;diff=4130"/>
		<updated>2012-03-13T09:48:13Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Creating a group=&lt;br /&gt;
&lt;br /&gt;
Before you can [[Adding a question|add questions]] to your survey you must create a group. Create a new group by clicking on the Add icon [[File:add.png]] in the Survey Button Bar. Alternatively you can import a previously exported group. The import feature does NOT import groups from LimeSurvey (PHPSurveyor) versions older than 1.45.&lt;br /&gt;
&lt;br /&gt;
You can create as many groups as you like.&lt;br /&gt;
&lt;br /&gt;
=Using groups for summarizing questions=&lt;br /&gt;
&lt;br /&gt;
Groups can be used to group questions in a survey. If you are going to have multiple groups, you should note that by default the survey questions will be displayed group by group (you can change that at the survey settings). To display the groups in a particular order use the group re-ordering feature. If you have only one group in your survey then the name of this group is irrelevant (except of course for display).&lt;br /&gt;
&lt;br /&gt;
=Group elements=&lt;br /&gt;
&lt;br /&gt;
Groups can also include a &amp;quot;description&amp;quot;. This field allows you to publish an explanatory note for any set of questions. If you add a description, it will be presented at the survey before commencing any of the questions in that group. If you do not include any text here, then public participants will simply move on to the first question in the group with no stop. You can use the HTML editor to include images, formatted text, etc. to your liking.&lt;br /&gt;
&lt;br /&gt;
=Show/Hide groups conditionally=&lt;br /&gt;
&lt;br /&gt;
==Limesurvey 1.92 and above==&lt;br /&gt;
&lt;br /&gt;
Starting in Version 1.92, you can set a Relevance Equation for the group using [[Expression Manager|Expression Manager]] syntax.  This is helpful for &amp;quot;looping&amp;quot; or other cases where you are repeating similar content multiple times.  For example, say you want to ask the same set of follow-up questions for each child in a household, and you asked how many children there are via a question named &#039;&#039;numKids&#039;&#039;.  Then, for each group of follow-up questions, you would use relevance equations the following (which would collect data about the third child):  &#039;&#039;&#039;numKids &amp;gt;= 3&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
An explanation and example for hiding question groups is available at the [Expression+Manager+Examples#Hide_question_group_if_answer_from_previous_question_is_Yes_or_No|Expression Manager Examples page].&lt;br /&gt;
&lt;br /&gt;
==Prior Limesurvey 1.92==&lt;br /&gt;
&lt;br /&gt;
To hide all questions of a certain group at Limesurvey 1.91 or older, proceed as follows:&lt;br /&gt;
* Set a condition on the first question of the according group&lt;br /&gt;
* Use the [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey#Copying_conditions_to_later_questions copy condition feature] to copy the previously set condition to all following questions of that group:&lt;br /&gt;
&lt;br /&gt;
[[File:copy_conditions_example_1.png]]&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Accessing_the_source_code&amp;diff=858</id>
		<title>Accessing the source code</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Accessing_the_source_code&amp;diff=858"/>
		<updated>2012-02-27T15:49:26Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
Until recently we used Subversion as versioning control system but now have [[Switch from Subversion to Git|moved to Git.]]&lt;br /&gt;
&lt;br /&gt;
=Accessing the LimeSurvey Source Code=&lt;br /&gt;
&lt;br /&gt;
Always be aware that most of the LimeSurvey Source code is &#039;&#039;&#039;bleeding edge&#039;&#039;&#039;. Do not use it for production purposes (except fo the master branch!&lt;br /&gt;
&lt;br /&gt;
As for many other free software projects only community support is available.&lt;br /&gt;
&lt;br /&gt;
Access the LimeSurvey source code with a Subversion client for your operating system.&lt;br /&gt;
*For Windows we recommend: [http://www.syntevo.com/smartgit/download.html SmartGit] because it is very easy to use.&lt;br /&gt;
*For Linux 1 Mac we recommend: [http://git-scm.com/ Git]. Commandline , or use git gui.&lt;br /&gt;
&lt;br /&gt;
==Step-by-Step How-To (Windows)==&lt;br /&gt;
# Create a [https://github.com/ GitHub] account.&lt;br /&gt;
# Download and install Git for Windows from [http://code.google.com/p/msysgit/downloads/list]. Make sure that during install when asked for adding the Git path to your system path that you choose the &amp;quot;Run Git from the Windows Command Prompt&amp;quot; option. For further help see [http://help.github.com/win-set-up-git/ Set Up Git]&lt;br /&gt;
# Download and install [http://www.syntevo.com/smartgit/download.html SmartGit].&lt;br /&gt;
# Clone the LimeSurvey repository with SmartGit. You can find the right clone URL at https://github.com/LimeSurvey/LimeSurvey .&lt;br /&gt;
# The whole source code repository should be downloading now.&lt;br /&gt;
# By default you should see the &#039;master&#039; branch in the current directory&lt;br /&gt;
# Use the Switch command from the SmartGit GUI to switch to the branch you need.&lt;br /&gt;
# That&#039;s it.&lt;br /&gt;
&lt;br /&gt;
Please add instructions for other OSs or complete the existing ones.&lt;br /&gt;
&lt;br /&gt;
=Available branches=&lt;br /&gt;
&lt;br /&gt;
These are the available GitHub branches right now:&lt;br /&gt;
*master - This is the always the current stable (plus) version including any fixes not yet released.&lt;br /&gt;
*Dev - this is currently the branch for the 1.92 version being in Release candidate period&lt;br /&gt;
*Yii - the branch for the Yii 2.0 version which is the bleeding edge currently&lt;br /&gt;
*original_art and original_art 2: These are the SVG files for almost all icons the stable and Yii version.&lt;br /&gt;
*other_scripts, server_scripts, translation status: These are scripts being used in limesurvey.org or for new releases. We will merge these to a single &#039;server-scripts&#039; branch soon.&lt;br /&gt;
*Codeigniter - The old CodeIgniter branch - it is deprecated, do not use it, and will be removed soon&lt;br /&gt;
&lt;br /&gt;
=Further documentation=&lt;br /&gt;
&lt;br /&gt;
Please make sure you code accoding to our [[Coding guidelines]].&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4444</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4444"/>
		<updated>2012-02-02T09:31:34Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Laden Sie die Daten- und die Syntax-Datei herunter.&lt;br /&gt;
#Speichern sie beide Dateien im R Arbeitsverzeichnis (benutzen Sie &#039;&#039;getwd()&#039;&#039; und &#039;&#039;setwd()&#039;&#039; im R Kommandofenster um es zu setzen und anzeigen).&lt;br /&gt;
#Geben Sie &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; im R Kommandofenster ein.&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
* 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 to heading lines to match the new group id/question id. See &#039;&#039;&#039;Adjusting vv file headings&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:limesurveyExportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
example (structure of a vv file):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Delete old answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 3: Add new answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Add new answers (at the end of the document)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Adjusting vv file headings===&lt;br /&gt;
&lt;br /&gt;
When importing a survey it might happen that the survey id stays the same while the group and question ids change. In order to import the survey results you have to adjust the headings of the vv file. How to import a new survey and the survey results will be explained below.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Import the new survey&lt;br /&gt;
&lt;br /&gt;
Step 2: Activate the new survey&lt;br /&gt;
&lt;br /&gt;
Step 3: Export the &amp;quot;empty&amp;quot; results of the new survey as vv file&lt;br /&gt;
&lt;br /&gt;
Step 4: Open the &amp;quot;empty&amp;quot; vv file (new SGQA: 46492X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;45&amp;lt;/span&amp;gt;X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;3269&amp;lt;/span&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X45X3269&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 5: Copy the first two lines/rows from the &amp;quot;empty&amp;quot; vv file&lt;br /&gt;
&lt;br /&gt;
Step 6: Open the exported vv file from the old LimeSurvey installation (old SGQA: 46492X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;40&amp;lt;/span&amp;gt;X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;1991&amp;lt;/span&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 7: Paste the new headings (copied two lines/rows) into the first two lines/rows of the old vv export file (now the SGQA should be 46492X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;45&amp;lt;/span&amp;gt;X&amp;lt;span style=&#039;color:#F00&#039;&amp;gt;3269&amp;lt;/span&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X45X3269&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can now import the vv file and the headings are correct.&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyImportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; file you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them (use this option for the use case &amp;quot;Adding new responses to the existing responses of a survey&amp;quot;). If you un-check this box, then the original record id&#039;s will be imported (use this option for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Replace the existing record (uses this for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4445</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4445"/>
		<updated>2012-02-02T08:38:06Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Laden Sie die Daten- und die Syntax-Datei herunter.&lt;br /&gt;
#Speichern sie beide Dateien im R Arbeitsverzeichnis (benutzen Sie &#039;&#039;getwd()&#039;&#039; und &#039;&#039;setwd()&#039;&#039; im R Kommandofenster um es zu setzen und anzeigen).&lt;br /&gt;
#Geben Sie &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; im R Kommandofenster ein.&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
* 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 to heading lines to match the new group id/question id. See &#039;&#039;&#039;Adjusting vv file headings&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:limesurveyExportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
example (structure of a vv file):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Delete old answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 3: Add new answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Add new answers (at the end of the document)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Adjusting vv file headings===&lt;br /&gt;
&lt;br /&gt;
When importing a survey it might happen that the survey id stays the same while the group and question ids change. In order to import the survey results you have to adjust the headings of the vv file. How to import a new survey and the survey results will be explained below.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Import the new survey&lt;br /&gt;
&lt;br /&gt;
Step 2: Activate the new survey&lt;br /&gt;
&lt;br /&gt;
Step 3: Export the &amp;quot;empty&amp;quot; results as vv file&lt;br /&gt;
&lt;br /&gt;
Step 4: Open file&lt;br /&gt;
&lt;br /&gt;
(will be updated soon)&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyImportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; file you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them (use this option for the use case &amp;quot;Adding new responses to the existing responses of a survey&amp;quot;). If you un-check this box, then the original record id&#039;s will be imported (use this option for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Replace the existing record (uses this for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Survey_participants&amp;diff=3434</id>
		<title>Survey participants</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Survey_participants&amp;diff=3434"/>
		<updated>2012-01-31T10:01:42Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note&#039;&#039;&#039;:  Tokens have changed alot in Version 1.85 and later. So if you are using an earlier version there will be differences between your version and the documentation. We recommend to upgrade as soon as possible.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
On many occasions you will want to invite a group of people to participate in your survey, keep track of who has completed the survey, and ensure that each person can only participate once. The tokens feature allows you to do the following:&lt;br /&gt;
*Manually create invitations (name, email address, ...)&lt;br /&gt;
*Import a list of names and email addresses for participants (from a CSV file or an LDAP query)&lt;br /&gt;
*Add/Remove invitations&lt;br /&gt;
*Generate a unique token number for each participant (invitation code)&lt;br /&gt;
*Send an email invitation to each person in your list, by group or individually&lt;br /&gt;
*Send a reminder email to each person in your list who has not yet responded, by group or individually&lt;br /&gt;
*Track who from your list has responded&lt;br /&gt;
*Restrict access against people who have not got a token, and those with a token who have already responded&lt;br /&gt;
*Edit/change any details in your list&lt;br /&gt;
&lt;br /&gt;
Once the survey is switched to Closed-access mode (you have enabled tokens for this survey), then &#039;&#039;&#039;only the people with a valid token code (not already used) can access the survey&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If you enable &#039;&#039;Auto-registration&#039;&#039; in the survey properties, participants will be able to register for your survey to have their personal token code automatically generated.&lt;br /&gt;
&lt;br /&gt;
==Can a survey using tokens ensure anonymous answers?==&lt;br /&gt;
&lt;br /&gt;
The answer to this question is &#039;&#039;&#039;Yes&#039;&#039;&#039;. Tokens can be used both for anonymous and non-anonymous surveys. This is determined when creating a survey. If a survey is not anonymous (or &#039;tracked&#039;) then the token list can be used to find the responses that an individual has made to the survey. If the survey is anonymous, then no link (technically: foreign key relationship) is available between the tokens table and the responses.&lt;br /&gt;
&lt;br /&gt;
=How to activate tokens?=&lt;br /&gt;
&lt;br /&gt;
There are two ways to activate tokens:&lt;br /&gt;
#After survey activation you will be asked if you want to activate tokens: [[File:Switch-to-closed-access-mode.png]]&lt;br /&gt;
# &#039;&#039;&#039;OR &#039;&#039;&#039;you can click on the tokens symbol [[File:tokens.png]] - even before the survey is activated.&lt;br /&gt;
&lt;br /&gt;
=The token management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:token-menu2.png]]&lt;br /&gt;
&lt;br /&gt;
After creating the tokens table you can click on the tokens icon to get to the token administration. The following is a brief rundown of the menu options in the tokens screen:&lt;br /&gt;
*&#039;&#039;&#039;Admin&#039;&#039;&#039;: Returns to the main survey admin screen&lt;br /&gt;
*&#039;&#039;&#039;Summary&#039;&#039;&#039;: Displays just the brief summary of tokens in the table (number of tokens, how many have been sent an invitation, and how many have responded). Also provides access to the Database Admin functions (see below). This is the default screen.&lt;br /&gt;
*&#039;&#039;&#039;Browse&#039;&#039;&#039;: Displays the complete list of participants in the tokens table. From the browse screen you can edit or delete individual entries in the token table as well as perform a number of other useful functions (see browse section below)&lt;br /&gt;
*&#039;&#039;&#039;Add new token entry&#039;&#039;&#039;: Allows you to add an entry to the tokens table&lt;br /&gt;
*&#039;&#039;&#039;Add dummy token&#039;&#039;&#039;: Allows you to add 1 or more tokens to the token table&lt;br /&gt;
*&#039;&#039;&#039;Manage additional field attributes&#039;&#039;&#039;: Allows you to add additional fields to the tokens table to store custom participant data&lt;br /&gt;
*&#039;&#039;&#039;Import from CSV&#039;&#039;&#039;: Allows you to import information from a csv file&lt;br /&gt;
*&#039;&#039;&#039;Import from LDAP&#039;&#039;&#039;: Allows you to import information from an LDAP query (tested on openLdap but should work in any LDAP compliant directory including ActiveDirectory)&lt;br /&gt;
*&#039;&#039;&#039;Export tokens to CSV file&#039;&#039;&#039;: creates a standard CSV (comma delimited) file with a complete list of participants of your current tokens table&lt;br /&gt;
*&#039;&#039;&#039;Edit email templates&#039;&#039;&#039;: Used to customize the templates used for the invitations, reminders, confirmations, and registration emails&lt;br /&gt;
*&#039;&#039;&#039;Send email invitation&#039;&#039;&#039;: Sends bulk email invitations to all participants in the tokens table who have not already been sent an invitation.&lt;br /&gt;
*&#039;&#039;&#039;Send email reminder&#039;&#039;&#039;: Sends bulk email reminders to all participants in the tokens table who have not yet responded, but have been sent their first invitation.&lt;br /&gt;
*&#039;&#039;&#039;Generate tokens&#039;&#039;&#039;: Creates unique tokens for all individual entries in the tokens table that do not yet have one&lt;br /&gt;
*&#039;&#039;&#039;Drop token table&#039;&#039;&#039;: delete the token table and set the survey to Open-access mode.&lt;br /&gt;
*&#039;&#039;&#039;Bounce settings&#039;&#039;&#039;:  Email bounce back settings.   Bounce back settings can be set at the survey level or at the system level.    This feature was added in version 1.91&lt;br /&gt;
&lt;br /&gt;
=Editing/adding a token=&lt;br /&gt;
&lt;br /&gt;
A typical token entry contains the following fields:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:token_editing2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;First and last name&#039;&#039;&#039;: .. of the participant (can be used in the emails &amp;amp; survey)&lt;br /&gt;
*&#039;&#039;&#039;Email&#039;&#039;&#039;: the participant&#039;s email address&lt;br /&gt;
*&#039;&#039;&#039;Email status&#039;&#039;&#039;: a field to keep track of bad emails. For instance, if the survey administrator received email error notifications from this email, the he can set this field to anything other than &#039;OK&#039; (for instance &#039;user unknown&#039;, or &#039;mailbox quota exceeded&#039;). Marking this token with an email status other than &#039;OK&#039;, will help skip this entry when sending invitation or reminder emails. Note that this is completely manual, unless you decide to implement a script which does update this field automatically.&lt;br /&gt;
*&#039;&#039;&#039;Token&#039;&#039;&#039;: this is the invitation code. It is usually automatically generated by the &#039;Generate tokens&#039; button&lt;br /&gt;
*&#039;&#039;&#039;Language&#039;&#039;&#039;: if you want to set the default language for this participant&lt;br /&gt;
*&#039;&#039;&#039;Invite sent&#039;&#039;&#039;: defaults to &#039;N&#039;, otherwise would contain the date when the invitation email was sent&lt;br /&gt;
*&#039;&#039;&#039;Reminder sent&#039;&#039;&#039;: defaults to &#039;N&#039;, otherwise would contain the date when the reminder email was sent&lt;br /&gt;
*&#039;&#039;&#039;Completed&#039;&#039;&#039;: defaults to &#039;N&#039;, otherwise would contain the date when the survey was submitted for not anonymous survey, or &#039;Y&#039; for anonymous survey&lt;br /&gt;
*&#039;&#039;&#039;Uses left&#039;&#039;&#039;: A counter of number of times the token can be used.&lt;br /&gt;
*&#039;&#039;&#039;Valid from&#039;&#039;&#039; &amp;amp; &#039;&#039;&#039;Valid until&#039;&#039;&#039; : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don&#039;t want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won&#039;t be able to finish the survey.&lt;br /&gt;
*&#039;&#039;&#039;Attribute1 to Attribute x&#039;&#039;&#039;: These are user-definable attribute fields - see the next paragraph.&lt;br /&gt;
&lt;br /&gt;
=Dummy Tokens=&lt;br /&gt;
&lt;br /&gt;
Dummy Tokens were added in 1.91. Here is a typical screen:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:dummyToken.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
*&#039;&#039;&#039;Number of tokens&#039;&#039;&#039;:  Number of tokens to be added.  Default is 100.&lt;br /&gt;
*&#039;&#039;&#039;Token length&#039;&#039;&#039;: Number of characters or length of token.  Default 15&lt;br /&gt;
*&#039;&#039;&#039;First and last name&#039;&#039;&#039;: .. of the participant.&lt;br /&gt;
*&#039;&#039;&#039;Email&#039;&#039;&#039;: the participant&#039;s email address&lt;br /&gt;
*&#039;&#039;&#039;Language&#039;&#039;&#039;: If you want to set the default language for this participant&lt;br /&gt;
*&#039;&#039;&#039;Uses left&#039;&#039;&#039;: A counter of number of times the token can be used.&lt;br /&gt;
*&#039;&#039;&#039;Valid from&#039;&#039;&#039; &amp;amp; &#039;&#039;&#039;Valid until&#039;&#039;&#039; : You can set a date/time range where this token would be allowed to use. You can leave these empty if you don&#039;t want to limit participation time frame for certain users. Note: If the user is answering the survey and the participation time ends then the user is locked out immediately and won&#039;t be able to finish the survey.&lt;br /&gt;
*&#039;&#039;&#039;Attribute1 to Attribute x&#039;&#039;&#039;: These are user-definable attribute fields - see the next paragraph.&lt;br /&gt;
&lt;br /&gt;
Note that Name, email, language will be set to the same value for all dummy Tokens&lt;br /&gt;
&lt;br /&gt;
=Bounce Settings=&lt;br /&gt;
&lt;br /&gt;
Email bounce back processing was added in 1.91.&lt;br /&gt;
&lt;br /&gt;
[[File:surveyBounseSettings.png]]&lt;br /&gt;
*&#039;&#039;&#039;Survey bounce email&#039;&#039;&#039;:  A valid email address for return mail.   For faster bounce back processing, this email box should be limited to bounce back only.&lt;br /&gt;
*&#039;&#039;&#039;Bounce settings to be used&#039;&#039;&#039;: There are three options:  1) None (default) - no bounce back processing, 2) Use settings below - Will set bounce back processing at the survey level, or 3) Use global settings -- Settings based on the system level.&lt;br /&gt;
*&#039;&#039;&#039;Server type&#039;&#039;&#039;: Three options: 1) Off, 2) IMAP or 3) POP&lt;br /&gt;
*&#039;&#039;&#039;Server name &amp;amp; port&#039;&#039;&#039;:  Host name and port number.   Port number isn&#039;t typically needed unless the email host uses a non-standard port. Example:  mail.example.net:25 or imap.gmail.com:995&lt;br /&gt;
*&#039;&#039;&#039;User name&#039;&#039;&#039;:  User Name or User ID of the email account&lt;br /&gt;
*&#039;&#039;&#039;Password&#039;&#039;&#039;:  password of the email account&lt;br /&gt;
*&#039;&#039;&#039;Encryption type&#039;&#039;&#039;:  Three options:  1) None (default), 2) SSL, or 3) TLS&lt;br /&gt;
&lt;br /&gt;
=User-defined attribute fields=&lt;br /&gt;
&lt;br /&gt;
It is possible to add a number of additional fields to the tokens table to save additional data for a participant. By clicking on the [[File:token_manage.png]] icon you can manage these fields. You can add more attribute fields (by default they have a a length of 255 chars) and also set descriptions for each field - so they look nicer in the administration, when you browse tokens, when creating [[Setting conditions|conditions]] based on attribute fields or even when you export results for non-anonymous surveys.&lt;br /&gt;
&lt;br /&gt;
=Using the browse screen and editing tokens=&lt;br /&gt;
&lt;br /&gt;
[[File:token-browse.png]]&lt;br /&gt;
&lt;br /&gt;
The browse screen will show you a list of all entries in the tokens table, as well as giving you some &#039;action&#039; buttons that can perform specific tasks for that individual entry.&lt;br /&gt;
&lt;br /&gt;
The top row of the table has three columns: The dialogue on the right gives options for displaying a number of records, and a starting point. In the middle is a search bar and the symbols on the left let you move backwards or forwards through your list.&lt;br /&gt;
&lt;br /&gt;
The second row of the table (see image below) includes various criteria to sort the entries and for each a green arrow that - if clicked - will refresh the screen showing the tokens ordered by that criterion.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Actions&amp;quot; column gives a list of specific tasks that can be performed on that individual entry:&lt;br /&gt;
&lt;br /&gt;
[[File:token-actions.png]]&lt;br /&gt;
*Do the survey using the unique token of this entry&lt;br /&gt;
*Edit this entry&lt;br /&gt;
*Delete this entry&lt;br /&gt;
*Send a invitation/reminder to this individual entry&lt;br /&gt;
*If the survey is a &#039;tracked&#039; (ie: not anonymous) survey, another button will appear, allowing you to view the response from this individual entry.&lt;br /&gt;
&lt;br /&gt;
=Database Admin=&lt;br /&gt;
&lt;br /&gt;
[[File:token-summary.png]][[File:token-db-mgt.png]]&lt;br /&gt;
&lt;br /&gt;
While the summary screen shows a brief summary of tokens in the table, it also provides access to the &amp;quot;Database Admin&amp;quot; features which include:&lt;br /&gt;
*Clear invites: Sets all records that an invitation has been sent out to &#039;N&#039;. Obviously shouldn&#039;t normally be used.&lt;br /&gt;
*Clear tokens: Clears all tokens. Similarly shouldn&#039;t normally be used.&lt;br /&gt;
*Drop tokens: Allows you to remove the tokens feature from your script. Deletes the entire table and all records, and allows the survey to be accessed by anybody who knows the URL.&lt;br /&gt;
&lt;br /&gt;
= Importing/exporting tokens=&lt;br /&gt;
&lt;br /&gt;
== CSV import==&lt;br /&gt;
&lt;br /&gt;
When you click the icon to import tokens you will be presented with the following screen:&lt;br /&gt;
&lt;br /&gt;
[[File:uploadtoken.jpg]]&lt;br /&gt;
&lt;br /&gt;
Your CSV file must be a standard [http://en.wikipedia.org/wiki/Comma-separated_values CSV (Comma Separated Value) file]. The first line of text is always the header information and will be used to identify the field data. Possible data fields are:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;firstname,lastname,email,emailstatus,token,language code,tid,attribute_1,attribute_2, attribute_...&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To obtain a full list of token field names, export an existing token table.&lt;br /&gt;
&lt;br /&gt;
The fields can be in any order but &#039;&#039;firstname, lastname and email are mandatory&#039;&#039;, and they must contain at least one character. Empty data (such as &amp;quot;&amp;quot;) is not sufficient. If you would like to import data for attribute fields, you must add the desired attribute fields to the token table prior to importing token data.&lt;br /&gt;
&lt;br /&gt;
A bare minimum CSV file could look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;firstname,lastname,email&lt;br /&gt;
&lt;br /&gt;
John,Doe,john@doe.net&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Date format for token import&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The date format for the &amp;quot;validfrom&amp;quot; and &amp;quot;validuntil&amp;quot; fields in the CSV token inport file is &amp;quot;YYYY-MM-DD HH:MM&amp;quot;, e.g.:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;2012-01-01 00:00&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
--would correspond to 1st January, 2012, at 12:00 AM.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Filtering duplicates&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you activate the option to filter for duplicates you can set which fields are used to identify duplicates. By default First name, Last name &amp;amp; Email-address are pre-selected. If a duplicate is found while importing the related line is omitted.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Troubleshooting the token import&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A common error when users try to import tokens is an invalid CSV file. This is often caused by Microsoft Excel. Many users have a list of e-mail addresses saved as an XLS document. A file can be saved as CSV in Excel, however, Microsoft uses semi-colon (;) as the comma separator, while a standard CSV file uses comma (,) as the separator. If you try to import an Excel saved CSV file you will get an error message. A simple solution is to save your XLS document as a CSV file in Excel and then open the file in a raw text editor and replace all semi-colon characters with commas.&lt;br /&gt;
&lt;br /&gt;
Recommended free raw text editors are: [http://www.pspad.com/ PSPad], [http://www.flos-freeware.ch/notepad2.html NotePad2] or [http://notepad-plus-plus.org/ Notepad++] for Windows, and [http://www.barebones.com/products/textwrangler/ TextWrangler] for Macintosh.&lt;br /&gt;
&lt;br /&gt;
You can use [http://www.libreoffice.org/features/calc/ LibreOffice Calc] to export import your xls file and export your csv file.&lt;br /&gt;
&lt;br /&gt;
== CSV export==&lt;br /&gt;
&lt;br /&gt;
When you export your tokens the following fieldorder is exported:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;tid,firstname,lastname,email,emailstatus,token,language code,attribute_1,attribute_2,etc..&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== LDAP import==&lt;br /&gt;
&lt;br /&gt;
[[File:token-Ldap-import.png]]&lt;br /&gt;
* Queries are manually defined by the system administrator in the config-ldap.php file&lt;br /&gt;
* Duplicates are identified by First Name, Last Name &amp;amp; Email-Address. If a duplicate is found while importing the related line is omitted, unless you have unchecked the Filter Duplicates checkbox.&lt;br /&gt;
&lt;br /&gt;
== A tip for generating a large number of fake e-mail addresses==&lt;br /&gt;
&lt;br /&gt;
Sometimes you may need a large number of fake e-mail addresses and tokens. You can use functions in a spreadsheet (e.g. OpenOffice Calc) to generate them. Let&#039;s assume you want thousands addresses in a form: 1@test.com, 2@test.com, 3@test.com... Put consecutive numbers in column A: 1 in the A1, then insert function =A1+1 in A2, then copy A2 down as many times as you need. In B1 use concatenation function to join A1 and &amp;quot;@test.com&amp;quot;, which is =CONCATENATE(A1;&amp;quot;@test.com&amp;quot;). Then copy B1 down for each copied A. You may generate fake names in a similar way. Finally, save the file as CSV for import in LS.&lt;br /&gt;
&lt;br /&gt;
With the 1.91, you can use &amp;quot;Generate dummy token&amp;quot; functionnality&lt;br /&gt;
&lt;br /&gt;
= Emailing=&lt;br /&gt;
&lt;br /&gt;
== Email placeholders==&lt;br /&gt;
&lt;br /&gt;
The following field names are allowed in invitation/reminder email templates and must be entered in the survey properties. When sending out the emails these field names will be already replaced in the preview of your invitation/reminder email.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|{ADMINEMAIL}||Email of the Survey admin&lt;br /&gt;
|-&lt;br /&gt;
|{ADMINNAME}||Name of Survey Admin&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYNAME}||Title of your survey&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYDESCRIPTION}||Description of your survey&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The following field names are allowed in invitation/reminder emails (subject and/or body) and will be replaced while sending out the mails:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|{EMAIL}||Email of the recipient&lt;br /&gt;
|-&lt;br /&gt;
|{FIRSTNAME}||First Name&lt;br /&gt;
|-&lt;br /&gt;
|{LASTNAME}||Last Name&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYURL}||The URL pointing to the survey start - if you are sending HTML emails this will be a fully linked HTML version&lt;br /&gt;
|-&lt;br /&gt;
|@@SURVEYURL@@||The URL pointing to the survey start - this is the barebone link. Use this if you want to integrate the link in your custom HTML elements somewhere (available in v1.90 and later)&lt;br /&gt;
|-&lt;br /&gt;
|{OPTOUTURL}||The URL to deactivate sending of mail for this survey  - this will be a fully linked HTML version&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN}||Token to access the survey&lt;br /&gt;
|-&lt;br /&gt;
|{ATTRIBUTE_1}||Attribute 1&lt;br /&gt;
|-&lt;br /&gt;
|{ATTRIBUTE_2}||Attribute 2 (...and so on for more attribute fields)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If your survey is NOT anonymous, the following field names are available to insert token data in survey text and javascript:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|{TOKEN:EMAIL}||Email of the recipient&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:FIRSTNAME}||First Name&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:LASTNAME}||Last Name&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN}||Token to access the survey&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_1}||Attribute 1&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_2}||Attribute 2 (and so on for more attribute fields)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See examples on using [http://docs.limesurvey.org/tiki-index.php?page=Adding+A+Question+#Information_from_tokens_table information from tokens table].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Starting in Version 1.92, you can use [[Expression Manager|Expression Manager]] to use expressions for tailoring an email. Please have a look at the [[Expression Manager HowTos|Expression Manager HowTos]] for an example.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Emails settings==&lt;br /&gt;
#&#039;&#039;&#039;Invitation Email Subject&#039;&#039;&#039;: The subject line for the invitation email that gets sent out when tokens are used with your survey.&lt;br /&gt;
#&#039;&#039;&#039;Invitation Email&#039;&#039;&#039;: This is the text for the invitation email that gets sent out when tokens are used with your survey. This is initially filled by the default invitation message (from the language files) but you can modify it to suit yourself. If you are using English as your base language, the default invitation and reminder text can be found in the limesurvey/tokens.php file. Of course if you don&#039;t plan to use tokens on your survey, whatever is in this field is irrelevant.  You can use the following &amp;quot;form&amp;quot; fields to insert individualized information in each email:&lt;br /&gt;
**&#039;&#039;&#039;{FIRSTNAME}&#039;&#039;&#039; - gets replaced with the token table&#039;s &amp;quot;firstname&amp;quot; value&lt;br /&gt;
**&#039;&#039;&#039;{LASTNAME}&#039;&#039;&#039; - gets replaced with the token table&#039;s &amp;quot;lastname&amp;quot; value&lt;br /&gt;
**&#039;&#039;&#039;{SURVEYNAME}&#039;&#039;&#039; - gets replaced with your surveys name&lt;br /&gt;
**&#039;&#039;&#039;{SURVEYDESCRIPTION}&#039;&#039;&#039; - gets replaced with your surveys description&lt;br /&gt;
**&#039;&#039;&#039;{ATTRIBUTE_1}&#039;&#039;&#039; - gets replaced with the token table&#039;s &amp;quot;attribute_1&amp;quot; value&lt;br /&gt;
**&#039;&#039;&#039;{ATTRIBUTE_2}&#039;&#039;&#039; - gets replaced with the token table&#039;s &amp;quot;attribute_2&amp;quot; value and so on&lt;br /&gt;
**&#039;&#039;&#039;{SURVEYURL}&#039;&#039;&#039; - gets replaced with the fully qualified URL to this particular survey - in HTML emails this is a fully linked HTML link&lt;br /&gt;
**&#039;&#039;&#039;@@SURVEYURL@@&#039;&#039;&#039; - Gets replaced with the survey barebone link. Use this if you want to integrate the link in your custom email HTML (available in v1.90 and later)&lt;br /&gt;
**&#039;&#039;&#039;{OPTOUTURL}&#039;&#039;&#039; - gets replaced with the URL for a respondent to opt-out of this particular survey&lt;br /&gt;
&lt;br /&gt;
Note that these &amp;quot;form fields&amp;quot; apply to the following email fields.&lt;br /&gt;
#&#039;&#039;&#039;Email Reminder Subject&#039;&#039;&#039;: The subject line for the reminder email that gets sent out from the tokens tool&lt;br /&gt;
#&#039;&#039;&#039;Email Reminder&#039;&#039;&#039;: This is the text for the reminder email that gets sent out when tokens are used with your survey. See &amp;quot;invitation email&amp;quot; for specific details on how this field is used.&lt;br /&gt;
#&#039;&#039;&#039;Confirmation Email Subject&#039;&#039;&#039;: When tokens are used, this is the subject line of the email that gets automatically sent to participants after completion of the survey&lt;br /&gt;
#&#039;&#039;&#039;Confirmation Email&#039;&#039;&#039;: This is the text of the email that gets sent to users after completion of the survey. Delete/blank this text remove the confirmation email sending.&lt;br /&gt;
#&#039;&#039;&#039;Public Registration Email Subject&#039;&#039;&#039;: This is the subject line for the invitation email sent to members of the public who register for a survey.&lt;br /&gt;
#&#039;&#039;&#039;Public Registration Email&#039;&#039;&#039;: This is the text for the invitation email sent to members of the public who register for a survey. The same &amp;quot;form fields&amp;quot; apply in this email as in the earlier ones.&lt;br /&gt;
&lt;br /&gt;
==Sending emails==&lt;br /&gt;
&lt;br /&gt;
=== Send invitations===&lt;br /&gt;
&lt;br /&gt;
[[File:token-invite.png]]&lt;br /&gt;
&lt;br /&gt;
You can skip tokens for which the email status field is different from &#039;OK&#039;, by choosing the &#039;Bypass token with failing email addresses&#039; option.&lt;br /&gt;
&lt;br /&gt;
==== Resending invitations====&lt;br /&gt;
&lt;br /&gt;
Sometimes you might want to send invitations again to certain token entries / persons. When you use the &#039;&#039;&#039;send invitations&#039;&#039;&#039;-function only e-mail addresses that &#039;&#039;has not previously received an invitation&#039;&#039; will get one. This means that if you add new addresses to the token list after the first time you sent invitations, only these new addresses will receive an invitation the second time you send invitations.&lt;br /&gt;
&lt;br /&gt;
This means that you can also edit/change an e-mail in a particular token entry that you got a bounce from and then send to only this edited address. Just substitute the date &#039;&#039;&#039;Invite sent?&#039;&#039;&#039; for a capital &#039;&#039;&#039;N&#039;&#039;&#039; (no) and click &#039;&#039;&#039;send invitations&#039;&#039;&#039; again.&lt;br /&gt;
&lt;br /&gt;
==== Participant opt-out====&lt;br /&gt;
&lt;br /&gt;
When you use the {OPTOUTURL} tag in your invitation/reminder email, your participants have the possibility to opt out of this particular survey by just clicking on the related URL in the email - so you don&#039;t harrass them with reminder emails. A participant that opted out of your survey will have the email status &#039;OptOut&#039; set in the token.&lt;br /&gt;
&lt;br /&gt;
=== Send reminders===&lt;br /&gt;
&lt;br /&gt;
[[File:token-remind.png]]&lt;br /&gt;
&lt;br /&gt;
When sending reminders you can:&lt;br /&gt;
* bypass tokens with failing email addresses&lt;br /&gt;
* skip tokens for which an email has been &#039;recently&#039; sent&lt;br /&gt;
* skip tokens for which a given number of emails have already been sent&lt;br /&gt;
&lt;br /&gt;
Note: A reminder will only be send to tokens where the &amp;quot;completed&amp;quot; field is not &amp;quot;N&amp;quot; (this means the respondent has either not taken or has not completed the survey).&lt;br /&gt;
&lt;br /&gt;
=== Sending emails by batch===&lt;br /&gt;
&lt;br /&gt;
When you have to send a lot of emails at the same time, LimeSurvey will only send a first batch of N emails (this threshold is set by the administrator in the Global Settings).&lt;br /&gt;
&lt;br /&gt;
You&#039;ll then need to click &amp;quot;Next&amp;quot; to send the next batch, and so on untill all emails have been sent.&lt;br /&gt;
&lt;br /&gt;
=== Confirmation email===&lt;br /&gt;
&lt;br /&gt;
If you are using tokens and a participant fills out the survey, a confirmation email is sent to his/her email address.&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t want this message to be sent, remove all content from the &amp;quot;Confirmation email subject&amp;quot; and &amp;quot;Confirmation email&amp;quot; fields -  [http://docs.limesurvey.org/tiki-index.php?page=General+FAQ#How_can_I_stop_the_system_from_sending_confirmation_emails see these instructions].&lt;br /&gt;
&lt;br /&gt;
= Public registration=&lt;br /&gt;
&lt;br /&gt;
==Allowing public registration==&lt;br /&gt;
&lt;br /&gt;
You may want to open your survey to the public, but utilize the sort of respondent control available when using tokens. This is possible: If you initialize your tokens table, and have chosen to Allow Public Registration in the main survey setup, people who visit your survey&#039;s URL without a token, will be given the opportunity to register. If they provide an email address that is not already in the current survey&#039;s tokens table, an entry in the tokens table will be created, and they will be emailed an invitation containing their unique Token. All tokens provided to &amp;quot;registering&amp;quot; visitors will begin with the letter &amp;quot;R&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Captchas in public registration==&lt;br /&gt;
&lt;br /&gt;
To protect your survey from robot registration there is a captcha feature on all Registration, Save and Load forms. (starting from version 1.48) This feature is only available if you have GD-support activated in your PHP configuration. (see [[Installation|Installation Requirements]])&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Recurring_forum_posts&amp;diff=2874</id>
		<title>Recurring forum posts</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Recurring_forum_posts&amp;diff=2874"/>
		<updated>2012-01-28T18:02:42Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
This is a collection of recurring forum posts which can be used to copy/paste common answers. Please update if anything is missing.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=More Information=&lt;br /&gt;
&lt;br /&gt;
==Version/Build==&lt;br /&gt;
&lt;br /&gt;
Which &#039;&#039;&#039;version and build&#039;&#039;&#039; of Limesurvey do you use?&lt;br /&gt;
&lt;br /&gt;
............................&lt;br /&gt;
&lt;br /&gt;
Welche Version und welchen Build nutzt du?&lt;br /&gt;
&lt;br /&gt;
==More Details==&lt;br /&gt;
&lt;br /&gt;
Your description as rather vague. Can you please &#039;&#039;&#039;describe your problem in more detail&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
1. What do you do exactly?&lt;br /&gt;
&lt;br /&gt;
2. What do you expect to happen?&lt;br /&gt;
&lt;br /&gt;
3. What happens instead?&lt;br /&gt;
&lt;br /&gt;
4. Any configuration parameters we should know about?&lt;br /&gt;
&lt;br /&gt;
==Path problems==&lt;br /&gt;
&lt;br /&gt;
1. Please post the URL you use to call the admin login.&lt;br /&gt;
&lt;br /&gt;
2. What did you set for $rooturl in config.php?&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
1. Unter welcher URL rufst du den Admin-Login auf?&lt;br /&gt;
&lt;br /&gt;
2. Was hast du in config.php f&amp;amp;uuml;r $rooturl eingesetzt?&lt;br /&gt;
&lt;br /&gt;
==Any Progress?==&lt;br /&gt;
&lt;br /&gt;
Any &#039;&#039;&#039;progress&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
Have you been able to solve your problem? If so, how did you solve it? Any kind of feedback is always appreciated so we know which solution helps best to solve common problems.&lt;br /&gt;
&lt;br /&gt;
..........................&lt;br /&gt;
&lt;br /&gt;
Konntest du das &#039;&#039;&#039;Problem inzwischen l&amp;amp;ouml;sen&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
Falls ja, wie hast du es umgesetzt? Jede Art von Feedback ist immer willkommen, da wir nur so herausfinden, welche L&amp;amp;ouml;sungsvorschl&amp;amp;auml;ge sich f&amp;amp;uuml;r bestimmte Problemstellungen eignen.&lt;br /&gt;
&lt;br /&gt;
==Config.php Settings==&lt;br /&gt;
&lt;br /&gt;
Please post the &#039;&#039;&#039;settings you set in config.php&#039;&#039;&#039; (no real passwords please).&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
Poste bitte mal deine Einstellungen, die du in config.php vorgenommen hast. Bitte keine Passw&amp;amp;ouml;rter offen posten.&lt;br /&gt;
&lt;br /&gt;
==Phpinfo File==&lt;br /&gt;
&lt;br /&gt;
Please upload a &#039;&#039;&#039;phpinfo file&#039;&#039;&#039; so we can take a look at your server configuration. Just put the following code into a file named &#039;&#039;phpinfo.php&#039;&#039; and upload it to your webserver:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[code]&lt;br /&gt;
&lt;br /&gt;
&amp;lt; ?php&lt;br /&gt;
&lt;br /&gt;
phpinfo();&lt;br /&gt;
&lt;br /&gt;
? &amp;gt;&lt;br /&gt;
&lt;br /&gt;
[/code](Delete the spaces next to &amp;lt;/&amp;gt; when copying the code.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After uploading please post the link to the file.&lt;br /&gt;
&lt;br /&gt;
......................................&lt;br /&gt;
&lt;br /&gt;
Bitte erstelle eine &#039;&#039;&#039;phpinfo Datei&#039;&#039;&#039;, damit wir mal einen Blick auf deine Serverkonfiguration werfen k&amp;amp;ouml;nnen. Einfach folgende Zeile in eine neue Textdatei kopieren und diese unter dem Namen &#039;&#039;phpinfo.php&#039;&#039; speichern:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[code]&lt;br /&gt;
&lt;br /&gt;
&amp;lt; ?php&lt;br /&gt;
&lt;br /&gt;
phpinfo();&lt;br /&gt;
&lt;br /&gt;
? &amp;gt;&lt;br /&gt;
&lt;br /&gt;
[/code](Die Leerzeichen bei &amp;lt;/&amp;gt; l&amp;amp;ouml;schen, wenn du den Code kopierst.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dann die Datei auf deinen Server laden und hier den Link posten, Beispiel: &amp;lt;nowiki&amp;gt;www.meinehomepage.de/phpinfo.php&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Bugs/Features=&lt;br /&gt;
&lt;br /&gt;
==Debug Mode==&lt;br /&gt;
&lt;br /&gt;
Please switch on &#039;&#039;&#039;debug mode&#039;&#039;&#039; by adding the following line to your config.php file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]$debug = &#039;1&#039;;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Are there any additional errors reported on top of the page?&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
Schalte bitte mal den &#039;&#039;&#039;Debugging-Modus&#039;&#039;&#039; ein, indem du folgenden Eintrag in deine config.php Datei kopierst:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]$debug = &#039;1&#039;;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Werden irgendwelche zus&amp;amp;auml;tzlichen Fehlermeldungen oben auf der Seite angezeigt?&lt;br /&gt;
&lt;br /&gt;
==Online-Demo==&lt;br /&gt;
&lt;br /&gt;
You can test if this is fixed at the latest version by &amp;lt;nowiki&amp;gt;[url=http://demo.limesurvey.org/admin]testing our online demo[/url]&amp;lt;/nowiki&amp;gt; which always runs the latest Limesurvey version.&lt;br /&gt;
&lt;br /&gt;
Username: admin&lt;br /&gt;
&lt;br /&gt;
Password: test&lt;br /&gt;
&lt;br /&gt;
If you can reproduce the problem there please...&lt;br /&gt;
&lt;br /&gt;
..............................&lt;br /&gt;
&lt;br /&gt;
Du kannst mal auf unserer Onlinedemo, die immer die neueste Limesurveyversion nutzt, testen, ob das Problem dort reproduzierbar ist: &amp;lt;nowiki&amp;gt;[url=http://demo.limesurvey.org/admin]Link[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Username: admin&lt;br /&gt;
&lt;br /&gt;
Password: test&lt;br /&gt;
&lt;br /&gt;
Wenn das Problem dort auch auftaucht, ...&lt;br /&gt;
&lt;br /&gt;
==Update==&lt;br /&gt;
&lt;br /&gt;
Please &#039;&#039;&#039;upgrade&#039;&#039;&#039; to the latest release which contains recent bug fixes and new features.&lt;br /&gt;
&lt;br /&gt;
More information:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]Download latest release[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version]Upgrade instructions[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
..........................&lt;br /&gt;
&lt;br /&gt;
Bitte f&amp;amp;uuml;hre ein &#039;&#039;&#039;Update&#039;&#039;&#039; auf die neueste Version durch, das alle aktuellen Bugfixes enth&amp;amp;auml;lt.&lt;br /&gt;
&lt;br /&gt;
Weitere Infos:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]Download der neuesten Version[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version]Update Anleitung[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Report Bug==&lt;br /&gt;
&lt;br /&gt;
Please test if the problem still exists at  &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]the latest release[/url].&amp;lt;/nowiki&amp;gt; If so please &amp;lt;nowiki&amp;gt;[url=http://bugs.limesurvey.org/]open a ticket at the bugtracker [/url]&amp;lt;/nowiki&amp;gt; and...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[ol]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Give as much information as possible[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Attach your survey. You can mark your ticket &amp;quot;private&amp;quot; so that only the developers will be able to take a look at it.[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Provide step-by-step instructions how to reproduce the problem.[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]If possible/helpful please provide screenshots[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[/ol]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Afterwards please post the link to the bugtracker so we can follow the progress.&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
...............&lt;br /&gt;
&lt;br /&gt;
Pr&amp;amp;uuml;fe bitte, ob das Problem auch in &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]der neuesten Version[/url]&amp;lt;/nowiki&amp;gt; reproduzierbar ist. Falls ja &amp;amp;ouml;ffne bitte ein &amp;lt;nowiki&amp;gt;[url=http://bugs.limesurvey.org/]Ticket im Bugtracker [/url]&amp;lt;/nowiki&amp;gt; und...&lt;br /&gt;
&lt;br /&gt;
1. Beschreibe das Problem so detailliert wie m&amp;amp;ouml;glich (bitte in Englisch).&lt;br /&gt;
&lt;br /&gt;
2. Lade deinen Fragebogen (als exportierte .csv-Datei) hoch. Du kannst deinen Eintrag &amp;quot;privat&amp;quot; machen, so dass nur Entwickler die Datei einsehen k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
3. Schreibe eine kurze Schritt-f&amp;amp;uuml;r-Schritt Anleitung, wie man das Problem reproduzieren kann.&lt;br /&gt;
&lt;br /&gt;
4. Falls m&amp;amp;ouml;glich/sinnvoll h&amp;amp;auml;nge Screenshots an.&lt;br /&gt;
&lt;br /&gt;
Wenn du den &#039;&#039;&#039;Bug berichtet&#039;&#039;&#039; hast, bitte hier den Link eintragen, damit wir den Fortschritt verfolgen k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
Danke!&lt;br /&gt;
&lt;br /&gt;
==Add Feature Request==&lt;br /&gt;
&lt;br /&gt;
You can &amp;lt;nowiki&amp;gt;[url=http://ideas.limesurvey.org/ideatorrent/all_limeSurvey_1/]add this as a feature request at our feature tracker[/url]&amp;lt;/nowiki&amp;gt;. Please describe your idea as detailed as possible and try to outline a suitable solution/implementation as well.&lt;br /&gt;
&lt;br /&gt;
..............................&lt;br /&gt;
&lt;br /&gt;
Du kannst &amp;lt;nowiki&amp;gt;[url=http://ideas.limesurvey.org/ideatorrent/all_limeSurvey_1/]dies als Feature-Request in unserem Feature-Tracker hinzuf&amp;amp;uuml;gen[/url]&amp;lt;/nowiki&amp;gt;. Bitte beschreibe (in Englisch) das Problem so ausf&amp;amp;uuml;hrlich wie m&amp;amp;ouml;glich und versuche Vorschl&amp;amp;auml;ge zur L&amp;amp;ouml;sung des Problems bzw. der Implementierung zu machen. Danke!&lt;br /&gt;
&lt;br /&gt;
=Thanks=&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;You&#039;re welcome :-)&lt;br /&gt;
&lt;br /&gt;
If our hints have been helpful and you enjoy limesurvey [url=http://donate.limesurvey.org/] please consider a donation to the team[/url] .&lt;br /&gt;
&lt;br /&gt;
We do all this in our free time and you don&#039;t have to pay a penny for this software.&lt;br /&gt;
&lt;br /&gt;
Without your help we can&#039;t keep this project alive.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Gern geschehen !&lt;br /&gt;
&lt;br /&gt;
Wenn wir helfen konnten und du Limesurvey magst, schau doch mal, ob du uns [url=http://donate.limesurvey.org/] eine kleine Spende zukommen lassen kannst[/url].&lt;br /&gt;
&lt;br /&gt;
Wir machen das hier alles in unserer Freizeit und das Programm ist absolut kostenlos.&lt;br /&gt;
&lt;br /&gt;
Ohne eure Hilfe kann das Projekt nicht fortgef&amp;amp;uuml;hrt werden.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
................................&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Merci de votre retour !&lt;br /&gt;
&lt;br /&gt;
Si ces informations vous ont aid&amp;amp;eacute; et que vous aimez LimeSurvey&lt;br /&gt;
&lt;br /&gt;
[url=http://donate.limesurvey.org/] veuillez consid&amp;amp;eacute;rer l&#039;opportunit&amp;amp;eacute; d&#039;une donation au projet[/url] .&lt;br /&gt;
&lt;br /&gt;
Le projet LimeSurvey est effectu&amp;amp;eacute; sur notre temps libre et nous ne recevons aucune r&amp;amp;eacute;mun&amp;amp;eacute;ration.&lt;br /&gt;
&lt;br /&gt;
Sans votre aide , le projet ne peut survivre.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Tipps and Tricks=&lt;br /&gt;
&lt;br /&gt;
==SGQA Codes==&lt;br /&gt;
&lt;br /&gt;
You can set Limesurvey to show all codes at the printable survey screen, see this setting:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;$showsgqacode: (&amp;gt;1.91) This setting is used at the printable survey feature Image and defaults to false. If you set $showsgqacode = true; the IDs for each question - and answer if applicable - will be shown; these IDs match the column heading at the Lime_survey_12345 table which holds the answer data for a certain survey. These Ids can be used for a code book for manual database queries.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/Optional+settings&amp;amp;structure;=English+Instructions+for+LimeSurvey#Statistics_and_Response_Browsing]Link to optional settings[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Javascript to hide questions==&lt;br /&gt;
&lt;br /&gt;
To hide a question using Javascript you first have to disable the internal XSS filter at the admin section (global settings -&amp;gt; security -&amp;gt; &amp;quot;Filter HTML for XSS = &#039;no&#039;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Then you have to edit the according question. Edit the question text &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/First+login+-+Your+user+preferences#X._Source_code_mode:]in source code mode[/url]&amp;lt;/nowiki&amp;gt; and add this snippet at the end of the text:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  $(document).ready(function()&lt;br /&gt;
&lt;br /&gt;
  {&lt;br /&gt;
&lt;br /&gt;
     $(&#039;#question4444&#039;).hide();&lt;br /&gt;
&lt;br /&gt;
  });&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/script&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You have to replace the question ID (&amp;quot;4444&amp;quot;) with the &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey#General_Description]ID of the current question[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Configuration=&lt;br /&gt;
&lt;br /&gt;
==XSS Filter==&lt;br /&gt;
&lt;br /&gt;
There is a &#039;&#039;&#039;filter for security reasons&#039;&#039;&#039; which filters javascript input to prevent XSS attacs: &amp;lt;nowiki&amp;gt;[i]&amp;quot;This setting enables filtering of suspicious html tags in survey, group, questions and answer texts in the administration interface. Only leave this to &#039;false&#039; if you absolutely trust the users you created for the administration of LimeSurvey and if you want to allow these users to be able to use Javascript, Flash Movies, etc.&amp;quot;[/i]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check config-defaults.php for a &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Security]setting like &amp;quot;filterxsshtml&amp;quot;[/url]&amp;lt;/nowiki&amp;gt;, copy this setting to config.php and disable the filter.&lt;br /&gt;
&lt;br /&gt;
==Public statistics==&lt;br /&gt;
&lt;br /&gt;
The new feature to &#039;&#039;&#039;show statistics to the user&#039;&#039;&#039; at the end of a survey was introduced in version 1.80RC3. Using this feature the user is presented a link at the end of the survey which takes him to the public statistics.&lt;br /&gt;
&lt;br /&gt;
There are two important settings. At first you have to &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey#Presentation_amp_Navigation]enable public statistics for your current survey[/url]&amp;lt;/nowiki&amp;gt; at survey settings -&amp;gt; presentation &amp;amp; navigation -&amp;gt; Public statistics.&lt;br /&gt;
&lt;br /&gt;
Because often you only want to show statistics for certain questions there is an &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#public_statistics]additional question attribute &amp;quot;public_statistics&amp;quot;[/url]&amp;lt;/nowiki&amp;gt;. This question attribute has to be applied to all questions which should be shown to the user. Note that the use of this question attribute is limited to certain question types (see list at manual -&amp;gt; question attributes -&amp;gt; public_statistics).&lt;br /&gt;
&lt;br /&gt;
Furthermore it is possible to &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey#Presentation_amp_Navigation]set if the public statistics should contain graphs[/url]&amp;lt;/nowiki&amp;gt;. This can also be set individually for each survey at survey settings -&amp;gt; presentation &amp;amp; navigation -&amp;gt; public graphs&lt;br /&gt;
&lt;br /&gt;
=Wiki=&lt;br /&gt;
&lt;br /&gt;
==Add Missing Information==&lt;br /&gt;
&lt;br /&gt;
If you are &#039;&#039;&#039;missing some information in the manual&#039;&#039;&#039; feel free to improve it. &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=English+Instructions+for+LimeSurvey]Our manual[/url]&amp;lt;/nowiki&amp;gt; is a wiki, everyone can edit it and you can&#039;t do much wrong.&lt;br /&gt;
&lt;br /&gt;
So if you miss anything in the manual and you found out how to do it please add this information. Thanks!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org]Unser Handbuch[/url]&amp;lt;/nowiki&amp;gt; ist ein Wiki, jeder kann es &amp;amp;auml;ndern/verbessern. Wir sind hier auf die Hilfe unserer Nutzer angewiesen, also sei doch bitte so nett und f&amp;amp;uuml;ge eine kurze Notiz zu dieser Problematik hinzu, um anderen Nutzern zu helfen.&lt;br /&gt;
&lt;br /&gt;
Danke!&lt;br /&gt;
&lt;br /&gt;
==Add Instructions to Manual==&lt;br /&gt;
&lt;br /&gt;
Thanks a lot for this &#039;&#039;&#039;helpful instructions&#039;&#039;&#039;. Can you &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org]add this to our wiki[/url]&amp;lt;/nowiki&amp;gt;  so that other users can benefit from your solution, too? Would be great!&lt;br /&gt;
&lt;br /&gt;
==Add workaround==&lt;br /&gt;
&lt;br /&gt;
Can you please &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Workarounds] add your solution to the workaround section of our manual[/url]&amp;lt;/nowiki&amp;gt; so other users can beneffit from your solution, too!?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
=IRC=&lt;br /&gt;
&lt;br /&gt;
==Development==&lt;br /&gt;
&lt;br /&gt;
If you have questions about the limesurvey code or how to implement new features it&#039;s always best to &amp;lt;nowiki&amp;gt;[url=http://www.limesurvey.org/index.php/Live-Chat]join the limesurvey IRC[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Our developers don&#039;t hang around in the forum much so please &#039;&#039;&#039;contact them at our IRC&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Be patient, often our developers only answer after a few minutes or the developer who can help you isn&#039;t around. In this case please try again later.&lt;br /&gt;
&lt;br /&gt;
==Donate==&lt;br /&gt;
&lt;br /&gt;
You&#039;re welcome! If our hints have been helpful and you enjoy limesurvey please consider a donation to the team (see &amp;lt;nowiki&amp;gt; http://donate.limesurvey.org&amp;lt;/nowiki&amp;gt;) . We do all this in our free time and you don&#039;t have to pay a penny for this software.&lt;br /&gt;
&lt;br /&gt;
Without your help we can&#039;t keep this project alive.&lt;br /&gt;
&lt;br /&gt;
==Update==&lt;br /&gt;
&lt;br /&gt;
Please upgrade to the latest release. A lot of errors have been fixed in the latest release.&lt;br /&gt;
&lt;br /&gt;
More information:&lt;br /&gt;
&lt;br /&gt;
- Download latest release: http://sourceforge.net/project/showfiles.php?group_id=74605&lt;br /&gt;
&lt;br /&gt;
- Upgrade instructions: http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version&lt;br /&gt;
&lt;br /&gt;
==User pacthes==&lt;br /&gt;
&lt;br /&gt;
Please open a ticket at our bugtracker at the &amp;quot;user patches&amp;quot; section and attach your code files there. The forum is cleaned up regularly so this might get lost if you post it here.&lt;br /&gt;
&lt;br /&gt;
When you are done, please post the link to the bugtracker ticket here.&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
=PM=&lt;br /&gt;
&lt;br /&gt;
Sorry, we don&#039;t give personal support via PM. Please always post your questions in the forum so that other users can participate from the solution.&lt;br /&gt;
&lt;br /&gt;
Best regards,&lt;br /&gt;
&lt;br /&gt;
Mazi (Forum Support)&lt;br /&gt;
&lt;br /&gt;
.....................&lt;br /&gt;
&lt;br /&gt;
Sorry, aber wir geben keinen pers&amp;amp;ouml;nlichen Support per PM. Bitte stelle deine Frage immer im Forum, damit andere Nutzer auch von der L&amp;amp;ouml;sung profitieren k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
Beste Gr&amp;amp;uuml;&amp;amp;szlig;e,&lt;br /&gt;
&lt;br /&gt;
Mazi (Forum Support)&lt;br /&gt;
&lt;br /&gt;
=Login Problems=&lt;br /&gt;
&lt;br /&gt;
==Synchronize Passwords==&lt;br /&gt;
&lt;br /&gt;
We synchronized forum, wiki/manual and bugtracker usernames and passwords. Please set a new password by clicking your username in the forum and chosing edit -&amp;gt; update your profile -&amp;gt; contact info. This way everything will get synchronized and you should be able to log in.&lt;br /&gt;
&lt;br /&gt;
.......................&lt;br /&gt;
&lt;br /&gt;
Wir haben Forum, Handbuch/Wiki und den Bugtracker synchronisiert, so dass man nur noch einen Login ben&amp;amp;ouml;tigt. Damit dies korrekt funktioniert, musst du evtl. auf www.limesurvey.org ein neues Passwort setzen. Einfach im Forum auf deinen Benutzernamen klicken und dann bei edit -&amp;gt; update your profile -&amp;gt; contact info ein neues Passwort festlegen. So sollten alle Komponenten synchronisiert werden.&lt;br /&gt;
&lt;br /&gt;
=Misc=&lt;br /&gt;
&lt;br /&gt;
==Search Forum==&lt;br /&gt;
&lt;br /&gt;
I can&#039;t solve your problem but I think this has been discussed before. Perhaps &#039;&#039;&#039;searching the forum&#039;&#039;&#039; might return helpful results.&lt;br /&gt;
&lt;br /&gt;
==Advanced support==&lt;br /&gt;
&lt;br /&gt;
Sorry, I help users a lot but your request is beyond the common free support. Please &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=UserPage%20Mazi]check out advanced support options[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;X&amp;quot; within certain words==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Limesurvey adds an &amp;quot;X&amp;quot;&#039;&#039;&#039; to certain words for security reasons. These are words like &amp;quot;link, url, ...&amp;quot; which can be used to hack the system. Normally this &amp;quot;X&amp;quot; won&#039;t show up at the final but is only shown at the admin panel.&lt;br /&gt;
&lt;br /&gt;
==Styling questions==&lt;br /&gt;
&lt;br /&gt;
Take a look at the &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Templates+%2F+The+template+editor#Styling_questions_in_LimeSurvey_1_8]instructions about styling questions[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Edit Translation==&lt;br /&gt;
&lt;br /&gt;
This text string can be changed by &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+1.x+Translating+LimeSurvey]editing the translation[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Cross postings==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=]No cross posting please! [/url]&amp;lt;/nowiki&amp;gt; It&#039;s always best to ask your question at the english forum because there are more user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;-&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=]Bitte keine doppelten Postings! [/url]&amp;lt;/nowiki&amp;gt; Am besten stellst du deine Frage immer im englischen Unterforum, dort sind mehr Leute unterwegs.&lt;br /&gt;
&lt;br /&gt;
==German threads in german forum==&lt;br /&gt;
&lt;br /&gt;
In den englischen Foren bitte nur englisch schreiben, das sorgt sonst immer mal wieder f&amp;amp;uuml;r Verwirrung. Wenn du einen deutschen Beitrag verfasst bitte das &amp;lt;nowiki&amp;gt;[url=www.limesurvey.org/de/forum/deutsches-forum]deutsche Forum[/url]&amp;lt;/nowiki&amp;gt; benutzen. Ich werde einen Mod kurz darauf hinweisen diesen Thread hier mal schnell in das deutsche Forum zu verschieben.&lt;br /&gt;
&lt;br /&gt;
@Mods: Can someone please move this thread to the German forum? Thank you!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2170</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2170"/>
		<updated>2012-01-26T14:04:39Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= User management=&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user open the user management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAddUser.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation email with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation email to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Setting global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetGlobalPermissions.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following rights.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This right can only be added or removed by the user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This right is very powerful and you should be very carfefully with granting this right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This right lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: 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.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the rights.&lt;br /&gt;
* &#039;&#039;&#039;Use all/manage templates&#039;&#039;&#039;: 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 use the template permissions.&lt;br /&gt;
* &#039;&#039;&#039;Manage labels&#039;&#039;&#039;: This right grants all rights regarding label sets (create, edit and delete).&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user rights are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
==Setting template permissions for a user==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
To set/edit the template permissions for a user simply click the key symbol for design templates [[File:LimeSurveySchluesselSymbolTemplates.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now select the design templates this user can select. After you finished your selection/deselection just hit &#039;&#039;&#039;Save settings&#039;&#039;&#039; .&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user rights are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=Setting permissions for a single survey=&lt;br /&gt;
&lt;br /&gt;
These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; An existing user account is required to set permissions for a single survey. If the account doesn&#039;t exist you have to create it first and then change the survey permissions. You don&#039;t have to apply any global rights to the user, it is just necessary that the user account itself exists.&lt;br /&gt;
&lt;br /&gt;
==Setting user permissions for a single survey==&lt;br /&gt;
&lt;br /&gt;
To change the survey permissions you have to select &#039;&#039;&#039;Survey permissions&#039;&#039;&#039; from the &#039;&#039;&#039;Survey properties&#039;&#039;&#039; menu.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySurveyPermissions.jpg]]&lt;br /&gt;
&lt;br /&gt;
In the next step you select the user you want to change the survey rights and click &#039;&#039;&#039;Add user&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAddSurveyPermission.jpg]]&lt;br /&gt;
&lt;br /&gt;
After you click &#039;&#039;&#039;Set survey permissions&#039;&#039;&#039; the survey permissions matrix for the survey and user will be shown.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUserPermissionMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In the other columns you can choose whether a user can do a single actions from this feature/part.&lt;br /&gt;
&lt;br /&gt;
After you finished editing the survey permissions click &#039;&#039;&#039;Save now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user rights are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=use cases=&lt;br /&gt;
&lt;br /&gt;
In this part of the article we&#039;ll provide a few ideas which use cases may exist and how and which rights would be a good choice.&lt;br /&gt;
&lt;br /&gt;
==A new person in charge for administrating LimeSurvey will be added==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039;&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;&lt;br /&gt;
* not necessary: Setting the template permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all templates)&lt;br /&gt;
* not necessary: Setting the survey permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all surveys)&lt;br /&gt;
&lt;br /&gt;
==A new user wants to create own surveys==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;Create survey&#039;&#039;&#039;&lt;br /&gt;
* Set template permissions for user to the template/s that should be used by the user/user-group&lt;br /&gt;
* not necessary: Setting the survey permissions (The creator of a survey has all permissions for his/her surveys)&lt;br /&gt;
&lt;br /&gt;
==The creator of a survey needs another person to edit his/her survey==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* 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 &#039;&#039;&#039;&amp;lt;&amp;lt;&#039;&#039;&#039; or &#039;&#039;&#039;&amp;gt;&amp;gt;&#039;&#039;&#039; button as header).&lt;br /&gt;
&lt;br /&gt;
==A person responisble for the survey wants to see the results of the survey and export them==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set survey permissions to: &#039;&#039;&#039;Responses&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039; and &#039;&#039;&#039;export&#039;&#039;&#039; , &#039;&#039;&#039;Statistics&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyCusomerOwnStatistics.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Article was translated and used with approval from &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; (24/7 IT-SERVICES GmbH).&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2171</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2171"/>
		<updated>2012-01-26T13:51:16Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAddUser.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Setting global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetGlobalPermissions.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following permissions.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This permission can only be added or removed by the  Diese Berechtigung user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This permission is very powerful and you should be very carfefully with granting this permission/right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This permission lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: With this permission a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: Having this permission 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the permissions.&lt;br /&gt;
* &#039;&#039;&#039;Use all/manage templates&#039;&#039;&#039;: It allows the user to use all design templates and edit all non standard templates. A person with this permission 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 use the template permissions.&lt;br /&gt;
* &#039;&#039;&#039;Manage labels&#039;&#039;&#039;: This permission grants all rights regarding label sets (create, edit and delete).&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
==Setting template permissions for a user==&lt;br /&gt;
&lt;br /&gt;
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 design templates to be used in a survey.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
To set/edit the template permissions for a user for a user simply click the key symbol for design templates [[File:LimeSurveySchluesselSymbolTemplates.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now select the design templates this user can select. After you finished your selection/deselection just hit &#039;&#039;&#039;Save settings&#039;&#039;&#039; .&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=Setting permissions for a single survey=&lt;br /&gt;
&lt;br /&gt;
These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; An existing user account is required to set permissions for a single survey. If it doesn&#039;t exist you have to create it first and then change the survey permissions. You don&#039;t have to apply any global permissions to the user, it is just necessary that the user account itself exists.&lt;br /&gt;
&lt;br /&gt;
==Setting user permissions for a single survey==&lt;br /&gt;
&lt;br /&gt;
To change the survey permissions you have to select &#039;&#039;&#039;Survey permissions&#039;&#039;&#039; from the &#039;&#039;&#039;Survey properties&#039;&#039;&#039; menu.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySurveyPermissions.jpg]]&lt;br /&gt;
&lt;br /&gt;
In the next step you select the user you want to change the survey permissions and click &#039;&#039;&#039;Add user&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAddSurveyPermission.jpg]]&lt;br /&gt;
&lt;br /&gt;
After you click &#039;&#039;&#039;Set survey permissions&#039;&#039;&#039; the survey permissions matrix for the survey and user will be shown.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUserPermissionMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In this matrix you can set the permissions for the different features and parts. You simply click  a checkbox if you want to add or remove this permission. If you click a checkbox in the first column all permissions for this line will be selected/removed.&lt;br /&gt;
&lt;br /&gt;
In the other columns you can choose whether a user can do a single actions from this feature/part.&lt;br /&gt;
&lt;br /&gt;
After you finished editing the survey permissions click &#039;&#039;&#039;Save now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=use cases=&lt;br /&gt;
&lt;br /&gt;
In this part of the article we&#039;ll provide a few ideas which use cases may exist and how and which permissions would be a good choice.&lt;br /&gt;
&lt;br /&gt;
==A new person in charge for administrating LimeSurvey will be added==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039;&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;&lt;br /&gt;
* not necessary: Setting the template permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all templates)&lt;br /&gt;
* not necessary: Setting the survey permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all surveys)&lt;br /&gt;
&lt;br /&gt;
==A new user wants to create own surveys==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;Create survey&#039;&#039;&#039;&lt;br /&gt;
* Set template permissions for user to the template/s that should be used by the user/user-group&lt;br /&gt;
* not necessary: Setting the survey permissions (The creator of a survey has all permissions for his/her surveys)&lt;br /&gt;
&lt;br /&gt;
==The creator of a survey needs another person to edit his/her survey==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* 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 &#039;&#039;&#039;&amp;lt;&amp;lt;&#039;&#039;&#039; or &#039;&#039;&#039;&amp;gt;&amp;gt;&#039;&#039;&#039; button as header).&lt;br /&gt;
&lt;br /&gt;
==A person responisble for the survey wants to see the results of the survey and export them==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set survey permissions to: &#039;&#039;&#039;Responses&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039; and &#039;&#039;&#039;export&#039;&#039;&#039; , &#039;&#039;&#039;Statistics&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyCusomerOwnStatistics.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Article was translated and used with approval from &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; (24/7 IT-SERVICES GmbH).&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2172</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2172"/>
		<updated>2012-01-26T13:13:41Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; This aritcle is currently being updated/re-translated form the german version. Please remain from editing this page unless this banner is removed.&lt;br /&gt;
&lt;br /&gt;
Thank you! vierundzwanzig&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerHinzufuegen.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Setting global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetzeGlobalBer.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following permissions.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This permission can only be added or removed by the  Diese Berechtigung user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This permission is very powerful and you should be very carfefully with granting this permission/right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This permission lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: With this permission a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: Having this permission 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the permissions.&lt;br /&gt;
* &#039;&#039;&#039;Use all/manage templates&#039;&#039;&#039;: It allows the user to use all design templates and edit all non standard templates. A person with this permission 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 use the template permissions.&lt;br /&gt;
* &#039;&#039;&#039;Manage labels&#039;&#039;&#039;: This permission grants all rights regarding label sets (create, edit and delete).&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
==Setting template permissions for a user==&lt;br /&gt;
&lt;br /&gt;
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 design templates to be used in a survey.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
To set/edit the template permissions for a user for a user simply click the key symbol for design templates [[File:LimeSurveySchluesselSymbolTemplates.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAuswahlDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now select the design templates this user can select. After you finished your selection/deselection just hit &#039;&#039;&#039;Save settings&#039;&#039;&#039; .&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=Setting permissions for a single survey=&lt;br /&gt;
&lt;br /&gt;
These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; An existing user account is required to set permissions for a single survey. If it doesn&#039;t exist you have to create it first and then change the survey permissions. You don&#039;t have to apply any global permissions to the user, it is just necessary that the user account itself exists.&lt;br /&gt;
&lt;br /&gt;
==Setting user permissions for a single survey==&lt;br /&gt;
&lt;br /&gt;
To change the survey permissions you have to select &#039;&#039;&#039;Survey permissions&#039;&#039;&#039; from the &#039;&#039;&#039;Survey properties&#039;&#039;&#039; menu.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUmfragenBerechtigungen.jpg]]&lt;br /&gt;
&lt;br /&gt;
In the next step you select the user you want to change the survey permissions and click &#039;&#039;&#039;Add user&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenBerHinz.jpg]]&lt;br /&gt;
&lt;br /&gt;
After you click &#039;&#039;&#039;Set survey permissions&#039;&#039;&#039; the survey permissions matrix for the survey and user will be shown.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerBerechtigungMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In this matrix you can set the permissions for the different features and parts. You simply click  a checkbox if you want to add or remove this permission. If you click a checkbox in the first column all permissions for this line will be selected/removed.&lt;br /&gt;
&lt;br /&gt;
In the other columns you can choose whether a user can do a single actions from this feature/part.&lt;br /&gt;
&lt;br /&gt;
After you finished editing the survey permissions click &#039;&#039;&#039;Save now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=use cases=&lt;br /&gt;
&lt;br /&gt;
In this part of the article we&#039;ll provide a few ideas which use cases may exist and how and which permissions would be a good choice.&lt;br /&gt;
&lt;br /&gt;
==A new person in charge for administrating LimeSurvey will be added==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039;&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;&lt;br /&gt;
* not necessary: Setting the template permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all templates)&lt;br /&gt;
* not necessary: Setting the survey permissions (&#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has all permissions for all surveys)&lt;br /&gt;
&lt;br /&gt;
==A new user wants to create own surveys==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set global permissions for user to &#039;&#039;&#039;Create survey&#039;&#039;&#039;&lt;br /&gt;
* Set template permissions for user to the template/s that should be used by the user/user-group&lt;br /&gt;
* not necessary: Setting the survey permissions (The creator of a survey has all permissions for his/her surveys)&lt;br /&gt;
&lt;br /&gt;
==The creator of a survey needs another person to edit his/her survey==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* 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 &#039;&#039;&#039;&amp;lt;&amp;lt;&#039;&#039;&#039; or &#039;&#039;&#039;&amp;gt;&amp;gt;&#039;&#039;&#039; button as header).&lt;br /&gt;
&lt;br /&gt;
==A person responisble for the survey wants to see the results of the survey and export them==&lt;br /&gt;
* login as &#039;&#039;&#039;admin&#039;&#039;&#039; or user with &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; permission.&lt;br /&gt;
* Create a new user account&lt;br /&gt;
* Set &#039;&#039;&#039;no global permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set &#039;&#039;&#039;no template permissions&#039;&#039;&#039; for user&lt;br /&gt;
* Set survey permissions to: &#039;&#039;&#039;Responses&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039; and &#039;&#039;&#039;export&#039;&#039;&#039; , &#039;&#039;&#039;Statistics&#039;&#039;&#039;: &#039;&#039;&#039;View/read&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyKundeEigeneAuswertung.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Article was translated and used with approval from &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; (24/7 IT-SERVICES GmbH).&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2173</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2173"/>
		<updated>2012-01-26T10:09:55Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; This aritcle is currently being updated/re-translated form the german version. Please remain from editing this page unless this banner is removed.&lt;br /&gt;
&lt;br /&gt;
Thank you! vierundzwanzig&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerHinzufuegen.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Setting global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetzeGlobalBer.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following permissions.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This permission can only be added or removed by the  Diese Berechtigung user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This permission is very powerful and you should be very carfefully with granting this permission/right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This permission lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: With this permission a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: Having this permission 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the permissions.&lt;br /&gt;
* &#039;&#039;&#039;Use all/manage templates&#039;&#039;&#039;: It allows the user to use all design templates and edit all non standard templates. A person with this permission 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 use the template permissions.&lt;br /&gt;
* &#039;&#039;&#039;Manage labels&#039;&#039;&#039;: This permission grants all rights regarding label sets (create, edit and delete).&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
==Setting template permissions for a user==&lt;br /&gt;
&lt;br /&gt;
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 design templates to be used in a survey.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
To set/edit the template permissions for a user for a user simply click the key symbol for design templates [[File:LimeSurveySchluesselSymbolTemplates.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAuswahlDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now select the design templates this user can select. After you finished your selection/deselection just hit &#039;&#039;&#039;Save settings&#039;&#039;&#039; .&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=Setting permissions for a single survey=&lt;br /&gt;
&lt;br /&gt;
These permissions only apply for a single survey. If you want to set permissions for the whole system you can use the global permissions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; An existing user account is required to set permissions for a single survey. If it doesn&#039;t exist you have to create it first and then change the survey permissions. You don&#039;t have to apply any global permissions to the user, it is just necessary that the user account itself exists.&lt;br /&gt;
&lt;br /&gt;
==Setting user permissions for a single survey==&lt;br /&gt;
&lt;br /&gt;
To change the survey permissions you have to select &#039;&#039;&#039;Survey permissions&#039;&#039;&#039; from the &#039;&#039;&#039;Survey properties&#039;&#039;&#039; menu.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUmfragenBerechtigungen.jpg]]&lt;br /&gt;
&lt;br /&gt;
In the next step you select the user you want to change the survey permissions and click &#039;&#039;&#039;Add user&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenBerHinz.jpg]]&lt;br /&gt;
&lt;br /&gt;
After you click &#039;&#039;&#039;Set survey permissions&#039;&#039;&#039; the survey permissions matrix for the survey and user will be shown.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerBerechtigungMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In this matrix you can set the permissions for the different features and parts. You simply click  a checkbox if you want to add or remove this permission. If you click a checkbox in the first column all permissions for this line will be selected/removed.&lt;br /&gt;
&lt;br /&gt;
In the other columns you can choose whether a user can do a single actions from this feature/part.&lt;br /&gt;
&lt;br /&gt;
After you finished editing the survey permissions click &#039;&#039;&#039;Save now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
=use cases=&lt;br /&gt;
&lt;br /&gt;
In this part of the article we&#039;ll provide a few ideas which use cases may exist and how and which permissions would be good.&lt;br /&gt;
&lt;br /&gt;
==Neuer Betreuer der LimeSurvey-Software kommt hinzu==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Vorlagen-Berechtigungen (hat &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; eh alle)&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (&#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; hat eh alle Berechtigungen f&amp;amp;uuml;r alle Umfragen)&lt;br /&gt;
&lt;br /&gt;
==Neuer Benutzer m&amp;amp;ouml;chte Umfragen selbst erstellen==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Erstelle Umfrage&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen nach Herkunft/Gruppe des Benutzers/Kunden&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (Benutzer hat f&amp;amp;uuml;r die Umfragen die er erstellt eh alle Berechtigungen)&lt;br /&gt;
&lt;br /&gt;
==Ersteller braucht weiteren Benutzer der seine Umfrage bearbeiten darf==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: Nach Wunsch des Besitzers der Umfrage und wie viel Macht der Benutzer haben darf/soll. Wenn gleiche Rechte f&amp;amp;uuml;r Umfrage wie der Besitzer ausgew&amp;amp;auml;hlt werden soll f&amp;amp;uuml;r alle Bereiche alle Berechtigungen ausw&amp;amp;auml;hlen (Klick auf die Checkboxen in der ersten Spalte nach den Bereichsbezeichnungen)&lt;br /&gt;
&lt;br /&gt;
==Verantwortlicher m&amp;amp;ouml;chte die Ergebnisse einer beauftragten Umfrage einsehen und exportieren==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: &#039;&#039;&#039;Antworten&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039; und &#039;&#039;&#039;Export&#039;&#039;&#039; , &#039;&#039;&#039;Statistiken&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyKundeEigeneAuswertung.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Artikel wurde mit Einverst&amp;amp;auml;ndniserkl&amp;amp;auml;rung von &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; aus dem Firmen-Wiki der 24/7 IT-SERVICES GmbH &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2174</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2174"/>
		<updated>2012-01-25T15:42:23Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; This aritcle is currently being updated/re-translated form the german version. Please remain from editing this page unless this banner is removed.&lt;br /&gt;
&lt;br /&gt;
Thank you! vierundzwanzig&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerHinzufuegen.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
Global permissions apply to the whole LimeSurvey installation. If you want to set a permission only for a specific survey you can use the Survey permissions settings.&lt;br /&gt;
&lt;br /&gt;
==Set global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetzeGlobalBer.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following permissions.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This permission can only be added or removed by the  Diese Berechtigung user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This permission is very powerful and you should be very carfefully with granting this permission/right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This permission lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: With this permission a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: Having this permission 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the permissions.&lt;br /&gt;
* &#039;&#039;&#039;Use all/manage templates&#039;&#039;&#039;: It allows the user to use all design templates and edit all non standard templates. A person with this permission 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 use the template permissions.&lt;br /&gt;
* &#039;&#039;&#039;Manage labels&#039;&#039;&#039;: This permission grants all rights regarding label sets (create, edit and delete).&lt;br /&gt;
&lt;br /&gt;
The most important use cases for granting user permissions are collected at the &#039;&#039;&#039;use cases&#039;&#039;&#039; part of this article.&lt;br /&gt;
&lt;br /&gt;
==Vorlagenberechtigungen f&amp;amp;uuml;r einen Benutzer setzen==&lt;br /&gt;
&lt;br /&gt;
Mit den Vorlagenberechtigungen kann festgelegt werden welche Design-Vorlagen der Nutzer beim Erstellen oder Bearbeiten einer Umfrage ausw&amp;amp;auml;hlen/verwenden kann. Es ist sinnvoll jene Auswahl einzuschr&amp;amp;auml;nken um den Benutzer nicht zu &amp;amp;uuml;berfordern und zu verhindern dass ungewollt Design-Vorlagen verwendet werden die nicht verwendet werden sollen.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Wenn es f&amp;amp;uuml;r bestimmte Benutzer-Gruppen oder Kunden eigene Design-Vorlagen gibt sollten wenn m&amp;amp;ouml;glich auch nur jene auf verf&amp;amp;uuml;gbar gestellt werden.&lt;br /&gt;
&lt;br /&gt;
Zum Setzen der Vorlagenberechtigungen einfach auf das Schl&amp;amp;uuml;ssel-Symbol f&amp;amp;uuml;r die Design-Vorlagen&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySchluesselSymbolTemplates.jpg]] klicken.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAuswahlDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nun k&amp;amp;ouml;nnen die gew&amp;amp;uuml;nschten Design-Vorlagen die der Benutzer verwenden k&amp;amp;ouml;nnen soll ausgew&amp;amp;auml;hlt werden. Am Ende werden die Einstellungen mit einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; best&amp;amp;auml;tigt.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Berechtigungen nur f&amp;amp;uuml;r eine einzelne Umfrage=&lt;br /&gt;
&lt;br /&gt;
Diese Berechtigungen gelten nur f&amp;amp;uuml;r eine einzelne Umfrage. Sollen einem Benutzer Berechtigungen f&amp;amp;uuml;r das ganze System &amp;amp;uuml;bergeben werden m&amp;amp;uuml;ssen die globalen Berechtigungen verwendet werden.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Auch f&amp;amp;uuml;r Berechtigungen f&amp;amp;uuml;r einzelne Umfragen muss ein Benutzer-Account vorhanden sein bzw. angelegt werden wenn er es noch nicht sein sollte. Der Benutzer muss jedoch keine globale Berechtigung besitzen, es reicht wenn er nur existiert.&lt;br /&gt;
&lt;br /&gt;
==Benutzer-Berechtigungen f&amp;amp;uuml;r eine Umfrage &amp;amp;auml;ndern==&lt;br /&gt;
&lt;br /&gt;
Um die Berechtigungen f&amp;amp;uuml;r eine einzelne Umfrage zu setzen w&amp;amp;auml;hlt man im Men&amp;amp;uuml; &#039;&#039;&#039;Umfragen-Einstellungen&#039;&#039;&#039; den Men&amp;amp;uuml;punkt &#039;&#039;&#039;Umfrageberechtigungen&#039;&#039;&#039; aus.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUmfragenBerechtigungen.jpg]]&lt;br /&gt;
&lt;br /&gt;
Im n&amp;amp;auml;chsten Schritt wird der Benutzer ausgew&amp;amp;auml;hlt dem die Berechtigung gesetzt werden soll und auf &#039;&#039;&#039;Benutzer hinzuf&amp;amp;uuml;gen&#039;&#039;&#039; geklickt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenBerHinz.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nach einem Klick auf &#039;&#039;&#039;Bearbeite Umfrageberechtigungen&#039;&#039;&#039; wird die Benutzerberechtigungsmatrix f&amp;amp;uuml;r die Umfrage angezeigt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerBerechtigungMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In dieser Matrix k&amp;amp;ouml;nnen die Berechtigungen f&amp;amp;uuml;r die einzelnen Bereiche festgelegt werden. Durch einen Klick in die Checkbox in der ersten Spalte nach den Bereichsbezeichnungen k&amp;amp;ouml;nnen alle Berechtigungen f&amp;amp;uuml;r einen Bereich ausgew&amp;amp;auml;hlt werden. In den weiteren Spalten k&amp;amp;ouml;nnen wenn ben&amp;amp;ouml;tigt die einzelnen Berechtigungen hinzugef&amp;amp;uuml;gt oder entfernt werden falls nicht alle Berechtigungen ausgew&amp;amp;auml;hlt/m&amp;amp;ouml;glich sein sollen. Nach einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; werden die &amp;amp;Auml;nderungen &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Anwendungsf&amp;amp;auml;lle=&lt;br /&gt;
&lt;br /&gt;
Hier wird f&amp;amp;uuml;r die h&amp;amp;auml;ufigsten Anwendungsf&amp;amp;auml;lle und Vorkommnisse festgehalten welche Berechtigungen in diesem Fall gesetzt werden sollten.&lt;br /&gt;
&lt;br /&gt;
==Neuer Betreuer der LimeSurvey-Software kommt hinzu==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Vorlagen-Berechtigungen (hat &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; eh alle)&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (&#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; hat eh alle Berechtigungen f&amp;amp;uuml;r alle Umfragen)&lt;br /&gt;
&lt;br /&gt;
==Neuer Benutzer m&amp;amp;ouml;chte Umfragen selbst erstellen==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Erstelle Umfrage&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen nach Herkunft/Gruppe des Benutzers/Kunden&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (Benutzer hat f&amp;amp;uuml;r die Umfragen die er erstellt eh alle Berechtigungen)&lt;br /&gt;
&lt;br /&gt;
==Ersteller braucht weiteren Benutzer der seine Umfrage bearbeiten darf==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: Nach Wunsch des Besitzers der Umfrage und wie viel Macht der Benutzer haben darf/soll. Wenn gleiche Rechte f&amp;amp;uuml;r Umfrage wie der Besitzer ausgew&amp;amp;auml;hlt werden soll f&amp;amp;uuml;r alle Bereiche alle Berechtigungen ausw&amp;amp;auml;hlen (Klick auf die Checkboxen in der ersten Spalte nach den Bereichsbezeichnungen)&lt;br /&gt;
&lt;br /&gt;
==Verantwortlicher m&amp;amp;ouml;chte die Ergebnisse einer beauftragten Umfrage einsehen und exportieren==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: &#039;&#039;&#039;Antworten&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039; und &#039;&#039;&#039;Export&#039;&#039;&#039; , &#039;&#039;&#039;Statistiken&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyKundeEigeneAuswertung.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Artikel wurde mit Einverst&amp;amp;auml;ndniserkl&amp;amp;auml;rung von &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; aus dem Firmen-Wiki der 24/7 IT-SERVICES GmbH &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2175</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2175"/>
		<updated>2012-01-25T15:23:43Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; This aritcle is currently being updated/re-translated form the german version. Please remain from editing this page unless this banner is removed.&lt;br /&gt;
&lt;br /&gt;
Thank you! vierundzwanzig&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerHinzufuegen.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user permissions if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit users==&lt;br /&gt;
&lt;br /&gt;
You can use the pen symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Delete users==&lt;br /&gt;
&lt;br /&gt;
To delete a user account simply click the delete button [[File:LimeSurveyBenutzerLoeschen.jpg]] in the line with the user account that should be deleted and hit &#039;&#039;&#039;OK&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
=Global permissions=&lt;br /&gt;
&lt;br /&gt;
Global permissions apply to the whole LimeSurvey installation. If you want to set a permission only for a specific survey you can use the Survey permissions settings.&lt;br /&gt;
&lt;br /&gt;
==Set global permissions for a user==&lt;br /&gt;
&lt;br /&gt;
To set global permissions for a user just click the key symbol [[File:LimeSurveySchluesselSymbol.jpg]].&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetzeGlobalBer.jpg]]&lt;br /&gt;
&lt;br /&gt;
You can now add or remove the following permissions.&lt;br /&gt;
* &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039;: This permission can only be added or removed by the  Diese Berechtigung user called &#039;&#039;&#039;admin&#039;&#039;&#039; and grants full rights to the whole LimeSurvey installation. &#039;&#039;&#039;Please note:&#039;&#039;&#039; This permission is very powerful and you should be very carfefully with granting this permission/right.&lt;br /&gt;
* &#039;&#039;&#039;Create survey&#039;&#039;&#039;: This permission lets the user create a survey as well as start, stop and it . This is the standard permission for people creating their own surveys.&lt;br /&gt;
* &#039;&#039;&#039;Configurator&#039;&#039;&#039;: With this permission a user can check data integrity, save the SQL database to an sql file and view the php info in the global settings.&lt;br /&gt;
* &#039;&#039;&#039;Create user&#039;&#039;&#039;: Having this permission 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 &#039;&#039;&#039;SuperAdministrator&#039;&#039;&#039; has to grant the permissions.&lt;br /&gt;
* &#039;&#039;&#039;Nutze alle/verwalte Vorlagen&#039;&#039;&#039;: Mit dieser Berechtigung kann der Benutzer auf alle Design-Vorlagen zugreifen und jene alle Nicht-Standard-Vorlagen bearbeiten. Diese Berechtigung ist vermutlich nur sinnvoll f&amp;amp;uuml;r Personen die Design-Templates bearbeiten m&amp;amp;uuml;ssen und &amp;amp;uuml;ber ausreichende HTML/php, Javascript und CSS-Kenntnisse verf&amp;amp;uuml;gen. F&amp;amp;uuml;r normale Benutzer empfiehlt es sich die Berechtigung &amp;amp;uuml;ber die Vorlagenberechtigungen nach Bedarf zu setzen.&lt;br /&gt;
* &#039;&#039;&#039;Beschriftungs-Sets verwalten&#039;&#039;&#039;: Mit dieser Berechtigungen k&amp;amp;ouml;nnen alle Beschriftungssets verwaltet (neue erstellt, vorhandene bearbeitet und gel&amp;amp;ouml;scht werden).&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
==Vorlagenberechtigungen f&amp;amp;uuml;r einen Benutzer setzen==&lt;br /&gt;
&lt;br /&gt;
Mit den Vorlagenberechtigungen kann festgelegt werden welche Design-Vorlagen der Nutzer beim Erstellen oder Bearbeiten einer Umfrage ausw&amp;amp;auml;hlen/verwenden kann. Es ist sinnvoll jene Auswahl einzuschr&amp;amp;auml;nken um den Benutzer nicht zu &amp;amp;uuml;berfordern und zu verhindern dass ungewollt Design-Vorlagen verwendet werden die nicht verwendet werden sollen.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Wenn es f&amp;amp;uuml;r bestimmte Benutzer-Gruppen oder Kunden eigene Design-Vorlagen gibt sollten wenn m&amp;amp;ouml;glich auch nur jene auf verf&amp;amp;uuml;gbar gestellt werden.&lt;br /&gt;
&lt;br /&gt;
Zum Setzen der Vorlagenberechtigungen einfach auf das Schl&amp;amp;uuml;ssel-Symbol f&amp;amp;uuml;r die Design-Vorlagen&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySchluesselSymbolTemplates.jpg]] klicken.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAuswahlDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nun k&amp;amp;ouml;nnen die gew&amp;amp;uuml;nschten Design-Vorlagen die der Benutzer verwenden k&amp;amp;ouml;nnen soll ausgew&amp;amp;auml;hlt werden. Am Ende werden die Einstellungen mit einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; best&amp;amp;auml;tigt.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Berechtigungen nur f&amp;amp;uuml;r eine einzelne Umfrage=&lt;br /&gt;
&lt;br /&gt;
Diese Berechtigungen gelten nur f&amp;amp;uuml;r eine einzelne Umfrage. Sollen einem Benutzer Berechtigungen f&amp;amp;uuml;r das ganze System &amp;amp;uuml;bergeben werden m&amp;amp;uuml;ssen die globalen Berechtigungen verwendet werden.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Auch f&amp;amp;uuml;r Berechtigungen f&amp;amp;uuml;r einzelne Umfragen muss ein Benutzer-Account vorhanden sein bzw. angelegt werden wenn er es noch nicht sein sollte. Der Benutzer muss jedoch keine globale Berechtigung besitzen, es reicht wenn er nur existiert.&lt;br /&gt;
&lt;br /&gt;
==Benutzer-Berechtigungen f&amp;amp;uuml;r eine Umfrage &amp;amp;auml;ndern==&lt;br /&gt;
&lt;br /&gt;
Um die Berechtigungen f&amp;amp;uuml;r eine einzelne Umfrage zu setzen w&amp;amp;auml;hlt man im Men&amp;amp;uuml; &#039;&#039;&#039;Umfragen-Einstellungen&#039;&#039;&#039; den Men&amp;amp;uuml;punkt &#039;&#039;&#039;Umfrageberechtigungen&#039;&#039;&#039; aus.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUmfragenBerechtigungen.jpg]]&lt;br /&gt;
&lt;br /&gt;
Im n&amp;amp;auml;chsten Schritt wird der Benutzer ausgew&amp;amp;auml;hlt dem die Berechtigung gesetzt werden soll und auf &#039;&#039;&#039;Benutzer hinzuf&amp;amp;uuml;gen&#039;&#039;&#039; geklickt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenBerHinz.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nach einem Klick auf &#039;&#039;&#039;Bearbeite Umfrageberechtigungen&#039;&#039;&#039; wird die Benutzerberechtigungsmatrix f&amp;amp;uuml;r die Umfrage angezeigt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerBerechtigungMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In dieser Matrix k&amp;amp;ouml;nnen die Berechtigungen f&amp;amp;uuml;r die einzelnen Bereiche festgelegt werden. Durch einen Klick in die Checkbox in der ersten Spalte nach den Bereichsbezeichnungen k&amp;amp;ouml;nnen alle Berechtigungen f&amp;amp;uuml;r einen Bereich ausgew&amp;amp;auml;hlt werden. In den weiteren Spalten k&amp;amp;ouml;nnen wenn ben&amp;amp;ouml;tigt die einzelnen Berechtigungen hinzugef&amp;amp;uuml;gt oder entfernt werden falls nicht alle Berechtigungen ausgew&amp;amp;auml;hlt/m&amp;amp;ouml;glich sein sollen. Nach einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; werden die &amp;amp;Auml;nderungen &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Anwendungsf&amp;amp;auml;lle=&lt;br /&gt;
&lt;br /&gt;
Hier wird f&amp;amp;uuml;r die h&amp;amp;auml;ufigsten Anwendungsf&amp;amp;auml;lle und Vorkommnisse festgehalten welche Berechtigungen in diesem Fall gesetzt werden sollten.&lt;br /&gt;
&lt;br /&gt;
==Neuer Betreuer der LimeSurvey-Software kommt hinzu==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Vorlagen-Berechtigungen (hat &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; eh alle)&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (&#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; hat eh alle Berechtigungen f&amp;amp;uuml;r alle Umfragen)&lt;br /&gt;
&lt;br /&gt;
==Neuer Benutzer m&amp;amp;ouml;chte Umfragen selbst erstellen==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Erstelle Umfrage&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen nach Herkunft/Gruppe des Benutzers/Kunden&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (Benutzer hat f&amp;amp;uuml;r die Umfragen die er erstellt eh alle Berechtigungen)&lt;br /&gt;
&lt;br /&gt;
==Ersteller braucht weiteren Benutzer der seine Umfrage bearbeiten darf==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: Nach Wunsch des Besitzers der Umfrage und wie viel Macht der Benutzer haben darf/soll. Wenn gleiche Rechte f&amp;amp;uuml;r Umfrage wie der Besitzer ausgew&amp;amp;auml;hlt werden soll f&amp;amp;uuml;r alle Bereiche alle Berechtigungen ausw&amp;amp;auml;hlen (Klick auf die Checkboxen in der ersten Spalte nach den Bereichsbezeichnungen)&lt;br /&gt;
&lt;br /&gt;
==Verantwortlicher m&amp;amp;ouml;chte die Ergebnisse einer beauftragten Umfrage einsehen und exportieren==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: &#039;&#039;&#039;Antworten&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039; und &#039;&#039;&#039;Export&#039;&#039;&#039; , &#039;&#039;&#039;Statistiken&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyKundeEigeneAuswertung.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Artikel wurde mit Einverst&amp;amp;auml;ndniserkl&amp;amp;auml;rung von &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; aus dem Firmen-Wiki der 24/7 IT-SERVICES GmbH &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Questions_-_introduction&amp;diff=894</id>
		<title>Questions - introduction</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Questions_-_introduction&amp;diff=894"/>
		<updated>2012-01-25T14:51:38Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2176</id>
		<title>Manage users</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Manage_users&amp;diff=2176"/>
		<updated>2012-01-25T14:47:37Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
* Superadmin rights&lt;br /&gt;
* Create Surveys&lt;br /&gt;
* Configurator&lt;br /&gt;
* Create Users&lt;br /&gt;
* Delete Users&lt;br /&gt;
* Manage templates&lt;br /&gt;
* Manage label-sets/labels&lt;br /&gt;
&lt;br /&gt;
==Create users==&lt;br /&gt;
&lt;br /&gt;
To create a new user you please open the user-management (&#039;&#039;&#039;main menu&#039;&#039;&#039; -&amp;gt; &#039;&#039;&#039;Create/Edit users &#039;&#039;&#039; [[File:LimeSurveyBenuzerVerwaltung.jpg]]).&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerHinzufuegen.jpg]]&lt;br /&gt;
* Enter the desired username into the textfield &#039;&#039;&#039;Username&#039;&#039;&#039;.&lt;br /&gt;
* Enter the email adress into the textfield  &#039;&#039;&#039;Email&#039;&#039;&#039;. Please note&lt;br /&gt;
** If you don&#039;t want the user to recieve the confirmation e-mail with a link to the LimeSurvey installation, username and password you can use your own email adress to send the confirmation email to you. After that you can change the email adress to the adress of the user.&lt;br /&gt;
** LimeSurvey sends out a confirmation e-mail to the adress enterd into &#039;&#039;&#039;Email&#039;&#039;&#039;. This email adress will be used as standard contact email adress for surveys created by this user.&lt;br /&gt;
* Enter the users full name into the textfield &#039;&#039;&#039;Full name&#039;&#039;&#039; . Please note&lt;br /&gt;
** The full name entered here will be used as standard contact person name for surveys created by this user.&lt;br /&gt;
* Click &#039;&#039;&#039;Add user&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
So you created a new user. You will find out more about setting user rights if you continue reading further.&lt;br /&gt;
&lt;br /&gt;
==Edit user==&lt;br /&gt;
&lt;br /&gt;
You can use the pen-symbol [[File:LimeSurveyBleistiftSymbol.jpg]] to edit a user.&lt;br /&gt;
&lt;br /&gt;
You can set a new email adress, full name and even change the password. If you have finished what you want to do click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Benutzer l&amp;amp;ouml;schen==&lt;br /&gt;
&lt;br /&gt;
Um einen Benutzer zu l&amp;amp;ouml;schen einfach auf den L&amp;amp;ouml;sch-Button [[File:LimeSurveyBenutzerLoeschen.jpg]] beim Benutzer dr&amp;amp;uuml;cken und die L&amp;amp;ouml;schung mit &#039;&#039;&#039;OK&#039;&#039;&#039; best&amp;amp;auml;tigen.&lt;br /&gt;
&lt;br /&gt;
=Globale Berechtigungen=&lt;br /&gt;
&lt;br /&gt;
Globale Berechtigungen gelten in der gesamten LimeSurvey-Installation. Soll einem Nutzer nur eine Berechtigung f&amp;amp;uuml;r eine spezielle Umfrage erteilt werden kann dies in den Umfragen-Einstellungen festgelegt werden.&lt;br /&gt;
&lt;br /&gt;
==Globale Berechtigungen f&amp;amp;uuml;r einen Nutzer setzen==&lt;br /&gt;
&lt;br /&gt;
Um die globalen Berechtigungen f&amp;amp;uuml;r einen Benutzer zu bearbeiten einfach auf das Schl&amp;amp;uuml;ssel-Symbol [[File:LimeSurveySchluesselSymbol.jpg]] klicken.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySetzeGlobalBer.jpg]]&lt;br /&gt;
&lt;br /&gt;
Es k&amp;amp;ouml;nnen hier nun eine oder mehrere Berechtigungen f&amp;amp;uuml;r den Benutzer gesetzt werden.&lt;br /&gt;
* &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;: Diese Berechtigung kann nur vom Benutzer &#039;&#039;&#039;admin&#039;&#039;&#039; vergeben werden und hatte alle Berechtigungen f&amp;amp;uuml;r diese LimeSurvey-Installation. &#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Mit dieser Berechtigung vorsichtig umgehen da sie sehr m&amp;amp;auml;chtig ist.&lt;br /&gt;
* &#039;&#039;&#039;Erstelle Umfrage&#039;&#039;&#039;: Diese Berechtigung erm&amp;amp;ouml;glicht es dem Benutzer eine Umfrage zu erstellen, starten/stoppen und auszuwerten. Dies ist die Standard-Berechtigung f&amp;amp;uuml;r Personen die eigene Umfragen erstellen sollen.&lt;br /&gt;
* &#039;&#039;&#039;Konfigurator&#039;&#039;&#039;: Dieser Benutzer hat die M&amp;amp;ouml;glichkeit die Datenintegrit&amp;amp;auml;t zu &amp;amp;uuml;berpr&amp;amp;uuml;fen, die SQL-Datenbank in einem .sql-File zu sichern und die php-Info in den globalen Einstellungen aufzurufen.&lt;br /&gt;
* &#039;&#039;&#039;Neuer Benutzer&#039;&#039;&#039;: Mit dieser Berechtigung kann Benutzer selbst neue Benutzer anlegen und die von ihm selbst angelegten Benutzer l&amp;amp;ouml;schen. Die angelegten Benutzer k&amp;amp;ouml;nnen jedoch nicht mehr Rechte haben als der &amp;quot;Vater&amp;quot; selbst, jene m&amp;amp;uuml;ssen ansonsten vom Super-Administrator vergeben werden.&lt;br /&gt;
* &#039;&#039;&#039;Nutze alle/verwalte Vorlagen&#039;&#039;&#039;: Mit dieser Berechtigung kann der Benutzer auf alle Design-Vorlagen zugreifen und jene alle Nicht-Standard-Vorlagen bearbeiten. Diese Berechtigung ist vermutlich nur sinnvoll f&amp;amp;uuml;r Personen die Design-Templates bearbeiten m&amp;amp;uuml;ssen und &amp;amp;uuml;ber ausreichende HTML/php, Javascript und CSS-Kenntnisse verf&amp;amp;uuml;gen. F&amp;amp;uuml;r normale Benutzer empfiehlt es sich die Berechtigung &amp;amp;uuml;ber die Vorlagenberechtigungen nach Bedarf zu setzen.&lt;br /&gt;
* &#039;&#039;&#039;Beschriftungs-Sets verwalten&#039;&#039;&#039;: Mit dieser Berechtigungen k&amp;amp;ouml;nnen alle Beschriftungssets verwaltet (neue erstellt, vorhandene bearbeitet und gel&amp;amp;ouml;scht werden).&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
==Vorlagenberechtigungen f&amp;amp;uuml;r einen Benutzer setzen==&lt;br /&gt;
&lt;br /&gt;
Mit den Vorlagenberechtigungen kann festgelegt werden welche Design-Vorlagen der Nutzer beim Erstellen oder Bearbeiten einer Umfrage ausw&amp;amp;auml;hlen/verwenden kann. Es ist sinnvoll jene Auswahl einzuschr&amp;amp;auml;nken um den Benutzer nicht zu &amp;amp;uuml;berfordern und zu verhindern dass ungewollt Design-Vorlagen verwendet werden die nicht verwendet werden sollen.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Wenn es f&amp;amp;uuml;r bestimmte Benutzer-Gruppen oder Kunden eigene Design-Vorlagen gibt sollten wenn m&amp;amp;ouml;glich auch nur jene auf verf&amp;amp;uuml;gbar gestellt werden.&lt;br /&gt;
&lt;br /&gt;
Zum Setzen der Vorlagenberechtigungen einfach auf das Schl&amp;amp;uuml;ssel-Symbol f&amp;amp;uuml;r die Design-Vorlagen&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveySchluesselSymbolTemplates.jpg]] klicken.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyAuswahlDesignTemplatesLS.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nun k&amp;amp;ouml;nnen die gew&amp;amp;uuml;nschten Design-Vorlagen die der Benutzer verwenden k&amp;amp;ouml;nnen soll ausgew&amp;amp;auml;hlt werden. Am Ende werden die Einstellungen mit einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; best&amp;amp;auml;tigt.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Berechtigungen nur f&amp;amp;uuml;r eine einzelne Umfrage=&lt;br /&gt;
&lt;br /&gt;
Diese Berechtigungen gelten nur f&amp;amp;uuml;r eine einzelne Umfrage. Sollen einem Benutzer Berechtigungen f&amp;amp;uuml;r das ganze System &amp;amp;uuml;bergeben werden m&amp;amp;uuml;ssen die globalen Berechtigungen verwendet werden.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Wichtig:&#039;&#039;&#039; Auch f&amp;amp;uuml;r Berechtigungen f&amp;amp;uuml;r einzelne Umfragen muss ein Benutzer-Account vorhanden sein bzw. angelegt werden wenn er es noch nicht sein sollte. Der Benutzer muss jedoch keine globale Berechtigung besitzen, es reicht wenn er nur existiert.&lt;br /&gt;
&lt;br /&gt;
==Benutzer-Berechtigungen f&amp;amp;uuml;r eine Umfrage &amp;amp;auml;ndern==&lt;br /&gt;
&lt;br /&gt;
Um die Berechtigungen f&amp;amp;uuml;r eine einzelne Umfrage zu setzen w&amp;amp;auml;hlt man im Men&amp;amp;uuml; &#039;&#039;&#039;Umfragen-Einstellungen&#039;&#039;&#039; den Men&amp;amp;uuml;punkt &#039;&#039;&#039;Umfrageberechtigungen&#039;&#039;&#039; aus.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyUmfragenBerechtigungen.jpg]]&lt;br /&gt;
&lt;br /&gt;
Im n&amp;amp;auml;chsten Schritt wird der Benutzer ausgew&amp;amp;auml;hlt dem die Berechtigung gesetzt werden soll und auf &#039;&#039;&#039;Benutzer hinzuf&amp;amp;uuml;gen&#039;&#039;&#039; geklickt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenBerHinz.jpg]]&lt;br /&gt;
&lt;br /&gt;
Nach einem Klick auf &#039;&#039;&#039;Bearbeite Umfrageberechtigungen&#039;&#039;&#039; wird die Benutzerberechtigungsmatrix f&amp;amp;uuml;r die Umfrage angezeigt.&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyBenutzerBerechtigungMatrix.jpg]]&lt;br /&gt;
&lt;br /&gt;
In dieser Matrix k&amp;amp;ouml;nnen die Berechtigungen f&amp;amp;uuml;r die einzelnen Bereiche festgelegt werden. Durch einen Klick in die Checkbox in der ersten Spalte nach den Bereichsbezeichnungen k&amp;amp;ouml;nnen alle Berechtigungen f&amp;amp;uuml;r einen Bereich ausgew&amp;amp;auml;hlt werden. In den weiteren Spalten k&amp;amp;ouml;nnen wenn ben&amp;amp;ouml;tigt die einzelnen Berechtigungen hinzugef&amp;amp;uuml;gt oder entfernt werden falls nicht alle Berechtigungen ausgew&amp;amp;auml;hlt/m&amp;amp;ouml;glich sein sollen. Nach einem Klick auf &#039;&#039;&#039;Speichern&#039;&#039;&#039; werden die &amp;amp;Auml;nderungen &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
Unter dem Punkt &#039;&#039;&#039;Anwendungsf&amp;amp;auml;lle&#039;&#039;&#039; werden die h&amp;amp;auml;ufigsten Standardf&amp;amp;auml;lle f&amp;amp;uuml;r neue Nutzer aufgelistet.&lt;br /&gt;
&lt;br /&gt;
=Anwendungsf&amp;amp;auml;lle=&lt;br /&gt;
&lt;br /&gt;
Hier wird f&amp;amp;uuml;r die h&amp;amp;auml;ufigsten Anwendungsf&amp;amp;auml;lle und Vorkommnisse festgehalten welche Berechtigungen in diesem Fall gesetzt werden sollten.&lt;br /&gt;
&lt;br /&gt;
==Neuer Betreuer der LimeSurvey-Software kommt hinzu==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Vorlagen-Berechtigungen (hat &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; eh alle)&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (&#039;&#039;&#039;Super-Administrator&#039;&#039;&#039; hat eh alle Berechtigungen f&amp;amp;uuml;r alle Umfragen)&lt;br /&gt;
&lt;br /&gt;
==Neuer Benutzer m&amp;amp;ouml;chte Umfragen selbst erstellen==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung &#039;&#039;&#039;Erstelle Umfrage&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen nach Herkunft/Gruppe des Benutzers/Kunden&lt;br /&gt;
* nicht n&amp;amp;ouml;tig: Setzen der Umfrage-Berechtigungen (Benutzer hat f&amp;amp;uuml;r die Umfragen die er erstellt eh alle Berechtigungen)&lt;br /&gt;
&lt;br /&gt;
==Ersteller braucht weiteren Benutzer der seine Umfrage bearbeiten darf==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: Nach Wunsch des Besitzers der Umfrage und wie viel Macht der Benutzer haben darf/soll. Wenn gleiche Rechte f&amp;amp;uuml;r Umfrage wie der Besitzer ausgew&amp;amp;auml;hlt werden soll f&amp;amp;uuml;r alle Bereiche alle Berechtigungen ausw&amp;amp;auml;hlen (Klick auf die Checkboxen in der ersten Spalte nach den Bereichsbezeichnungen)&lt;br /&gt;
&lt;br /&gt;
==Verantwortlicher m&amp;amp;ouml;chte die Ergebnisse einer beauftragten Umfrage einsehen und exportieren==&lt;br /&gt;
* Login &amp;amp;uuml;ber den &#039;&#039;&#039;admin&#039;&#039;&#039;-Account oder mit einem Account der &#039;&#039;&#039;Super-Administrator&#039;&#039;&#039;-Rechte hat&lt;br /&gt;
* Erstellen eines Benutzeraccounts f&amp;amp;uuml;r den Benutzer&lt;br /&gt;
* Setzen der globalen Berechtigung: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Vorlagen-Berechtigungen: &#039;&#039;&#039;keine&#039;&#039;&#039;&lt;br /&gt;
* Setzen der Umfrage-Berechtigungen: &#039;&#039;&#039;Antworten&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039; und &#039;&#039;&#039;Export&#039;&#039;&#039; , &#039;&#039;&#039;Statistiken&#039;&#039;&#039;: Darf &#039;&#039;&#039;Anzeigen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyKundeEigeneAuswertung.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Artikel wurde mit Einverst&amp;amp;auml;ndniserkl&amp;amp;auml;rung von &#039;&#039;&#039;vierundzwanzig&#039;&#039;&#039; aus dem Firmen-Wiki der 24/7 IT-SERVICES GmbH &amp;amp;uuml;bernommen.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
To be moved somewhere else once better defined:&lt;br /&gt;
&lt;br /&gt;
There are several classes of possible people who access a LimeSurvey installation.  But only one set of people is actually termed a &#039;&#039;&#039;user&#039;&#039;&#039; in the code and documentation.  So lets understand what these classes of people are so we can better understand the terminology of the program.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Class||Description&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Use one time passwords=&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
To enable this login method [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Use_one_time_passwords a setting has to be turned on] ($use_one_time_passwords = true;) in config.php.&lt;br /&gt;
&lt;br /&gt;
The URL has to contain the following variables:&lt;br /&gt;
* &#039;&#039;&#039;user:&#039;&#039;&#039; The username normally used to login into Limesurvey. This username has to exist in the &#039;users&#039; table of the database.&lt;br /&gt;
* &#039;&#039;&#039;onepass:&#039;&#039;&#039; The plain text password which is then compared to the password in the &#039;users&#039; table&lt;br /&gt;
&lt;br /&gt;
A valid URL to login using a one time password will look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;http://www.yourdomain.org/limesurvey/admin/admin.php?user=myusername&amp;amp;onepass;=secretpassword&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Things to watch out for:&#039;&#039;&#039;&lt;br /&gt;
* One time passwords have to be enabled by setting $use_one_time_passwords = true; in config.php&lt;br /&gt;
* The passed username has to exist in Limesurvey&#039;s &#039;&#039;users&#039;&#039; table&lt;br /&gt;
* The one time password, which can be set by an external application, has to be stored as [http://de.php.net/md5 MD5 hash] in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;&lt;br /&gt;
* The passed plain text password will be hashed using md5() function and will then be compared to the stored hash in column &#039;&#039;one_time_pw&#039;&#039; of table &#039;&#039;users&#039;&#039;. Both passwords have to match.&lt;br /&gt;
* After the first login with the one time password this password is deleted from the database. The user won&#039;t be able to login with this password anymore. If you are confronted with session timeout problems [http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Survey_Behavior raise the setting for $sessionlifetime] (default is 3600 seconds).&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Recurring_forum_posts&amp;diff=2876</id>
		<title>Recurring forum posts</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Recurring_forum_posts&amp;diff=2876"/>
		<updated>2012-01-18T12:02:16Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
This is a collection of recurring forum posts which can be used to copy/paste common answers. Please update if anything is missing.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=More Information=&lt;br /&gt;
&lt;br /&gt;
==Version/Build==&lt;br /&gt;
&lt;br /&gt;
Which &#039;&#039;&#039;version and build&#039;&#039;&#039; of Limesurvey do you use?&lt;br /&gt;
&lt;br /&gt;
............................&lt;br /&gt;
&lt;br /&gt;
Welche Version und welchen Build nutzt du?&lt;br /&gt;
&lt;br /&gt;
==More Details==&lt;br /&gt;
&lt;br /&gt;
Your description as rather vague. Can you please &#039;&#039;&#039;describe your problem in more detail&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
1. What do you do exactly?&lt;br /&gt;
&lt;br /&gt;
2. What do you expect to happen?&lt;br /&gt;
&lt;br /&gt;
3. What happens instead?&lt;br /&gt;
&lt;br /&gt;
4. Any configuration parameters we should know about?&lt;br /&gt;
&lt;br /&gt;
==Path problems==&lt;br /&gt;
&lt;br /&gt;
1. Please post the URL you use to call the admin login.&lt;br /&gt;
&lt;br /&gt;
2. What did you set for $rooturl in config.php?&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
1. Unter welcher URL rufst du den Admin-Login auf?&lt;br /&gt;
&lt;br /&gt;
2. Was hast du in config.php f&amp;amp;uuml;r $rooturl eingesetzt?&lt;br /&gt;
&lt;br /&gt;
==Any Progress?==&lt;br /&gt;
&lt;br /&gt;
Any &#039;&#039;&#039;progress&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
Have you been able to solve your problem? If so, how did you solve it? Any kind of feedback is always appreciated so we know which solution helps best to solve common problems.&lt;br /&gt;
&lt;br /&gt;
..........................&lt;br /&gt;
&lt;br /&gt;
Konntest du das &#039;&#039;&#039;Problem inzwischen l&amp;amp;ouml;sen&#039;&#039;&#039;?&lt;br /&gt;
&lt;br /&gt;
Falls ja, wie hast du es umgesetzt? Jede Art von Feedback ist immer willkommen, da wir nur so herausfinden, welche L&amp;amp;ouml;sungsvorschl&amp;amp;auml;ge sich f&amp;amp;uuml;r bestimmte Problemstellungen eignen.&lt;br /&gt;
&lt;br /&gt;
==Config.php Settings==&lt;br /&gt;
&lt;br /&gt;
Please post the &#039;&#039;&#039;settings you set in config.php&#039;&#039;&#039; (no real passwords please).&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
Poste bitte mal deine Einstellungen, die du in config.php vorgenommen hast. Bitte keine Passw&amp;amp;ouml;rter offen posten.&lt;br /&gt;
&lt;br /&gt;
==Phpinfo File==&lt;br /&gt;
&lt;br /&gt;
Please upload a &#039;&#039;&#039;phpinfo file&#039;&#039;&#039; so we can take a look at your server configuration. Just put the following code into a file named &#039;&#039;phpinfo.php&#039;&#039; and upload it to your webserver:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[code]&lt;br /&gt;
&lt;br /&gt;
&amp;lt; ?php&lt;br /&gt;
&lt;br /&gt;
phpinfo();&lt;br /&gt;
&lt;br /&gt;
? &amp;gt;&lt;br /&gt;
&lt;br /&gt;
[/code](Delete the spaces next to &amp;lt;/&amp;gt; when copying the code.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After uploading please post the link to the file.&lt;br /&gt;
&lt;br /&gt;
......................................&lt;br /&gt;
&lt;br /&gt;
Bitte erstelle eine &#039;&#039;&#039;phpinfo Datei&#039;&#039;&#039;, damit wir mal einen Blick auf deine Serverkonfiguration werfen k&amp;amp;ouml;nnen. Einfach folgende Zeile in eine neue Textdatei kopieren und diese unter dem Namen &#039;&#039;phpinfo.php&#039;&#039; speichern:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[code]&lt;br /&gt;
&lt;br /&gt;
&amp;lt; ?php&lt;br /&gt;
&lt;br /&gt;
phpinfo();&lt;br /&gt;
&lt;br /&gt;
? &amp;gt;&lt;br /&gt;
&lt;br /&gt;
[/code](Die Leerzeichen bei &amp;lt;/&amp;gt; l&amp;amp;ouml;schen, wenn du den Code kopierst.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Dann die Datei auf deinen Server laden und hier den Link posten, Beispiel: &amp;lt;nowiki&amp;gt;www.meinehomepage.de/phpinfo.php&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Bugs/Features=&lt;br /&gt;
&lt;br /&gt;
==Debug Mode==&lt;br /&gt;
&lt;br /&gt;
Please switch on &#039;&#039;&#039;debug mode&#039;&#039;&#039; by adding the following line to your config.php file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]$debug = &#039;1&#039;;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Are there any additional errors reported on top of the page?&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
Schalte bitte mal den &#039;&#039;&#039;Debugging-Modus&#039;&#039;&#039; ein, indem du folgenden Eintrag in deine config.php Datei kopierst:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]$debug = &#039;1&#039;;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Werden irgendwelche zus&amp;amp;auml;tzlichen Fehlermeldungen oben auf der Seite angezeigt?&lt;br /&gt;
&lt;br /&gt;
==Online-Demo==&lt;br /&gt;
&lt;br /&gt;
You can test if this is fixed at the latest version by testing our online demo at http://demo.limesurvey.org/admin which always runs the latest Limesurvey version.&lt;br /&gt;
&lt;br /&gt;
Username: admin&lt;br /&gt;
&lt;br /&gt;
Password: test&lt;br /&gt;
&lt;br /&gt;
If you can reproduce the problem there please...&lt;br /&gt;
&lt;br /&gt;
..............................&lt;br /&gt;
&lt;br /&gt;
Du kannst mal auf unserer Onlinedemo, die immer die neueste Limesurveyversion nutzt, testen, ob das Problem dort reproduzierbar ist: http://demo.limesurvey.org/admin&lt;br /&gt;
&lt;br /&gt;
Username: admin&lt;br /&gt;
&lt;br /&gt;
Password: test&lt;br /&gt;
&lt;br /&gt;
Wenn das Problem dort auch auftaucht, ...&lt;br /&gt;
&lt;br /&gt;
==Update==&lt;br /&gt;
&lt;br /&gt;
Please &#039;&#039;&#039;upgrade&#039;&#039;&#039; to the latest release which contains recent bug fixes and new features.&lt;br /&gt;
&lt;br /&gt;
More information:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]Download latest release[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version]Upgrade instructions[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
..........................&lt;br /&gt;
&lt;br /&gt;
Bitte f&amp;amp;uuml;hre ein &#039;&#039;&#039;Update&#039;&#039;&#039; auf die neueste Version durch, das alle aktuellen Bugfixes enth&amp;amp;auml;lt.&lt;br /&gt;
&lt;br /&gt;
Weitere Infos:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]Download der neuesten Version[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version]Update Anleitung[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Report Bug==&lt;br /&gt;
&lt;br /&gt;
Please test if the problem still exists at  &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]the latest release[/url].&amp;lt;/nowiki&amp;gt; If so please &amp;lt;nowiki&amp;gt;[url=http://bugs.limesurvey.org/]open a ticket at the bugtracker [/url]&amp;lt;/nowiki&amp;gt; and...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[ol]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Give as much information as possible[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Attach your survey. You can mark your ticket &amp;quot;private&amp;quot; so that only the developers will be able to take a look at it.[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]Provide step-by-step instructions how to reproduce the problem.[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[li]If possible/helpful please provide screenshots[/li]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[/ol]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Afterwards please post the link to the bugtracker so we can follow the progress.&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
...............&lt;br /&gt;
&lt;br /&gt;
Pr&amp;amp;uuml;fe bitte, ob das Problem auch in &amp;lt;nowiki&amp;gt;[url=http://sourceforge.net/project/showfiles.php?group_id=74605]der neuesten Version[/url]&amp;lt;/nowiki&amp;gt; reproduzierbar ist. Falls ja &amp;amp;ouml;ffne bitte ein &amp;lt;nowiki&amp;gt;[url=http://bugs.limesurvey.org/]Ticket im Bugtracker [/url]&amp;lt;/nowiki&amp;gt; und...&lt;br /&gt;
&lt;br /&gt;
1. Beschreibe das Problem so detailliert wie m&amp;amp;ouml;glich (bitte in Englisch).&lt;br /&gt;
&lt;br /&gt;
2. Lade deinen Fragebogen (als exportierte .csv-Datei) hoch. Du kannst deinen Eintrag &amp;quot;privat&amp;quot; machen, so dass nur Entwickler die Datei einsehen k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
3. Schreibe eine kurze Schritt-f&amp;amp;uuml;r-Schritt Anleitung, wie man das Problem reproduzieren kann.&lt;br /&gt;
&lt;br /&gt;
4. Falls m&amp;amp;ouml;glich/sinnvoll h&amp;amp;auml;nge Screenshots an.&lt;br /&gt;
&lt;br /&gt;
Wenn du den &#039;&#039;&#039;Bug berichtet&#039;&#039;&#039; hast, bitte hier den Link eintragen, damit wir den Fortschritt verfolgen k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
Danke!&lt;br /&gt;
&lt;br /&gt;
==Add Feature Request==&lt;br /&gt;
&lt;br /&gt;
You can &amp;lt;nowiki&amp;gt;[url=http://ideas.limesurvey.org/ideatorrent/all_limeSurvey_1/]add this as a feature request at our feature tracker[/url]&amp;lt;/nowiki&amp;gt;. Please describe your idea as detailed as possible and try to outline a suitable solution/implementation as well.&lt;br /&gt;
&lt;br /&gt;
..............................&lt;br /&gt;
&lt;br /&gt;
Du kannst &amp;lt;nowiki&amp;gt;[url=http://ideas.limesurvey.org/ideatorrent/all_limeSurvey_1/]dies als Feature-Request in unserem Feature-Tracker hinzuf&amp;amp;uuml;gen[/url]&amp;lt;/nowiki&amp;gt;. Bitte beschreibe (in Englisch) das Problem so ausf&amp;amp;uuml;hrlich wie m&amp;amp;ouml;glich und versuche Vorschl&amp;amp;auml;ge zur L&amp;amp;ouml;sung des Problems bzw. der Implementierung zu machen. Danke!&lt;br /&gt;
&lt;br /&gt;
=Thanks=&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;You&#039;re welcome :-)&lt;br /&gt;
&lt;br /&gt;
If our hints have been helpful and you enjoy limesurvey [url=http://donate.limesurvey.org/] please consider a donation to the team[/url] .&lt;br /&gt;
&lt;br /&gt;
We do all this in our free time and you don&#039;t have to pay a penny for this software.&lt;br /&gt;
&lt;br /&gt;
Without your help we can&#039;t keep this project alive.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...........................&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Gern geschehen !&lt;br /&gt;
&lt;br /&gt;
Wenn wir helfen konnten und du Limesurvey magst, schau doch mal, ob du uns [url=http://donate.limesurvey.org/] eine kleine Spende zukommen lassen kannst[/url].&lt;br /&gt;
&lt;br /&gt;
Wir machen das hier alles in unserer Freizeit und das Programm ist absolut kostenlos.&lt;br /&gt;
&lt;br /&gt;
Ohne eure Hilfe kann das Projekt nicht fortgef&amp;amp;uuml;hrt werden.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
................................&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;Merci de votre retour !&lt;br /&gt;
&lt;br /&gt;
Si ces informations vous ont aid&amp;amp;eacute; et que vous aimez LimeSurvey&lt;br /&gt;
&lt;br /&gt;
[url=http://donate.limesurvey.org/] veuillez consid&amp;amp;eacute;rer l&#039;opportunit&amp;amp;eacute; d&#039;une donation au projet[/url] .&lt;br /&gt;
&lt;br /&gt;
Le projet LimeSurvey est effectu&amp;amp;eacute; sur notre temps libre et nous ne recevons aucune r&amp;amp;eacute;mun&amp;amp;eacute;ration.&lt;br /&gt;
&lt;br /&gt;
Sans votre aide , le projet ne peut survivre.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Tipps and Tricks=&lt;br /&gt;
&lt;br /&gt;
==SGQA Codes==&lt;br /&gt;
&lt;br /&gt;
You can set Limesurvey to show all codes at the printable survey screen, see this setting:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;$showsgqacode: (&amp;gt;1.91) This setting is used at the printable survey feature Image and defaults to false. If you set $showsgqacode = true; the IDs for each question - and answer if applicable - will be shown; these IDs match the column heading at the Lime_survey_12345 table which holds the answer data for a certain survey. These Ids can be used for a code book for manual database queries.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/Optional+settings&amp;amp;structure;=English+Instructions+for+LimeSurvey#Statistics_and_Response_Browsing]Link to optional settings[/url]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Javascript to hide questions==&lt;br /&gt;
&lt;br /&gt;
To hide a question using Javascript you first have to disable the internal XSS filter at the admin section (global settings -&amp;gt; security -&amp;gt; &amp;quot;Filter HTML for XSS = &#039;no&#039;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Then you have to edit the according question. Edit the question text &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/First+login+-+Your+user+preferences#X._Source_code_mode:]in source code mode[/url]&amp;lt;/nowiki&amp;gt; and add this snippet at the end of the text:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  $(document).ready(function()&lt;br /&gt;
&lt;br /&gt;
  {&lt;br /&gt;
&lt;br /&gt;
     $(&#039;#question4444&#039;).hide();&lt;br /&gt;
&lt;br /&gt;
  });&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/script&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[/code]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You have to replace the question ID (&amp;quot;4444&amp;quot;) with the &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey#General_Description]ID of the current question[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Configuration=&lt;br /&gt;
&lt;br /&gt;
==XSS Filter==&lt;br /&gt;
&lt;br /&gt;
There is a &#039;&#039;&#039;filter for security reasons&#039;&#039;&#039; which filters javascript input to prevent XSS attacs: &amp;lt;nowiki&amp;gt;[i]&amp;quot;This setting enables filtering of suspicious html tags in survey, group, questions and answer texts in the administration interface. Only leave this to &#039;false&#039; if you absolutely trust the users you created for the administration of LimeSurvey and if you want to allow these users to be able to use Javascript, Flash Movies, etc.&amp;quot;[/i]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check config-defaults.php for a &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Optional+settings#Security]setting like &amp;quot;filterxsshtml&amp;quot;[/url]&amp;lt;/nowiki&amp;gt;, copy this setting to config.php and disable the filter.&lt;br /&gt;
&lt;br /&gt;
==Public statistics==&lt;br /&gt;
&lt;br /&gt;
The new feature to &#039;&#039;&#039;show statistics to the user&#039;&#039;&#039; at the end of a survey was introduced in version 1.80RC3. Using this feature the user is presented a link at the end of the survey which takes him to the public statistics.&lt;br /&gt;
&lt;br /&gt;
There are two important settings. At first you have to &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey#Presentation_amp_Navigation]enable public statistics for your current survey[/url]&amp;lt;/nowiki&amp;gt; at survey settings -&amp;gt; presentation &amp;amp; navigation -&amp;gt; Public statistics.&lt;br /&gt;
&lt;br /&gt;
Because often you only want to show statistics for certain questions there is an &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#public_statistics]additional question attribute &amp;quot;public_statistics&amp;quot;[/url]&amp;lt;/nowiki&amp;gt;. This question attribute has to be applied to all questions which should be shown to the user. Note that the use of this question attribute is limited to certain question types (see list at manual -&amp;gt; question attributes -&amp;gt; public_statistics).&lt;br /&gt;
&lt;br /&gt;
Furthermore it is possible to &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Creating+a+new+survey#Presentation_amp_Navigation]set if the public statistics should contain graphs[/url]&amp;lt;/nowiki&amp;gt;. This can also be set individually for each survey at survey settings -&amp;gt; presentation &amp;amp; navigation -&amp;gt; public graphs&lt;br /&gt;
&lt;br /&gt;
=Wiki=&lt;br /&gt;
&lt;br /&gt;
==Add Missing Information==&lt;br /&gt;
&lt;br /&gt;
If you are &#039;&#039;&#039;missing some information in the manual&#039;&#039;&#039; feel free to improve it. &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=English+Instructions+for+LimeSurvey]Our manual[/url]&amp;lt;/nowiki&amp;gt; is a wiki, everyone can edit it and you can&#039;t do much wrong.&lt;br /&gt;
&lt;br /&gt;
So if you miss anything in the manual and you found out how to do it please add this information. Thanks!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org]Unser Handbuch[/url]&amp;lt;/nowiki&amp;gt; ist ein Wiki, jeder kann es &amp;amp;auml;ndern/verbessern. Wir sind hier auf die Hilfe unserer Nutzer angewiesen, also sei doch bitte so nett und f&amp;amp;uuml;ge eine kurze Notiz zu dieser Problematik hinzu, um anderen Nutzern zu helfen.&lt;br /&gt;
&lt;br /&gt;
Danke!&lt;br /&gt;
&lt;br /&gt;
==Add Instructions to Manual==&lt;br /&gt;
&lt;br /&gt;
Thanks a lot for this &#039;&#039;&#039;helpful instructions&#039;&#039;&#039;. Can you &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org]add this to our wiki[/url]&amp;lt;/nowiki&amp;gt;  so that other users can benefit from your solution, too? Would be great!&lt;br /&gt;
&lt;br /&gt;
==Add workaround==&lt;br /&gt;
&lt;br /&gt;
Can you please &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Workarounds] add your solution to the workaround section of our manual[/url]&amp;lt;/nowiki&amp;gt; so other users can beneffit from your solution, too!?&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
=IRC=&lt;br /&gt;
&lt;br /&gt;
==Development==&lt;br /&gt;
&lt;br /&gt;
If you have questions about the limesurvey code or how to implement new features it&#039;s always best to &amp;lt;nowiki&amp;gt;[url=http://www.limesurvey.org/index.php/Live-Chat]join the limesurvey IRC[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Our developers don&#039;t hang around in the forum much so please &#039;&#039;&#039;contact them at our IRC&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Be patient, often our developers only answer after a few minutes or the developer who can help you isn&#039;t around. In this case please try again later.&lt;br /&gt;
&lt;br /&gt;
==Donate==&lt;br /&gt;
&lt;br /&gt;
You&#039;re welcome! If our hints have been helpful and you enjoy limesurvey please consider a donation to the team (see &amp;lt;nowiki&amp;gt; http://donate.limesurvey.org&amp;lt;/nowiki&amp;gt;) . We do all this in our free time and you don&#039;t have to pay a penny for this software.&lt;br /&gt;
&lt;br /&gt;
Without your help we can&#039;t keep this project alive.&lt;br /&gt;
&lt;br /&gt;
==Update==&lt;br /&gt;
&lt;br /&gt;
Please upgrade to the latest release. A lot of errors have been fixed in the latest release.&lt;br /&gt;
&lt;br /&gt;
More information:&lt;br /&gt;
&lt;br /&gt;
- Download latest release: http://sourceforge.net/project/showfiles.php?group_id=74605&lt;br /&gt;
&lt;br /&gt;
- Upgrade instructions: http://docs.limesurvey.org/tiki-index.php?page=Upgrading+from+a+previous+version&lt;br /&gt;
&lt;br /&gt;
==User pacthes==&lt;br /&gt;
&lt;br /&gt;
Please open a ticket at our bugtracker at the &amp;quot;user patches&amp;quot; section and attach your code files there. The forum is cleaned up regularly so this might get lost if you post it here.&lt;br /&gt;
&lt;br /&gt;
When you are done, please post the link to the bugtracker ticket here.&lt;br /&gt;
&lt;br /&gt;
Thanks!&lt;br /&gt;
&lt;br /&gt;
=PM=&lt;br /&gt;
&lt;br /&gt;
Sorry, we don&#039;t give personal support via PM. Please always post your questions in the forum so that other users can participate from the solution.&lt;br /&gt;
&lt;br /&gt;
Best regards,&lt;br /&gt;
&lt;br /&gt;
Mazi (Forum Support)&lt;br /&gt;
&lt;br /&gt;
.....................&lt;br /&gt;
&lt;br /&gt;
Sorry, aber wir geben keinen pers&amp;amp;ouml;nlichen Support per PM. Bitte stelle deine Frage immer im Forum, damit andere Nutzer auch von der L&amp;amp;ouml;sung profitieren k&amp;amp;ouml;nnen.&lt;br /&gt;
&lt;br /&gt;
Beste Gr&amp;amp;uuml;&amp;amp;szlig;e,&lt;br /&gt;
&lt;br /&gt;
Mazi (Forum Support)&lt;br /&gt;
&lt;br /&gt;
=Login Problems=&lt;br /&gt;
&lt;br /&gt;
==Synchronize Passwords==&lt;br /&gt;
&lt;br /&gt;
We synchronized forum, wiki/manual and bugtracker usernames and passwords. Please set a new password by clicking your username in the forum and chosing edit -&amp;gt; update your profile -&amp;gt; contact info. This way everything will get synchronized and you should be able to log in.&lt;br /&gt;
&lt;br /&gt;
.......................&lt;br /&gt;
&lt;br /&gt;
Wir haben Forum, Handbuch/Wiki und den Bugtracker synchronisiert, so dass man nur noch einen Login ben&amp;amp;ouml;tigt. Damit dies korrekt funktioniert, musst du evtl. auf www.limesurvey.org ein neues Passwort setzen. Einfach im Forum auf deinen Benutzernamen klicken und dann bei edit -&amp;gt; update your profile -&amp;gt; contact info ein neues Passwort festlegen. So sollten alle Komponenten synchronisiert werden.&lt;br /&gt;
&lt;br /&gt;
=Misc=&lt;br /&gt;
&lt;br /&gt;
==Search Forum==&lt;br /&gt;
&lt;br /&gt;
I can&#039;t solve your problem but I think this has been discussed before. Perhaps &#039;&#039;&#039;searching the forum&#039;&#039;&#039; might return helpful results.&lt;br /&gt;
&lt;br /&gt;
==Advanced support==&lt;br /&gt;
&lt;br /&gt;
Sorry, I help users a lot but your request is beyond the common free support. Please &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=UserPage%20Mazi]check out advanced support options[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;X&amp;quot; within certain words==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Limesurvey adds an &amp;quot;X&amp;quot;&#039;&#039;&#039; to certain words for security reasons. These are words like &amp;quot;link, url, ...&amp;quot; which can be used to hack the system. Normally this &amp;quot;X&amp;quot; won&#039;t show up at the final but is only shown at the admin panel.&lt;br /&gt;
&lt;br /&gt;
==Styling questions==&lt;br /&gt;
&lt;br /&gt;
Take a look at the &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=Templates+%2F+The+template+editor#Styling_questions_in_LimeSurvey_1_8]instructions about styling questions[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Edit Translation==&lt;br /&gt;
&lt;br /&gt;
This text string can be changed by &amp;lt;nowiki&amp;gt;[url=http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+1.x+Translating+LimeSurvey]editing the translation[/url]&amp;lt;/nowiki&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Cross postings==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=]No cross posting please! [/url]&amp;lt;/nowiki&amp;gt; It&#039;s always best to ask your question at the english forum because there are more user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;-&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;[url=]Bitte keine doppelten Postings! [/url]&amp;lt;/nowiki&amp;gt; Am besten stellst du deine Frage immer im englischen Unterforum, dort sind mehr Leute unterwegs.&lt;br /&gt;
&lt;br /&gt;
==German threads in german forum==&lt;br /&gt;
&lt;br /&gt;
In den englischen Foren bitte nur englisch schreiben, das sorgt sonst immer mal wieder f&amp;amp;uuml;r Verwirrung. Wenn du einen deutschen Beitrag verfasst bitte das &amp;lt;nowiki&amp;gt;[url=www.limesurvey.org/de/forum/deutsches-forum]deutsche Forum[/url]&amp;lt;/nowiki&amp;gt; benutzen.&lt;br /&gt;
&lt;br /&gt;
Danke.&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3376</id>
		<title>Theme editor</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3376"/>
		<updated>2012-01-11T08:54:56Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{maketoc title=&amp;quot;Contents:&amp;quot;}&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has a basic template and style system providing a theme-like capability found in many browser-based applications.  They are simply termed &#039;&#039;&#039;Templates&#039;&#039;&#039; here.  The Templates allow control over the look and feel of pages during a survey.  A survey administrator can select the template to use for each survey to thus personalize that survey&#039;s look and feel.  Changes to a Template can be as simple as adding a unique logo on the welcome page, changing background colors, or maybe new text colors for specific types of questions.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey comes with a set of templates right out of the box. These initial templates are defined by directories within the LimeSurvey installation &amp;quot;templates&amp;quot; directory.  Each template has it&#039;s own directory.  Within the main directory of a template are numerous files: &#039;&#039;&#039;templates (.pstpl)&#039;&#039;&#039;, &#039;&#039;&#039;cascading style sheets (.css)&#039;&#039;&#039;, &#039;&#039;&#039;images&#039;&#039;&#039; (&#039;&#039;&#039;.jpg&#039;&#039;&#039; or &#039;&#039;&#039;.png&#039;&#039;&#039;) and maybe others.&lt;br /&gt;
&lt;br /&gt;
Like in other theme-based systems, fragments of HTML code are stored in the .pstpl template files.  These fragments are read in and used to construct the page to display to the end user during the operation of a survey. Often &#039;&#039;&#039;keywords&#039;&#039;&#039; surrounded by curly braces are included in the files that are then replaced with the relevant text.  The following gives an example of a template file content and its result when used in a survey page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&amp;lt;font face=&#039;verdana&#039; color=&#039;red&#039;&amp;gt;{SURVEYNAME}&amp;lt;/font&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font face=&#039;verdana&#039; color=&#039;blue&#039;&amp;gt;&amp;lt;u&amp;gt;{SURVEYDESCRIPTION}&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One gets a result that looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&#039;color:red&#039;&amp;gt;My New Survey&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;u&amp;gt;&amp;lt;span style=&#039;color:#0000ff&#039;&amp;gt;This is a survey written by me to find out what sort of chocolate people like.&amp;lt;/span&amp;gt;&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Templates, being HTML code, tend to define the positioning and type of text to be displayed and similar structural features of the page.  They often reference or include other files.  Most reference a common cascading style sheets (CSS) file that defines the font style, color, size, background and similar parameters common to all pages in the survey. Style sheets reference HTML &#039;&#039;&#039;class&#039;&#039;&#039; parameters that are associated with the various types of objects in the HTML code.  This allows the style sheet to describe once how to display each of the many types of text or other objects that may appear in multiple places.  There are unique classes for each question type in LimeSurvey and thus giving detailed control over the appearance of each.  Image files, like logos or special progress-bar constructors, may be referenced as well in the Template file.  Finally, special Keywords in curly braces are replaced with text defined in the Survey for each of its corresponding language translations (for example, the Survey Title or Question Text for each language defined).&lt;br /&gt;
&lt;br /&gt;
If you create a new custom template, please consider contributing it back to the LimeSurvey community, and make it available to others. With your help, we can grow our repository of templates, surveys, and other ad-ons, to make LimeSurvey even better! See the shared [http://www.limesurvey.org/component/remository/lang,en-gb/ Template Repository]&lt;br /&gt;
&lt;br /&gt;
=Creating a new Template=&lt;br /&gt;
&lt;br /&gt;
To be able to create a new template (or edit an existing template), you need Template Editing user permission in LimeSurvey as well as permission to manipulate the files in the underlying operating system hosting your LimeSurvey installation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note of Warning:&#039;&#039;&#039; As template changes can affect all surveys in an installation, changes should be limited to those skilled in understanding general concepts in the code base. Templates are an advanced feature that can take some experimentation to get correct if you are not familiar with HTML code methods.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The preferred way to create a new template is through the Template Editor (see below) via the web Admin interface. Some people may like to work directly with template files so that they can use their favorite text editor instead of the web interface. In this case, still use the Template Editor to first create your new template. This will create a new base template with all the files you need in the LimeSurvey_web_root/upload/templates/your_new_template directory. From there you can use your text editor to manually adjust the template files.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Permissions Note:&#039;&#039;&#039; on unix/linux systems, these template files will be owned by the group and user who the web server is running as (may be &amp;quot;www&amp;quot; for some systems). So make sure you have access to edit these files, and when you save them make sure they don&#039;t change ownership, so you can still use the web Template Editing interface if needed&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Template files may seem complex to understand at first. You have to likely understand HTML code, possibly Styles and Style Sheets, and have access to the underlying LimeSurvey installation files if the template files and directories are not editable. Copy an existing template to a new directory to play around with the content. This may help make the concept clearer.&lt;br /&gt;
&lt;br /&gt;
A number of the &#039;public&#039; elements of LimeSurvey can be adjusted by a series of templates. This section provides a very brief explanation of these templates, however more detailed information - especially regarding the editing/creation of new templates is available under [[Templates + Styles]].&lt;br /&gt;
&lt;br /&gt;
=The LimeSurvey Template Editor=&lt;br /&gt;
&lt;br /&gt;
To ease the understanding and quick update of a Template, LimeSurvey provides a &#039;&#039;&#039;Template Editor&#039;&#039;&#039; in the main &#039;&#039;&#039;administrative&#039;&#039;&#039; toolbar of the application.  This Template Editor is only available to users given the privilege in the User Security settings.  A template effects all surveys and can render a survey inoperable if not constructed properly.  So Template editing is thought best restricted to a very limited, knowledgeable set of users.  Having permission to enter the Template Editor is not enough though.&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey Template Editor allows you to edit the contents of your templates online. Start the Template Editor by clicking on the &amp;quot;Template Editor&amp;quot; icon [[File:templates.png]] in the LimeSurvey Administration toolbar (Templates). The main screen is similar to the LimeSurvey Survey Administration screen. It allows you to select the template to edit/view. Once this has been selected you can then select from one of the different public survey pages. You are then presented with a list of the template files that make up that particular page.&lt;br /&gt;
&lt;br /&gt;
==The Template Menu==&lt;br /&gt;
*&#039;&#039;&#039;Edit Icon:&#039;&#039;&#039; The &amp;quot;edit&amp;quot; icon indicates whether or not the template is editable. A blurred out icon indicates that the template is read only; a clickable icon indicates you may make modifications. To change the icon from blurred to clear, you have to modify the template&#039;s permissions.&lt;br /&gt;
*&#039;&#039;&#039;Rename this template:&#039;&#039;&#039; Allows you to change the name of the template.  Generally used after copying an existing template or importing a template by manipulating the underlying directories.&lt;br /&gt;
*&#039;&#039;&#039;Export Template:&#039;&#039;&#039; Allows you to export the current template to a .zip-File.&lt;br /&gt;
*&#039;&#039;&#039;Copy Template:&#039;&#039;&#039; Allows you to make a new template by copying the current one.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Screen&amp;quot; drop-down list on the right allows you to choose which particular survey page you are currently looking at.&lt;br /&gt;
&lt;br /&gt;
==Import/Export/Copy a Template==&lt;br /&gt;
&lt;br /&gt;
When you &#039;&#039;&#039;export &#039;&#039;&#039;a template, this will create a zip-file archive with all the files your template consists of (.pstpl files, images, css files, ...). You can simply &#039;&#039;&#039;import &#039;&#039;&#039;the exported zip-file at other Limesurvey systems by using the import feature or you can manually copy the archive to another installation and extract it into the corresponding template directory there. If you copy the template in the same installation, you will need to rename the folder to create another named copy of that template.&lt;br /&gt;
&lt;br /&gt;
If the file and directory permissions are open for the LimeSurvey application to write, then you can use the programs &#039;&#039;&#039;copy &#039;&#039;&#039;and rename features to make a local copy of a template.&lt;br /&gt;
&lt;br /&gt;
==Page Structure / Template Use==&lt;br /&gt;
*&#039;&#039;&#039;The Welcome Page:&#039;&#039;&#039; startpage.pstpl, welcome.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Questions Pages:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, startgroup.pstpl, groupdescription.pstpl, question.pstpl, endgroup.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Submit Page:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, submit.pstpl, (privacy.pstpl), navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Final Page:&#039;&#039;&#039; startpage.pstpl, completed.pstpl, endpage.pstpl&lt;br /&gt;
&lt;br /&gt;
==Template Files==&lt;br /&gt;
&lt;br /&gt;
The following template files are used to produce your public survey and must exist in any new template folder you create:&lt;br /&gt;
*&#039;&#039;&#039;startpage.pstpl:&#039;&#039;&#039; Produces the start of each html page. It starts at the &amp;quot;&amp;lt;head&amp;gt;&amp;quot; tag, and should not contain the &amp;quot;&amp;lt;html&amp;gt;&amp;quot; tag. This &#039;very beginning&#039; of a standard html page is written by the scripts. Please ensure that your startpage.pstpl files contains a &amp;lt;body&amp;gt; tag, even though many browsers do not require strict adherence to the W3 HTML stanards, the LimeSurvey script needs to find a &amp;lt;body&amp;gt; tag, to run certain javascript elements. It is not expected that many &#039;keywords&#039; will be used in the startpage.pstpl file, however you may wish to put the {SURVEYNAME} into the title. The startpage.pstpl file can contain code that ends in the corresponding endpage.pstpl file, so you can start a table in this file and close the table in the endpage.pstpl file. The startpage.pstpl and endpage.pstpl files wrap around every possible page used by LimeSurvey.&lt;br /&gt;
*&#039;&#039;&#039;survey.pstpl:&#039;&#039;&#039; This template is the second used on most pages, and provides a space to put the survey name and description. This template does not have a corresponding &#039;closing&#039; template, and subsequently you should close all tags opened in this template file (ie: don&#039;t leave a table open here because there is nowhere else to close it)&lt;br /&gt;
*&#039;&#039;&#039;welcome.pstpl:&#039;&#039;&#039; This template is only used in the welcome screen (which is also on the main page for &#039;all in one&#039; surveys). You can use this to print out the welcome text, and other information that should be provided in the introduction. Like the &#039;survey.pstpl&#039; file, there is no corresponding &#039;closing&#039; template, so all tags opened in this template file should be closed as well.&lt;br /&gt;
*&#039;&#039;&#039;startgroup.pstpl:&#039;&#039;&#039; This template can provide a &#039;summary&#039; wrap around for questions within a group. It has a matching &#039;endgroup.pstpl&#039; template that can be used to close any opened tags in this file, so you can open a table within this.&lt;br /&gt;
*&#039;&#039;&#039;groupdescription.pstpl:&#039;&#039;&#039; This template file is used to display a description of a group. It is separate to the startgroup.pstpl file because in a &amp;quot;question by question&amp;quot; survey it will be displayed on its own unique page in between groups, whereas in a &amp;quot;group by group&amp;quot; or &amp;quot;all in one&amp;quot; survey it provides a header to the subsequent questions. groupdescription.pstpl does not have a corresponding &#039;closing&#039; template file, so all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question.pstpl:&#039;&#039;&#039; This file contains the question, answer and help text sections of your survey, and in the &amp;quot;group by group&amp;quot; and &amp;quot;all in one&amp;quot; surveys this template is cycled repeatedly with each question. There is no corresponding closing file for this and all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question_start.pstpl:&#039;&#039;&#039; This file contains the individual elements found at the start of a question. It is included within &#039;question.pstpl&#039; via the {QUESTION} keyword. It is intended to allow template designers more control over the layout of a question. This template sits outside the normal templating system and &#039;&#039;&#039;was superseeded (as of LS1.87)&#039;&#039;&#039;. All keywords from this template are now available directly in question.pstpl. NOTE: templates using question_start.pstpl will still work at least for a couple more versions of LS 1.x&lt;br /&gt;
*&#039;&#039;&#039;submit.pstpl (and privacy.pstpl):&#039;&#039;&#039; This page is the penultimate page for all types of survey (except the &amp;quot;all in one&amp;quot; type) where the participant is given an option to review questions before submitting their responses. It provides privacy information where a survey is anonymous, which it extracts from the &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039; file.&lt;br /&gt;
*&#039;&#039;&#039;completed.pstpl:&#039;&#039;&#039; This page is displayed as the final page when the survey responses have been saved and the survey is over. It can be used to display a &amp;quot;forwarding link&amp;quot; as set in the survey setup.&lt;br /&gt;
*&#039;&#039;&#039;endgroup.pstpl:&#039;&#039;&#039; This file closes the group, and can be used to close off any tags opened in the startgroup.pstpl file&lt;br /&gt;
*&#039;&#039;&#039;navigator.pstpl:&#039;&#039;&#039; This file contains the buttons that navigate through the survey, &amp;quot;next&amp;quot;, &amp;quot;prev&amp;quot;, &amp;quot;last&amp;quot;, &amp;quot;submit&amp;quot;, &amp;quot;save so far&amp;quot;  and the &amp;quot;clear all&amp;quot; link. It is used in all pages except the completed page.&lt;br /&gt;
*&#039;&#039;&#039;printanswers.pstpl:&#039;&#039;&#039; This file has the HTML wrapper for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_group.pstpl:&#039;&#039;&#039; This file is the same as startgroup.pstpl endgroup.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_question.pstpl:&#039;&#039;&#039; This file is the same as question.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_survey.pstpl:&#039;&#039;&#039; This file is the same as survey.pstpl but for the print version of the survey.&lt;br /&gt;
&lt;br /&gt;
==Other Template Files==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;invitationemail.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;reminderemail.pstpl&#039;&#039;&#039; and &#039;&#039;&#039;confirmationemail.pstpl&#039;&#039;&#039; are no longer used by LimeSurvey and defaults are instead set in the applicable language files. The email messages can now be edited on a survey by survey basis.&lt;br /&gt;
&lt;br /&gt;
==Standard Pages==&lt;br /&gt;
&lt;br /&gt;
There are ten standard pages that a survey participant may see in the course of taking or accessing the LimeSurvey application.  Each is constructed from a number of common &#039;&#039;&#039;Template&#039;&#039;&#039; files from the &#039;&#039;&#039;Template&#039;&#039;&#039; specified in the survey&#039;s settings.  The table below indicates which template files are used in constructing each of these pages.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|  &#039;&#039;&#039;Survey Pages:&#039;&#039;&#039;&amp;lt;br/&amp;gt;&#039;&#039;&#039;Template Files&#039;&#039;&#039;||Survey&amp;lt;br/&amp;gt;List||Welcome||Question||Completed||Clear All||Register||Load||Save||Print&amp;lt;br/&amp;gt;Answers||Print&amp;lt;br/&amp;gt;Survey&lt;br /&gt;
|-&lt;br /&gt;
|SurveyList|| [[File:check.gif]]|| || || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Welcome|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Privacy|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Navigator|| || [[File:check.gif]]|| [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Survey|| || || [[File:check.gif]]|| || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|StartGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|GroupDescription|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Question&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|EndGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Assessment|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Completed|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|ClearAll|| || || || || [[File:check.gif]]|| || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Register|| || || || || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Load|| || || || || || || [[File:check.gif]]|| || ||&lt;br /&gt;
|-&lt;br /&gt;
|Save|| || || || || || || || [[File:check.gif]]|| ||&lt;br /&gt;
|-&lt;br /&gt;
|PrintAnswers|| || || || || || || || || [[File:check.gif]]||&lt;br /&gt;
|-&lt;br /&gt;
|Print Survey || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Group || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Question || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|StartPage&amp;lt;br/&amp;gt;EndPage&amp;lt;br/&amp;gt;Template.css|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;NOTE: In versions 1.90 and up this replaces question.pstpl AND question_start.pstpl. If you are using an old custom template, you need to add the following line to the beginning of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div {QUESTION_ESSENTIALS} class=&amp;quot;{QUESTION_CLASS}{QUESTION_MAN_CLASS}{QUESTION_INPUT_ERROR_CLASS}&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;And then add the corresponding closing tag to the end of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The File Control Section==&lt;br /&gt;
&lt;br /&gt;
In the &amp;quot;file control&amp;quot; window on the left, you can click on one of the template files that is used to compile the page. The HTML code for that file will then appear in the &amp;quot;Now editing&amp;quot; window in the center. If the template is editable (determined by directory permissions) you can then make any changes and save them.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Other Files&amp;quot; window shows a list of all other files in the template directory. You can use the right side to &#039;&#039;&#039;upload and select image files (your pics, logos,...) or other files needed to create your template&#039;&#039;&#039;. Note: Instead of a link directly to each picture in your template you can use the field string {TEMPLATEURL}.  So instead of:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;/limesurvey/templates/yourtemplate/mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt; You can use:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;{TEMPLATEURL}mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A &amp;quot;sample&amp;quot; of the template page you are editing will be visible at the bottom of the screen. There is no way to to delete a template from the template editor. This must be done by accessing the underlying directory and deleting the file there.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; The shipped templates cannot be edited using the Template Editor and should never be changed. If you want to modify them, create a copy first and modify the copy.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Location of template files==&lt;br /&gt;
&lt;br /&gt;
LimeSurvey stores each of the &#039;standard&#039; templates in their own distinct sub-directory within the /templates directory that is kept in the public directory with the other LimeSurvey public files. Customized user templates are stored in the /upload/templates directory.&lt;br /&gt;
&lt;br /&gt;
To create a new template, use the according icon in the template editor.&lt;br /&gt;
&lt;br /&gt;
There should ALWAYS be a &amp;quot;default&amp;quot; directory in the templates directory. This template is used by default and as a fall-back if a template folder doesn&#039;t exist, or can&#039;t be found. The &amp;quot;default&amp;quot; directory comes with the package.&lt;br /&gt;
&lt;br /&gt;
You can use any image files that you upload into the template management area with syntax like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;{TEMPLATEURL}filename.xyz&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Styling questions with CSS=&lt;br /&gt;
&lt;br /&gt;
Styling of questions in CSS has become much easier. Each question type now has a unique class. Mandatory question&#039;s also have an additional mandatory class. For example, for a non-mandatory question:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory but the user didn&#039;t answer it or if there is validation on a question&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question has validation applied but the user hasn&#039;t answered correctly&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question6&amp;quot; class=&amp;quot;text-short input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The full list of question classes==&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;Question Type&#039;&#039;&#039;||&#039;&#039;&#039;Question Class&#039;&#039;&#039;||&#039;&#039;&#039;Question ID&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|5 point choice||.choice-5-pt-radio||5&lt;br /&gt;
|-&lt;br /&gt;
|Array (10 point choice)||.array-10-pt||B&lt;br /&gt;
|-&lt;br /&gt;
|Array (5 point choice)||.array-5-pt||A&lt;br /&gt;
|-&lt;br /&gt;
|Array (Flexible Labels) dual scale||.array-flexible-duel-scale ||1&lt;br /&gt;
|-&lt;br /&gt;
|Array (Increase, Same, Decrease)||.array-increase-same-decrease||E&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Numbers)||.array-multi-flexi ||:&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Text)||.array-multi-flexi-text||;&lt;br /&gt;
|-&lt;br /&gt;
|Array (Yes/No/Uncertain)||.array-yes-uncertain-no||C&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels)||.array-flexible-row ||F&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels) by column||.array-flexible-column||H&lt;br /&gt;
|-&lt;br /&gt;
|Boilerplate question||.boilerplate||X&lt;br /&gt;
|-&lt;br /&gt;
|Date||.date||D&lt;br /&gt;
|-&lt;br /&gt;
|Gender||.gender||G&lt;br /&gt;
|-&lt;br /&gt;
|Huge free text||.text-huge||U&lt;br /&gt;
|-&lt;br /&gt;
|Language switch||.language||I&lt;br /&gt;
|-&lt;br /&gt;
|List (dropdown)||.list-dropdown||!&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (dropdown)||.list-dropdown-flexible||W&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (radio)||.list-radio-flexible||Z&lt;br /&gt;
|-&lt;br /&gt;
|List (radio)||.list-radio||L&lt;br /&gt;
|-&lt;br /&gt;
|List with comment||.list-with-comment||O&lt;br /&gt;
|-&lt;br /&gt;
|Long free text||.text-long||T&lt;br /&gt;
|-&lt;br /&gt;
|Multiple numerical input||.numeric-multi||K&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options||.multiple-opt||M&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options with comments||.multiple-opt-comments||P&lt;br /&gt;
|-&lt;br /&gt;
|Multiple short text||.multiple-short-txt||Q&lt;br /&gt;
|-&lt;br /&gt;
|Numerical input||.numeric||N&lt;br /&gt;
|-&lt;br /&gt;
|Ranking||.ranking||R&lt;br /&gt;
|-&lt;br /&gt;
|Short free text||.text-short||S&lt;br /&gt;
|-&lt;br /&gt;
|Yes/No||.yes-no||Y&lt;br /&gt;
|-&lt;br /&gt;
|Mandatory||.mandatory||&lt;br /&gt;
|-&lt;br /&gt;
|User input error||.input_error|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Importing styles into your custom template==&lt;br /&gt;
&lt;br /&gt;
The custom question styles are near the bottom of each template&#039;s CSS file and start with:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;/* &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;----&lt;br /&gt;
&lt;br /&gt;
  START: Question styles  &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt; */&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you&#039;re styling your own custom template, You should be able to copy everything after the above from templates/default/template.css (for tables based layouts) or /templates/limespired/template.css (for CSS based layouts) into your own style sheet without any impact on your other styles.&lt;br /&gt;
&lt;br /&gt;
==Internet Explorer conditional style sheets==&lt;br /&gt;
&lt;br /&gt;
Because of the marked discrepancies in rendering between IE6, IE7 and most other browsers, there are special IE conditional style sheets included for each template.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;You should include the above code within your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; and copies of both the IE style sheets from either /templates/default/ or /templates/limespired for Tables base layout and CSS based layout respectively.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; If you copy the styles into your own style sheet you will almost certainly need to tweak them.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Right-to-Left (RTL) Languages and justify==&lt;br /&gt;
&lt;br /&gt;
The text editor within LimeSurvey is able to format RTL Text. However, the editor itself shows the RTL language in a left to right format when justified.  This is just an editor display issue. The RTL and justified question or text will display correctly from right to left, even when justified, in your survey or on preview.&lt;br /&gt;
&lt;br /&gt;
==Keywords==&lt;br /&gt;
&lt;br /&gt;
Keywords within a template file get replaced by the current survey information. They are surrounded by curly brackets, for example: {SURVEYNAME}&lt;br /&gt;
&lt;br /&gt;
The following strings will be replaced by LimeSurvey when parsing the template file and presenting it to survey users. These field strings will work on almost every template except for the &#039;Completed Page&#039;. (Most of these strings can be found in the common.php file. If it&#039;s not there, look in the index.php file.)&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;::KEYWORD::&#039;&#039;&#039;|| &#039;&#039;&#039;TEMPLATE FILES::&#039;&#039;&#039; || &#039;&#039;&#039;::DESCRIPTION::&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYNAME}||All Files||The survey title&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYDESCRIPTION}||All Files||The survey description&lt;br /&gt;
|-&lt;br /&gt;
|{WELCOME}||All files (mainly for welcome.pstpl)||The survey &#039;welcome&#039; text&lt;br /&gt;
|-&lt;br /&gt;
|{PERCENTCOMPLETE}||survey.pstpl||A small graph showing the percentage of the survey completed&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPNAME}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group name&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPDESCRIPTION}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group description&lt;br /&gt;
|-&lt;br /&gt;
|{NUMBEROFQUESTIONS}||welcome.pstpl||Displays the total number of questions in the survey (just the number)&lt;br /&gt;
|-&lt;br /&gt;
|{THEREAREXQUESTIONS}||welcome.pstpl||Displays the sentence &amp;quot;There are X questions in this survey&amp;quot; - from the relevant language file. The X is replaced with the number of questions. Note that this will also work appropriately for singular or plural. If there is only 1 question, it will print &amp;quot;There is 1 question in this survey&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|{CHECKJAVASCRIPT}||All files (mainly for welcome.pstpl)||Warning message when end-user browser have javascript disabled&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION}||Question.pstpl||(&#039;&#039;&#039;Has been superseeded but the {QUESTION_...} keywords as of LS1.87&#039;&#039;&#039;) Displays the current question text (The format of {QUESTION} can customised by editing &#039;question_start.pstpl&#039;) Use the following: {QUESTION_TEXT}, {QUESTION_MANDATORY}, {QUESTION_HELP}, {QUESTION_MAN_MESSAGE}, {QUESTION_VALID_MESSAGE} and {QUESTION_INPUT_ERROR_CLASS} and appropriate wrapping HTML instead of {QUESTION})&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWER}||question.pstpl, print_question.pstpl||presents the answer form for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{SGQ}||question.pstpl, question text||Can be used in the question text itself, to reference the input field of the question dynamically by displaying the Survey-Group-Question id for the current question. (as of svn build 9755)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTIONHELP}||question.pstpl, print_question.pstpl||Displays help text for the current questionm for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CLASS}||question.pstpl, print_question.pstpl||unique class for each question type. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CODE}||question.pstpl, print_question.pstpl||Displays the current question code&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ESSENTIALS}||question.pstpl||the question ID and (if a question is conditional), &#039;style=&amp;quot;display:none;&amp;quot;&#039;. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_HELP}||question.pstp, question_start.pstpl||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TYPE_HELP}||print_question.pstp||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_INPUT_ERROR_CLASS}||question.pstp, question_start.pstpl||Provides a class if there was user input error&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ID}||print_question.pstp||Provides a unique ID for each question to allow styling for specific questions&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TEXT}||question.pstp, print_question.pstp, question_start.pstpl||Displays the text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MANDATORY}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_CLASS}||question.pstpl, print_question.pstpl||class if a question is mandatory. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_NUMBER}||print_question.pstpl||Incremental count of questions.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_VALID_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated valid help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_SCENARIO}||print_question.pstp||Prints out the &#039;scenario&#039; text for conditional questions.&lt;br /&gt;
|-&lt;br /&gt;
|{NAVIGATOR}||navigator.pstpl||Displays navigation buttons (next, prev, last)&lt;br /&gt;
|-&lt;br /&gt;
|{CLEARALL}||All files (but intended for navigator.pstpl)||Displays the &amp;quot;Exit and Clear Results&amp;quot; link&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITBUTTON}||submit.pstpl||Displays the final submit button&lt;br /&gt;
|-&lt;br /&gt;
|{COMPLETED}||completed.pstpl||Displays the &#039;completed&#039; messagem for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{url}||completed.pstpl||Displays the survey &#039;url&#039; and &#039;url text&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACY}||submit.pstpl||Displays privacy information when survey is anonymous&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACYMESSAGE}||privacy.pstpl||The privacy message is shown if you set your survey to be anonymous. [http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+1.x+Translating+LimeSurvey The text can be edited/translated] in the language files. This can also be changed manually by editing the privacy.pstpl template you wish to use.&lt;br /&gt;
|-&lt;br /&gt;
|{TEMPLATEURL}||All Files||The URL to the current template location (useful for referencing image files in your template)&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITCOMPLETE}||endpage.pstpl||The statement (from the language files) that tells the user they have completed the survey, and to press the &amp;quot;Submit&amp;quot; button&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITREVIEW}||survey.pstpl||The statement (from the language files) that tells the user they can review/change the answers they have made by clicking &amp;quot;&amp;lt;&amp;lt; prev&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:FIRSTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users first name from the tokens table&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:LASTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users last name from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:EMAIL}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users email from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_1}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_1 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_2}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_2 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWERSCLEARED}||Preferably in navigator.pstpl||The &amp;quot;Answers Cleared&amp;quot; statement from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{RESTART}||clearall.pstpl||URL to restart the survey&lt;br /&gt;
|-&lt;br /&gt;
|{CLOSEWINDOW}||All Files (Preferably in navigator.pstpl)||URL to close current window&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERERROR}||register.pstpl||Shows any error messages in the register page (ie: &amp;quot;You must include an email address&amp;quot;)&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE1}||register.pstpl||The statement &amp;quot;You must be registered to complete this survey&amp;quot; from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE2}||register.pstpl||Details about registering from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERFORM}||register.pstpl||The actual form for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{SAVE}||Works suitable on navigator.pstpl||Displays the &#039;Save your responses so far&#039; button to offer the user to save and come back later to continue the survey. If the Save option is deactivated in the survey properties the tag will not be shown and ignored.&lt;br /&gt;
|-&lt;br /&gt;
|{LANGUAGECHANGER}||survey.pstpl||Displays a switch in multilingual surveys to change the question.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Input/Buttons==&lt;br /&gt;
&lt;br /&gt;
Each &amp;quot;input&amp;quot; type in a survey has been given its own class name, so that you can add CSS to your &amp;quot;startpage.pstpl&amp;quot; file, and have some control over the appearance of form buttons and inputs. These class names are as follows:&lt;br /&gt;
*&#039;&#039;&#039;submit&#039;&#039;&#039; (Submit Buttons)&lt;br /&gt;
*&#039;&#039;&#039;text&#039;&#039;&#039; (Text Inputs - for short free text, date and numerical type)&lt;br /&gt;
*&#039;&#039;&#039;answertext&#039;&#039;&#039; (Text of answers)&lt;br /&gt;
*&#039;&#039;&#039;radio&#039;&#039;&#039; (Radio Buttons)&lt;br /&gt;
*&#039;&#039;&#039;checkbox&#039;&#039;&#039; (Check Boxes)&lt;br /&gt;
*&#039;&#039;&#039;select&#039;&#039;&#039; (Select / List Boxes)&lt;br /&gt;
*&#039;&#039;&#039;textarea&#039;&#039;&#039; (Large text inputs - for long free text)&lt;br /&gt;
*&#039;&#039;&#039;clearall&#039;&#039;&#039; (The &amp;quot;Exit and Clear Survey&amp;quot; link)&lt;br /&gt;
*&#039;&#039;&#039;rank&#039;&#039;&#039; (The rank style question. Doesn&#039;t set the colour of the select box or the text boxes (these are set by relevant section above) but does allow changing of background colour, text colour and size etc for the rest of the ranking question)&lt;br /&gt;
*&#039;&#039;&#039;graph&#039;&#039;&#039; (The &amp;quot;percentage completed&amp;quot; graph table)&lt;br /&gt;
*&#039;&#039;&#039;innergraph&#039;&#039;&#039; (The table inside the graph table - this contains the 0% and 100% text. Use this for changing the size of this text&lt;br /&gt;
*&#039;&#039;&#039;question&#039;&#039;&#039; (General settings for any question that is displayed within a table. Generally you should use this to make sure that their font size and colour is the same as you have used elsewhere as a default)&lt;br /&gt;
*&#039;&#039;&#039;mandatory&#039;&#039;&#039;  (Mandatory questions)&lt;br /&gt;
*&#039;&#039;&#039;input_error&#039;&#039;&#039; (User input error - for if a user has made a mistake with a mandatory question or question with validation)&lt;br /&gt;
*&#039;&#039;&#039;array1&#039;&#039;&#039; and &#039;&#039;&#039;array2&#039;&#039;&#039; (These two styles are cycled when presenting the range of answers for an array type question. This allows you to set an alternating background colour for these question types. &#039;&#039;&#039;Array1&#039;&#039;&#039; is also used for the column headings in these question types)&lt;br /&gt;
*&#039;&#039;&#039;errormandatory&#039;&#039;&#039; (Sets the colour and style of the &amp;quot;This question is mandatory&amp;quot; error message)&lt;br /&gt;
*&#039;&#039;&#039;warningjs&#039;&#039;&#039; (Sets the colour and style of the warning message displayed if the participant&#039;s browser has javascript disabled)&lt;br /&gt;
&lt;br /&gt;
There are also some elements that can be accessed using the ID of the element (&#039;&#039;&#039;#ID&#039;&#039;&#039; in CSS):&lt;br /&gt;
*&#039;&#039;&#039;surveycontact&#039;&#039;&#039; (The contact message shown on the start page)&lt;br /&gt;
*&#039;&#039;&#039;tokenmessage&#039;&#039;&#039; (used for messages inside the survey, e.g. the session expired error message)&lt;br /&gt;
&lt;br /&gt;
An example of using these classes with style sheets can be found in the &amp;quot;bubblegum&amp;quot; template that comes with the LimeSurvey application.&lt;br /&gt;
&lt;br /&gt;
Because you can edit all the HTML aspects, there&#039;s no reason to surround your templates with a &amp;lt;div class=&#039;new_name&#039;&amp;gt; and then define a css for that new_name class.&lt;br /&gt;
&lt;br /&gt;
==Styling the progress bar==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before version 1.87:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The chart.jpg file is a simple one pixel image file which is used to create the progress bar image in the &#039;PERCENTCOMPLETE&#039; table. If the file does not exist, LimeSurvey will use the default &#039;maroon&#039; coloured image in the public directory. If you want to create a bar to match your own colour scheme, then you should save the color in this file. Remember it should be a &#039;&#039;&#039;JPEG&#039;&#039;&#039; file, 1 pixel x 1 pixel, in the colour desired.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The progress bar appearance can be modified with CSS.&lt;br /&gt;
&lt;br /&gt;
To change the background colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 background-color: #3300FF;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To change the border colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-content,&lt;br /&gt;
#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 border: 1px solid #FF0000;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Advanced Features Available to Developers==&lt;br /&gt;
&lt;br /&gt;
Starting with version 0.99, LimeSurvey has integrated some user-made patches that allow for some special changes.  These very advanced features generally require changes to the underlying code base of LimeSurvey and should be done carefully so as not to introduce security holes.&lt;br /&gt;
&lt;br /&gt;
===Basic CMS Integration support===&lt;br /&gt;
&lt;br /&gt;
To be able to integrate LimeSurvey into another CMS, use the following options in &#039;&#039;&#039;config.php&#039;&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
// Set $embedded to true and specify the header and footer functions if the survey is to be displayed embedded in a CMS&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$embedded = false;&lt;br /&gt;
&lt;br /&gt;
$embedded_inc = &amp;quot;&amp;quot;;               // path to the header to include if any&lt;br /&gt;
&lt;br /&gt;
$embedded_headerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteHeader for geeklog&lt;br /&gt;
&lt;br /&gt;
$embedded_footerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteFooter for geeklog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set &#039;&#039;&#039;$embedded = true;&#039;&#039;&#039; to enable CMS-embedding. By using the &#039;&#039;&#039;$embedded_inc&#039;&#039;&#039; variable one can include their own &#039;&#039;&#039;.php&#039;&#039;&#039; files.  By setting &#039;&#039;&#039;$embedded_headerfunc&#039;&#039;&#039; or &#039;&#039;&#039;$embedded_footerfunc&#039;&#039;&#039;, one can call functions from within included files that output the relevant headers or footers instead of LimeSurveys default ones.&lt;br /&gt;
&lt;br /&gt;
===Support for your own Javascript functions===&lt;br /&gt;
&lt;br /&gt;
Some users may need to run Javascript on the survey pages, but calling &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; in the BODY element made it impossible to do so.  This call has been replaced with a small JavaScript function in the HEAD that sniffs for the existence of &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; and &#039;&#039;&#039;template_onload()&#039;&#039;&#039; before calling each.  This way a template author can create their own &#039;&#039;&#039;template_onload()&#039;&#039;&#039; function in the HEAD that replaces the default one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
*Disable XSS filter - in Global settings -&amp;gt; Security, set &amp;quot;Filter HTML for XSS&amp;quot; to No.&lt;br /&gt;
*Enter your script in the source of a question or group description.&lt;br /&gt;
*There are more details in the [http://docs.limesurvey.org/tiki-index.php?page=Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#How_to_use_Script_eg._JavaScript_etc._in_LimeSurvey_ workaround section].&lt;br /&gt;
&lt;br /&gt;
=Videos on Templates=&lt;br /&gt;
&lt;br /&gt;
These videos will demonstrate the basic and advanced template functions that are available to all LimeSurvey users. This includes changing the appearance of certain forms and inserting custom graphics. Additionally, it will thoroughly walk you through on how to edit and preview specific page templates, importing/exporting templates, modify appearance of questions in the CSS, customizing survey description page, and completed page.&lt;br /&gt;
&lt;br /&gt;
Part I&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;nLsfxMjRXyk?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part II&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;yrAXStFH34Q?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part III&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;TYlJXHgt8R0?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part IV&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;Rml0gqeErVc?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part V&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;LX24Ix1ylmY?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part VI&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;-202CqQcW8g?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
=Tips &amp;amp; Tricks=&lt;br /&gt;
&lt;br /&gt;
==Change the layout of the survey page==&lt;br /&gt;
&lt;br /&gt;
When editing a template this template can be assigned to a single survey while the survey list page, which is shown at www.yourdomain.org/limesurveyinstallfolder, lists all your surveys.&lt;br /&gt;
&lt;br /&gt;
To use your current template for this page you have change the according setting at the Global Settings screen; at older versions this change can be done by editing the $defaulttemplate setting at the config file: Copy this setting from config-defaults.php to config.php which overrides config-defaults.php and edit this setting to $defaulttemplate = &#039;yourtemplatename&#039;;&lt;br /&gt;
&lt;br /&gt;
==Import/Export of templates: Mac users==&lt;br /&gt;
&lt;br /&gt;
Mac users, please note: Mac OSX default archive utility may have problems with zip folders &amp;quot;generated on the fly&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
a work around is to unix&#039;es unzip from the command line:&lt;br /&gt;
&lt;br /&gt;
$ unzip template.zip -d template&lt;br /&gt;
&lt;br /&gt;
Archive: template.zip&lt;br /&gt;
&lt;br /&gt;
 inflating: template/startpage&lt;br /&gt;
&lt;br /&gt;
 inflating: ...&lt;br /&gt;
&lt;br /&gt;
or scripts in their mac-compiled counterparts:&lt;br /&gt;
&lt;br /&gt;
http://homepage.mac.com/roger_jolly/software/&lt;br /&gt;
&lt;br /&gt;
==Changing your templates traffic light from red to green==&lt;br /&gt;
&lt;br /&gt;
If you haven&#039;t already, set the admin directory to read/write/execute (777). The files within it, however, may be set to read/execute only (chmod 755).&lt;br /&gt;
&lt;br /&gt;
GO to file directory ie file manager, find templates directory.&lt;br /&gt;
&lt;br /&gt;
1 change permission on eg&amp;quot;vallendar&amp;quot; (or any template of your choice) directory to read 777&lt;br /&gt;
&lt;br /&gt;
2 voila! the red traffic light on &amp;quot;vallendar&amp;quot; is now green.&lt;br /&gt;
&lt;br /&gt;
3 NOTE: to restrict access for safety, when finished editing template files, change all templates files back to what they were eg 644&lt;br /&gt;
&lt;br /&gt;
==Replacing the help icon==&lt;br /&gt;
&lt;br /&gt;
When a question help text is shown then an help.gif image is used from the default template folder.&lt;br /&gt;
&lt;br /&gt;
You can replace this image by uploading a new help.gif, help.png or help.jpg in your custom template folder. It then will be automatically used instead of the default help icon.&lt;br /&gt;
&lt;br /&gt;
==Replacing an existing logo==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Before uploading new logo delete previous one.&lt;br /&gt;
&lt;br /&gt;
1. To edit logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
2. Find and Click Search button, to find place where is logo style text.&lt;br /&gt;
&lt;br /&gt;
[[File:2.PNG]]&lt;br /&gt;
&lt;br /&gt;
3. Find in search &amp;lt;u&amp;gt;#logo&amp;lt;/u&amp;gt; (It is logo design code)&lt;br /&gt;
&lt;br /&gt;
[[File:3.PNG]]&lt;br /&gt;
&lt;br /&gt;
4. Edit style file&lt;br /&gt;
&lt;br /&gt;
You will see something like this code:&lt;br /&gt;
&lt;br /&gt;
[[File:4.PNG]] &lt;br /&gt;
&lt;br /&gt;
If you want change image just replace logo.gif to antoher image link. Like: (&amp;lt;u&amp;gt;logo.png&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.jpg&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.swf&amp;lt;/u&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
If you want change image size just change, width and height (in pixels) like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;Width:100px; Height:100px;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adding your own logo==&lt;br /&gt;
&lt;br /&gt;
1. Find and Open &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; template file.&lt;br /&gt;
&lt;br /&gt;
[[File:5.PNG]] &lt;br /&gt;
&lt;br /&gt;
2. Write in &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; this line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;img id=&amp;amp;rdquo;page_logo&amp;amp;rdquo; src=&amp;amp;rdquo;{TEMPLATEURL}logo.png&amp;amp;rdquo;&amp;gt;&amp;lt;br&amp;gt;&amp;lt;/syntaxhighlight&amp;gt; After &amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;body ... &amp;gt;&amp;lt;/syntaxhighlight&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
[[File:6.PNG]] &lt;br /&gt;
&lt;br /&gt;
3. To add logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
3.1 Go to end of &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo; style file.&lt;br /&gt;
&lt;br /&gt;
3.2 Write in end:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in left side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:left;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in right side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:right;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in center:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   display: block;&lt;br /&gt;
&lt;br /&gt;
   margin-left: auto;&lt;br /&gt;
&lt;br /&gt;
   margin-right: auto;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the default help to all question (hide_tip)==&lt;br /&gt;
&lt;br /&gt;
There are 2 solution to remove the default help, like a [[Advanced question settings|#hide_tip|hide_tip attribute]] but for all question and survey.&lt;br /&gt;
# you can remove the {QUESTIONHELP} and is container from the file question.pstl, but it can be a bad idea for screenreader.&lt;br /&gt;
# for the default template and some other , add this at the end of tempate.css&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;span.questionhelp{display:none;}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display custom favicon==&lt;br /&gt;
&lt;br /&gt;
A favicon is the little icon you see in the browser&#039;s address bar, list of bookmarks or tab. You can display your own icon as follows:&lt;br /&gt;
#Create a favicon - google will find you lots of free favicon generators&lt;br /&gt;
#Name your new favicon &amp;quot;favicon.ico&amp;quot; and place it in your template directory&lt;br /&gt;
#Add the following code to your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; before the &amp;lt;/head&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;link rel=&amp;quot;shortcut icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;link rel=&amp;quot;icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Different appearance for survey-/question-pages==&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;Version 1.91 and newer&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
If you want LimeSurvey to change the appearance of every second page (i.e. of even and odd survey pages) you can use &#039;&#039;&#039;.page-odd&#039;&#039;&#039; class in your css file to change the appearance of odd pages.&lt;br /&gt;
&lt;br /&gt;
example from default template of LimeSurvey 1.91+&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
.page-odd table.question-group {&lt;br /&gt;
&lt;br /&gt;
 background-color: #D2F2D3;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To &#039;&#039;&#039;not&#039;&#039;&#039; differentiate even and odd pages at the (default) template find all instances of &#039;&#039;.page-odd&#039;&#039; in template.css and remove those styles.&lt;br /&gt;
&lt;br /&gt;
==Create a vertical separator  border for dual scale array==&lt;br /&gt;
&lt;br /&gt;
To create a vertical separator border for a dual scale array you can add the following lines to your &#039;&#039;&#039;template.css&#039;&#039;&#039;-file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
table.question thead td.header_separator,&lt;br /&gt;
&lt;br /&gt;
table.question tbody td.dual_scale_separator&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   border-right:solid 1px #00A8E1;&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
header_separator is used to adress the separator for the header &amp;quot;td&amp;quot; and &amp;quot;dual_scale_separator&amp;quot; is used to adress the separator column in the dual scale array.&lt;br /&gt;
&lt;br /&gt;
==Hide the survey contact message shown on the start page/survey list==&lt;br /&gt;
&lt;br /&gt;
To hide the &amp;quot;Please contact ...&amp;quot; meassage on the start page (with the survey list) you can add the following to the &#039;&#039;&#039;$(document).ready&#039;&#039;&#039; function in the &#039;&#039;&#039;template.js&#039;&#039;&#039; of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$(&#039;#surveycontact&#039;).hide(); //Hides the survey contact message&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the survey contact message shown on error messages==&lt;br /&gt;
&lt;br /&gt;
If you want to remove the survey contact message from error messages it&#039;ll be trickier. You can add the following function call to the &#039;&#039;&#039;$(document).ready&#039;&#039;&#039; function in the &#039;&#039;&#039;template.css&#039;&#039;&#039; of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
removeContactAdressFromMessage(); //Removes the survey contact message from error messages&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and add the following function to your *template.js* file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
function removeContactAdressFromMessage()&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
if ($(&#039;#tokenmessage&#039;).length &amp;gt; 0)&lt;br /&gt;
&lt;br /&gt;
   {&lt;br /&gt;
&lt;br /&gt;
   var oldMessage = $(&#039;#tokenmessage&#039;).html();&lt;br /&gt;
&lt;br /&gt;
   var indexContact = oldMessage.indexOf(&#039;Bitte kontaktieren&#039;);&lt;br /&gt;
&lt;br /&gt;
   var newMessage = oldMessage.substr(0, indexContact);&lt;br /&gt;
&lt;br /&gt;
   $(&#039;#tokenmessage&#039;).html(newMessage);&lt;br /&gt;
&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will probably not work for an englisch survey and have to be extended when using for multilingual surveys. But it&#039;s an idea/tip how to solve this.&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3377</id>
		<title>Theme editor</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3377"/>
		<updated>2012-01-11T08:41:02Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{maketoc title=&amp;quot;Contents:&amp;quot;}&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has a basic template and style system providing a theme-like capability found in many browser-based applications.  They are simply termed &#039;&#039;&#039;Templates&#039;&#039;&#039; here.  The Templates allow control over the look and feel of pages during a survey.  A survey administrator can select the template to use for each survey to thus personalize that survey&#039;s look and feel.  Changes to a Template can be as simple as adding a unique logo on the welcome page, changing background colors, or maybe new text colors for specific types of questions.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey comes with a set of templates right out of the box. These initial templates are defined by directories within the LimeSurvey installation &amp;quot;templates&amp;quot; directory.  Each template has it&#039;s own directory.  Within the main directory of a template are numerous files: &#039;&#039;&#039;templates (.pstpl)&#039;&#039;&#039;, &#039;&#039;&#039;cascading style sheets (.css)&#039;&#039;&#039;, &#039;&#039;&#039;images&#039;&#039;&#039; (&#039;&#039;&#039;.jpg&#039;&#039;&#039; or &#039;&#039;&#039;.png&#039;&#039;&#039;) and maybe others.&lt;br /&gt;
&lt;br /&gt;
Like in other theme-based systems, fragments of HTML code are stored in the .pstpl template files.  These fragments are read in and used to construct the page to display to the end user during the operation of a survey. Often &#039;&#039;&#039;keywords&#039;&#039;&#039; surrounded by curly braces are included in the files that are then replaced with the relevant text.  The following gives an example of a template file content and its result when used in a survey page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&amp;lt;font face=&#039;verdana&#039; color=&#039;red&#039;&amp;gt;{SURVEYNAME}&amp;lt;/font&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font face=&#039;verdana&#039; color=&#039;blue&#039;&amp;gt;&amp;lt;u&amp;gt;{SURVEYDESCRIPTION}&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One gets a result that looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&#039;color:red&#039;&amp;gt;My New Survey&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;u&amp;gt;&amp;lt;span style=&#039;color:#0000ff&#039;&amp;gt;This is a survey written by me to find out what sort of chocolate people like.&amp;lt;/span&amp;gt;&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Templates, being HTML code, tend to define the positioning and type of text to be displayed and similar structural features of the page.  They often reference or include other files.  Most reference a common cascading style sheets (CSS) file that defines the font style, color, size, background and similar parameters common to all pages in the survey. Style sheets reference HTML &#039;&#039;&#039;class&#039;&#039;&#039; parameters that are associated with the various types of objects in the HTML code.  This allows the style sheet to describe once how to display each of the many types of text or other objects that may appear in multiple places.  There are unique classes for each question type in LimeSurvey and thus giving detailed control over the appearance of each.  Image files, like logos or special progress-bar constructors, may be referenced as well in the Template file.  Finally, special Keywords in curly braces are replaced with text defined in the Survey for each of its corresponding language translations (for example, the Survey Title or Question Text for each language defined).&lt;br /&gt;
&lt;br /&gt;
If you create a new custom template, please consider contributing it back to the LimeSurvey community, and make it available to others. With your help, we can grow our repository of templates, surveys, and other ad-ons, to make LimeSurvey even better! See the shared [http://www.limesurvey.org/component/remository/lang,en-gb/ Template Repository]&lt;br /&gt;
&lt;br /&gt;
=Creating a new Template=&lt;br /&gt;
&lt;br /&gt;
To be able to create a new template (or edit an existing template), you need Template Editing user permission in LimeSurvey as well as permission to manipulate the files in the underlying operating system hosting your LimeSurvey installation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note of Warning:&#039;&#039;&#039; As template changes can affect all surveys in an installation, changes should be limited to those skilled in understanding general concepts in the code base. Templates are an advanced feature that can take some experimentation to get correct if you are not familiar with HTML code methods.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The preferred way to create a new template is through the Template Editor (see below) via the web Admin interface. Some people may like to work directly with template files so that they can use their favorite text editor instead of the web interface. In this case, still use the Template Editor to first create your new template. This will create a new base template with all the files you need in the LimeSurvey_web_root/upload/templates/your_new_template directory. From there you can use your text editor to manually adjust the template files.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Permissions Note:&#039;&#039;&#039; on unix/linux systems, these template files will be owned by the group and user who the web server is running as (may be &amp;quot;www&amp;quot; for some systems). So make sure you have access to edit these files, and when you save them make sure they don&#039;t change ownership, so you can still use the web Template Editing interface if needed&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Template files may seem complex to understand at first. You have to likely understand HTML code, possibly Styles and Style Sheets, and have access to the underlying LimeSurvey installation files if the template files and directories are not editable. Copy an existing template to a new directory to play around with the content. This may help make the concept clearer.&lt;br /&gt;
&lt;br /&gt;
A number of the &#039;public&#039; elements of LimeSurvey can be adjusted by a series of templates. This section provides a very brief explanation of these templates, however more detailed information - especially regarding the editing/creation of new templates is available under [[Templates + Styles]].&lt;br /&gt;
&lt;br /&gt;
=The LimeSurvey Template Editor=&lt;br /&gt;
&lt;br /&gt;
To ease the understanding and quick update of a Template, LimeSurvey provides a &#039;&#039;&#039;Template Editor&#039;&#039;&#039; in the main &#039;&#039;&#039;administrative&#039;&#039;&#039; toolbar of the application.  This Template Editor is only available to users given the privilege in the User Security settings.  A template effects all surveys and can render a survey inoperable if not constructed properly.  So Template editing is thought best restricted to a very limited, knowledgeable set of users.  Having permission to enter the Template Editor is not enough though.&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey Template Editor allows you to edit the contents of your templates online. Start the Template Editor by clicking on the &amp;quot;Template Editor&amp;quot; icon [[File:templates.png]] in the LimeSurvey Administration toolbar (Templates). The main screen is similar to the LimeSurvey Survey Administration screen. It allows you to select the template to edit/view. Once this has been selected you can then select from one of the different public survey pages. You are then presented with a list of the template files that make up that particular page.&lt;br /&gt;
&lt;br /&gt;
==The Template Menu==&lt;br /&gt;
*&#039;&#039;&#039;Edit Icon:&#039;&#039;&#039; The &amp;quot;edit&amp;quot; icon indicates whether or not the template is editable. A blurred out icon indicates that the template is read only; a clickable icon indicates you may make modifications. To change the icon from blurred to clear, you have to modify the template&#039;s permissions.&lt;br /&gt;
*&#039;&#039;&#039;Rename this template:&#039;&#039;&#039; Allows you to change the name of the template.  Generally used after copying an existing template or importing a template by manipulating the underlying directories.&lt;br /&gt;
*&#039;&#039;&#039;Export Template:&#039;&#039;&#039; Allows you to export the current template to a .zip-File.&lt;br /&gt;
*&#039;&#039;&#039;Copy Template:&#039;&#039;&#039; Allows you to make a new template by copying the current one.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Screen&amp;quot; drop-down list on the right allows you to choose which particular survey page you are currently looking at.&lt;br /&gt;
&lt;br /&gt;
==Import/Export/Copy a Template==&lt;br /&gt;
&lt;br /&gt;
When you &#039;&#039;&#039;export &#039;&#039;&#039;a template, this will create a zip-file archive with all the files your template consists of (.pstpl files, images, css files, ...). You can simply &#039;&#039;&#039;import &#039;&#039;&#039;the exported zip-file at other Limesurvey systems by using the import feature or you can manually copy the archive to another installation and extract it into the corresponding template directory there. If you copy the template in the same installation, you will need to rename the folder to create another named copy of that template.&lt;br /&gt;
&lt;br /&gt;
If the file and directory permissions are open for the LimeSurvey application to write, then you can use the programs &#039;&#039;&#039;copy &#039;&#039;&#039;and rename features to make a local copy of a template.&lt;br /&gt;
&lt;br /&gt;
==Page Structure / Template Use==&lt;br /&gt;
*&#039;&#039;&#039;The Welcome Page:&#039;&#039;&#039; startpage.pstpl, welcome.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Questions Pages:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, startgroup.pstpl, groupdescription.pstpl, question.pstpl, endgroup.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Submit Page:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, submit.pstpl, (privacy.pstpl), navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Final Page:&#039;&#039;&#039; startpage.pstpl, completed.pstpl, endpage.pstpl&lt;br /&gt;
&lt;br /&gt;
==Template Files==&lt;br /&gt;
&lt;br /&gt;
The following template files are used to produce your public survey and must exist in any new template folder you create:&lt;br /&gt;
*&#039;&#039;&#039;startpage.pstpl:&#039;&#039;&#039; Produces the start of each html page. It starts at the &amp;quot;&amp;lt;head&amp;gt;&amp;quot; tag, and should not contain the &amp;quot;&amp;lt;html&amp;gt;&amp;quot; tag. This &#039;very beginning&#039; of a standard html page is written by the scripts. Please ensure that your startpage.pstpl files contains a &amp;lt;body&amp;gt; tag, even though many browsers do not require strict adherence to the W3 HTML stanards, the LimeSurvey script needs to find a &amp;lt;body&amp;gt; tag, to run certain javascript elements. It is not expected that many &#039;keywords&#039; will be used in the startpage.pstpl file, however you may wish to put the {SURVEYNAME} into the title. The startpage.pstpl file can contain code that ends in the corresponding endpage.pstpl file, so you can start a table in this file and close the table in the endpage.pstpl file. The startpage.pstpl and endpage.pstpl files wrap around every possible page used by LimeSurvey.&lt;br /&gt;
*&#039;&#039;&#039;survey.pstpl:&#039;&#039;&#039; This template is the second used on most pages, and provides a space to put the survey name and description. This template does not have a corresponding &#039;closing&#039; template, and subsequently you should close all tags opened in this template file (ie: don&#039;t leave a table open here because there is nowhere else to close it)&lt;br /&gt;
*&#039;&#039;&#039;welcome.pstpl:&#039;&#039;&#039; This template is only used in the welcome screen (which is also on the main page for &#039;all in one&#039; surveys). You can use this to print out the welcome text, and other information that should be provided in the introduction. Like the &#039;survey.pstpl&#039; file, there is no corresponding &#039;closing&#039; template, so all tags opened in this template file should be closed as well.&lt;br /&gt;
*&#039;&#039;&#039;startgroup.pstpl:&#039;&#039;&#039; This template can provide a &#039;summary&#039; wrap around for questions within a group. It has a matching &#039;endgroup.pstpl&#039; template that can be used to close any opened tags in this file, so you can open a table within this.&lt;br /&gt;
*&#039;&#039;&#039;groupdescription.pstpl:&#039;&#039;&#039; This template file is used to display a description of a group. It is separate to the startgroup.pstpl file because in a &amp;quot;question by question&amp;quot; survey it will be displayed on its own unique page in between groups, whereas in a &amp;quot;group by group&amp;quot; or &amp;quot;all in one&amp;quot; survey it provides a header to the subsequent questions. groupdescription.pstpl does not have a corresponding &#039;closing&#039; template file, so all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question.pstpl:&#039;&#039;&#039; This file contains the question, answer and help text sections of your survey, and in the &amp;quot;group by group&amp;quot; and &amp;quot;all in one&amp;quot; surveys this template is cycled repeatedly with each question. There is no corresponding closing file for this and all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question_start.pstpl:&#039;&#039;&#039; This file contains the individual elements found at the start of a question. It is included within &#039;question.pstpl&#039; via the {QUESTION} keyword. It is intended to allow template designers more control over the layout of a question. This template sits outside the normal templating system and &#039;&#039;&#039;was superseeded (as of LS1.87)&#039;&#039;&#039;. All keywords from this template are now available directly in question.pstpl. NOTE: templates using question_start.pstpl will still work at least for a couple more versions of LS 1.x&lt;br /&gt;
*&#039;&#039;&#039;submit.pstpl (and privacy.pstpl):&#039;&#039;&#039; This page is the penultimate page for all types of survey (except the &amp;quot;all in one&amp;quot; type) where the participant is given an option to review questions before submitting their responses. It provides privacy information where a survey is anonymous, which it extracts from the &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039; file.&lt;br /&gt;
*&#039;&#039;&#039;completed.pstpl:&#039;&#039;&#039; This page is displayed as the final page when the survey responses have been saved and the survey is over. It can be used to display a &amp;quot;forwarding link&amp;quot; as set in the survey setup.&lt;br /&gt;
*&#039;&#039;&#039;endgroup.pstpl:&#039;&#039;&#039; This file closes the group, and can be used to close off any tags opened in the startgroup.pstpl file&lt;br /&gt;
*&#039;&#039;&#039;navigator.pstpl:&#039;&#039;&#039; This file contains the buttons that navigate through the survey, &amp;quot;next&amp;quot;, &amp;quot;prev&amp;quot;, &amp;quot;last&amp;quot;, &amp;quot;submit&amp;quot;, &amp;quot;save so far&amp;quot;  and the &amp;quot;clear all&amp;quot; link. It is used in all pages except the completed page.&lt;br /&gt;
*&#039;&#039;&#039;printanswers.pstpl:&#039;&#039;&#039; This file has the HTML wrapper for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_group.pstpl:&#039;&#039;&#039; This file is the same as startgroup.pstpl endgroup.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_question.pstpl:&#039;&#039;&#039; This file is the same as question.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_survey.pstpl:&#039;&#039;&#039; This file is the same as survey.pstpl but for the print version of the survey.&lt;br /&gt;
&lt;br /&gt;
==Other Template Files==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;invitationemail.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;reminderemail.pstpl&#039;&#039;&#039; and &#039;&#039;&#039;confirmationemail.pstpl&#039;&#039;&#039; are no longer used by LimeSurvey and defaults are instead set in the applicable language files. The email messages can now be edited on a survey by survey basis.&lt;br /&gt;
&lt;br /&gt;
==Standard Pages==&lt;br /&gt;
&lt;br /&gt;
There are ten standard pages that a survey participant may see in the course of taking or accessing the LimeSurvey application.  Each is constructed from a number of common &#039;&#039;&#039;Template&#039;&#039;&#039; files from the &#039;&#039;&#039;Template&#039;&#039;&#039; specified in the survey&#039;s settings.  The table below indicates which template files are used in constructing each of these pages.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|  &#039;&#039;&#039;Survey Pages:&#039;&#039;&#039;&amp;lt;br/&amp;gt;&#039;&#039;&#039;Template Files&#039;&#039;&#039;||Survey&amp;lt;br/&amp;gt;List||Welcome||Question||Completed||Clear All||Register||Load||Save||Print&amp;lt;br/&amp;gt;Answers||Print&amp;lt;br/&amp;gt;Survey&lt;br /&gt;
|-&lt;br /&gt;
|SurveyList|| [[File:check.gif]]|| || || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Welcome|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Privacy|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Navigator|| || [[File:check.gif]]|| [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Survey|| || || [[File:check.gif]]|| || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|StartGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|GroupDescription|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Question&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|EndGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Assessment|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Completed|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|ClearAll|| || || || || [[File:check.gif]]|| || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Register|| || || || || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Load|| || || || || || || [[File:check.gif]]|| || ||&lt;br /&gt;
|-&lt;br /&gt;
|Save|| || || || || || || || [[File:check.gif]]|| ||&lt;br /&gt;
|-&lt;br /&gt;
|PrintAnswers|| || || || || || || || || [[File:check.gif]]||&lt;br /&gt;
|-&lt;br /&gt;
|Print Survey || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Group || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Question || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|StartPage&amp;lt;br/&amp;gt;EndPage&amp;lt;br/&amp;gt;Template.css|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;NOTE: In versions 1.90 and up this replaces question.pstpl AND question_start.pstpl. If you are using an old custom template, you need to add the following line to the beginning of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div {QUESTION_ESSENTIALS} class=&amp;quot;{QUESTION_CLASS}{QUESTION_MAN_CLASS}{QUESTION_INPUT_ERROR_CLASS}&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;And then add the corresponding closing tag to the end of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The File Control Section==&lt;br /&gt;
&lt;br /&gt;
In the &amp;quot;file control&amp;quot; window on the left, you can click on one of the template files that is used to compile the page. The HTML code for that file will then appear in the &amp;quot;Now editing&amp;quot; window in the center. If the template is editable (determined by directory permissions) you can then make any changes and save them.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Other Files&amp;quot; window shows a list of all other files in the template directory. You can use the right side to &#039;&#039;&#039;upload and select image files (your pics, logos,...) or other files needed to create your template&#039;&#039;&#039;. Note: Instead of a link directly to each picture in your template you can use the field string {TEMPLATEURL}.  So instead of:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;/limesurvey/templates/yourtemplate/mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt; You can use:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;{TEMPLATEURL}mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A &amp;quot;sample&amp;quot; of the template page you are editing will be visible at the bottom of the screen. There is no way to to delete a template from the template editor. This must be done by accessing the underlying directory and deleting the file there.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; The shipped templates cannot be edited using the Template Editor and should never be changed. If you want to modify them, create a copy first and modify the copy.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Location of template files==&lt;br /&gt;
&lt;br /&gt;
LimeSurvey stores each of the &#039;standard&#039; templates in their own distinct sub-directory within the /templates directory that is kept in the public directory with the other LimeSurvey public files. Customized user templates are stored in the /upload/templates directory.&lt;br /&gt;
&lt;br /&gt;
To create a new template, use the according icon in the template editor.&lt;br /&gt;
&lt;br /&gt;
There should ALWAYS be a &amp;quot;default&amp;quot; directory in the templates directory. This template is used by default and as a fall-back if a template folder doesn&#039;t exist, or can&#039;t be found. The &amp;quot;default&amp;quot; directory comes with the package.&lt;br /&gt;
&lt;br /&gt;
You can use any image files that you upload into the template management area with syntax like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;{TEMPLATEURL}filename.xyz&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Styling questions with CSS=&lt;br /&gt;
&lt;br /&gt;
Styling of questions in CSS has become much easier. Each question type now has a unique class. Mandatory question&#039;s also have an additional mandatory class. For example, for a non-mandatory question:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory but the user didn&#039;t answer it or if there is validation on a question&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question has validation applied but the user hasn&#039;t answered correctly&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question6&amp;quot; class=&amp;quot;text-short input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The full list of question classes==&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;Question Type&#039;&#039;&#039;||&#039;&#039;&#039;Question Class&#039;&#039;&#039;||&#039;&#039;&#039;Question ID&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|5 point choice||.choice-5-pt-radio||5&lt;br /&gt;
|-&lt;br /&gt;
|Array (10 point choice)||.array-10-pt||B&lt;br /&gt;
|-&lt;br /&gt;
|Array (5 point choice)||.array-5-pt||A&lt;br /&gt;
|-&lt;br /&gt;
|Array (Flexible Labels) dual scale||.array-flexible-duel-scale ||1&lt;br /&gt;
|-&lt;br /&gt;
|Array (Increase, Same, Decrease)||.array-increase-same-decrease||E&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Numbers)||.array-multi-flexi ||:&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Text)||.array-multi-flexi-text||;&lt;br /&gt;
|-&lt;br /&gt;
|Array (Yes/No/Uncertain)||.array-yes-uncertain-no||C&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels)||.array-flexible-row ||F&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels) by column||.array-flexible-column||H&lt;br /&gt;
|-&lt;br /&gt;
|Boilerplate question||.boilerplate||X&lt;br /&gt;
|-&lt;br /&gt;
|Date||.date||D&lt;br /&gt;
|-&lt;br /&gt;
|Gender||.gender||G&lt;br /&gt;
|-&lt;br /&gt;
|Huge free text||.text-huge||U&lt;br /&gt;
|-&lt;br /&gt;
|Language switch||.language||I&lt;br /&gt;
|-&lt;br /&gt;
|List (dropdown)||.list-dropdown||!&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (dropdown)||.list-dropdown-flexible||W&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (radio)||.list-radio-flexible||Z&lt;br /&gt;
|-&lt;br /&gt;
|List (radio)||.list-radio||L&lt;br /&gt;
|-&lt;br /&gt;
|List with comment||.list-with-comment||O&lt;br /&gt;
|-&lt;br /&gt;
|Long free text||.text-long||T&lt;br /&gt;
|-&lt;br /&gt;
|Multiple numerical input||.numeric-multi||K&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options||.multiple-opt||M&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options with comments||.multiple-opt-comments||P&lt;br /&gt;
|-&lt;br /&gt;
|Multiple short text||.multiple-short-txt||Q&lt;br /&gt;
|-&lt;br /&gt;
|Numerical input||.numeric||N&lt;br /&gt;
|-&lt;br /&gt;
|Ranking||.ranking||R&lt;br /&gt;
|-&lt;br /&gt;
|Short free text||.text-short||S&lt;br /&gt;
|-&lt;br /&gt;
|Yes/No||.yes-no||Y&lt;br /&gt;
|-&lt;br /&gt;
|Mandatory||.mandatory||&lt;br /&gt;
|-&lt;br /&gt;
|User input error||.input_error|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Importing styles into your custom template==&lt;br /&gt;
&lt;br /&gt;
The custom question styles are near the bottom of each template&#039;s CSS file and start with:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;/* &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;----&lt;br /&gt;
&lt;br /&gt;
  START: Question styles  &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt; */&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you&#039;re styling your own custom template, You should be able to copy everything after the above from templates/default/template.css (for tables based layouts) or /templates/limespired/template.css (for CSS based layouts) into your own style sheet without any impact on your other styles.&lt;br /&gt;
&lt;br /&gt;
==Internet Explorer conditional style sheets==&lt;br /&gt;
&lt;br /&gt;
Because of the marked discrepancies in rendering between IE6, IE7 and most other browsers, there are special IE conditional style sheets included for each template.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;You should include the above code within your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; and copies of both the IE style sheets from either /templates/default/ or /templates/limespired for Tables base layout and CSS based layout respectively.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; If you copy the styles into your own style sheet you will almost certainly need to tweak them.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Right-to-Left (RTL) Languages and justify==&lt;br /&gt;
&lt;br /&gt;
The text editor within LimeSurvey is able to format RTL Text. However, the editor itself shows the RTL language in a left to right format when justified.  This is just an editor display issue. The RTL and justified question or text will display correctly from right to left, even when justified, in your survey or on preview.&lt;br /&gt;
&lt;br /&gt;
==Keywords==&lt;br /&gt;
&lt;br /&gt;
Keywords within a template file get replaced by the current survey information. They are surrounded by curly brackets, for example: {SURVEYNAME}&lt;br /&gt;
&lt;br /&gt;
The following strings will be replaced by LimeSurvey when parsing the template file and presenting it to survey users. These field strings will work on almost every template except for the &#039;Completed Page&#039;. (Most of these strings can be found in the common.php file. If it&#039;s not there, look in the index.php file.)&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;::KEYWORD::&#039;&#039;&#039;|| &#039;&#039;&#039;TEMPLATE FILES::&#039;&#039;&#039; || &#039;&#039;&#039;::DESCRIPTION::&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYNAME}||All Files||The survey title&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYDESCRIPTION}||All Files||The survey description&lt;br /&gt;
|-&lt;br /&gt;
|{WELCOME}||All files (mainly for welcome.pstpl)||The survey &#039;welcome&#039; text&lt;br /&gt;
|-&lt;br /&gt;
|{PERCENTCOMPLETE}||survey.pstpl||A small graph showing the percentage of the survey completed&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPNAME}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group name&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPDESCRIPTION}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group description&lt;br /&gt;
|-&lt;br /&gt;
|{NUMBEROFQUESTIONS}||welcome.pstpl||Displays the total number of questions in the survey (just the number)&lt;br /&gt;
|-&lt;br /&gt;
|{THEREAREXQUESTIONS}||welcome.pstpl||Displays the sentence &amp;quot;There are X questions in this survey&amp;quot; - from the relevant language file. The X is replaced with the number of questions. Note that this will also work appropriately for singular or plural. If there is only 1 question, it will print &amp;quot;There is 1 question in this survey&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|{CHECKJAVASCRIPT}||All files (mainly for welcome.pstpl)||Warning message when end-user browser have javascript disabled&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION}||Question.pstpl||(&#039;&#039;&#039;Has been superseeded but the {QUESTION_...} keywords as of LS1.87&#039;&#039;&#039;) Displays the current question text (The format of {QUESTION} can customised by editing &#039;question_start.pstpl&#039;) Use the following: {QUESTION_TEXT}, {QUESTION_MANDATORY}, {QUESTION_HELP}, {QUESTION_MAN_MESSAGE}, {QUESTION_VALID_MESSAGE} and {QUESTION_INPUT_ERROR_CLASS} and appropriate wrapping HTML instead of {QUESTION})&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWER}||question.pstpl, print_question.pstpl||presents the answer form for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{SGQ}||question.pstpl, question text||Can be used in the question text itself, to reference the input field of the question dynamically by displaying the Survey-Group-Question id for the current question. (as of svn build 9755)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTIONHELP}||question.pstpl, print_question.pstpl||Displays help text for the current questionm for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CLASS}||question.pstpl, print_question.pstpl||unique class for each question type. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CODE}||question.pstpl, print_question.pstpl||Displays the current question code&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ESSENTIALS}||question.pstpl||the question ID and (if a question is conditional), &#039;style=&amp;quot;display:none;&amp;quot;&#039;. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_HELP}||question.pstp, question_start.pstpl||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TYPE_HELP}||print_question.pstp||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_INPUT_ERROR_CLASS}||question.pstp, question_start.pstpl||Provides a class if there was user input error&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ID}||print_question.pstp||Provides a unique ID for each question to allow styling for specific questions&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TEXT}||question.pstp, print_question.pstp, question_start.pstpl||Displays the text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MANDATORY}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_CLASS}||question.pstpl, print_question.pstpl||class if a question is mandatory. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_NUMBER}||print_question.pstpl||Incremental count of questions.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_VALID_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated valid help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_SCENARIO}||print_question.pstp||Prints out the &#039;scenario&#039; text for conditional questions.&lt;br /&gt;
|-&lt;br /&gt;
|{NAVIGATOR}||navigator.pstpl||Displays navigation buttons (next, prev, last)&lt;br /&gt;
|-&lt;br /&gt;
|{CLEARALL}||All files (but intended for navigator.pstpl)||Displays the &amp;quot;Exit and Clear Results&amp;quot; link&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITBUTTON}||submit.pstpl||Displays the final submit button&lt;br /&gt;
|-&lt;br /&gt;
|{COMPLETED}||completed.pstpl||Displays the &#039;completed&#039; messagem for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{url}||completed.pstpl||Displays the survey &#039;url&#039; and &#039;url text&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACY}||submit.pstpl||Displays privacy information when survey is anonymous&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACYMESSAGE}||privacy.pstpl||The privacy message is shown if you set your survey to be anonymous. [http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+1.x+Translating+LimeSurvey The text can be edited/translated] in the language files. This can also be changed manually by editing the privacy.pstpl template you wish to use.&lt;br /&gt;
|-&lt;br /&gt;
|{TEMPLATEURL}||All Files||The URL to the current template location (useful for referencing image files in your template)&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITCOMPLETE}||endpage.pstpl||The statement (from the language files) that tells the user they have completed the survey, and to press the &amp;quot;Submit&amp;quot; button&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITREVIEW}||survey.pstpl||The statement (from the language files) that tells the user they can review/change the answers they have made by clicking &amp;quot;&amp;lt;&amp;lt; prev&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:FIRSTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users first name from the tokens table&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:LASTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users last name from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:EMAIL}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users email from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_1}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_1 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_2}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_2 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWERSCLEARED}||Preferably in navigator.pstpl||The &amp;quot;Answers Cleared&amp;quot; statement from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{RESTART}||clearall.pstpl||URL to restart the survey&lt;br /&gt;
|-&lt;br /&gt;
|{CLOSEWINDOW}||All Files (Preferably in navigator.pstpl)||URL to close current window&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERERROR}||register.pstpl||Shows any error messages in the register page (ie: &amp;quot;You must include an email address&amp;quot;)&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE1}||register.pstpl||The statement &amp;quot;You must be registered to complete this survey&amp;quot; from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE2}||register.pstpl||Details about registering from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERFORM}||register.pstpl||The actual form for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{SAVE}||Works suitable on navigator.pstpl||Displays the &#039;Save your responses so far&#039; button to offer the user to save and come back later to continue the survey. If the Save option is deactivated in the survey properties the tag will not be shown and ignored.&lt;br /&gt;
|-&lt;br /&gt;
|{LANGUAGECHANGER}||survey.pstpl||Displays a switch in multilingual surveys to change the question.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Input/Buttons==&lt;br /&gt;
&lt;br /&gt;
Each &amp;quot;input&amp;quot; type in a survey has been given its own class name, so that you can add CSS to your &amp;quot;startpage.pstpl&amp;quot; file, and have some control over the appearance of form buttons and inputs. These class names are as follows:&lt;br /&gt;
*&#039;&#039;&#039;submit&#039;&#039;&#039; (Submit Buttons)&lt;br /&gt;
*&#039;&#039;&#039;text&#039;&#039;&#039; (Text Inputs - for short free text, date and numerical type)&lt;br /&gt;
*&#039;&#039;&#039;answertext&#039;&#039;&#039; (Text of answers)&lt;br /&gt;
*&#039;&#039;&#039;radio&#039;&#039;&#039; (Radio Buttons)&lt;br /&gt;
*&#039;&#039;&#039;checkbox&#039;&#039;&#039; (Check Boxes)&lt;br /&gt;
*&#039;&#039;&#039;select&#039;&#039;&#039; (Select / List Boxes)&lt;br /&gt;
*&#039;&#039;&#039;textarea&#039;&#039;&#039; (Large text inputs - for long free text)&lt;br /&gt;
*&#039;&#039;&#039;clearall&#039;&#039;&#039; (The &amp;quot;Exit and Clear Survey&amp;quot; link)&lt;br /&gt;
*&#039;&#039;&#039;rank&#039;&#039;&#039; (The rank style question. Doesn&#039;t set the colour of the select box or the text boxes (these are set by relevant section above) but does allow changing of background colour, text colour and size etc for the rest of the ranking question)&lt;br /&gt;
*&#039;&#039;&#039;graph&#039;&#039;&#039; (The &amp;quot;percentage completed&amp;quot; graph table)&lt;br /&gt;
*&#039;&#039;&#039;innergraph&#039;&#039;&#039; (The table inside the graph table - this contains the 0% and 100% text. Use this for changing the size of this text&lt;br /&gt;
*&#039;&#039;&#039;question&#039;&#039;&#039; (General settings for any question that is displayed within a table. Generally you should use this to make sure that their font size and colour is the same as you have used elsewhere as a default)&lt;br /&gt;
*&#039;&#039;&#039;mandatory&#039;&#039;&#039;  (Mandatory questions)&lt;br /&gt;
*&#039;&#039;&#039;input_error&#039;&#039;&#039; (User input error - for if a user has made a mistake with a mandatory question or question with validation)&lt;br /&gt;
*&#039;&#039;&#039;array1&#039;&#039;&#039; and &#039;&#039;&#039;array2&#039;&#039;&#039; (These two styles are cycled when presenting the range of answers for an array type question. This allows you to set an alternating background colour for these question types. &#039;&#039;&#039;Array1&#039;&#039;&#039; is also used for the column headings in these question types)&lt;br /&gt;
*&#039;&#039;&#039;errormandatory&#039;&#039;&#039; (Sets the colour and style of the &amp;quot;This question is mandatory&amp;quot; error message)&lt;br /&gt;
*&#039;&#039;&#039;warningjs&#039;&#039;&#039; (Sets the colour and style of the warning message displayed if the participant&#039;s browser has javascript disabled)&lt;br /&gt;
&lt;br /&gt;
An example of using these classes with style sheets can be found in the &amp;quot;bubblegum&amp;quot; template that comes with the LimeSurvey application.&lt;br /&gt;
&lt;br /&gt;
Because you can edit all the HTML aspects, there&#039;s no reason to surround your templates with a &amp;lt;div class=&#039;new_name&#039;&amp;gt; and then define a css for that new_name class.&lt;br /&gt;
&lt;br /&gt;
==Styling the progress bar==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before version 1.87:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The chart.jpg file is a simple one pixel image file which is used to create the progress bar image in the &#039;PERCENTCOMPLETE&#039; table. If the file does not exist, LimeSurvey will use the default &#039;maroon&#039; coloured image in the public directory. If you want to create a bar to match your own colour scheme, then you should save the color in this file. Remember it should be a &#039;&#039;&#039;JPEG&#039;&#039;&#039; file, 1 pixel x 1 pixel, in the colour desired.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The progress bar appearance can be modified with CSS.&lt;br /&gt;
&lt;br /&gt;
To change the background colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 background-color: #3300FF;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To change the border colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-content,&lt;br /&gt;
#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 border: 1px solid #FF0000;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Advanced Features Available to Developers==&lt;br /&gt;
&lt;br /&gt;
Starting with version 0.99, LimeSurvey has integrated some user-made patches that allow for some special changes.  These very advanced features generally require changes to the underlying code base of LimeSurvey and should be done carefully so as not to introduce security holes.&lt;br /&gt;
&lt;br /&gt;
===Basic CMS Integration support===&lt;br /&gt;
&lt;br /&gt;
To be able to integrate LimeSurvey into another CMS, use the following options in &#039;&#039;&#039;config.php&#039;&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
// Set $embedded to true and specify the header and footer functions if the survey is to be displayed embedded in a CMS&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$embedded = false;&lt;br /&gt;
&lt;br /&gt;
$embedded_inc = &amp;quot;&amp;quot;;               // path to the header to include if any&lt;br /&gt;
&lt;br /&gt;
$embedded_headerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteHeader for geeklog&lt;br /&gt;
&lt;br /&gt;
$embedded_footerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteFooter for geeklog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set &#039;&#039;&#039;$embedded = true;&#039;&#039;&#039; to enable CMS-embedding. By using the &#039;&#039;&#039;$embedded_inc&#039;&#039;&#039; variable one can include their own &#039;&#039;&#039;.php&#039;&#039;&#039; files.  By setting &#039;&#039;&#039;$embedded_headerfunc&#039;&#039;&#039; or &#039;&#039;&#039;$embedded_footerfunc&#039;&#039;&#039;, one can call functions from within included files that output the relevant headers or footers instead of LimeSurveys default ones.&lt;br /&gt;
&lt;br /&gt;
===Support for your own Javascript functions===&lt;br /&gt;
&lt;br /&gt;
Some users may need to run Javascript on the survey pages, but calling &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; in the BODY element made it impossible to do so.  This call has been replaced with a small JavaScript function in the HEAD that sniffs for the existence of &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; and &#039;&#039;&#039;template_onload()&#039;&#039;&#039; before calling each.  This way a template author can create their own &#039;&#039;&#039;template_onload()&#039;&#039;&#039; function in the HEAD that replaces the default one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
*Disable XSS filter - in Global settings -&amp;gt; Security, set &amp;quot;Filter HTML for XSS&amp;quot; to No.&lt;br /&gt;
*Enter your script in the source of a question or group description.&lt;br /&gt;
*There are more details in the [http://docs.limesurvey.org/tiki-index.php?page=Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#How_to_use_Script_eg._JavaScript_etc._in_LimeSurvey_ workaround section].&lt;br /&gt;
&lt;br /&gt;
=Videos on Templates=&lt;br /&gt;
&lt;br /&gt;
These videos will demonstrate the basic and advanced template functions that are available to all LimeSurvey users. This includes changing the appearance of certain forms and inserting custom graphics. Additionally, it will thoroughly walk you through on how to edit and preview specific page templates, importing/exporting templates, modify appearance of questions in the CSS, customizing survey description page, and completed page.&lt;br /&gt;
&lt;br /&gt;
Part I&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;nLsfxMjRXyk?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part II&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;yrAXStFH34Q?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part III&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;TYlJXHgt8R0?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part IV&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;Rml0gqeErVc?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part V&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;LX24Ix1ylmY?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part VI&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;-202CqQcW8g?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
=Tips &amp;amp; Tricks=&lt;br /&gt;
&lt;br /&gt;
==Change the layout of the survey page==&lt;br /&gt;
&lt;br /&gt;
When editing a template this template can be assigned to a single survey while the survey list page, which is shown at www.yourdomain.org/limesurveyinstallfolder, lists all your surveys.&lt;br /&gt;
&lt;br /&gt;
To use your current template for this page you have change the according setting at the Global Settings screen; at older versions this change can be done by editing the $defaulttemplate setting at the config file: Copy this setting from config-defaults.php to config.php which overrides config-defaults.php and edit this setting to $defaulttemplate = &#039;yourtemplatename&#039;;&lt;br /&gt;
&lt;br /&gt;
==Import/Export of templates: Mac users==&lt;br /&gt;
&lt;br /&gt;
Mac users, please note: Mac OSX default archive utility may have problems with zip folders &amp;quot;generated on the fly&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
a work around is to unix&#039;es unzip from the command line:&lt;br /&gt;
&lt;br /&gt;
$ unzip template.zip -d template&lt;br /&gt;
&lt;br /&gt;
Archive: template.zip&lt;br /&gt;
&lt;br /&gt;
 inflating: template/startpage&lt;br /&gt;
&lt;br /&gt;
 inflating: ...&lt;br /&gt;
&lt;br /&gt;
or scripts in their mac-compiled counterparts:&lt;br /&gt;
&lt;br /&gt;
http://homepage.mac.com/roger_jolly/software/&lt;br /&gt;
&lt;br /&gt;
==Changing your templates traffic light from red to green==&lt;br /&gt;
&lt;br /&gt;
If you haven&#039;t already, set the admin directory to read/write/execute (777). The files within it, however, may be set to read/execute only (chmod 755).&lt;br /&gt;
&lt;br /&gt;
GO to file directory ie file manager, find templates directory.&lt;br /&gt;
&lt;br /&gt;
1 change permission on eg&amp;quot;vallendar&amp;quot; (or any template of your choice) directory to read 777&lt;br /&gt;
&lt;br /&gt;
2 voila! the red traffic light on &amp;quot;vallendar&amp;quot; is now green.&lt;br /&gt;
&lt;br /&gt;
3 NOTE: to restrict access for safety, when finished editing template files, change all templates files back to what they were eg 644&lt;br /&gt;
&lt;br /&gt;
==Replacing the help icon==&lt;br /&gt;
&lt;br /&gt;
When a question help text is shown then an help.gif image is used from the default template folder.&lt;br /&gt;
&lt;br /&gt;
You can replace this image by uploading a new help.gif, help.png or help.jpg in your custom template folder. It then will be automatically used instead of the default help icon.&lt;br /&gt;
&lt;br /&gt;
==Replacing an existing logo==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Before uploading new logo delete previous one.&lt;br /&gt;
&lt;br /&gt;
1. To edit logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
2. Find and Click Search button, to find place where is logo style text.&lt;br /&gt;
&lt;br /&gt;
[[File:2.PNG]]&lt;br /&gt;
&lt;br /&gt;
3. Find in search &amp;lt;u&amp;gt;#logo&amp;lt;/u&amp;gt; (It is logo design code)&lt;br /&gt;
&lt;br /&gt;
[[File:3.PNG]]&lt;br /&gt;
&lt;br /&gt;
4. Edit style file&lt;br /&gt;
&lt;br /&gt;
You will see something like this code:&lt;br /&gt;
&lt;br /&gt;
[[File:4.PNG]] &lt;br /&gt;
&lt;br /&gt;
If you want change image just replace logo.gif to antoher image link. Like: (&amp;lt;u&amp;gt;logo.png&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.jpg&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.swf&amp;lt;/u&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
If you want change image size just change, width and height (in pixels) like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;Width:100px; Height:100px;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adding your own logo==&lt;br /&gt;
&lt;br /&gt;
1. Find and Open &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; template file.&lt;br /&gt;
&lt;br /&gt;
[[File:5.PNG]] &lt;br /&gt;
&lt;br /&gt;
2. Write in &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; this line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;img id=&amp;amp;rdquo;page_logo&amp;amp;rdquo; src=&amp;amp;rdquo;{TEMPLATEURL}logo.png&amp;amp;rdquo;&amp;gt;&amp;lt;br&amp;gt;&amp;lt;/syntaxhighlight&amp;gt; After &amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;body ... &amp;gt;&amp;lt;/syntaxhighlight&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
[[File:6.PNG]] &lt;br /&gt;
&lt;br /&gt;
3. To add logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
3.1 Go to end of &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo; style file.&lt;br /&gt;
&lt;br /&gt;
3.2 Write in end:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in left side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:left;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in right side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:right;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in center:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   display: block;&lt;br /&gt;
&lt;br /&gt;
   margin-left: auto;&lt;br /&gt;
&lt;br /&gt;
   margin-right: auto;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the default help to all question (hide_tip)==&lt;br /&gt;
&lt;br /&gt;
There are 2 solution to remove the default help, like a [[Advanced question settings|#hide_tip|hide_tip attribute]] but for all question and survey.&lt;br /&gt;
# you can remove the {QUESTIONHELP} and is container from the file question.pstl, but it can be a bad idea for screenreader.&lt;br /&gt;
# for the default template and some other , add this at the end of tempate.css&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;span.questionhelp{display:none;}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display custom favicon==&lt;br /&gt;
&lt;br /&gt;
A favicon is the little icon you see in the browser&#039;s address bar, list of bookmarks or tab. You can display your own icon as follows:&lt;br /&gt;
#Create a favicon - google will find you lots of free favicon generators&lt;br /&gt;
#Name your new favicon &amp;quot;favicon.ico&amp;quot; and place it in your template directory&lt;br /&gt;
#Add the following code to your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; before the &amp;lt;/head&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;link rel=&amp;quot;shortcut icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;link rel=&amp;quot;icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Different appearance for survey-/question-pages==&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;Version 1.91 and newer&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
If you want LimeSurvey to change the appearance of every second page (i.e. of even and odd survey pages) you can use &#039;&#039;&#039;.page-odd&#039;&#039;&#039; class in your css file to change the appearance of odd pages.&lt;br /&gt;
&lt;br /&gt;
example from default template of LimeSurvey 1.91+&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
.page-odd table.question-group {&lt;br /&gt;
&lt;br /&gt;
 background-color: #D2F2D3;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To &#039;&#039;&#039;not&#039;&#039;&#039; differentiate even and odd pages at the (default) template find all instances of &#039;&#039;.page-odd&#039;&#039; in template.css and remove those styles.&lt;br /&gt;
&lt;br /&gt;
==Create a vertical separator  border for dual scale array==&lt;br /&gt;
&lt;br /&gt;
To create a vertical separator border for a dual scale array you can add the following lines to your &#039;&#039;&#039;template.css&#039;&#039;&#039;-file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
table.question thead td.header_separator,&lt;br /&gt;
&lt;br /&gt;
table.question tbody td.dual_scale_separator&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   border-right:solid 1px #00A8E1;&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
header_separator is used to adress the separator for the header &amp;quot;td&amp;quot; and &amp;quot;dual_scale_separator&amp;quot; is used to adress the separator column in the dual scale array.&lt;br /&gt;
&lt;br /&gt;
==Hide the survey contact message shown on the start page/survey list==&lt;br /&gt;
&lt;br /&gt;
To hide the &amp;quot;Please contact ...&amp;quot; meassage on the start page (with the survey list) you can add the following to the &#039;&#039;&#039;$(document).ready&#039;&#039;&#039; function in the &#039;&#039;&#039;template.js&#039;&#039;&#039; of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$(&#039;#surveycontact&#039;).hide(); //Hides the survey contact message&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the survey contact message shown on error messages==&lt;br /&gt;
&lt;br /&gt;
If you want to remove the survey contact message from error messages it&#039;ll be trickier. You can add the following function call to the &#039;&#039;&#039;$(document).ready&#039;&#039;&#039; function in the &#039;&#039;&#039;template.css&#039;&#039;&#039; of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
removeContactAdressFromMessage(); //Removes the survey contact message from error messages&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and add the following function to your *template.js* file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
function removeContactAdressFromMessage()&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
if ($(&#039;#tokenmessage&#039;).length &amp;gt; 0)&lt;br /&gt;
&lt;br /&gt;
   {&lt;br /&gt;
&lt;br /&gt;
   var oldMessage = $(&#039;#tokenmessage&#039;).html();&lt;br /&gt;
&lt;br /&gt;
   var indexContact = oldMessage.indexOf(&#039;Bitte kontaktieren&#039;);&lt;br /&gt;
&lt;br /&gt;
   var newMessage = oldMessage.substr(0, indexContact);&lt;br /&gt;
&lt;br /&gt;
   $(&#039;#tokenmessage&#039;).html(newMessage);&lt;br /&gt;
&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will probably not work for an englisch survey and have to be extended when using for multilingual surveys. But it&#039;s an idea/tip how to solve this.&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3378</id>
		<title>Theme editor</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Theme_editor&amp;diff=3378"/>
		<updated>2012-01-11T08:38:57Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{maketoc title=&amp;quot;Contents:&amp;quot;}&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has a basic template and style system providing a theme-like capability found in many browser-based applications.  They are simply termed &#039;&#039;&#039;Templates&#039;&#039;&#039; here.  The Templates allow control over the look and feel of pages during a survey.  A survey administrator can select the template to use for each survey to thus personalize that survey&#039;s look and feel.  Changes to a Template can be as simple as adding a unique logo on the welcome page, changing background colors, or maybe new text colors for specific types of questions.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey comes with a set of templates right out of the box. These initial templates are defined by directories within the LimeSurvey installation &amp;quot;templates&amp;quot; directory.  Each template has it&#039;s own directory.  Within the main directory of a template are numerous files: &#039;&#039;&#039;templates (.pstpl)&#039;&#039;&#039;, &#039;&#039;&#039;cascading style sheets (.css)&#039;&#039;&#039;, &#039;&#039;&#039;images&#039;&#039;&#039; (&#039;&#039;&#039;.jpg&#039;&#039;&#039; or &#039;&#039;&#039;.png&#039;&#039;&#039;) and maybe others.&lt;br /&gt;
&lt;br /&gt;
Like in other theme-based systems, fragments of HTML code are stored in the .pstpl template files.  These fragments are read in and used to construct the page to display to the end user during the operation of a survey. Often &#039;&#039;&#039;keywords&#039;&#039;&#039; surrounded by curly braces are included in the files that are then replaced with the relevant text.  The following gives an example of a template file content and its result when used in a survey page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&amp;lt;font face=&#039;verdana&#039; color=&#039;red&#039;&amp;gt;{SURVEYNAME}&amp;lt;/font&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font face=&#039;verdana&#039; color=&#039;blue&#039;&amp;gt;&amp;lt;u&amp;gt;{SURVEYDESCRIPTION}&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One gets a result that looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&amp;lt;center&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&#039;color:red&#039;&amp;gt;My New Survey&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&amp;lt;u&amp;gt;&amp;lt;span style=&#039;color:#0000ff&#039;&amp;gt;This is a survey written by me to find out what sort of chocolate people like.&amp;lt;/span&amp;gt;&amp;lt;/u&amp;gt;&amp;lt;/center&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Templates, being HTML code, tend to define the positioning and type of text to be displayed and similar structural features of the page.  They often reference or include other files.  Most reference a common cascading style sheets (CSS) file that defines the font style, color, size, background and similar parameters common to all pages in the survey. Style sheets reference HTML &#039;&#039;&#039;class&#039;&#039;&#039; parameters that are associated with the various types of objects in the HTML code.  This allows the style sheet to describe once how to display each of the many types of text or other objects that may appear in multiple places.  There are unique classes for each question type in LimeSurvey and thus giving detailed control over the appearance of each.  Image files, like logos or special progress-bar constructors, may be referenced as well in the Template file.  Finally, special Keywords in curly braces are replaced with text defined in the Survey for each of its corresponding language translations (for example, the Survey Title or Question Text for each language defined).&lt;br /&gt;
&lt;br /&gt;
If you create a new custom template, please consider contributing it back to the LimeSurvey community, and make it available to others. With your help, we can grow our repository of templates, surveys, and other ad-ons, to make LimeSurvey even better! See the shared [http://www.limesurvey.org/component/remository/lang,en-gb/ Template Repository]&lt;br /&gt;
&lt;br /&gt;
=Creating a new Template=&lt;br /&gt;
&lt;br /&gt;
To be able to create a new template (or edit an existing template), you need Template Editing user permission in LimeSurvey as well as permission to manipulate the files in the underlying operating system hosting your LimeSurvey installation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note of Warning:&#039;&#039;&#039; As template changes can affect all surveys in an installation, changes should be limited to those skilled in understanding general concepts in the code base. Templates are an advanced feature that can take some experimentation to get correct if you are not familiar with HTML code methods.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The preferred way to create a new template is through the Template Editor (see below) via the web Admin interface. Some people may like to work directly with template files so that they can use their favorite text editor instead of the web interface. In this case, still use the Template Editor to first create your new template. This will create a new base template with all the files you need in the LimeSurvey_web_root/upload/templates/your_new_template directory. From there you can use your text editor to manually adjust the template files.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Permissions Note:&#039;&#039;&#039; on unix/linux systems, these template files will be owned by the group and user who the web server is running as (may be &amp;quot;www&amp;quot; for some systems). So make sure you have access to edit these files, and when you save them make sure they don&#039;t change ownership, so you can still use the web Template Editing interface if needed&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Template files may seem complex to understand at first. You have to likely understand HTML code, possibly Styles and Style Sheets, and have access to the underlying LimeSurvey installation files if the template files and directories are not editable. Copy an existing template to a new directory to play around with the content. This may help make the concept clearer.&lt;br /&gt;
&lt;br /&gt;
A number of the &#039;public&#039; elements of LimeSurvey can be adjusted by a series of templates. This section provides a very brief explanation of these templates, however more detailed information - especially regarding the editing/creation of new templates is available under [[Templates + Styles]].&lt;br /&gt;
&lt;br /&gt;
=The LimeSurvey Template Editor=&lt;br /&gt;
&lt;br /&gt;
To ease the understanding and quick update of a Template, LimeSurvey provides a &#039;&#039;&#039;Template Editor&#039;&#039;&#039; in the main &#039;&#039;&#039;administrative&#039;&#039;&#039; toolbar of the application.  This Template Editor is only available to users given the privilege in the User Security settings.  A template effects all surveys and can render a survey inoperable if not constructed properly.  So Template editing is thought best restricted to a very limited, knowledgeable set of users.  Having permission to enter the Template Editor is not enough though.&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey Template Editor allows you to edit the contents of your templates online. Start the Template Editor by clicking on the &amp;quot;Template Editor&amp;quot; icon [[File:templates.png]] in the LimeSurvey Administration toolbar (Templates). The main screen is similar to the LimeSurvey Survey Administration screen. It allows you to select the template to edit/view. Once this has been selected you can then select from one of the different public survey pages. You are then presented with a list of the template files that make up that particular page.&lt;br /&gt;
&lt;br /&gt;
==The Template Menu==&lt;br /&gt;
*&#039;&#039;&#039;Edit Icon:&#039;&#039;&#039; The &amp;quot;edit&amp;quot; icon indicates whether or not the template is editable. A blurred out icon indicates that the template is read only; a clickable icon indicates you may make modifications. To change the icon from blurred to clear, you have to modify the template&#039;s permissions.&lt;br /&gt;
*&#039;&#039;&#039;Rename this template:&#039;&#039;&#039; Allows you to change the name of the template.  Generally used after copying an existing template or importing a template by manipulating the underlying directories.&lt;br /&gt;
*&#039;&#039;&#039;Export Template:&#039;&#039;&#039; Allows you to export the current template to a .zip-File.&lt;br /&gt;
*&#039;&#039;&#039;Copy Template:&#039;&#039;&#039; Allows you to make a new template by copying the current one.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Screen&amp;quot; drop-down list on the right allows you to choose which particular survey page you are currently looking at.&lt;br /&gt;
&lt;br /&gt;
==Import/Export/Copy a Template==&lt;br /&gt;
&lt;br /&gt;
When you &#039;&#039;&#039;export &#039;&#039;&#039;a template, this will create a zip-file archive with all the files your template consists of (.pstpl files, images, css files, ...). You can simply &#039;&#039;&#039;import &#039;&#039;&#039;the exported zip-file at other Limesurvey systems by using the import feature or you can manually copy the archive to another installation and extract it into the corresponding template directory there. If you copy the template in the same installation, you will need to rename the folder to create another named copy of that template.&lt;br /&gt;
&lt;br /&gt;
If the file and directory permissions are open for the LimeSurvey application to write, then you can use the programs &#039;&#039;&#039;copy &#039;&#039;&#039;and rename features to make a local copy of a template.&lt;br /&gt;
&lt;br /&gt;
==Page Structure / Template Use==&lt;br /&gt;
*&#039;&#039;&#039;The Welcome Page:&#039;&#039;&#039; startpage.pstpl, welcome.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Questions Pages:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, startgroup.pstpl, groupdescription.pstpl, question.pstpl, endgroup.pstpl, navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Submit Page:&#039;&#039;&#039; startpage.pstpl, survey.pstpl, submit.pstpl, (privacy.pstpl), navigator.pstpl, endpage.pstpl&lt;br /&gt;
*&#039;&#039;&#039;The Final Page:&#039;&#039;&#039; startpage.pstpl, completed.pstpl, endpage.pstpl&lt;br /&gt;
&lt;br /&gt;
==Template Files==&lt;br /&gt;
&lt;br /&gt;
The following template files are used to produce your public survey and must exist in any new template folder you create:&lt;br /&gt;
*&#039;&#039;&#039;startpage.pstpl:&#039;&#039;&#039; Produces the start of each html page. It starts at the &amp;quot;&amp;lt;head&amp;gt;&amp;quot; tag, and should not contain the &amp;quot;&amp;lt;html&amp;gt;&amp;quot; tag. This &#039;very beginning&#039; of a standard html page is written by the scripts. Please ensure that your startpage.pstpl files contains a &amp;lt;body&amp;gt; tag, even though many browsers do not require strict adherence to the W3 HTML stanards, the LimeSurvey script needs to find a &amp;lt;body&amp;gt; tag, to run certain javascript elements. It is not expected that many &#039;keywords&#039; will be used in the startpage.pstpl file, however you may wish to put the {SURVEYNAME} into the title. The startpage.pstpl file can contain code that ends in the corresponding endpage.pstpl file, so you can start a table in this file and close the table in the endpage.pstpl file. The startpage.pstpl and endpage.pstpl files wrap around every possible page used by LimeSurvey.&lt;br /&gt;
*&#039;&#039;&#039;survey.pstpl:&#039;&#039;&#039; This template is the second used on most pages, and provides a space to put the survey name and description. This template does not have a corresponding &#039;closing&#039; template, and subsequently you should close all tags opened in this template file (ie: don&#039;t leave a table open here because there is nowhere else to close it)&lt;br /&gt;
*&#039;&#039;&#039;welcome.pstpl:&#039;&#039;&#039; This template is only used in the welcome screen (which is also on the main page for &#039;all in one&#039; surveys). You can use this to print out the welcome text, and other information that should be provided in the introduction. Like the &#039;survey.pstpl&#039; file, there is no corresponding &#039;closing&#039; template, so all tags opened in this template file should be closed as well.&lt;br /&gt;
*&#039;&#039;&#039;startgroup.pstpl:&#039;&#039;&#039; This template can provide a &#039;summary&#039; wrap around for questions within a group. It has a matching &#039;endgroup.pstpl&#039; template that can be used to close any opened tags in this file, so you can open a table within this.&lt;br /&gt;
*&#039;&#039;&#039;groupdescription.pstpl:&#039;&#039;&#039; This template file is used to display a description of a group. It is separate to the startgroup.pstpl file because in a &amp;quot;question by question&amp;quot; survey it will be displayed on its own unique page in between groups, whereas in a &amp;quot;group by group&amp;quot; or &amp;quot;all in one&amp;quot; survey it provides a header to the subsequent questions. groupdescription.pstpl does not have a corresponding &#039;closing&#039; template file, so all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question.pstpl:&#039;&#039;&#039; This file contains the question, answer and help text sections of your survey, and in the &amp;quot;group by group&amp;quot; and &amp;quot;all in one&amp;quot; surveys this template is cycled repeatedly with each question. There is no corresponding closing file for this and all tags should be closed.&lt;br /&gt;
*&#039;&#039;&#039;question_start.pstpl:&#039;&#039;&#039; This file contains the individual elements found at the start of a question. It is included within &#039;question.pstpl&#039; via the {QUESTION} keyword. It is intended to allow template designers more control over the layout of a question. This template sits outside the normal templating system and &#039;&#039;&#039;was superseeded (as of LS1.87)&#039;&#039;&#039;. All keywords from this template are now available directly in question.pstpl. NOTE: templates using question_start.pstpl will still work at least for a couple more versions of LS 1.x&lt;br /&gt;
*&#039;&#039;&#039;submit.pstpl (and privacy.pstpl):&#039;&#039;&#039; This page is the penultimate page for all types of survey (except the &amp;quot;all in one&amp;quot; type) where the participant is given an option to review questions before submitting their responses. It provides privacy information where a survey is anonymous, which it extracts from the &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039; file.&lt;br /&gt;
*&#039;&#039;&#039;completed.pstpl:&#039;&#039;&#039; This page is displayed as the final page when the survey responses have been saved and the survey is over. It can be used to display a &amp;quot;forwarding link&amp;quot; as set in the survey setup.&lt;br /&gt;
*&#039;&#039;&#039;endgroup.pstpl:&#039;&#039;&#039; This file closes the group, and can be used to close off any tags opened in the startgroup.pstpl file&lt;br /&gt;
*&#039;&#039;&#039;navigator.pstpl:&#039;&#039;&#039; This file contains the buttons that navigate through the survey, &amp;quot;next&amp;quot;, &amp;quot;prev&amp;quot;, &amp;quot;last&amp;quot;, &amp;quot;submit&amp;quot;, &amp;quot;save so far&amp;quot;  and the &amp;quot;clear all&amp;quot; link. It is used in all pages except the completed page.&lt;br /&gt;
*&#039;&#039;&#039;printanswers.pstpl:&#039;&#039;&#039; This file has the HTML wrapper for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_group.pstpl:&#039;&#039;&#039; This file is the same as startgroup.pstpl endgroup.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_question.pstpl:&#039;&#039;&#039; This file is the same as question.pstpl but for the print version of the survey.&lt;br /&gt;
*&#039;&#039;&#039;print_survey.pstpl:&#039;&#039;&#039; This file is the same as survey.pstpl but for the print version of the survey.&lt;br /&gt;
&lt;br /&gt;
==Other Template Files==&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;privacy.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;invitationemail.pstpl&#039;&#039;&#039;, &#039;&#039;&#039;reminderemail.pstpl&#039;&#039;&#039; and &#039;&#039;&#039;confirmationemail.pstpl&#039;&#039;&#039; are no longer used by LimeSurvey and defaults are instead set in the applicable language files. The email messages can now be edited on a survey by survey basis.&lt;br /&gt;
&lt;br /&gt;
==Standard Pages==&lt;br /&gt;
&lt;br /&gt;
There are ten standard pages that a survey participant may see in the course of taking or accessing the LimeSurvey application.  Each is constructed from a number of common &#039;&#039;&#039;Template&#039;&#039;&#039; files from the &#039;&#039;&#039;Template&#039;&#039;&#039; specified in the survey&#039;s settings.  The table below indicates which template files are used in constructing each of these pages.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|  &#039;&#039;&#039;Survey Pages:&#039;&#039;&#039;&amp;lt;br/&amp;gt;&#039;&#039;&#039;Template Files&#039;&#039;&#039;||Survey&amp;lt;br/&amp;gt;List||Welcome||Question||Completed||Clear All||Register||Load||Save||Print&amp;lt;br/&amp;gt;Answers||Print&amp;lt;br/&amp;gt;Survey&lt;br /&gt;
|-&lt;br /&gt;
|SurveyList|| [[File:check.gif]]|| || || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Welcome|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Privacy|| || [[File:check.gif]]|| || || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Navigator|| || [[File:check.gif]]|| [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Survey|| || || [[File:check.gif]]|| || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|StartGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|GroupDescription|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Question&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|EndGroup|| || || [[File:check.gif]]|| || || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Assessment|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Completed|| || || || [[File:check.gif]]|| || || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|ClearAll|| || || || || [[File:check.gif]]|| || || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Register|| || || || || || [[File:check.gif]]|| || || ||&lt;br /&gt;
|-&lt;br /&gt;
|Load|| || || || || || || [[File:check.gif]]|| || ||&lt;br /&gt;
|-&lt;br /&gt;
|Save|| || || || || || || || [[File:check.gif]]|| ||&lt;br /&gt;
|-&lt;br /&gt;
|PrintAnswers|| || || || || || || || || [[File:check.gif]]||&lt;br /&gt;
|-&lt;br /&gt;
|Print Survey || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Group || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|Print Question || || || || || || || || || || [[File:check.gif]]&lt;br /&gt;
|-&lt;br /&gt;
|StartPage&amp;lt;br/&amp;gt;EndPage&amp;lt;br/&amp;gt;Template.css|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| [[File:check.gif]]|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&#039;color:red&#039;&amp;gt;&#039;&#039;&#039;*&#039;&#039;&#039;&amp;lt;/span&amp;gt;NOTE: In versions 1.90 and up this replaces question.pstpl AND question_start.pstpl. If you are using an old custom template, you need to add the following line to the beginning of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div {QUESTION_ESSENTIALS} class=&amp;quot;{QUESTION_CLASS}{QUESTION_MAN_CLASS}{QUESTION_INPUT_ERROR_CLASS}&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;And then add the corresponding closing tag to the end of question.pstpl:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The File Control Section==&lt;br /&gt;
&lt;br /&gt;
In the &amp;quot;file control&amp;quot; window on the left, you can click on one of the template files that is used to compile the page. The HTML code for that file will then appear in the &amp;quot;Now editing&amp;quot; window in the center. If the template is editable (determined by directory permissions) you can then make any changes and save them.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Other Files&amp;quot; window shows a list of all other files in the template directory. You can use the right side to &#039;&#039;&#039;upload and select image files (your pics, logos,...) or other files needed to create your template&#039;&#039;&#039;. Note: Instead of a link directly to each picture in your template you can use the field string {TEMPLATEURL}.  So instead of:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;/limesurvey/templates/yourtemplate/mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt; You can use:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;img src=&#039;{TEMPLATEURL}mypicture.jpg&#039;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A &amp;quot;sample&amp;quot; of the template page you are editing will be visible at the bottom of the screen. There is no way to to delete a template from the template editor. This must be done by accessing the underlying directory and deleting the file there.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; The shipped templates cannot be edited using the Template Editor and should never be changed. If you want to modify them, create a copy first and modify the copy.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Location of template files==&lt;br /&gt;
&lt;br /&gt;
LimeSurvey stores each of the &#039;standard&#039; templates in their own distinct sub-directory within the /templates directory that is kept in the public directory with the other LimeSurvey public files. Customized user templates are stored in the /upload/templates directory.&lt;br /&gt;
&lt;br /&gt;
To create a new template, use the according icon in the template editor.&lt;br /&gt;
&lt;br /&gt;
There should ALWAYS be a &amp;quot;default&amp;quot; directory in the templates directory. This template is used by default and as a fall-back if a template folder doesn&#039;t exist, or can&#039;t be found. The &amp;quot;default&amp;quot; directory comes with the package.&lt;br /&gt;
&lt;br /&gt;
You can use any image files that you upload into the template management area with syntax like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;{TEMPLATEURL}filename.xyz&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Styling questions with CSS=&lt;br /&gt;
&lt;br /&gt;
Styling of questions in CSS has become much easier. Each question type now has a unique class. Mandatory question&#039;s also have an additional mandatory class. For example, for a non-mandatory question:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question is mandatory but the user didn&#039;t answer it or if there is validation on a question&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question5&amp;quot; class=&amp;quot;gender mandatory input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and if the question has validation applied but the user hasn&#039;t answered correctly&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;div id=&amp;quot;question6&amp;quot; class=&amp;quot;text-short input_error&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The full list of question classes==&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;Question Type&#039;&#039;&#039;||&#039;&#039;&#039;Question Class&#039;&#039;&#039;||&#039;&#039;&#039;Question ID&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|5 point choice||.choice-5-pt-radio||5&lt;br /&gt;
|-&lt;br /&gt;
|Array (10 point choice)||.array-10-pt||B&lt;br /&gt;
|-&lt;br /&gt;
|Array (5 point choice)||.array-5-pt||A&lt;br /&gt;
|-&lt;br /&gt;
|Array (Flexible Labels) dual scale||.array-flexible-duel-scale ||1&lt;br /&gt;
|-&lt;br /&gt;
|Array (Increase, Same, Decrease)||.array-increase-same-decrease||E&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Numbers)||.array-multi-flexi ||:&lt;br /&gt;
|-&lt;br /&gt;
|Array (Multi Flexible) (Text)||.array-multi-flexi-text||;&lt;br /&gt;
|-&lt;br /&gt;
|Array (Yes/No/Uncertain)||.array-yes-uncertain-no||C&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels)||.array-flexible-row ||F&lt;br /&gt;
|-&lt;br /&gt;
|Array (flexible labels) by column||.array-flexible-column||H&lt;br /&gt;
|-&lt;br /&gt;
|Boilerplate question||.boilerplate||X&lt;br /&gt;
|-&lt;br /&gt;
|Date||.date||D&lt;br /&gt;
|-&lt;br /&gt;
|Gender||.gender||G&lt;br /&gt;
|-&lt;br /&gt;
|Huge free text||.text-huge||U&lt;br /&gt;
|-&lt;br /&gt;
|Language switch||.language||I&lt;br /&gt;
|-&lt;br /&gt;
|List (dropdown)||.list-dropdown||!&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (dropdown)||.list-dropdown-flexible||W&lt;br /&gt;
|-&lt;br /&gt;
|List (flexible labels) (radio)||.list-radio-flexible||Z&lt;br /&gt;
|-&lt;br /&gt;
|List (radio)||.list-radio||L&lt;br /&gt;
|-&lt;br /&gt;
|List with comment||.list-with-comment||O&lt;br /&gt;
|-&lt;br /&gt;
|Long free text||.text-long||T&lt;br /&gt;
|-&lt;br /&gt;
|Multiple numerical input||.numeric-multi||K&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options||.multiple-opt||M&lt;br /&gt;
|-&lt;br /&gt;
|Multiple options with comments||.multiple-opt-comments||P&lt;br /&gt;
|-&lt;br /&gt;
|Multiple short text||.multiple-short-txt||Q&lt;br /&gt;
|-&lt;br /&gt;
|Numerical input||.numeric||N&lt;br /&gt;
|-&lt;br /&gt;
|Ranking||.ranking||R&lt;br /&gt;
|-&lt;br /&gt;
|Short free text||.text-short||S&lt;br /&gt;
|-&lt;br /&gt;
|Yes/No||.yes-no||Y&lt;br /&gt;
|-&lt;br /&gt;
|Mandatory||.mandatory||&lt;br /&gt;
|-&lt;br /&gt;
|User input error||.input_error|| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Importing styles into your custom template==&lt;br /&gt;
&lt;br /&gt;
The custom question styles are near the bottom of each template&#039;s CSS file and start with:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;/* &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;----&lt;br /&gt;
&lt;br /&gt;
  START: Question styles  &amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt; */&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you&#039;re styling your own custom template, You should be able to copy everything after the above from templates/default/template.css (for tables based layouts) or /templates/limespired/template.css (for CSS based layouts) into your own style sheet without any impact on your other styles.&lt;br /&gt;
&lt;br /&gt;
==Internet Explorer conditional style sheets==&lt;br /&gt;
&lt;br /&gt;
Because of the marked discrepancies in rendering between IE6, IE7 and most other browsers, there are special IE conditional style sheets included for each template.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;You should include the above code within your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; and copies of both the IE style sheets from either /templates/default/ or /templates/limespired for Tables base layout and CSS based layout respectively.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;&#039;&#039;&#039;Note:&#039;&#039;&#039; If you copy the styles into your own style sheet you will almost certainly need to tweak them.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Right-to-Left (RTL) Languages and justify==&lt;br /&gt;
&lt;br /&gt;
The text editor within LimeSurvey is able to format RTL Text. However, the editor itself shows the RTL language in a left to right format when justified.  This is just an editor display issue. The RTL and justified question or text will display correctly from right to left, even when justified, in your survey or on preview.&lt;br /&gt;
&lt;br /&gt;
==Keywords==&lt;br /&gt;
&lt;br /&gt;
Keywords within a template file get replaced by the current survey information. They are surrounded by curly brackets, for example: {SURVEYNAME}&lt;br /&gt;
&lt;br /&gt;
The following strings will be replaced by LimeSurvey when parsing the template file and presenting it to survey users. These field strings will work on almost every template except for the &#039;Completed Page&#039;. (Most of these strings can be found in the common.php file. If it&#039;s not there, look in the index.php file.)&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&#039;&#039;&#039;::KEYWORD::&#039;&#039;&#039;|| &#039;&#039;&#039;TEMPLATE FILES::&#039;&#039;&#039; || &#039;&#039;&#039;::DESCRIPTION::&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYNAME}||All Files||The survey title&lt;br /&gt;
|-&lt;br /&gt;
|{SURVEYDESCRIPTION}||All Files||The survey description&lt;br /&gt;
|-&lt;br /&gt;
|{WELCOME}||All files (mainly for welcome.pstpl)||The survey &#039;welcome&#039; text&lt;br /&gt;
|-&lt;br /&gt;
|{PERCENTCOMPLETE}||survey.pstpl||A small graph showing the percentage of the survey completed&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPNAME}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group name&lt;br /&gt;
|-&lt;br /&gt;
|{GROUPDESCRIPTION}||startgroup.pstpl, groupdescription.pstpl, endgroup.pstpl||Displays the current group description&lt;br /&gt;
|-&lt;br /&gt;
|{NUMBEROFQUESTIONS}||welcome.pstpl||Displays the total number of questions in the survey (just the number)&lt;br /&gt;
|-&lt;br /&gt;
|{THEREAREXQUESTIONS}||welcome.pstpl||Displays the sentence &amp;quot;There are X questions in this survey&amp;quot; - from the relevant language file. The X is replaced with the number of questions. Note that this will also work appropriately for singular or plural. If there is only 1 question, it will print &amp;quot;There is 1 question in this survey&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|{CHECKJAVASCRIPT}||All files (mainly for welcome.pstpl)||Warning message when end-user browser have javascript disabled&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION}||Question.pstpl||(&#039;&#039;&#039;Has been superseeded but the {QUESTION_...} keywords as of LS1.87&#039;&#039;&#039;) Displays the current question text (The format of {QUESTION} can customised by editing &#039;question_start.pstpl&#039;) Use the following: {QUESTION_TEXT}, {QUESTION_MANDATORY}, {QUESTION_HELP}, {QUESTION_MAN_MESSAGE}, {QUESTION_VALID_MESSAGE} and {QUESTION_INPUT_ERROR_CLASS} and appropriate wrapping HTML instead of {QUESTION})&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWER}||question.pstpl, print_question.pstpl||presents the answer form for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{SGQ}||question.pstpl, question text||Can be used in the question text itself, to reference the input field of the question dynamically by displaying the Survey-Group-Question id for the current question. (as of svn build 9755)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTIONHELP}||question.pstpl, print_question.pstpl||Displays help text for the current questionm for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CLASS}||question.pstpl, print_question.pstpl||unique class for each question type. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_CODE}||question.pstpl, print_question.pstpl||Displays the current question code&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ESSENTIALS}||question.pstpl||the question ID and (if a question is conditional), &#039;style=&amp;quot;display:none;&amp;quot;&#039;. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_HELP}||question.pstp, question_start.pstpl||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TYPE_HELP}||print_question.pstp||Displays the user defined help text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_INPUT_ERROR_CLASS}||question.pstp, question_start.pstpl||Provides a class if there was user input error&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_ID}||print_question.pstp||Provides a unique ID for each question to allow styling for specific questions&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_TEXT}||question.pstp, print_question.pstp, question_start.pstpl||Displays the text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MANDATORY}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_CLASS}||question.pstpl, print_question.pstpl||class if a question is mandatory. (To be included in the question&#039;s wrapping tag.)&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_MAN_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated &#039;Mandatory&#039; help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_NUMBER}||print_question.pstpl||Incremental count of questions.&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_VALID_MESSAGE}||question.pstp, print_question.pstp, question_start.pstpl||Displays the translated valid help message text for the current question&lt;br /&gt;
|-&lt;br /&gt;
|{QUESTION_SCENARIO}||print_question.pstp||Prints out the &#039;scenario&#039; text for conditional questions.&lt;br /&gt;
|-&lt;br /&gt;
|{NAVIGATOR}||navigator.pstpl||Displays navigation buttons (next, prev, last)&lt;br /&gt;
|-&lt;br /&gt;
|{CLEARALL}||All files (but intended for navigator.pstpl)||Displays the &amp;quot;Exit and Clear Results&amp;quot; link&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITBUTTON}||submit.pstpl||Displays the final submit button&lt;br /&gt;
|-&lt;br /&gt;
|{COMPLETED}||completed.pstpl||Displays the &#039;completed&#039; messagem for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{url}||completed.pstpl||Displays the survey &#039;url&#039; and &#039;url text&#039;&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACY}||submit.pstpl||Displays privacy information when survey is anonymous&lt;br /&gt;
|-&lt;br /&gt;
|{PRIVACYMESSAGE}||privacy.pstpl||The privacy message is shown if you set your survey to be anonymous. [http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+1.x+Translating+LimeSurvey The text can be edited/translated] in the language files. This can also be changed manually by editing the privacy.pstpl template you wish to use.&lt;br /&gt;
|-&lt;br /&gt;
|{TEMPLATEURL}||All Files||The URL to the current template location (useful for referencing image files in your template)&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITCOMPLETE}||endpage.pstpl||The statement (from the language files) that tells the user they have completed the survey, and to press the &amp;quot;Submit&amp;quot; button&lt;br /&gt;
|-&lt;br /&gt;
|{SUBMITREVIEW}||survey.pstpl||The statement (from the language files) that tells the user they can review/change the answers they have made by clicking &amp;quot;&amp;lt;&amp;lt; prev&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:FIRSTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users first name from the tokens table&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:LASTNAME}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users last name from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:EMAIL}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users email from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_1}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_1 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{TOKEN:ATTRIBUTE_2}||All Files||***If survey answers are NOT ANONYMOUS - gets replaced with the users attribute_2 from the tokens table***&lt;br /&gt;
|-&lt;br /&gt;
|{ANSWERSCLEARED}||Preferably in navigator.pstpl||The &amp;quot;Answers Cleared&amp;quot; statement from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{RESTART}||clearall.pstpl||URL to restart the survey&lt;br /&gt;
|-&lt;br /&gt;
|{CLOSEWINDOW}||All Files (Preferably in navigator.pstpl)||URL to close current window&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERERROR}||register.pstpl||Shows any error messages in the register page (ie: &amp;quot;You must include an email address&amp;quot;)&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE1}||register.pstpl||The statement &amp;quot;You must be registered to complete this survey&amp;quot; from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERMESSAGE2}||register.pstpl||Details about registering from the language files&lt;br /&gt;
|-&lt;br /&gt;
|{REGISTERFORM}||register.pstpl||The actual form for registering, will change depending on whether the attribute_1 and attribute_2 fields are set.&lt;br /&gt;
|-&lt;br /&gt;
|{SAVE}||Works suitable on navigator.pstpl||Displays the &#039;Save your responses so far&#039; button to offer the user to save and come back later to continue the survey. If the Save option is deactivated in the survey properties the tag will not be shown and ignored.&lt;br /&gt;
|-&lt;br /&gt;
|{LANGUAGECHANGER}||survey.pstpl||Displays a switch in multilingual surveys to change the question.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Input/Buttons==&lt;br /&gt;
&lt;br /&gt;
Each &amp;quot;input&amp;quot; type in a survey has been given its own class name, so that you can add CSS to your &amp;quot;startpage.pstpl&amp;quot; file, and have some control over the appearance of form buttons and inputs. These class names are as follows:&lt;br /&gt;
*&#039;&#039;&#039;submit&#039;&#039;&#039; (Submit Buttons)&lt;br /&gt;
*&#039;&#039;&#039;text&#039;&#039;&#039; (Text Inputs - for short free text, date and numerical type)&lt;br /&gt;
*&#039;&#039;&#039;answertext&#039;&#039;&#039; (Text of answers)&lt;br /&gt;
*&#039;&#039;&#039;radio&#039;&#039;&#039; (Radio Buttons)&lt;br /&gt;
*&#039;&#039;&#039;checkbox&#039;&#039;&#039; (Check Boxes)&lt;br /&gt;
*&#039;&#039;&#039;select&#039;&#039;&#039; (Select / List Boxes)&lt;br /&gt;
*&#039;&#039;&#039;textarea&#039;&#039;&#039; (Large text inputs - for long free text)&lt;br /&gt;
*&#039;&#039;&#039;clearall&#039;&#039;&#039; (The &amp;quot;Exit and Clear Survey&amp;quot; link)&lt;br /&gt;
*&#039;&#039;&#039;rank&#039;&#039;&#039; (The rank style question. Doesn&#039;t set the colour of the select box or the text boxes (these are set by relevant section above) but does allow changing of background colour, text colour and size etc for the rest of the ranking question)&lt;br /&gt;
*&#039;&#039;&#039;graph&#039;&#039;&#039; (The &amp;quot;percentage completed&amp;quot; graph table)&lt;br /&gt;
*&#039;&#039;&#039;innergraph&#039;&#039;&#039; (The table inside the graph table - this contains the 0% and 100% text. Use this for changing the size of this text&lt;br /&gt;
*&#039;&#039;&#039;question&#039;&#039;&#039; (General settings for any question that is displayed within a table. Generally you should use this to make sure that their font size and colour is the same as you have used elsewhere as a default)&lt;br /&gt;
*&#039;&#039;&#039;mandatory&#039;&#039;&#039;  (Mandatory questions)&lt;br /&gt;
*&#039;&#039;&#039;input_error&#039;&#039;&#039; (User input error - for if a user has made a mistake with a mandatory question or question with validation)&lt;br /&gt;
*&#039;&#039;&#039;array1&#039;&#039;&#039; and &#039;&#039;&#039;array2&#039;&#039;&#039; (These two styles are cycled when presenting the range of answers for an array type question. This allows you to set an alternating background colour for these question types. &#039;&#039;&#039;Array1&#039;&#039;&#039; is also used for the column headings in these question types)&lt;br /&gt;
*&#039;&#039;&#039;errormandatory&#039;&#039;&#039; (Sets the colour and style of the &amp;quot;This question is mandatory&amp;quot; error message)&lt;br /&gt;
*&#039;&#039;&#039;warningjs&#039;&#039;&#039; (Sets the colour and style of the warning message displayed if the participant&#039;s browser has javascript disabled)&lt;br /&gt;
&lt;br /&gt;
An example of using these classes with style sheets can be found in the &amp;quot;bubblegum&amp;quot; template that comes with the LimeSurvey application.&lt;br /&gt;
&lt;br /&gt;
Because you can edit all the HTML aspects, there&#039;s no reason to surround your templates with a &amp;lt;div class=&#039;new_name&#039;&amp;gt; and then define a css for that new_name class.&lt;br /&gt;
&lt;br /&gt;
==Styling the progress bar==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Before version 1.87:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The chart.jpg file is a simple one pixel image file which is used to create the progress bar image in the &#039;PERCENTCOMPLETE&#039; table. If the file does not exist, LimeSurvey will use the default &#039;maroon&#039; coloured image in the public directory. If you want to create a bar to match your own colour scheme, then you should save the color in this file. Remember it should be a &#039;&#039;&#039;JPEG&#039;&#039;&#039; file, 1 pixel x 1 pixel, in the colour desired.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The progress bar appearance can be modified with CSS.&lt;br /&gt;
&lt;br /&gt;
To change the background colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 background-color: #3300FF;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To change the border colour of the bar, add something like the following to the end of your template.css file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#progress-wrapper .ui-widget-content,&lt;br /&gt;
#progress-wrapper .ui-widget-header {&lt;br /&gt;
&lt;br /&gt;
 border: 1px solid #FF0000;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Advanced Features Available to Developers==&lt;br /&gt;
&lt;br /&gt;
Starting with version 0.99, LimeSurvey has integrated some user-made patches that allow for some special changes.  These very advanced features generally require changes to the underlying code base of LimeSurvey and should be done carefully so as not to introduce security holes.&lt;br /&gt;
&lt;br /&gt;
===Basic CMS Integration support===&lt;br /&gt;
&lt;br /&gt;
To be able to integrate LimeSurvey into another CMS, use the following options in &#039;&#039;&#039;config.php&#039;&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
// Set $embedded to true and specify the header and footer functions if the survey is to be displayed embedded in a CMS&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$embedded = false;&lt;br /&gt;
&lt;br /&gt;
$embedded_inc = &amp;quot;&amp;quot;;               // path to the header to include if any&lt;br /&gt;
&lt;br /&gt;
$embedded_headerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteHeader for geeklog&lt;br /&gt;
&lt;br /&gt;
$embedded_footerfunc = &amp;quot;&amp;quot;;        // e.g. COM_siteFooter for geeklog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set &#039;&#039;&#039;$embedded = true;&#039;&#039;&#039; to enable CMS-embedding. By using the &#039;&#039;&#039;$embedded_inc&#039;&#039;&#039; variable one can include their own &#039;&#039;&#039;.php&#039;&#039;&#039; files.  By setting &#039;&#039;&#039;$embedded_headerfunc&#039;&#039;&#039; or &#039;&#039;&#039;$embedded_footerfunc&#039;&#039;&#039;, one can call functions from within included files that output the relevant headers or footers instead of LimeSurveys default ones.&lt;br /&gt;
&lt;br /&gt;
===Support for your own Javascript functions===&lt;br /&gt;
&lt;br /&gt;
Some users may need to run Javascript on the survey pages, but calling &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; in the BODY element made it impossible to do so.  This call has been replaced with a small JavaScript function in the HEAD that sniffs for the existence of &#039;&#039;&#039;checkconditions()&#039;&#039;&#039; and &#039;&#039;&#039;template_onload()&#039;&#039;&#039; before calling each.  This way a template author can create their own &#039;&#039;&#039;template_onload()&#039;&#039;&#039; function in the HEAD that replaces the default one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Version 1.87 and newer:&#039;&#039;&#039;&lt;br /&gt;
*Disable XSS filter - in Global settings -&amp;gt; Security, set &amp;quot;Filter HTML for XSS&amp;quot; to No.&lt;br /&gt;
*Enter your script in the source of a question or group description.&lt;br /&gt;
*There are more details in the [http://docs.limesurvey.org/tiki-index.php?page=Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#How_to_use_Script_eg._JavaScript_etc._in_LimeSurvey_ workaround section].&lt;br /&gt;
&lt;br /&gt;
=Videos on Templates=&lt;br /&gt;
&lt;br /&gt;
These videos will demonstrate the basic and advanced template functions that are available to all LimeSurvey users. This includes changing the appearance of certain forms and inserting custom graphics. Additionally, it will thoroughly walk you through on how to edit and preview specific page templates, importing/exporting templates, modify appearance of questions in the CSS, customizing survey description page, and completed page.&lt;br /&gt;
&lt;br /&gt;
Part I&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;nLsfxMjRXyk?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part II&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;yrAXStFH34Q?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part III&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;TYlJXHgt8R0?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part IV&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;Rml0gqeErVc?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part V&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;LX24Ix1ylmY?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
Part VI&lt;br /&gt;
&lt;br /&gt;
{YOUTUBE(movie=&amp;quot;-202CqQcW8g?fs=1&amp;amp;amp;hl=en_US&amp;amp;amp;rel=0&amp;quot;,width=&amp;quot;640&amp;quot;,height=&amp;quot;385&amp;quot;)}{YOUTUBE}&lt;br /&gt;
&lt;br /&gt;
=Tips &amp;amp; Tricks=&lt;br /&gt;
&lt;br /&gt;
==Change the layout of the survey page==&lt;br /&gt;
&lt;br /&gt;
When editing a template this template can be assigned to a single survey while the survey list page, which is shown at www.yourdomain.org/limesurveyinstallfolder, lists all your surveys.&lt;br /&gt;
&lt;br /&gt;
To use your current template for this page you have change the according setting at the Global Settings screen; at older versions this change can be done by editing the $defaulttemplate setting at the config file: Copy this setting from config-defaults.php to config.php which overrides config-defaults.php and edit this setting to $defaulttemplate = &#039;yourtemplatename&#039;;&lt;br /&gt;
&lt;br /&gt;
==Import/Export of templates: Mac users==&lt;br /&gt;
&lt;br /&gt;
Mac users, please note: Mac OSX default archive utility may have problems with zip folders &amp;quot;generated on the fly&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
a work around is to unix&#039;es unzip from the command line:&lt;br /&gt;
&lt;br /&gt;
$ unzip template.zip -d template&lt;br /&gt;
&lt;br /&gt;
Archive: template.zip&lt;br /&gt;
&lt;br /&gt;
 inflating: template/startpage&lt;br /&gt;
&lt;br /&gt;
 inflating: ...&lt;br /&gt;
&lt;br /&gt;
or scripts in their mac-compiled counterparts:&lt;br /&gt;
&lt;br /&gt;
http://homepage.mac.com/roger_jolly/software/&lt;br /&gt;
&lt;br /&gt;
==Changing your templates traffic light from red to green==&lt;br /&gt;
&lt;br /&gt;
If you haven&#039;t already, set the admin directory to read/write/execute (777). The files within it, however, may be set to read/execute only (chmod 755).&lt;br /&gt;
&lt;br /&gt;
GO to file directory ie file manager, find templates directory.&lt;br /&gt;
&lt;br /&gt;
1 change permission on eg&amp;quot;vallendar&amp;quot; (or any template of your choice) directory to read 777&lt;br /&gt;
&lt;br /&gt;
2 voila! the red traffic light on &amp;quot;vallendar&amp;quot; is now green.&lt;br /&gt;
&lt;br /&gt;
3 NOTE: to restrict access for safety, when finished editing template files, change all templates files back to what they were eg 644&lt;br /&gt;
&lt;br /&gt;
==Replacing the help icon==&lt;br /&gt;
&lt;br /&gt;
When a question help text is shown then an help.gif image is used from the default template folder.&lt;br /&gt;
&lt;br /&gt;
You can replace this image by uploading a new help.gif, help.png or help.jpg in your custom template folder. It then will be automatically used instead of the default help icon.&lt;br /&gt;
&lt;br /&gt;
==Replacing an existing logo==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Before uploading new logo delete previous one.&lt;br /&gt;
&lt;br /&gt;
1. To edit logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
2. Find and Click Search button, to find place where is logo style text.&lt;br /&gt;
&lt;br /&gt;
[[File:2.PNG]]&lt;br /&gt;
&lt;br /&gt;
3. Find in search &amp;lt;u&amp;gt;#logo&amp;lt;/u&amp;gt; (It is logo design code)&lt;br /&gt;
&lt;br /&gt;
[[File:3.PNG]]&lt;br /&gt;
&lt;br /&gt;
4. Edit style file&lt;br /&gt;
&lt;br /&gt;
You will see something like this code:&lt;br /&gt;
&lt;br /&gt;
[[File:4.PNG]] &lt;br /&gt;
&lt;br /&gt;
If you want change image just replace logo.gif to antoher image link. Like: (&amp;lt;u&amp;gt;logo.png&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.jpg&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;logo.swf&amp;lt;/u&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
If you want change image size just change, width and height (in pixels) like:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;Width:100px; Height:100px;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adding your own logo==&lt;br /&gt;
&lt;br /&gt;
1. Find and Open &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; template file.&lt;br /&gt;
&lt;br /&gt;
[[File:5.PNG]] &lt;br /&gt;
&lt;br /&gt;
2. Write in &amp;amp;bdquo;&amp;lt;u&amp;gt;startpage.pstpl&amp;lt;/u&amp;gt;&amp;amp;rdquo; this line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;img id=&amp;amp;rdquo;page_logo&amp;amp;rdquo; src=&amp;amp;rdquo;{TEMPLATEURL}logo.png&amp;amp;rdquo;&amp;gt;&amp;lt;br&amp;gt;&amp;lt;/syntaxhighlight&amp;gt; After &amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;body ... &amp;gt;&amp;lt;/syntaxhighlight&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
[[File:6.PNG]] &lt;br /&gt;
&lt;br /&gt;
3. To add logo go to &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo;, you can find it here (see in screen):&lt;br /&gt;
&lt;br /&gt;
[[File:1.PNG]]&lt;br /&gt;
&lt;br /&gt;
3.1 Go to end of &amp;amp;bdquo;&amp;lt;u&amp;gt;template.css&amp;lt;/u&amp;gt;&amp;amp;rdquo; style file.&lt;br /&gt;
&lt;br /&gt;
3.2 Write in end:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in left side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:left;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in right side:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   float:right;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you want in center:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;#page_logo{&lt;br /&gt;
&lt;br /&gt;
   display: block;&lt;br /&gt;
&lt;br /&gt;
   margin-left: auto;&lt;br /&gt;
&lt;br /&gt;
   margin-right: auto;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the default help to all question (hide_tip)==&lt;br /&gt;
&lt;br /&gt;
There are 2 solution to remove the default help, like a [[Advanced question settings|#hide_tip|hide_tip attribute]] but for all question and survey.&lt;br /&gt;
# you can remove the {QUESTIONHELP} and is container from the file question.pstl, but it can be a bad idea for screenreader.&lt;br /&gt;
# for the default template and some other , add this at the end of tempate.css&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;span.questionhelp{display:none;}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Display custom favicon==&lt;br /&gt;
&lt;br /&gt;
A favicon is the little icon you see in the browser&#039;s address bar, list of bookmarks or tab. You can display your own icon as follows:&lt;br /&gt;
#Create a favicon - google will find you lots of free favicon generators&lt;br /&gt;
#Name your new favicon &amp;quot;favicon.ico&amp;quot; and place it in your template directory&lt;br /&gt;
#Add the following code to your &#039;&#039;&#039;startpage.pstpl&#039;&#039;&#039; before the &amp;lt;/head&amp;gt; tag&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&amp;lt;link rel=&amp;quot;shortcut icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;link rel=&amp;quot;icon&amp;quot; href=&amp;quot;{TEMPLATEURL}favicon.ico&amp;quot; type=&amp;quot;image/x-icon&amp;quot;&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Different appearance for survey-/question-pages==&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;Version 1.91 and newer&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
If you want LimeSurvey to change the appearance of every second page (i.e. of even and odd survey pages) you can use &#039;&#039;&#039;.page-odd&#039;&#039;&#039; class in your css file to change the appearance of odd pages.&lt;br /&gt;
&lt;br /&gt;
example from default template of LimeSurvey 1.91+&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
.page-odd table.question-group {&lt;br /&gt;
&lt;br /&gt;
 background-color: #D2F2D3;&lt;br /&gt;
&lt;br /&gt;
}&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To &#039;&#039;&#039;not&#039;&#039;&#039; differentiate even and odd pages at the (default) template find all instances of &#039;&#039;.page-odd&#039;&#039; in template.css and remove those styles.&lt;br /&gt;
&lt;br /&gt;
==Create a vertical separator  border for dual scale array==&lt;br /&gt;
&lt;br /&gt;
To create a vertical separator border for a dual scale array you can add the following lines to your &#039;&#039;&#039;template.css&#039;&#039;&#039;-file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
table.question thead td.header_separator,&lt;br /&gt;
&lt;br /&gt;
table.question tbody td.dual_scale_separator&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   border-right:solid 1px #00A8E1;&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
header_separator is used to adress the separator for the header &amp;quot;td&amp;quot; and &amp;quot;dual_scale_separator&amp;quot; is used to adress the separator column in the dual scale array.&lt;br /&gt;
&lt;br /&gt;
==Hide the survey contact message shown on the start page/survey list==&lt;br /&gt;
&lt;br /&gt;
To hide the &amp;quot;Please contact ...&amp;quot; meassage on the start page (with the survey list) you can add the following to the *$(document).ready* function in the *template.js* of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
$(&#039;#surveycontact&#039;).hide(); //Hides the survey contact message&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Remove the survey contact message shown on error messages==&lt;br /&gt;
&lt;br /&gt;
If you want to remove the survey contact message from error messages it&#039;ll be trickier. You can add the following function call to the *$(document).ready* function in the *template.css* of your used design template:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
removeContactAdressFromMessage(); //Removes the survey contact message from error messages&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and add the following function to your *template.js* file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
function removeContactAdressFromMessage()&lt;br /&gt;
&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
if ($(&#039;#tokenmessage&#039;).length &amp;gt; 0)&lt;br /&gt;
&lt;br /&gt;
   {&lt;br /&gt;
&lt;br /&gt;
   var oldMessage = $(&#039;#tokenmessage&#039;).html();&lt;br /&gt;
&lt;br /&gt;
   var indexContact = oldMessage.indexOf(&#039;Bitte kontaktieren&#039;);&lt;br /&gt;
&lt;br /&gt;
   var newMessage = oldMessage.substr(0, indexContact);&lt;br /&gt;
&lt;br /&gt;
   $(&#039;#tokenmessage&#039;).html(newMessage);&lt;br /&gt;
&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will probably not work for an englisch survey and have to be extended when using for multilingual surveys. But it&#039;s an idea/tip how to solve this.&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(Texts)&amp;diff=2630</id>
		<title>Question type - Array (Texts)</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(Texts)&amp;diff=2630"/>
		<updated>2012-01-05T11:38:25Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Short description=&lt;br /&gt;
&lt;br /&gt;
The Array (Text) question type allows for an array of text boxes with a set of subquestions as the &amp;amp;ldquo;y-axis&amp;amp;rdquo;, and another set of subquestions as the &amp;amp;ldquo;x-axis&amp;amp;rdquo;.&lt;br /&gt;
&lt;br /&gt;
[[File:SC_MFT.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
You can also limit this question type to allow numerical answers only (see [http://docs.limesurvey.org/Question+type+-+Array+%28Texts%29&amp;amp;structure;=English+Instructions+for+LimeSurvey#Numbers_only question attribute &amp;quot;numbers only&amp;quot;]) and [http://docs.limesurvey.org/Question+type+-+Array+%28Texts%29&amp;amp;structure;=English+Instructions+for+LimeSurvey#Show_totals_for enable showing totals] for rows, columns or both:&lt;br /&gt;
&lt;br /&gt;
[[File:array_text_numbers_totals.PNG]]&lt;br /&gt;
&lt;br /&gt;
=Advanced settings=&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_order&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!answer_width&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!text_input_width&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_group&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!hidden&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter_exclude&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!show_totals&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!numbers_only&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!show_grand_total&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!page_break&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(10_point_choice)&amp;diff=2578</id>
		<title>Question type - Array (10 point choice)</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(10_point_choice)&amp;diff=2578"/>
		<updated>2012-01-05T11:23:30Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Short description=&lt;br /&gt;
&lt;br /&gt;
An array type that is prefilled with answer choices on a 1 to 10 scale. You may also add a &amp;quot;No answer&amp;quot; choice if the question is not mandatory.&lt;br /&gt;
&lt;br /&gt;
[[File:B_10_point.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=Advanced settings=&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_order&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_group&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!answer_width&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!hidden&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter_exclusion&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!page_break&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!public_statistics&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(5_point_choice)&amp;diff=2589</id>
		<title>Question type - Array (5 point choice)</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Question_type_-_Array_(5_point_choice)&amp;diff=2589"/>
		<updated>2012-01-05T11:23:00Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Short description=&lt;br /&gt;
&lt;br /&gt;
An array type that is prefilled with answer choices on a 1 to 5 scale. You may also add a &amp;quot;No answer&amp;quot; choice if the question is not mandatory.&lt;br /&gt;
&lt;br /&gt;
[[File:A-5_point.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Note: If you need other other scales than 5 points just use the most flexible general [[Question type - Array|Array question type]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Advanced settings=&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_order&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!random_group&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!answer_width&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!hidden&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!array_filter_exclude&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!page_break&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Advanced question settings&amp;quot;,start=&amp;quot;!public_statistics&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2036</id>
		<title>LimeSurvey project ideas for Google Code-in 2011</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2036"/>
		<updated>2011-12-05T10:11:03Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome=&lt;br /&gt;
&lt;br /&gt;
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an [http://code.google.com/opensource/gci/2010-11/faqs.html eligible candidate] for the GCI program.&lt;br /&gt;
&lt;br /&gt;
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)&lt;br /&gt;
&lt;br /&gt;
All tasks aim at the development version 2.0a.&lt;br /&gt;
&lt;br /&gt;
=How to claim a task=&lt;br /&gt;
&lt;br /&gt;
All tasks below will be entered in the [http://www.google-melange.com/gci/program/list_tasks/google/gci2011 Google Code-in task tracker] (which is not yet available). You have to be a registered Google Code-In participant to claim a task.&lt;br /&gt;
&lt;br /&gt;
=Task ideas=&lt;br /&gt;
&lt;br /&gt;
==Idea Template==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is just a template you can use to add your ideas:&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: &amp;lt;myname&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Second wave==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;...add your ideas here...&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Documentation/Translation: (GERMAN) Merge article &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot; and add new/missing parts of english article &amp;quot;The template editor&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;The template editor&amp;quot; has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot;. For the reason of simplicity and unity both articles should be merged together. If the english article &amp;quot;The template editor&amp;quot; has new/missing parts this parts should be translated and added to the new merged article.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Then have a look at the german page at http://docs.limesurvey.org/Der+Vorlagen+Editor and http://docs.limesurvey.org/Templates+++Styles&lt;br /&gt;
*Merge the information from http://docs.limesurvey.org/Templates+++Styles into http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Copy the missing parts to a fitting place of http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Rewrite the article http://docs.limesurvey.org/Der+Vorlagen+Editor that it sounds acceptable.&lt;br /&gt;
*Compare http://docs.limesurvey.org/Der+Vorlagen+Editor with http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Translate new/missing parts of http://docs.limesurvey.org/The+template+editor into german and add them to http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
*Discuss the article http://docs.limesurvey.org/Der+Vorlagen+Editor with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German and English language|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation: Update the Limesurvey 2.0 database layout===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Enable filling out additional token attributes when registering for a survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: Update the German version of the english &amp;quot;optional settings&amp;quot; wiki page===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;optional settings&amp;quot; wiki page (http://docs.limesurvey.org/Optional+settings) holds information about Limesurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.&lt;br /&gt;
&lt;br /&gt;
The German version of this page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen) is outdated and needs to be updated based on the english page.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the &amp;quot;documentation&amp;quot; link on the Limesurvey main page.&lt;br /&gt;
*Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&lt;br /&gt;
*Port the document structure (page sections) to the German page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen)&lt;br /&gt;
*Check which settings are missing -&amp;gt; add those&lt;br /&gt;
*Check which settings are incomplete -&amp;gt; extend those&lt;br /&gt;
*Check which settings are not listd at the english version -&amp;gt; delete those&lt;br /&gt;
*When you are done, check carefuly if no settings is missing&lt;br /&gt;
*If you have any questions about a certain setting, ask it here, your mentor will be notified.&lt;br /&gt;
*When you are done, submit your work here (just give the link to the translated page).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German language, wiki editing|| moderate||Mazi, mot&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: Translate the english &amp;quot;optional settings&amp;quot; wiki page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;optional settings&amp;quot; wiki page (http://docs.limesurvey.org/Optional+settings) holds information about Limesurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.&lt;br /&gt;
&lt;br /&gt;
A Spanish version of this page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen) doesn&#039;t exist and needs to be created based on the english page.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the &amp;quot;documentation&amp;quot; link on the Limesurvey main page.&lt;br /&gt;
*Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&lt;br /&gt;
*On top right, choose the option to translate the current english version and assign the new page a matching name and the Spanish language&lt;br /&gt;
*Translate the english page to Spanish&lt;br /&gt;
*When you are done, check carefuly if no settings is missing&lt;br /&gt;
*If you have any questions about a certain setting, ask it here, your mentor will be notified.&lt;br /&gt;
*When you are done, submit your work here (just give the link to the translated page).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Spanish language, wiki editing|| difficult||Mazi, holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation: Include description from question type articles into question types overview page===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;Question Types&amp;quot;, http://docs.limesurvey.org/Question+types has its own description and images. It would be better to include the description from the question type articles. This can make maintenance easier.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
* Use http://docs.limesurvey.org/English+Instructions+for+LimeSurvey to get to the articles for the question types. For example, the first is &amp;quot;Question type - Array&amp;quot; at http://docs.limesurvey.org/Question+type+-+Array .&lt;br /&gt;
* If the article doesn&#039;t have a header called &amp;quot;short description&amp;quot; (Wiki: &amp;lt;nowiki&amp;gt;!Short description&amp;lt;/nowiki&amp;gt;) add the short description header.&lt;br /&gt;
* The short description should be short and tell the user in one to three sentences what this question type is used for. You can use the existing description in the article if it fits well or copy and customise it. After your work is done it should look like &amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Short description=&lt;br /&gt;
&lt;br /&gt;
An array allows you to create subquestions as your left hand headings, and let your participants respond to a series of possible answers options using those subquestions.&lt;br /&gt;
&lt;br /&gt;
[[File:F_AFL.jpg]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=General description=&lt;br /&gt;
&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
*Have a look at the english page http://docs.limesurvey.org/Question+types&lt;br /&gt;
*Edit http://docs.limesurvey.org/Question+types : Remove the old text/images and include the short description of the question type article.&lt;br /&gt;
* Before: &amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Array===&lt;br /&gt;
&lt;br /&gt;
[[File:F_AFL.jpg]]&lt;br /&gt;
&lt;br /&gt;
[[Media:F_-_Array_Flexible_Labels.csv|Download this question type to import it at your survey]]&lt;br /&gt;
&lt;br /&gt;
To show scale details left/right of the answer scale you can use &amp;quot;|&amp;quot; as a separator when adding the answer text e. g.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;sweet|bitter&amp;quot;&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
&amp;quot;not at all satisfied|extremely satisfied&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[File:H_SD.jpg]]&lt;br /&gt;
&lt;br /&gt;
[[Media:H_-_Array_Flexible_Labels_-_Semantic_Differential.csv|Download this question type to import it at your survey]]&lt;br /&gt;
&lt;br /&gt;
Find out [[Question type - Array|more about the Array question type...]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
* After:&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Array===&lt;br /&gt;
&lt;br /&gt;
{INCLUDE(page=&amp;quot;Question type - Array&amp;quot;,start=&amp;quot;!Short description&amp;quot;,stop=&amp;quot;---&amp;quot;)}{INCLUDE}&lt;br /&gt;
&lt;br /&gt;
Find out [[Question type - Array|more about the Array question type...]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
*Repeat this for all question types&lt;br /&gt;
*Discuss your changes with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||English language, understand wiki syntax|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==First wave (already ported to GCi system)==&lt;br /&gt;
&lt;br /&gt;
==Localization==&lt;br /&gt;
&lt;br /&gt;
===Localization: Translate LimeSurvey to your mother language===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.&lt;br /&gt;
*Read the documentation on [[how to update a translation or how to create a new one.|Translating LimeSurvey]]&lt;br /&gt;
*Translate as crazy - check your translation using a local copy of LimeSurvey.&lt;br /&gt;
*Submit your updated/new translation to us.&lt;br /&gt;
&lt;br /&gt;
Updating a translation from &amp;lt;70% to 100%:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Translation|| Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
New translation (at least 50%):&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Translation|| Moderate ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced qustion attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute update the German translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Tokens&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Installer&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the German translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;--&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions update the French translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Tokens&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Installer&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the French translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;---&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Question types&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Question types&amp;quot; page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Question+types english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Tokens&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn&#039;t exist yet. Your task is to create the Spanish translation of that wiki page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Translate the page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Spanish and English language|| difficult||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Installer&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the Spanish translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Usability changes for LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey, play around with the interface.&lt;br /&gt;
*Pick a couple things you would like to change to have better usability&lt;br /&gt;
*Discuss the found issues with your mentor&lt;br /&gt;
*Together we will either pick one of your found issues or the mentor will make an suggestion for another change.&lt;br /&gt;
*Code the usability change and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and the mentor&lt;br /&gt;
*If necessary make re-submit patch with discusse changes&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, HTML, CSS, maybe SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement &amp;quot;Embedd all text answers&amp;quot; setting at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.&lt;br /&gt;
&lt;br /&gt;
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new &amp;quot;Embedd all text answers&amp;quot; setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with text questions and add some dummy data.&lt;br /&gt;
*Have a look at the data summary and the available export options.&lt;br /&gt;
*Add a &amp;quot;Embedd all text answers&amp;quot; setting.&lt;br /&gt;
*Implement the code to embedd that data and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, some very basic HTML, SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement Google map at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a &amp;quot;Map&amp;quot; question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users&#039; answers at that overview.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a map question and add some dummy data.&lt;br /&gt;
*Have a look at the admin statistics of that question.&lt;br /&gt;
*Implement the code to embedd a Map and mark the users&#039; answers in there and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing)|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at token overview table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the token overview and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Difficult ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at browse response table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we&#039;ll hand that to you) and add some test answer data.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the browse response table and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve drag and drop functionality at attribute mapping===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Aniessh&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Central Participant&#039;s Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Create some attributes at the token level.&lt;br /&gt;
*Create some attributes at the Central Participant Database panel.&lt;br /&gt;
*Copy the previously added dummy people from token table to the central table.&lt;br /&gt;
*You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.&lt;br /&gt;
*Suggest how to improve the user interface.&lt;br /&gt;
*Improve the user interface and create a patch.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add drag and drop feature to ranking question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey contains a &amp;quot;ranking&amp;quot; question type (see http://docs.limesurvey.org/Question+type+-+Ranking&amp;amp;structure;=English+Instructions+for+LimeSurvey) which isn&#039;t very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.&lt;br /&gt;
&lt;br /&gt;
There is already a [http://docs.limesurvey.org/Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#Drag_and_Drop_Rankings workaround] and a [http://www.partnersinc.biz/surveys//index.php?sid=36981&amp;amp;newtest;=Y&amp;amp;lang;=en demo version] available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a test survey with ranking question types and different question attributes&lt;br /&gt;
*Have a look at the question type within the survey to see what could be improved.&lt;br /&gt;
*Check the workaround linked above and the demo survey to see where we would like to go to.&lt;br /&gt;
*Implement a generic solution to make the ranking question type a little nicer (no DB changes required).&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Javascript, PHP, CSS|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add option to switch between bar chart and pie chart at statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.&lt;br /&gt;
*Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.&lt;br /&gt;
*Discuss your suggestions with your mentor and together create a concept how to deal with the problem.&lt;br /&gt;
*Implement a generic solution.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||PHP, MySQL, a little HTML|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Refactor the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find a class or method with smelly (bad) code&lt;br /&gt;
*Discuss the code smell with the mentor and make a proposal on how to improve the code&lt;br /&gt;
*Work out the improvement and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen smell)||PHP, CodeIgniter (depending on chosen smell)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Make unit tests for the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find an untested class which could use some testing&lt;br /&gt;
*Discuss the badly tested class/method with the mentor and make a proposal on how to test the code&lt;br /&gt;
*Write tests for class/method and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen class/method)||PHP, CodeIgniter (depending on chosen class/method)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring HTML into views : CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Browse Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Check Integrity Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Conditions Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Database Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Data Entry Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Email Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Export Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Labels Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Printable Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Group Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Quotas Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Saved Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Statistics Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Permission Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Tokens Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Translate Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Groups Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite template editor wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the template editor documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite the survey settings page===&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Create a tutorial about how to replace the logo at a shipped template===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Problem is that some HTML and CSS knowledge is needed to fully style a template and this might be a problem to the common user. Usually replacing the logo at one of the shipped templates is all they need so the goal is to write a step by step tutorial with some screen shots about how to replace the logo.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing documentation about templates and create a new entry at the [http://docs.limesurvey.org/The+template+editor&amp;amp;structure;=English+Instructions+for+LimeSurvey#Tips_amp_Tricks Tipps &amp;amp; Tricks sub-section].&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Check the template editor at our demo system and note how the logos are embedded at different templates&lt;br /&gt;
*Write a step by step tutorial including screen shots on how to replace the images and/or change the logo file name at the templates&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
*Discuss your tutorial with your mentor and if necessary overwork some parts&lt;br /&gt;
* Add everything at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Wiki editing, LimeSurvey, HTML|| Easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite statistics wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers public statistics, which are shown to the user at the end of the survey, as well as more detailed statistics at the admin backend. The [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey current statistics documentation] is outdated and not very well structured. Lots of users don&#039;t know that they can filter data and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the statistics more clear to the user, the documentation should be updated, extended and better structured. A video showing how to set filters and demonstrating other statistic features should be added, too.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import the sample survey at /docs/demosurveys which contains all question types.&lt;br /&gt;
*Enable public statistics for this survey and all questions that are supported by this feature.&lt;br /&gt;
*Fill out the survey ~20-30 times (ask your friends for some help) to create some data to be used by the statistics.&lt;br /&gt;
*Explore the public and admin backend statistics and write down which features are available.&lt;br /&gt;
*Ask your mentor if all features are on your list.&lt;br /&gt;
*Think about a new structure for the wiki page&lt;br /&gt;
*Document each section and describe each feature in detail. Add some nice screenshots where appropriate.&lt;br /&gt;
*Create a short video showing how to set filters and use other important features.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Wiki editing, LimeSurvey, video capture|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite installation procedure.===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey 2.0 has a new automatic installer which makes installation process a cake-walk. Hence, installation procedure needs to be updated explaining each and every step of the installation procedure and possible errors/warnings that a user might see during installation of LimeSurvey and there solutions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Checkout LimeSurvey_CI branch.&lt;br /&gt;
*Read existing installation procedure.&lt;br /&gt;
*Run the automatic installer and play with it.&lt;br /&gt;
*Compare the missing things and update the wiki.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Make a troubleshooting section on installation wikipage which should contain possible warnings a user might see and there solution(s).&lt;br /&gt;
*Create a short video tutorial on how to install LimeSurvey.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Wiki editing, creating screen shots, writing documentation, creating videos|| difficult||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; Marketing==&lt;br /&gt;
&lt;br /&gt;
===Outreach: Blog about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
Write an independant article about LimeSurvey on your blog. Explain what are advantages, what are disadavantages of the software - show how to create a first survey and also write about problems are on the way getting there. Motivate people to participate to help use make LimeSurvey better. The article should be in-depth and correct. It should help other to get hooked up without false promises.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Use LimeSurvey to setup your own survey (you can use our demo version for that)&lt;br /&gt;
*Blog about your experience after discussing your article with us.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days|| Writing skills || Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee engagement survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An introduction.&lt;br /&gt;
#Setting up an employee engagement survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee engagement survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee engagement survey.&lt;br /&gt;
*Discuss the employee engagement metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an employee satisfaction survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee satisfaction survey.&lt;br /&gt;
*iscuss the employee satisfaction metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Blog about LimeSurvey (2)===&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
&lt;br /&gt;
- Research how a general basic customer satisfaction survey should look like&lt;br /&gt;
&lt;br /&gt;
- Create it in LimeSurvey&lt;br /&gt;
&lt;br /&gt;
- Write about your experience in setting this up.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Survey Creation, Technical Writing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey to create and distribute a customer satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
Show current and potential LimeSurvey users how they can use LimeSurvey to do customer satisfaction surveys.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an customer satisfaction survey with LimeSurvey.&lt;br /&gt;
#Importing the tokens into the customer satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide a link to the example customer satisfaction survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey and test it.&lt;br /&gt;
*Discuss the customer satisfaction metrics measured with your mentor.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Analyse user feedback and port suggestions to our idea tracker===&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey [http://survey.limesurvey.org/ conducts user feedback surveys] to find out how our users use the software and which features they are missing. We received quite a lot feedback during the last months and a lot of valuable information can be found at the textual feedback. It&#039;s a mixture of praise, suggestions for new features and other useful comments. This needs to be summed up. Also useful suggestions for new features should be ported to [http://ideas.limesurvey.org/ our idea tracker] so we have this on our list for future development.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will give you access to our survey system so you can export the survey data into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list of common complaints, suggested features and the like.&lt;br /&gt;
*Once you are done, order the lists by frequency and present it to your mentor.&lt;br /&gt;
*Your mentor will go through your list and mark those ideas worth porting to the idea tracker.&lt;br /&gt;
*Add ideas to the idea tracker&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Data analysis, Report Writing, Using idea tracker|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Training==&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a custom survey template===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Create a video tutorial showing users how to create a copy of the default template and modify it.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#An overview of the template editor and a description of what each area of the template editor is used for.&lt;br /&gt;
#An explanation of the different screens.&lt;br /&gt;
#Inserting a company logo in to the template.&lt;br /&gt;
#Basic adjustments in the css to modify the appearance of questions.&lt;br /&gt;
#Customizing the survey description page.&lt;br /&gt;
#Customizing the end page.&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a new survey from scratch===&lt;br /&gt;
&lt;br /&gt;
There are several videos around explaining how to create a survey with LimeSurvey. Unfortunately most of the are pretty outdated and old. We would like to have a kick-all video tutorial explaining how to create a survey that immediately will hook up people.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Creation of a survey, with an easy explanation of the concept behind it (Survey-&amp;gt;Question groups-&amp;gt;Questions)&lt;br /&gt;
#Creating the survey, explaining the most important settings&lt;br /&gt;
#Creating question groups and questions plus answers&lt;br /&gt;
#Showing off a number of question types&lt;br /&gt;
#Showing off how a simple condition is created.&lt;br /&gt;
#Activating the survey&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a &amp;quot;Maps&amp;quot; question===&lt;br /&gt;
&lt;br /&gt;
At last years Google Code in a student created an extension to the &amp;quot;short text&amp;quot; question type so it can be used as a &amp;quot;Maps&amp;quot; question type. If this feature is activated at the advanced question settings, the user will be displayed a map at the survey and he/she can place a mark on that map indicating a certain location. The results are then stored a s a text string with lat./long. data.&lt;br /&gt;
&lt;br /&gt;
Unfortunately [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service no real documentation exists] for this type of questions so your task would be to play around with the different settingsm, find out what each setting is used for and then extend the according section at the manual and create a short video tutorial explaining how this question type works.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Explaining what the question can be used for&lt;br /&gt;
#A summary of the most important settings&lt;br /&gt;
#Two sample setups for this question type&lt;br /&gt;
#Showing how the question look slike at the survey&lt;br /&gt;
#Showing how the recorded results wil look like&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service available &amp;quot;Maps&amp;quot; question type settings]&lt;br /&gt;
*Play around with them to find out what each setting does&lt;br /&gt;
*Extend/complete the documentation at our wiki&lt;br /&gt;
*Create a short video tutorial on how to use that question type&lt;br /&gt;
*Submit the documentation and video to your mentor for review.&lt;br /&gt;
*Discuss the results with your mentor and eventually overwork some parts&lt;br /&gt;
*Submit your video to your mentor and complete the codumentation at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create demo surveys for the most important features===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a wide range of features. Some of them are a little complex to set up in a survey. To help new users getting familiar with these feature, we intend to create several sample surveys which users can easily download from our manual and import for testing.&lt;br /&gt;
&lt;br /&gt;
Each survey should contain 8-10 questions, depending on the feature that is demonstrated.&lt;br /&gt;
&lt;br /&gt;
List of sample surveys:&lt;br /&gt;
#Use of [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#Array_Filter_and_Array_Filter_Exclusion array filter and array exclusive option]&lt;br /&gt;
#How to set different types of [http://docs.limesurvey.org/tiki-index.php?page=Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions]&lt;br /&gt;
#Create a quiz using [http://docs.limesurvey.org/tiki-index.php?page=Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments ]and [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier] to show the users answers at the end of the survey.&lt;br /&gt;
#Screen users by making use of [http://docs.limesurvey.org/tiki-index.php?page=Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas]&lt;br /&gt;
#Demonstrate the use of ~10 different [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey question attributes].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Get familiar with Limesurvey by using our [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey demo ]or installing Limesurvey yourself.&lt;br /&gt;
*Read the documentation linked above.&lt;br /&gt;
*Create a first survey and ask your mentor for feedback.&lt;br /&gt;
*Create the rest of the surveys.&lt;br /&gt;
*Create a topic in our forum and ask for some user feedback.&lt;br /&gt;
*Add feedback where useful.&lt;br /&gt;
*Merge all surveys in a big demo survey using group/question import/export while keeping the smaller survey versions.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Creating surveys using Limesurvey, communicate with coomunity|| easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Training: Create a &amp;quot;How to design a &#039;&#039;good&#039;&#039; survey&amp;quot; tutorial===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Our manual describes all available features in detail but we don&#039;t have instructions on how to create a good survey yet, e.g. users might have huge matrix question which are all mandatory at their survey, that&#039;s a no go. Your task is to find out about some basics of survey design by asking google and asking our experienced users at the forum and then collect that data and structure it so we can have a list of issues one should take care of when designing a survey.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a new forum topic explaining your task and asking for user feedback. Ask your mentor to also link this post at www.limesurvey.org and to twitter about it.&lt;br /&gt;
*Ask Google about the important issues when creating an online survey&lt;br /&gt;
*Sum up all information and create a structured document which deals with different parts to take care of.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Port all the details to a new wiki page&lt;br /&gt;
*Add the wiki page at a new tipps &amp;amp; tricks section of our wiki&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Using search engines, writing documentation|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new expression engine===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The enxt Limesurvey version will use a powerful Expression Manager which can be used for conditions, assessments, advanced filterinfg and many more. Since this feature is a little complex, it would be nice to have a video tutorial on how to set up the according expressions for certain features.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Expression manager documentation here: http://docs.limesurvey.org/Expression+Manager and here: http://docs.limesurvey.org/Expression+Manager+HowTos&lt;br /&gt;
*Create a list of the most important features for which the Expression manager can be used.&lt;br /&gt;
*Discuss the list with your mentor and think which parts should be covered at the video tutorial.&lt;br /&gt;
*Create a video tutorial about the most important features. The users should learn how the Expression manager works and how to set up expressions for different features&lt;br /&gt;
*Show the video to your mentor and discuss necessary changes.&lt;br /&gt;
*When you are done, upload the video at Limesurvey&#039;s youtube channel and also add it at the online documentation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Screen Recording, Video and Sound Editing|| hard||twmswhite, Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Research==&lt;br /&gt;
&lt;br /&gt;
===Research: Usability testing===&lt;br /&gt;
&lt;br /&gt;
Usability testing and user input is a great source of ideas for improving your application. The goal of this assignment is to identify usability problems in LimeSurvey and discussing possible solutions for them.&lt;br /&gt;
&lt;br /&gt;
The general steps for this assignment would be:&lt;br /&gt;
#Work with LimeSurvey like a regular user would&lt;br /&gt;
##Set up a new survey&lt;br /&gt;
##Answer the survey at least once&lt;br /&gt;
##Make changes to the survey&lt;br /&gt;
##Use and export the results&lt;br /&gt;
##&amp;amp;hellip; (be creative!)&lt;br /&gt;
#Identify usability problems in LimeSurvey&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#Write a social media post (blog, facebook, twitter) about your work at LimeSurvey, discuss the problems you have found and the ideas your propose to solve them.&lt;br /&gt;
##Tell others about what you have done during this assignment and how awesome LimeSurvey and their dev team is.&lt;br /&gt;
&lt;br /&gt;
For this assignment it is possible to make use of LimeService . LimeService provides free LimeSurvey installs for small users and requires no installation (even though installation could be a usability test in itself! How easy is it to install LimeSurvey). We advice to google for common usability problems before starting this assignment as a source of inspiration.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||None, skills in web development are a plus|| Easy||ttielu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Use Google Analytics to create a report about the common Limesurvey user===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses Google Analytics to gather some basic background information about our users like where they come from, which browser they are using, which pages are visited most and the like. Because Google Analyitcs offers a lot of information we need a summary of the most important details. That&#039;s where you can give a helping hand.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will grant you access to our Google Analytics account so you can play around with the data a little&lt;br /&gt;
*Have a look at the available information and create a list of available data. Mark which data you consider important.&lt;br /&gt;
*Discuss the list and your proposed priorities with your mentor&lt;br /&gt;
*After we have agreed on the information the final report should include, gather the required information and create a report containing a 1 page summary plus 3-4 pages of additional information and charts.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Create a news article for the www.limesurvey.org website summing up your findings.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||writing reports (MS WOrd/Excel)|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Question types===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
Now there are more than 20 question types at Limesurvey and we are planning to extend some of them. Therefore we need to know which question types are used most by our users.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the available question types at http://docs.limesurvey.org/Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Survey related features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
There are several survey related features like [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions], [http://docs.limesurvey.org/Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments] or [http://docs.limesurvey.org/Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas] but we don&#039;t really kniow to what extend they are used.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at [http://docs.limesurvey.org/English+Instructions+for+LimeSurvey&amp;amp;structure;=English+Instructions+for+LimeSurvey the Limesurvey documentation] and make a list of survey related features&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Limesurvey user feedback on templates and GUI design===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
After having ported the code to a PHP framework recently, we are planning to now focus on improving the really outdated GUI. Therefore we need to know what our users think about the current GUI and where we should start working. It&#039;s your task to have a look at the current GUI and think about some GUI related questions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin interface and make some notes about things you like and things you don&#039;t like.&lt;br /&gt;
*Import a test survey containing all question types (we can provide such a survey) and test it using the shipped templates. Create a like/dislike list.&lt;br /&gt;
*Have a look at your lists and think how we can ask other users about the issues you noted. This includes rating questions and open text questions.&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor.&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Limesurvey|| difficult||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Create a report on the &amp;quot;Limesurvey user feedback on templates and GUI design survey&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
One of these surveys includes comments about how we can improve the GUI. There will be lots of text comments so we need to sum them up in a report.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Wait until someone has completed the &amp;quot;Research: Limesurvey user feedback on templates and GUI design&amp;quot; task. There should be at least ~50 responses to that survey&lt;br /&gt;
*Export the survey results and check the text comments.&lt;br /&gt;
*There will be several similar comments like &amp;quot;the icons suck&amp;quot;. Sum them up and create a list about what is top priority.&lt;br /&gt;
*Create a report which should also include the closed questions and write a short summary text (~ 20 sentences)&lt;br /&gt;
*Discuss the finding with your mentor and eventually overwork the report.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey, report writing, data summary|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Icon creation===&lt;br /&gt;
&lt;br /&gt;
As easy as it is sounds icon creation is a demanding task. Icons have to fit to the existing theme and their meaning must be untuitive without being hard on the eye. We want you to create three icons for for LimeSurvey that represent the following entities:&lt;br /&gt;
*Survey&lt;br /&gt;
*Question group&lt;br /&gt;
*Question&lt;br /&gt;
&lt;br /&gt;
The icons must fit to the existing theme and shoudl be create using Inkscape as SVG file.&lt;br /&gt;
#Have a look at our existing icons in the LimeSurvey interface&lt;br /&gt;
#Have a look at our existing icons in SVG format in our Subversion repository at https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/original art&lt;br /&gt;
#Create a couple drafts with a tool of your choice&lt;br /&gt;
#Discuss the drafts with your mentor&lt;br /&gt;
#Create the final icons&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Design, Inkscape|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the token screen:&lt;br /&gt;
*Problem: When switching to the token admin screen you don&#039;t see a list of available tokens. You have to click on the &amp;quot;Display Tokens&amp;quot; icon first.&lt;br /&gt;
*Solution: List all tokens below the &amp;quot;Token Summary&amp;quot; and above the &amp;quot;Token database options&amp;quot;.&lt;br /&gt;
*Problem: After having added a token entry you only see a short &amp;quot;New token was added&amp;quot; message with options to display tokens or add another token.&lt;br /&gt;
*Solution: It would be better to show the confirmation as a pop-up, like it is done after having added answer options or having changed global settings, and directly move on to the &amp;quot;add token entry&amp;quot; page because usually users want to add several token entries one by one.&lt;br /&gt;
*Alternative solution: When adding a token have two radio options above the save button: a) add another token after save (should be default) OR b) display tokens after save.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece, for this task /admin/tokens.php is a good start&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Survey designer workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the survey designer at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the survey designer:&lt;br /&gt;
*Problem: When adding new answer option and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text. For following answer options the text is deleted automatically when clicking into the input field.&lt;br /&gt;
*Solution: Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Problem: When creating a new survey there are options to import or copy a survey. BUT there is a &amp;quot;save&amp;quot; button after the &amp;quot;import/copy survey&amp;quot; button as well. This is irritating because users might click the save button instead and then an error message will show up because no survey title etc. was entered at the previous tabs&lt;br /&gt;
*Solution: Hide &amp;quot;save&amp;quot; button at import and copy tab.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User and rights management workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when adding users and settings rights at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the user management and rights setting screens.&lt;br /&gt;
*Problem: After having added a new user there is a summary screen showing the username and email address. You can either click &amp;quot;continue&amp;quot; to get to the user list summary or click the &amp;quot;set user permissions&amp;quot; button which leads you to the next logical step of setting the permissions for this user (a user without any permissions set doesn&#039;t make much sense).&lt;br /&gt;
*Solution: We should show the summary as a pop uf and automatically redirect the admin to the screen where permissions for the newly added user can be set.&lt;br /&gt;
*Problem: After having set permissions as the next workflow step described below, the user receives a short status update and can only click &amp;quot;continue&amp;quot; which leads him to the user overview.&lt;br /&gt;
*Solution: We should automatically redirect the admin to the user overview and show the status update as a pop-up. We could also think about redirecting him to the screen where template permissions can be set which would be the next logical step.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=We want your ideas!=&lt;br /&gt;
&lt;br /&gt;
What floats your boat? Do you have another idea that gets you excited? Discuss your ideas in our [http://www.limesurvey.org/component/option,com_fireboard/Itemid,105/func,view/catid,11/id,24710/lang,en/ forums], [https://lists.sourceforge.net/lists/listinfo/limesurvey-developers mailing lists] or at #limesurvey on irc.freenode.net.&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=GSoC_Getting_Started How to get started with LimeSurvey]&lt;br /&gt;
&lt;br /&gt;
How to Get Started With LimeSurvey:&lt;br /&gt;
&lt;br /&gt;
- setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2037</id>
		<title>LimeSurvey project ideas for Google Code-in 2011</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2037"/>
		<updated>2011-12-05T10:00:11Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome=&lt;br /&gt;
&lt;br /&gt;
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an [http://code.google.com/opensource/gci/2010-11/faqs.html eligible candidate] for the GCI program.&lt;br /&gt;
&lt;br /&gt;
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)&lt;br /&gt;
&lt;br /&gt;
All tasks aim at the development version 2.0a.&lt;br /&gt;
&lt;br /&gt;
=How to claim a task=&lt;br /&gt;
&lt;br /&gt;
All tasks below will be entered in the [http://www.google-melange.com/gci/program/list_tasks/google/gci2011 Google Code-in task tracker] (which is not yet available). You have to be a registered Google Code-In participant to claim a task.&lt;br /&gt;
&lt;br /&gt;
=Task ideas=&lt;br /&gt;
&lt;br /&gt;
==Idea Template==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is just a template you can use to add your ideas:&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: &amp;lt;myname&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Second wave==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;...add your ideas here...&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Documentation/Translation: (GERMAN) Merge article &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot; and add new/missing parts of english article &amp;quot;The template editor&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;The template editor&amp;quot; has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot;. For the reason of simplicity and unity both articles should be merged together. If the english article &amp;quot;The template editor&amp;quot; has new/missing parts this parts should be translated and added to the new merged article.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Then have a look at the german page at http://docs.limesurvey.org/Der+Vorlagen+Editor and http://docs.limesurvey.org/Templates+++Styles&lt;br /&gt;
*Merge the information from http://docs.limesurvey.org/Templates+++Styles into http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Copy the missing parts to a fitting place of http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Rewrite the article http://docs.limesurvey.org/Der+Vorlagen+Editor that it sounds acceptable.&lt;br /&gt;
*Compare http://docs.limesurvey.org/Der+Vorlagen+Editor with http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Translate new/missing parts of http://docs.limesurvey.org/The+template+editor into german and add them to http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
*Discuss the article http://docs.limesurvey.org/Der+Vorlagen+Editor with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German and English language|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation: Update the Limesurvey 2.0 database layout===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Enable filling out additional token attributes when registering for a survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: Update the German version of the english &amp;quot;optional settings&amp;quot; wiki page===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;optional settings&amp;quot; wiki page (http://docs.limesurvey.org/Optional+settings) holds information about Limesurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.&lt;br /&gt;
&lt;br /&gt;
The German version of this page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen) is outdated and needs to be updated based on the english page.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the &amp;quot;documentation&amp;quot; link on the Limesurvey main page.&lt;br /&gt;
*Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&lt;br /&gt;
*Port the document structure (page sections) to the German page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen)&lt;br /&gt;
*Check which settings are missing -&amp;gt; add those&lt;br /&gt;
*Check which settings are incomplete -&amp;gt; extend those&lt;br /&gt;
*Check which settings are not listd at the english version -&amp;gt; delete those&lt;br /&gt;
*When you are done, check carefuly if no settings is missing&lt;br /&gt;
*If you have any questions about a certain setting, ask it here, your mentor will be notified.&lt;br /&gt;
*When you are done, submit your work here (just give the link to the translated page).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German language, wiki editing|| moderate||Mazi, mot&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: Translate the english &amp;quot;optional settings&amp;quot; wiki page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;optional settings&amp;quot; wiki page (http://docs.limesurvey.org/Optional+settings) holds information about Limesurvey settings for certain parts of the programm that are to be set at the config.php file and are not included at the global settings.&lt;br /&gt;
&lt;br /&gt;
A Spanish version of this page (http://docs.limesurvey.org/tiki-index.php?page=Optionale+Einstellungen) doesn&#039;t exist and needs to be created based on the english page.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Create a user account at www.limesurvey.org. This can be used to log in at the wiki as well. After having registered, click the &amp;quot;documentation&amp;quot; link on the Limesurvey main page.&lt;br /&gt;
*Have a look at the english base page: http://docs.limesurvey.org/tiki-index.php?page=Optional+settings&lt;br /&gt;
*On top right, choose the option to translate the current english version and assign the new page a matching name and the Spanish language&lt;br /&gt;
*Translate the english page to Spanish&lt;br /&gt;
*When you are done, check carefuly if no settings is missing&lt;br /&gt;
*If you have any questions about a certain setting, ask it here, your mentor will be notified.&lt;br /&gt;
*When you are done, submit your work here (just give the link to the translated page).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Spanish language, wiki editing|| difficult||Mazi, holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation: Include description from question type articles into question types overview page===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;Question Types&amp;quot;, http://docs.limesurvey.org/Question+types has its own description and images. It would be better to include the description from the question type articles. This can make maintenance easier.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
* Use http://docs.limesurvey.org/English+Instructions+for+LimeSurvey to get to the articles for the question types. For example, the first is &amp;quot;Question type - Array&amp;quot; at http://docs.limesurvey.org/Question+type+-+Array .&lt;br /&gt;
* If the article doesn&#039;t have a header called &amp;quot;short description&amp;quot; (Wiki: &amp;lt;nowiki&amp;gt;!Short description&amp;lt;/nowiki&amp;gt;) add the short description header.&lt;br /&gt;
* The short description should be short and tell the user in one to three sentences what this question type is used for. You can use the existing description in the article if it fits well or copy and customise it. After your work is done it should look like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Short description=&lt;br /&gt;
&lt;br /&gt;
An array allows you to create subquestions as your left hand headings, and let your participants respond to a series of possible answers options using those subquestions.&lt;br /&gt;
&lt;br /&gt;
[[File:F_AFL.jpg]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
*Have a look at the english page http://docs.limesurvey.org/Question+types&lt;br /&gt;
*Discuss your changes with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German and English language|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==First wave (already ported to GCi system)==&lt;br /&gt;
&lt;br /&gt;
==Localization==&lt;br /&gt;
&lt;br /&gt;
===Localization: Translate LimeSurvey to your mother language===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.&lt;br /&gt;
*Read the documentation on [[how to update a translation or how to create a new one.|Translating LimeSurvey]]&lt;br /&gt;
*Translate as crazy - check your translation using a local copy of LimeSurvey.&lt;br /&gt;
*Submit your updated/new translation to us.&lt;br /&gt;
&lt;br /&gt;
Updating a translation from &amp;lt;70% to 100%:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Translation|| Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
New translation (at least 50%):&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Translation|| Moderate ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced qustion attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute update the German translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Tokens&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Installer&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the German translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;--&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions update the French translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Tokens&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Installer&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the French translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;---&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Question types&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Question types&amp;quot; page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Question+types english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Tokens&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn&#039;t exist yet. Your task is to create the Spanish translation of that wiki page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Translate the page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Spanish and English language|| difficult||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Installer&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the Spanish translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Usability changes for LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey, play around with the interface.&lt;br /&gt;
*Pick a couple things you would like to change to have better usability&lt;br /&gt;
*Discuss the found issues with your mentor&lt;br /&gt;
*Together we will either pick one of your found issues or the mentor will make an suggestion for another change.&lt;br /&gt;
*Code the usability change and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and the mentor&lt;br /&gt;
*If necessary make re-submit patch with discusse changes&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, HTML, CSS, maybe SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement &amp;quot;Embedd all text answers&amp;quot; setting at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.&lt;br /&gt;
&lt;br /&gt;
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new &amp;quot;Embedd all text answers&amp;quot; setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with text questions and add some dummy data.&lt;br /&gt;
*Have a look at the data summary and the available export options.&lt;br /&gt;
*Add a &amp;quot;Embedd all text answers&amp;quot; setting.&lt;br /&gt;
*Implement the code to embedd that data and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, some very basic HTML, SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement Google map at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a &amp;quot;Map&amp;quot; question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users&#039; answers at that overview.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a map question and add some dummy data.&lt;br /&gt;
*Have a look at the admin statistics of that question.&lt;br /&gt;
*Implement the code to embedd a Map and mark the users&#039; answers in there and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing)|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at token overview table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the token overview and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Difficult ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at browse response table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we&#039;ll hand that to you) and add some test answer data.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the browse response table and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve drag and drop functionality at attribute mapping===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Aniessh&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Central Participant&#039;s Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Create some attributes at the token level.&lt;br /&gt;
*Create some attributes at the Central Participant Database panel.&lt;br /&gt;
*Copy the previously added dummy people from token table to the central table.&lt;br /&gt;
*You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.&lt;br /&gt;
*Suggest how to improve the user interface.&lt;br /&gt;
*Improve the user interface and create a patch.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add drag and drop feature to ranking question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey contains a &amp;quot;ranking&amp;quot; question type (see http://docs.limesurvey.org/Question+type+-+Ranking&amp;amp;structure;=English+Instructions+for+LimeSurvey) which isn&#039;t very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.&lt;br /&gt;
&lt;br /&gt;
There is already a [http://docs.limesurvey.org/Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#Drag_and_Drop_Rankings workaround] and a [http://www.partnersinc.biz/surveys//index.php?sid=36981&amp;amp;newtest;=Y&amp;amp;lang;=en demo version] available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a test survey with ranking question types and different question attributes&lt;br /&gt;
*Have a look at the question type within the survey to see what could be improved.&lt;br /&gt;
*Check the workaround linked above and the demo survey to see where we would like to go to.&lt;br /&gt;
*Implement a generic solution to make the ranking question type a little nicer (no DB changes required).&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Javascript, PHP, CSS|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add option to switch between bar chart and pie chart at statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.&lt;br /&gt;
*Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.&lt;br /&gt;
*Discuss your suggestions with your mentor and together create a concept how to deal with the problem.&lt;br /&gt;
*Implement a generic solution.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||PHP, MySQL, a little HTML|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Refactor the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find a class or method with smelly (bad) code&lt;br /&gt;
*Discuss the code smell with the mentor and make a proposal on how to improve the code&lt;br /&gt;
*Work out the improvement and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen smell)||PHP, CodeIgniter (depending on chosen smell)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Make unit tests for the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find an untested class which could use some testing&lt;br /&gt;
*Discuss the badly tested class/method with the mentor and make a proposal on how to test the code&lt;br /&gt;
*Write tests for class/method and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen class/method)||PHP, CodeIgniter (depending on chosen class/method)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring HTML into views : CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Browse Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Check Integrity Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Conditions Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Database Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Data Entry Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Email Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Export Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Labels Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Printable Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Group Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Quotas Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Saved Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Statistics Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Permission Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Tokens Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Translate Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Groups Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite template editor wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the template editor documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite the survey settings page===&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Create a tutorial about how to replace the logo at a shipped template===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Problem is that some HTML and CSS knowledge is needed to fully style a template and this might be a problem to the common user. Usually replacing the logo at one of the shipped templates is all they need so the goal is to write a step by step tutorial with some screen shots about how to replace the logo.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing documentation about templates and create a new entry at the [http://docs.limesurvey.org/The+template+editor&amp;amp;structure;=English+Instructions+for+LimeSurvey#Tips_amp_Tricks Tipps &amp;amp; Tricks sub-section].&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Check the template editor at our demo system and note how the logos are embedded at different templates&lt;br /&gt;
*Write a step by step tutorial including screen shots on how to replace the images and/or change the logo file name at the templates&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
*Discuss your tutorial with your mentor and if necessary overwork some parts&lt;br /&gt;
* Add everything at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Wiki editing, LimeSurvey, HTML|| Easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite statistics wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers public statistics, which are shown to the user at the end of the survey, as well as more detailed statistics at the admin backend. The [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey current statistics documentation] is outdated and not very well structured. Lots of users don&#039;t know that they can filter data and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the statistics more clear to the user, the documentation should be updated, extended and better structured. A video showing how to set filters and demonstrating other statistic features should be added, too.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import the sample survey at /docs/demosurveys which contains all question types.&lt;br /&gt;
*Enable public statistics for this survey and all questions that are supported by this feature.&lt;br /&gt;
*Fill out the survey ~20-30 times (ask your friends for some help) to create some data to be used by the statistics.&lt;br /&gt;
*Explore the public and admin backend statistics and write down which features are available.&lt;br /&gt;
*Ask your mentor if all features are on your list.&lt;br /&gt;
*Think about a new structure for the wiki page&lt;br /&gt;
*Document each section and describe each feature in detail. Add some nice screenshots where appropriate.&lt;br /&gt;
*Create a short video showing how to set filters and use other important features.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Wiki editing, LimeSurvey, video capture|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite installation procedure.===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey 2.0 has a new automatic installer which makes installation process a cake-walk. Hence, installation procedure needs to be updated explaining each and every step of the installation procedure and possible errors/warnings that a user might see during installation of LimeSurvey and there solutions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Checkout LimeSurvey_CI branch.&lt;br /&gt;
*Read existing installation procedure.&lt;br /&gt;
*Run the automatic installer and play with it.&lt;br /&gt;
*Compare the missing things and update the wiki.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Make a troubleshooting section on installation wikipage which should contain possible warnings a user might see and there solution(s).&lt;br /&gt;
*Create a short video tutorial on how to install LimeSurvey.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Wiki editing, creating screen shots, writing documentation, creating videos|| difficult||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; Marketing==&lt;br /&gt;
&lt;br /&gt;
===Outreach: Blog about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
Write an independant article about LimeSurvey on your blog. Explain what are advantages, what are disadavantages of the software - show how to create a first survey and also write about problems are on the way getting there. Motivate people to participate to help use make LimeSurvey better. The article should be in-depth and correct. It should help other to get hooked up without false promises.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Use LimeSurvey to setup your own survey (you can use our demo version for that)&lt;br /&gt;
*Blog about your experience after discussing your article with us.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days|| Writing skills || Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee engagement survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An introduction.&lt;br /&gt;
#Setting up an employee engagement survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee engagement survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee engagement survey.&lt;br /&gt;
*Discuss the employee engagement metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an employee satisfaction survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee satisfaction survey.&lt;br /&gt;
*iscuss the employee satisfaction metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Blog about LimeSurvey (2)===&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
&lt;br /&gt;
- Research how a general basic customer satisfaction survey should look like&lt;br /&gt;
&lt;br /&gt;
- Create it in LimeSurvey&lt;br /&gt;
&lt;br /&gt;
- Write about your experience in setting this up.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Survey Creation, Technical Writing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey to create and distribute a customer satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
Show current and potential LimeSurvey users how they can use LimeSurvey to do customer satisfaction surveys.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an customer satisfaction survey with LimeSurvey.&lt;br /&gt;
#Importing the tokens into the customer satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide a link to the example customer satisfaction survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey and test it.&lt;br /&gt;
*Discuss the customer satisfaction metrics measured with your mentor.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Analyse user feedback and port suggestions to our idea tracker===&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey [http://survey.limesurvey.org/ conducts user feedback surveys] to find out how our users use the software and which features they are missing. We received quite a lot feedback during the last months and a lot of valuable information can be found at the textual feedback. It&#039;s a mixture of praise, suggestions for new features and other useful comments. This needs to be summed up. Also useful suggestions for new features should be ported to [http://ideas.limesurvey.org/ our idea tracker] so we have this on our list for future development.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will give you access to our survey system so you can export the survey data into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list of common complaints, suggested features and the like.&lt;br /&gt;
*Once you are done, order the lists by frequency and present it to your mentor.&lt;br /&gt;
*Your mentor will go through your list and mark those ideas worth porting to the idea tracker.&lt;br /&gt;
*Add ideas to the idea tracker&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Data analysis, Report Writing, Using idea tracker|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Training==&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a custom survey template===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Create a video tutorial showing users how to create a copy of the default template and modify it.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#An overview of the template editor and a description of what each area of the template editor is used for.&lt;br /&gt;
#An explanation of the different screens.&lt;br /&gt;
#Inserting a company logo in to the template.&lt;br /&gt;
#Basic adjustments in the css to modify the appearance of questions.&lt;br /&gt;
#Customizing the survey description page.&lt;br /&gt;
#Customizing the end page.&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a new survey from scratch===&lt;br /&gt;
&lt;br /&gt;
There are several videos around explaining how to create a survey with LimeSurvey. Unfortunately most of the are pretty outdated and old. We would like to have a kick-all video tutorial explaining how to create a survey that immediately will hook up people.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Creation of a survey, with an easy explanation of the concept behind it (Survey-&amp;gt;Question groups-&amp;gt;Questions)&lt;br /&gt;
#Creating the survey, explaining the most important settings&lt;br /&gt;
#Creating question groups and questions plus answers&lt;br /&gt;
#Showing off a number of question types&lt;br /&gt;
#Showing off how a simple condition is created.&lt;br /&gt;
#Activating the survey&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a &amp;quot;Maps&amp;quot; question===&lt;br /&gt;
&lt;br /&gt;
At last years Google Code in a student created an extension to the &amp;quot;short text&amp;quot; question type so it can be used as a &amp;quot;Maps&amp;quot; question type. If this feature is activated at the advanced question settings, the user will be displayed a map at the survey and he/she can place a mark on that map indicating a certain location. The results are then stored a s a text string with lat./long. data.&lt;br /&gt;
&lt;br /&gt;
Unfortunately [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service no real documentation exists] for this type of questions so your task would be to play around with the different settingsm, find out what each setting is used for and then extend the according section at the manual and create a short video tutorial explaining how this question type works.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Explaining what the question can be used for&lt;br /&gt;
#A summary of the most important settings&lt;br /&gt;
#Two sample setups for this question type&lt;br /&gt;
#Showing how the question look slike at the survey&lt;br /&gt;
#Showing how the recorded results wil look like&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service available &amp;quot;Maps&amp;quot; question type settings]&lt;br /&gt;
*Play around with them to find out what each setting does&lt;br /&gt;
*Extend/complete the documentation at our wiki&lt;br /&gt;
*Create a short video tutorial on how to use that question type&lt;br /&gt;
*Submit the documentation and video to your mentor for review.&lt;br /&gt;
*Discuss the results with your mentor and eventually overwork some parts&lt;br /&gt;
*Submit your video to your mentor and complete the codumentation at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create demo surveys for the most important features===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a wide range of features. Some of them are a little complex to set up in a survey. To help new users getting familiar with these feature, we intend to create several sample surveys which users can easily download from our manual and import for testing.&lt;br /&gt;
&lt;br /&gt;
Each survey should contain 8-10 questions, depending on the feature that is demonstrated.&lt;br /&gt;
&lt;br /&gt;
List of sample surveys:&lt;br /&gt;
#Use of [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#Array_Filter_and_Array_Filter_Exclusion array filter and array exclusive option]&lt;br /&gt;
#How to set different types of [http://docs.limesurvey.org/tiki-index.php?page=Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions]&lt;br /&gt;
#Create a quiz using [http://docs.limesurvey.org/tiki-index.php?page=Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments ]and [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier] to show the users answers at the end of the survey.&lt;br /&gt;
#Screen users by making use of [http://docs.limesurvey.org/tiki-index.php?page=Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas]&lt;br /&gt;
#Demonstrate the use of ~10 different [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey question attributes].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Get familiar with Limesurvey by using our [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey demo ]or installing Limesurvey yourself.&lt;br /&gt;
*Read the documentation linked above.&lt;br /&gt;
*Create a first survey and ask your mentor for feedback.&lt;br /&gt;
*Create the rest of the surveys.&lt;br /&gt;
*Create a topic in our forum and ask for some user feedback.&lt;br /&gt;
*Add feedback where useful.&lt;br /&gt;
*Merge all surveys in a big demo survey using group/question import/export while keeping the smaller survey versions.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Creating surveys using Limesurvey, communicate with coomunity|| easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Training: Create a &amp;quot;How to design a &#039;&#039;good&#039;&#039; survey&amp;quot; tutorial===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Our manual describes all available features in detail but we don&#039;t have instructions on how to create a good survey yet, e.g. users might have huge matrix question which are all mandatory at their survey, that&#039;s a no go. Your task is to find out about some basics of survey design by asking google and asking our experienced users at the forum and then collect that data and structure it so we can have a list of issues one should take care of when designing a survey.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a new forum topic explaining your task and asking for user feedback. Ask your mentor to also link this post at www.limesurvey.org and to twitter about it.&lt;br /&gt;
*Ask Google about the important issues when creating an online survey&lt;br /&gt;
*Sum up all information and create a structured document which deals with different parts to take care of.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Port all the details to a new wiki page&lt;br /&gt;
*Add the wiki page at a new tipps &amp;amp; tricks section of our wiki&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Using search engines, writing documentation|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new expression engine===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The enxt Limesurvey version will use a powerful Expression Manager which can be used for conditions, assessments, advanced filterinfg and many more. Since this feature is a little complex, it would be nice to have a video tutorial on how to set up the according expressions for certain features.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Expression manager documentation here: http://docs.limesurvey.org/Expression+Manager and here: http://docs.limesurvey.org/Expression+Manager+HowTos&lt;br /&gt;
*Create a list of the most important features for which the Expression manager can be used.&lt;br /&gt;
*Discuss the list with your mentor and think which parts should be covered at the video tutorial.&lt;br /&gt;
*Create a video tutorial about the most important features. The users should learn how the Expression manager works and how to set up expressions for different features&lt;br /&gt;
*Show the video to your mentor and discuss necessary changes.&lt;br /&gt;
*When you are done, upload the video at Limesurvey&#039;s youtube channel and also add it at the online documentation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Screen Recording, Video and Sound Editing|| hard||twmswhite, Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Research==&lt;br /&gt;
&lt;br /&gt;
===Research: Usability testing===&lt;br /&gt;
&lt;br /&gt;
Usability testing and user input is a great source of ideas for improving your application. The goal of this assignment is to identify usability problems in LimeSurvey and discussing possible solutions for them.&lt;br /&gt;
&lt;br /&gt;
The general steps for this assignment would be:&lt;br /&gt;
#Work with LimeSurvey like a regular user would&lt;br /&gt;
##Set up a new survey&lt;br /&gt;
##Answer the survey at least once&lt;br /&gt;
##Make changes to the survey&lt;br /&gt;
##Use and export the results&lt;br /&gt;
##&amp;amp;hellip; (be creative!)&lt;br /&gt;
#Identify usability problems in LimeSurvey&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#Write a social media post (blog, facebook, twitter) about your work at LimeSurvey, discuss the problems you have found and the ideas your propose to solve them.&lt;br /&gt;
##Tell others about what you have done during this assignment and how awesome LimeSurvey and their dev team is.&lt;br /&gt;
&lt;br /&gt;
For this assignment it is possible to make use of LimeService . LimeService provides free LimeSurvey installs for small users and requires no installation (even though installation could be a usability test in itself! How easy is it to install LimeSurvey). We advice to google for common usability problems before starting this assignment as a source of inspiration.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||None, skills in web development are a plus|| Easy||ttielu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Use Google Analytics to create a report about the common Limesurvey user===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses Google Analytics to gather some basic background information about our users like where they come from, which browser they are using, which pages are visited most and the like. Because Google Analyitcs offers a lot of information we need a summary of the most important details. That&#039;s where you can give a helping hand.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will grant you access to our Google Analytics account so you can play around with the data a little&lt;br /&gt;
*Have a look at the available information and create a list of available data. Mark which data you consider important.&lt;br /&gt;
*Discuss the list and your proposed priorities with your mentor&lt;br /&gt;
*After we have agreed on the information the final report should include, gather the required information and create a report containing a 1 page summary plus 3-4 pages of additional information and charts.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Create a news article for the www.limesurvey.org website summing up your findings.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||writing reports (MS WOrd/Excel)|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Question types===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
Now there are more than 20 question types at Limesurvey and we are planning to extend some of them. Therefore we need to know which question types are used most by our users.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the available question types at http://docs.limesurvey.org/Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Survey related features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
There are several survey related features like [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions], [http://docs.limesurvey.org/Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments] or [http://docs.limesurvey.org/Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas] but we don&#039;t really kniow to what extend they are used.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at [http://docs.limesurvey.org/English+Instructions+for+LimeSurvey&amp;amp;structure;=English+Instructions+for+LimeSurvey the Limesurvey documentation] and make a list of survey related features&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Limesurvey user feedback on templates and GUI design===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
After having ported the code to a PHP framework recently, we are planning to now focus on improving the really outdated GUI. Therefore we need to know what our users think about the current GUI and where we should start working. It&#039;s your task to have a look at the current GUI and think about some GUI related questions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin interface and make some notes about things you like and things you don&#039;t like.&lt;br /&gt;
*Import a test survey containing all question types (we can provide such a survey) and test it using the shipped templates. Create a like/dislike list.&lt;br /&gt;
*Have a look at your lists and think how we can ask other users about the issues you noted. This includes rating questions and open text questions.&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor.&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Limesurvey|| difficult||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Create a report on the &amp;quot;Limesurvey user feedback on templates and GUI design survey&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
One of these surveys includes comments about how we can improve the GUI. There will be lots of text comments so we need to sum them up in a report.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Wait until someone has completed the &amp;quot;Research: Limesurvey user feedback on templates and GUI design&amp;quot; task. There should be at least ~50 responses to that survey&lt;br /&gt;
*Export the survey results and check the text comments.&lt;br /&gt;
*There will be several similar comments like &amp;quot;the icons suck&amp;quot;. Sum them up and create a list about what is top priority.&lt;br /&gt;
*Create a report which should also include the closed questions and write a short summary text (~ 20 sentences)&lt;br /&gt;
*Discuss the finding with your mentor and eventually overwork the report.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey, report writing, data summary|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Icon creation===&lt;br /&gt;
&lt;br /&gt;
As easy as it is sounds icon creation is a demanding task. Icons have to fit to the existing theme and their meaning must be untuitive without being hard on the eye. We want you to create three icons for for LimeSurvey that represent the following entities:&lt;br /&gt;
*Survey&lt;br /&gt;
*Question group&lt;br /&gt;
*Question&lt;br /&gt;
&lt;br /&gt;
The icons must fit to the existing theme and shoudl be create using Inkscape as SVG file.&lt;br /&gt;
#Have a look at our existing icons in the LimeSurvey interface&lt;br /&gt;
#Have a look at our existing icons in SVG format in our Subversion repository at https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/original art&lt;br /&gt;
#Create a couple drafts with a tool of your choice&lt;br /&gt;
#Discuss the drafts with your mentor&lt;br /&gt;
#Create the final icons&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Design, Inkscape|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the token screen:&lt;br /&gt;
*Problem: When switching to the token admin screen you don&#039;t see a list of available tokens. You have to click on the &amp;quot;Display Tokens&amp;quot; icon first.&lt;br /&gt;
*Solution: List all tokens below the &amp;quot;Token Summary&amp;quot; and above the &amp;quot;Token database options&amp;quot;.&lt;br /&gt;
*Problem: After having added a token entry you only see a short &amp;quot;New token was added&amp;quot; message with options to display tokens or add another token.&lt;br /&gt;
*Solution: It would be better to show the confirmation as a pop-up, like it is done after having added answer options or having changed global settings, and directly move on to the &amp;quot;add token entry&amp;quot; page because usually users want to add several token entries one by one.&lt;br /&gt;
*Alternative solution: When adding a token have two radio options above the save button: a) add another token after save (should be default) OR b) display tokens after save.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece, for this task /admin/tokens.php is a good start&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Survey designer workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the survey designer at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the survey designer:&lt;br /&gt;
*Problem: When adding new answer option and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text. For following answer options the text is deleted automatically when clicking into the input field.&lt;br /&gt;
*Solution: Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Problem: When creating a new survey there are options to import or copy a survey. BUT there is a &amp;quot;save&amp;quot; button after the &amp;quot;import/copy survey&amp;quot; button as well. This is irritating because users might click the save button instead and then an error message will show up because no survey title etc. was entered at the previous tabs&lt;br /&gt;
*Solution: Hide &amp;quot;save&amp;quot; button at import and copy tab.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User and rights management workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when adding users and settings rights at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the user management and rights setting screens.&lt;br /&gt;
*Problem: After having added a new user there is a summary screen showing the username and email address. You can either click &amp;quot;continue&amp;quot; to get to the user list summary or click the &amp;quot;set user permissions&amp;quot; button which leads you to the next logical step of setting the permissions for this user (a user without any permissions set doesn&#039;t make much sense).&lt;br /&gt;
*Solution: We should show the summary as a pop uf and automatically redirect the admin to the screen where permissions for the newly added user can be set.&lt;br /&gt;
*Problem: After having set permissions as the next workflow step described below, the user receives a short status update and can only click &amp;quot;continue&amp;quot; which leads him to the user overview.&lt;br /&gt;
*Solution: We should automatically redirect the admin to the user overview and show the status update as a pop-up. We could also think about redirecting him to the screen where template permissions can be set which would be the next logical step.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=We want your ideas!=&lt;br /&gt;
&lt;br /&gt;
What floats your boat? Do you have another idea that gets you excited? Discuss your ideas in our [http://www.limesurvey.org/component/option,com_fireboard/Itemid,105/func,view/catid,11/id,24710/lang,en/ forums], [https://lists.sourceforge.net/lists/listinfo/limesurvey-developers mailing lists] or at #limesurvey on irc.freenode.net.&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=GSoC_Getting_Started How to get started with LimeSurvey]&lt;br /&gt;
&lt;br /&gt;
How to Get Started With LimeSurvey:&lt;br /&gt;
&lt;br /&gt;
- setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2040</id>
		<title>LimeSurvey project ideas for Google Code-in 2011</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2040"/>
		<updated>2011-11-23T08:22:01Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome=&lt;br /&gt;
&lt;br /&gt;
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an [http://code.google.com/opensource/gci/2010-11/faqs.html eligible candidate] for the GCI program.&lt;br /&gt;
&lt;br /&gt;
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)&lt;br /&gt;
&lt;br /&gt;
All tasks aim at the development version 2.0a.&lt;br /&gt;
&lt;br /&gt;
=How to claim a task=&lt;br /&gt;
&lt;br /&gt;
All tasks below will be entered in the [http://www.google-melange.com/gci/program/list_tasks/google/gci2011 Google Code-in task tracker] (which is not yet available). You have to be a registered Google Code-In participant to claim a task.&lt;br /&gt;
&lt;br /&gt;
=Task ideas=&lt;br /&gt;
&lt;br /&gt;
==Idea Template==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is just a template you can use to add your ideas:&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: &amp;lt;myname&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Second wave==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;...add your ideas here...&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Documentation/Translation: (GERMAN) Merge article &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot; and add new/missing parts of english article &amp;quot;The template editor&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;The template editor&amp;quot; has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot;. For the reason of simplicity and unity both articles should be merged together. If the english article &amp;quot;The template editor&amp;quot; has new/missing parts this parts should be translated and added to the new merged article.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Then have a look at the german page at http://docs.limesurvey.org/Der+Vorlagen+Editor and http://docs.limesurvey.org/Templates+++Styles&lt;br /&gt;
*Merge the information from http://docs.limesurvey.org/Templates+++Styles into http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Copy the missing parts to a fitting place of http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Rewrite the article http://docs.limesurvey.org/Der+Vorlagen+Editor that it sounds acceptable.&lt;br /&gt;
*Compare http://docs.limesurvey.org/Der+Vorlagen+Editor with http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Translate new/missing parts of http://docs.limesurvey.org/The+template+editor into german and add them to http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
*Discuss the article http://docs.limesurvey.org/Der+Vorlagen+Editor with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||German and English language|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==First wave (already ported to GCi system)==&lt;br /&gt;
&lt;br /&gt;
==Localization==&lt;br /&gt;
&lt;br /&gt;
===Localization: Translate LimeSurvey to your mother language===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.&lt;br /&gt;
*Read the documentation on [[how to update a translation or how to create a new one.|Translating LimeSurvey]]&lt;br /&gt;
*Translate as crazy - check your translation using a local copy of LimeSurvey.&lt;br /&gt;
*Submit your updated/new translation to us.&lt;br /&gt;
&lt;br /&gt;
Updating a translation from &amp;lt;70% to 100%:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Translation|| Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
New translation (at least 50%):&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Translation|| Moderate ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced qustion attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute update the German translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Tokens&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Installer&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the German translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;--&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions update the French translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Tokens&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Installer&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the French translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;---&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Question types&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Question types&amp;quot; page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Question+types english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Tokens&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn&#039;t exist yet. Your task is to create the Spanish translation of that wiki page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Translate the page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Spanish and English language|| difficult||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Installer&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the Spanish translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Usability changes for LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey, play around with the interface.&lt;br /&gt;
*Pick a couple things you would like to change to have better usability&lt;br /&gt;
*Discuss the found issues with your mentor&lt;br /&gt;
*Together we will either pick one of your found issues or the mentor will make an suggestion for another change.&lt;br /&gt;
*Code the usability change and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and the mentor&lt;br /&gt;
*If necessary make re-submit patch with discusse changes&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, HTML, CSS, maybe SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement &amp;quot;Embedd all text answers&amp;quot; setting at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.&lt;br /&gt;
&lt;br /&gt;
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new &amp;quot;Embedd all text answers&amp;quot; setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with text questions and add some dummy data.&lt;br /&gt;
*Have a look at the data summary and the available export options.&lt;br /&gt;
*Add a &amp;quot;Embedd all text answers&amp;quot; setting.&lt;br /&gt;
*Implement the code to embedd that data and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, some very basic HTML, SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement Google map at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a &amp;quot;Map&amp;quot; question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users&#039; answers at that overview.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a map question and add some dummy data.&lt;br /&gt;
*Have a look at the admin statistics of that question.&lt;br /&gt;
*Implement the code to embedd a Map and mark the users&#039; answers in there and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing)|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at token overview table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the token overview and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Difficult ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at browse response table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we&#039;ll hand that to you) and add some test answer data.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the browse response table and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve drag and drop functionality at attribute mapping===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Aniessh&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Central Participant&#039;s Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Create some attributes at the token level.&lt;br /&gt;
*Create some attributes at the Central Participant Database panel.&lt;br /&gt;
*Copy the previously added dummy people from token table to the central table.&lt;br /&gt;
*You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.&lt;br /&gt;
*Suggest how to improve the user interface.&lt;br /&gt;
*Improve the user interface and create a patch.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add drag and drop feature to ranking question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey contains a &amp;quot;ranking&amp;quot; question type (see http://docs.limesurvey.org/Question+type+-+Ranking&amp;amp;structure;=English+Instructions+for+LimeSurvey) which isn&#039;t very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.&lt;br /&gt;
&lt;br /&gt;
There is already a [http://docs.limesurvey.org/Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#Drag_and_Drop_Rankings workaround] and a [http://www.partnersinc.biz/surveys//index.php?sid=36981&amp;amp;newtest;=Y&amp;amp;lang;=en demo version] available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a test survey with ranking question types and different question attributes&lt;br /&gt;
*Have a look at the question type within the survey to see what could be improved.&lt;br /&gt;
*Check the workaround linked above and the demo survey to see where we would like to go to.&lt;br /&gt;
*Implement a generic solution to make the ranking question type a little nicer (no DB changes required).&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Javascript, PHP, CSS|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add option to switch between bar chart and pie chart at statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.&lt;br /&gt;
*Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.&lt;br /&gt;
*Discuss your suggestions with your mentor and together create a concept how to deal with the problem.&lt;br /&gt;
*Implement a generic solution.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||PHP, MySQL, a little HTML|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Refactor the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find a class or method with smelly (bad) code&lt;br /&gt;
*Discuss the code smell with the mentor and make a proposal on how to improve the code&lt;br /&gt;
*Work out the improvement and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen smell)||PHP, CodeIgniter (depending on chosen smell)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Make unit tests for the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find an untested class which could use some testing&lt;br /&gt;
*Discuss the badly tested class/method with the mentor and make a proposal on how to test the code&lt;br /&gt;
*Write tests for class/method and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen class/method)||PHP, CodeIgniter (depending on chosen class/method)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring HTML into views : CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Browse Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Check Integrity Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Conditions Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Database Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Data Entry Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Email Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Export Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Labels Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Printable Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Group Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Quotas Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Saved Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Statistics Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Permission Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Tokens Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Translate Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Groups Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite template editor wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the template editor documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite the survey settings page===&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Create a tutorial about how to replace the logo at a shipped template===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Problem is that some HTML and CSS knowledge is needed to fully style a template and this might be a problem to the common user. Usually replacing the logo at one of the shipped templates is all they need so the goal is to write a step by step tutorial with some screen shots about how to replace the logo.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing documentation about templates and create a new entry at the [http://docs.limesurvey.org/The+template+editor&amp;amp;structure;=English+Instructions+for+LimeSurvey#Tips_amp_Tricks Tipps &amp;amp; Tricks sub-section].&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Check the template editor at our demo system and note how the logos are embedded at different templates&lt;br /&gt;
*Write a step by step tutorial including screen shots on how to replace the images and/or change the logo file name at the templates&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
*Discuss your tutorial with your mentor and if necessary overwork some parts&lt;br /&gt;
* Add everything at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Wiki editing, LimeSurvey, HTML|| Easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite statistics wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers public statistics, which are shown to the user at the end of the survey, as well as more detailed statistics at the admin backend. The [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey current statistics documentation] is outdated and not very well structured. Lots of users don&#039;t know that they can filter data and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the statistics more clear to the user, the documentation should be updated, extended and better structured. A video showing how to set filters and demonstrating other statistic features should be added, too.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import the sample survey at /docs/demosurveys which contains all question types.&lt;br /&gt;
*Enable public statistics for this survey and all questions that are supported by this feature.&lt;br /&gt;
*Fill out the survey ~20-30 times (ask your friends for some help) to create some data to be used by the statistics.&lt;br /&gt;
*Explore the public and admin backend statistics and write down which features are available.&lt;br /&gt;
*Ask your mentor if all features are on your list.&lt;br /&gt;
*Think about a new structure for the wiki page&lt;br /&gt;
*Document each section and describe each feature in detail. Add some nice screenshots where appropriate.&lt;br /&gt;
*Create a short video showing how to set filters and use other important features.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Wiki editing, LimeSurvey, video capture|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite installation procedure.===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey 2.0 has a new automatic installer which makes installation process a cake-walk. Hence, installation procedure needs to be updated explaining each and every step of the installation procedure and possible errors/warnings that a user might see during installation of LimeSurvey and there solutions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Checkout LimeSurvey_CI branch.&lt;br /&gt;
*Read existing installation procedure.&lt;br /&gt;
*Run the automatic installer and play with it.&lt;br /&gt;
*Compare the missing things and update the wiki.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Make a troubleshooting section on installation wikipage which should contain possible warnings a user might see and there solution(s).&lt;br /&gt;
*Create a short video tutorial on how to install LimeSurvey.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Wiki editing, creating screen shots, writing documentation, creating videos|| difficult||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; Marketing==&lt;br /&gt;
&lt;br /&gt;
===Outreach: Blog about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
Write an independant article about LimeSurvey on your blog. Explain what are advantages, what are disadavantages of the software - show how to create a first survey and also write about problems are on the way getting there. Motivate people to participate to help use make LimeSurvey better. The article should be in-depth and correct. It should help other to get hooked up without false promises.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Use LimeSurvey to setup your own survey (you can use our demo version for that)&lt;br /&gt;
*Blog about your experience after discussing your article with us.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days|| Writing skills || Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee engagement survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An introduction.&lt;br /&gt;
#Setting up an employee engagement survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee engagement survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee engagement survey.&lt;br /&gt;
*Discuss the employee engagement metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an employee satisfaction survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee satisfaction survey.&lt;br /&gt;
*iscuss the employee satisfaction metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Blog about LimeSurvey (2)===&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
&lt;br /&gt;
- Research how a general basic customer satisfaction survey should look like&lt;br /&gt;
&lt;br /&gt;
- Create it in LimeSurvey&lt;br /&gt;
&lt;br /&gt;
- Write about your experience in setting this up.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Survey Creation, Technical Writing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey to create and distribute a customer satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
Show current and potential LimeSurvey users how they can use LimeSurvey to do customer satisfaction surveys.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an customer satisfaction survey with LimeSurvey.&lt;br /&gt;
#Importing the tokens into the customer satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide a link to the example customer satisfaction survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey and test it.&lt;br /&gt;
*Discuss the customer satisfaction metrics measured with your mentor.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Analyse user feedback and port suggestions to our idea tracker===&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey [http://survey.limesurvey.org/ conducts user feedback surveys] to find out how our users use the software and which features they are missing. We received quite a lot feedback during the last months and a lot of valuable information can be found at the textual feedback. It&#039;s a mixture of praise, suggestions for new features and other useful comments. This needs to be summed up. Also useful suggestions for new features should be ported to [http://ideas.limesurvey.org/ our idea tracker] so we have this on our list for future development.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will give you access to our survey system so you can export the survey data into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list of common complaints, suggested features and the like.&lt;br /&gt;
*Once you are done, order the lists by frequency and present it to your mentor.&lt;br /&gt;
*Your mentor will go through your list and mark those ideas worth porting to the idea tracker.&lt;br /&gt;
*Add ideas to the idea tracker&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Data analysis, Report Writing, Using idea tracker|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Training==&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a custom survey template===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Create a video tutorial showing users how to create a copy of the default template and modify it.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#An overview of the template editor and a description of what each area of the template editor is used for.&lt;br /&gt;
#An explanation of the different screens.&lt;br /&gt;
#Inserting a company logo in to the template.&lt;br /&gt;
#Basic adjustments in the css to modify the appearance of questions.&lt;br /&gt;
#Customizing the survey description page.&lt;br /&gt;
#Customizing the end page.&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a new survey from scratch===&lt;br /&gt;
&lt;br /&gt;
There are several videos around explaining how to create a survey with LimeSurvey. Unfortunately most of the are pretty outdated and old. We would like to have a kick-all video tutorial explaining how to create a survey that immediately will hook up people.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Creation of a survey, with an easy explanation of the concept behind it (Survey-&amp;gt;Question groups-&amp;gt;Questions)&lt;br /&gt;
#Creating the survey, explaining the most important settings&lt;br /&gt;
#Creating question groups and questions plus answers&lt;br /&gt;
#Showing off a number of question types&lt;br /&gt;
#Showing off how a simple condition is created.&lt;br /&gt;
#Activating the survey&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a &amp;quot;Maps&amp;quot; question===&lt;br /&gt;
&lt;br /&gt;
At last years Google Code in a student created an extension to the &amp;quot;short text&amp;quot; question type so it can be used as a &amp;quot;Maps&amp;quot; question type. If this feature is activated at the advanced question settings, the user will be displayed a map at the survey and he/she can place a mark on that map indicating a certain location. The results are then stored a s a text string with lat./long. data.&lt;br /&gt;
&lt;br /&gt;
Unfortunately [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service no real documentation exists] for this type of questions so your task would be to play around with the different settingsm, find out what each setting is used for and then extend the according section at the manual and create a short video tutorial explaining how this question type works.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Explaining what the question can be used for&lt;br /&gt;
#A summary of the most important settings&lt;br /&gt;
#Two sample setups for this question type&lt;br /&gt;
#Showing how the question look slike at the survey&lt;br /&gt;
#Showing how the recorded results wil look like&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service available &amp;quot;Maps&amp;quot; question type settings]&lt;br /&gt;
*Play around with them to find out what each setting does&lt;br /&gt;
*Extend/complete the documentation at our wiki&lt;br /&gt;
*Create a short video tutorial on how to use that question type&lt;br /&gt;
*Submit the documentation and video to your mentor for review.&lt;br /&gt;
*Discuss the results with your mentor and eventually overwork some parts&lt;br /&gt;
*Submit your video to your mentor and complete the codumentation at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create demo surveys for the most important features===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a wide range of features. Some of them are a little complex to set up in a survey. To help new users getting familiar with these feature, we intend to create several sample surveys which users can easily download from our manual and import for testing.&lt;br /&gt;
&lt;br /&gt;
Each survey should contain 8-10 questions, depending on the feature that is demonstrated.&lt;br /&gt;
&lt;br /&gt;
List of sample surveys:&lt;br /&gt;
#Use of [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#Array_Filter_and_Array_Filter_Exclusion array filter and array exclusive option]&lt;br /&gt;
#How to set different types of [http://docs.limesurvey.org/tiki-index.php?page=Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions]&lt;br /&gt;
#Create a quiz using [http://docs.limesurvey.org/tiki-index.php?page=Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments ]and [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier] to show the users answers at the end of the survey.&lt;br /&gt;
#Screen users by making use of [http://docs.limesurvey.org/tiki-index.php?page=Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas]&lt;br /&gt;
#Demonstrate the use of ~10 different [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey question attributes].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Get familiar with Limesurvey by using our [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey demo ]or installing Limesurvey yourself.&lt;br /&gt;
*Read the documentation linked above.&lt;br /&gt;
*Create a first survey and ask your mentor for feedback.&lt;br /&gt;
*Create the rest of the surveys.&lt;br /&gt;
*Create a topic in our forum and ask for some user feedback.&lt;br /&gt;
*Add feedback where useful.&lt;br /&gt;
*Merge all surveys in a big demo survey using group/question import/export while keeping the smaller survey versions.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Creating surveys using Limesurvey, communicate with coomunity|| easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Training: Create a &amp;quot;How to design a &#039;&#039;good&#039;&#039; survey&amp;quot; tutorial===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Our manual describes all available features in detail but we don&#039;t have instructions on how to create a good survey yet, e.g. users might have huge matrix question which are all mandatory at their survey, that&#039;s a no go. Your task is to find out about some basics of survey design by asking google and asking our experienced users at the forum and then collect that data and structure it so we can have a list of issues one should take care of when designing a survey.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a new forum topic explaining your task and asking for user feedback. Ask your mentor to also link this post at www.limesurvey.org and to twitter about it.&lt;br /&gt;
*Ask Google about the important issues when creating an online survey&lt;br /&gt;
*Sum up all information and create a structured document which deals with different parts to take care of.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Port all the details to a new wiki page&lt;br /&gt;
*Add the wiki page at a new tipps &amp;amp; tricks section of our wiki&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Using search engines, writing documentation|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new expression engine===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The enxt Limesurvey version will use a powerful Expression Manager which can be used for conditions, assessments, advanced filterinfg and many more. Since this feature is a little complex, it would be nice to have a video tutorial on how to set up the according expressions for certain features.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Expression manager documentation here: http://docs.limesurvey.org/Expression+Manager and here: http://docs.limesurvey.org/Expression+Manager+HowTos&lt;br /&gt;
*Create a list of the most important features for which the Expression manager can be used.&lt;br /&gt;
*Discuss the list with your mentor and think which parts should be covered at the video tutorial.&lt;br /&gt;
*Create a video tutorial about the most important features. The users should learn how the Expression manager works and how to set up expressions for different features&lt;br /&gt;
*Show the video to your mentor and discuss necessary changes.&lt;br /&gt;
*When you are done, upload the video at Limesurvey&#039;s youtube channel and also add it at the online documentation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Screen Recording, Video and Sound Editing|| hard||twmswhite, Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Research==&lt;br /&gt;
&lt;br /&gt;
===Research: Usability testing===&lt;br /&gt;
&lt;br /&gt;
Usability testing and user input is a great source of ideas for improving your application. The goal of this assignment is to identify usability problems in LimeSurvey and discussing possible solutions for them.&lt;br /&gt;
&lt;br /&gt;
The general steps for this assignment would be:&lt;br /&gt;
#Work with LimeSurvey like a regular user would&lt;br /&gt;
##Set up a new survey&lt;br /&gt;
##Answer the survey at least once&lt;br /&gt;
##Make changes to the survey&lt;br /&gt;
##Use and export the results&lt;br /&gt;
##&amp;amp;hellip; (be creative!)&lt;br /&gt;
#Identify usability problems in LimeSurvey&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#Write a social media post (blog, facebook, twitter) about your work at LimeSurvey, discuss the problems you have found and the ideas your propose to solve them.&lt;br /&gt;
##Tell others about what you have done during this assignment and how awesome LimeSurvey and their dev team is.&lt;br /&gt;
&lt;br /&gt;
For this assignment it is possible to make use of LimeService . LimeService provides free LimeSurvey installs for small users and requires no installation (even though installation could be a usability test in itself! How easy is it to install LimeSurvey). We advice to google for common usability problems before starting this assignment as a source of inspiration.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||None, skills in web development are a plus|| Easy||ttielu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Use Google Analytics to create a report about the common Limesurvey user===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses Google Analytics to gather some basic background information about our users like where they come from, which browser they are using, which pages are visited most and the like. Because Google Analyitcs offers a lot of information we need a summary of the most important details. That&#039;s where you can give a helping hand.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will grant you access to our Google Analytics account so you can play around with the data a little&lt;br /&gt;
*Have a look at the available information and create a list of available data. Mark which data you consider important.&lt;br /&gt;
*Discuss the list and your proposed priorities with your mentor&lt;br /&gt;
*After we have agreed on the information the final report should include, gather the required information and create a report containing a 1 page summary plus 3-4 pages of additional information and charts.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Create a news article for the www.limesurvey.org website summing up your findings.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||writing reports (MS WOrd/Excel)|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Question types===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
Now there are more than 20 question types at Limesurvey and we are planning to extend some of them. Therefore we need to know which question types are used most by our users.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the available question types at http://docs.limesurvey.org/Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Survey related features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
There are several survey related features like [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions], [http://docs.limesurvey.org/Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments] or [http://docs.limesurvey.org/Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas] but we don&#039;t really kniow to what extend they are used.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at [http://docs.limesurvey.org/English+Instructions+for+LimeSurvey&amp;amp;structure;=English+Instructions+for+LimeSurvey the Limesurvey documentation] and make a list of survey related features&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Limesurvey user feedback on templates and GUI design===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
After having ported the code to a PHP framework recently, we are planning to now focus on improving the really outdated GUI. Therefore we need to know what our users think about the current GUI and where we should start working. It&#039;s your task to have a look at the current GUI and think about some GUI related questions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin interface and make some notes about things you like and things you don&#039;t like.&lt;br /&gt;
*Import a test survey containing all question types (we can provide such a survey) and test it using the shipped templates. Create a like/dislike list.&lt;br /&gt;
*Have a look at your lists and think how we can ask other users about the issues you noted. This includes rating questions and open text questions.&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor.&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Limesurvey|| difficult||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Create a report on the &amp;quot;Limesurvey user feedback on templates and GUI design survey&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
One of these surveys includes comments about how we can improve the GUI. There will be lots of text comments so we need to sum them up in a report.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Wait until someone has completed the &amp;quot;Research: Limesurvey user feedback on templates and GUI design&amp;quot; task. There should be at least ~50 responses to that survey&lt;br /&gt;
*Export the survey results and check the text comments.&lt;br /&gt;
*There will be several similar comments like &amp;quot;the icons suck&amp;quot;. Sum them up and create a list about what is top priority.&lt;br /&gt;
*Create a report which should also include the closed questions and write a short summary text (~ 20 sentences)&lt;br /&gt;
*Discuss the finding with your mentor and eventually overwork the report.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey, report writing, data summary|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Icon creation===&lt;br /&gt;
&lt;br /&gt;
As easy as it is sounds icon creation is a demanding task. Icons have to fit to the existing theme and their meaning must be untuitive without being hard on the eye. We want you to create three icons for for LimeSurvey that represent the following entities:&lt;br /&gt;
*Survey&lt;br /&gt;
*Question group&lt;br /&gt;
*Question&lt;br /&gt;
&lt;br /&gt;
The icons must fit to the existing theme and shoudl be create using Inkscape as SVG file.&lt;br /&gt;
#Have a look at our existing icons in the LimeSurvey interface&lt;br /&gt;
#Have a look at our existing icons in SVG format in our Subversion repository at https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/original art&lt;br /&gt;
#Create a couple drafts with a tool of your choice&lt;br /&gt;
#Discuss the drafts with your mentor&lt;br /&gt;
#Create the final icons&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Design, Inkscape|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the token screen:&lt;br /&gt;
*Problem: When switching to the token admin screen you don&#039;t see a list of available tokens. You have to click on the &amp;quot;Display Tokens&amp;quot; icon first.&lt;br /&gt;
*Solution: List all tokens below the &amp;quot;Token Summary&amp;quot; and above the &amp;quot;Token database options&amp;quot;.&lt;br /&gt;
*Problem: After having added a token entry you only see a short &amp;quot;New token was added&amp;quot; message with options to display tokens or add another token.&lt;br /&gt;
*Solution: It would be better to show the confirmation as a pop-up, like it is done after having added answer options or having changed global settings, and directly move on to the &amp;quot;add token entry&amp;quot; page because usually users want to add several token entries one by one.&lt;br /&gt;
*Alternative solution: When adding a token have two radio options above the save button: a) add another token after save (should be default) OR b) display tokens after save.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece, for this task /admin/tokens.php is a good start&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Survey designer workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the survey designer at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the survey designer:&lt;br /&gt;
*Problem: When adding new answer option and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text. For following answer options the text is deleted automatically when clicking into the input field.&lt;br /&gt;
*Solution: Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Problem: When creating a new survey there are options to import or copy a survey. BUT there is a &amp;quot;save&amp;quot; button after the &amp;quot;import/copy survey&amp;quot; button as well. This is irritating because users might click the save button instead and then an error message will show up because no survey title etc. was entered at the previous tabs&lt;br /&gt;
*Solution: Hide &amp;quot;save&amp;quot; button at import and copy tab.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User and rights management workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when adding users and settings rights at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the user management and rights setting screens.&lt;br /&gt;
*Problem: After having added a new user there is a summary screen showing the username and email address. You can either click &amp;quot;continue&amp;quot; to get to the user list summary or click the &amp;quot;set user permissions&amp;quot; button which leads you to the next logical step of setting the permissions for this user (a user without any permissions set doesn&#039;t make much sense).&lt;br /&gt;
*Solution: We should show the summary as a pop uf and automatically redirect the admin to the screen where permissions for the newly added user can be set.&lt;br /&gt;
*Problem: After having set permissions as the next workflow step described below, the user receives a short status update and can only click &amp;quot;continue&amp;quot; which leads him to the user overview.&lt;br /&gt;
*Solution: We should automatically redirect the admin to the user overview and show the status update as a pop-up. We could also think about redirecting him to the screen where template permissions can be set which would be the next logical step.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=We want your ideas!=&lt;br /&gt;
&lt;br /&gt;
What floats your boat? Do you have another idea that gets you excited? Discuss your ideas in our [http://www.limesurvey.org/component/option,com_fireboard/Itemid,105/func,view/catid,11/id,24710/lang,en/ forums], [https://lists.sourceforge.net/lists/listinfo/limesurvey-developers mailing lists] or at #limesurvey on irc.freenode.net.&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=GSoC_Getting_Started How to get started with LimeSurvey]&lt;br /&gt;
&lt;br /&gt;
How to Get Started With LimeSurvey:&lt;br /&gt;
&lt;br /&gt;
- setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2041</id>
		<title>LimeSurvey project ideas for Google Code-in 2011</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2041"/>
		<updated>2011-11-23T08:20:08Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome=&lt;br /&gt;
&lt;br /&gt;
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an [http://code.google.com/opensource/gci/2010-11/faqs.html eligible candidate] for the GCI program.&lt;br /&gt;
&lt;br /&gt;
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)&lt;br /&gt;
&lt;br /&gt;
All tasks aim at the development version 2.0a.&lt;br /&gt;
&lt;br /&gt;
=How to claim a task=&lt;br /&gt;
&lt;br /&gt;
All tasks below will be entered in the [http://www.google-melange.com/gci/program/list_tasks/google/gci2011 Google Code-in task tracker] (which is not yet available). You have to be a registered Google Code-In participant to claim a task.&lt;br /&gt;
&lt;br /&gt;
=Task ideas=&lt;br /&gt;
&lt;br /&gt;
==Idea Template==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is just a template you can use to add your ideas:&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: &amp;lt;myname&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Second wave==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;...add your ideas here...&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Documentation/Translation: (GERMAN) Merge article &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot; and add new/missing parts of english article &amp;quot;The template editor&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;The template editor&amp;quot; has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot;. For the reason of simplicity and unity both articles should be merged together. If the english article &amp;quot;The template editor&amp;quot; has new/missing parts this parts should be translated and added to the new merged article.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Then have a look at the german page at http://docs.limesurvey.org/Der+Vorlagen+Editor and http://docs.limesurvey.org/Templates+++Styles&lt;br /&gt;
*Merge the information from http://docs.limesurvey.org/Templates+++Styles into http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Copy the missing parts to a fitting place of http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
**Rewrite the article http://docs.limesurvey.org/Der+Vorlagen+Editor that it sounds acceptable.&lt;br /&gt;
*Compare http://docs.limesurvey.org/Der+Vorlagen+Editor with http://docs.limesurvey.org/The+template+editor&lt;br /&gt;
*Translate new/missing parts of http://docs.limesurvey.org/The+template+editor into german and add them to http://docs.limesurvey.org/Der+Vorlagen+Editor&lt;br /&gt;
*Discuss the article http://docs.limesurvey.org/Der+Vorlagen+Editor with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==First wave (already ported to GCi system)==&lt;br /&gt;
&lt;br /&gt;
==Localization==&lt;br /&gt;
&lt;br /&gt;
===Localization: Translate LimeSurvey to your mother language===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.&lt;br /&gt;
*Read the documentation on [[how to update a translation or how to create a new one.|Translating LimeSurvey]]&lt;br /&gt;
*Translate as crazy - check your translation using a local copy of LimeSurvey.&lt;br /&gt;
*Submit your updated/new translation to us.&lt;br /&gt;
&lt;br /&gt;
Updating a translation from &amp;lt;70% to 100%:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Translation|| Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
New translation (at least 50%):&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Translation|| Moderate ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced qustion attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute update the German translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Tokens&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Installer&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the German translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;--&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions update the French translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Tokens&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Installer&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the French translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;---&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Question types&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Question types&amp;quot; page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Question+types english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Tokens&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn&#039;t exist yet. Your task is to create the Spanish translation of that wiki page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Translate the page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Spanish and English language|| difficult||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Installer&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the Spanish translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Usability changes for LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey, play around with the interface.&lt;br /&gt;
*Pick a couple things you would like to change to have better usability&lt;br /&gt;
*Discuss the found issues with your mentor&lt;br /&gt;
*Together we will either pick one of your found issues or the mentor will make an suggestion for another change.&lt;br /&gt;
*Code the usability change and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and the mentor&lt;br /&gt;
*If necessary make re-submit patch with discusse changes&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, HTML, CSS, maybe SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement &amp;quot;Embedd all text answers&amp;quot; setting at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.&lt;br /&gt;
&lt;br /&gt;
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new &amp;quot;Embedd all text answers&amp;quot; setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with text questions and add some dummy data.&lt;br /&gt;
*Have a look at the data summary and the available export options.&lt;br /&gt;
*Add a &amp;quot;Embedd all text answers&amp;quot; setting.&lt;br /&gt;
*Implement the code to embedd that data and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, some very basic HTML, SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement Google map at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a &amp;quot;Map&amp;quot; question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users&#039; answers at that overview.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a map question and add some dummy data.&lt;br /&gt;
*Have a look at the admin statistics of that question.&lt;br /&gt;
*Implement the code to embedd a Map and mark the users&#039; answers in there and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing)|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at token overview table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the token overview and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Difficult ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at browse response table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we&#039;ll hand that to you) and add some test answer data.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the browse response table and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve drag and drop functionality at attribute mapping===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Aniessh&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Central Participant&#039;s Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Create some attributes at the token level.&lt;br /&gt;
*Create some attributes at the Central Participant Database panel.&lt;br /&gt;
*Copy the previously added dummy people from token table to the central table.&lt;br /&gt;
*You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.&lt;br /&gt;
*Suggest how to improve the user interface.&lt;br /&gt;
*Improve the user interface and create a patch.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add drag and drop feature to ranking question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey contains a &amp;quot;ranking&amp;quot; question type (see http://docs.limesurvey.org/Question+type+-+Ranking&amp;amp;structure;=English+Instructions+for+LimeSurvey) which isn&#039;t very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.&lt;br /&gt;
&lt;br /&gt;
There is already a [http://docs.limesurvey.org/Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#Drag_and_Drop_Rankings workaround] and a [http://www.partnersinc.biz/surveys//index.php?sid=36981&amp;amp;newtest;=Y&amp;amp;lang;=en demo version] available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a test survey with ranking question types and different question attributes&lt;br /&gt;
*Have a look at the question type within the survey to see what could be improved.&lt;br /&gt;
*Check the workaround linked above and the demo survey to see where we would like to go to.&lt;br /&gt;
*Implement a generic solution to make the ranking question type a little nicer (no DB changes required).&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Javascript, PHP, CSS|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add option to switch between bar chart and pie chart at statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.&lt;br /&gt;
*Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.&lt;br /&gt;
*Discuss your suggestions with your mentor and together create a concept how to deal with the problem.&lt;br /&gt;
*Implement a generic solution.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||PHP, MySQL, a little HTML|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Refactor the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find a class or method with smelly (bad) code&lt;br /&gt;
*Discuss the code smell with the mentor and make a proposal on how to improve the code&lt;br /&gt;
*Work out the improvement and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen smell)||PHP, CodeIgniter (depending on chosen smell)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Make unit tests for the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find an untested class which could use some testing&lt;br /&gt;
*Discuss the badly tested class/method with the mentor and make a proposal on how to test the code&lt;br /&gt;
*Write tests for class/method and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen class/method)||PHP, CodeIgniter (depending on chosen class/method)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring HTML into views : CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Browse Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Check Integrity Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Conditions Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Database Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Data Entry Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Email Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Export Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Labels Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Printable Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Group Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Quotas Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Saved Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Statistics Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Permission Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Tokens Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Translate Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Groups Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite template editor wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the template editor documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite the survey settings page===&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Create a tutorial about how to replace the logo at a shipped template===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Problem is that some HTML and CSS knowledge is needed to fully style a template and this might be a problem to the common user. Usually replacing the logo at one of the shipped templates is all they need so the goal is to write a step by step tutorial with some screen shots about how to replace the logo.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing documentation about templates and create a new entry at the [http://docs.limesurvey.org/The+template+editor&amp;amp;structure;=English+Instructions+for+LimeSurvey#Tips_amp_Tricks Tipps &amp;amp; Tricks sub-section].&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Check the template editor at our demo system and note how the logos are embedded at different templates&lt;br /&gt;
*Write a step by step tutorial including screen shots on how to replace the images and/or change the logo file name at the templates&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
*Discuss your tutorial with your mentor and if necessary overwork some parts&lt;br /&gt;
* Add everything at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Wiki editing, LimeSurvey, HTML|| Easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite statistics wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers public statistics, which are shown to the user at the end of the survey, as well as more detailed statistics at the admin backend. The [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey current statistics documentation] is outdated and not very well structured. Lots of users don&#039;t know that they can filter data and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the statistics more clear to the user, the documentation should be updated, extended and better structured. A video showing how to set filters and demonstrating other statistic features should be added, too.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import the sample survey at /docs/demosurveys which contains all question types.&lt;br /&gt;
*Enable public statistics for this survey and all questions that are supported by this feature.&lt;br /&gt;
*Fill out the survey ~20-30 times (ask your friends for some help) to create some data to be used by the statistics.&lt;br /&gt;
*Explore the public and admin backend statistics and write down which features are available.&lt;br /&gt;
*Ask your mentor if all features are on your list.&lt;br /&gt;
*Think about a new structure for the wiki page&lt;br /&gt;
*Document each section and describe each feature in detail. Add some nice screenshots where appropriate.&lt;br /&gt;
*Create a short video showing how to set filters and use other important features.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Wiki editing, LimeSurvey, video capture|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite installation procedure.===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey 2.0 has a new automatic installer which makes installation process a cake-walk. Hence, installation procedure needs to be updated explaining each and every step of the installation procedure and possible errors/warnings that a user might see during installation of LimeSurvey and there solutions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Checkout LimeSurvey_CI branch.&lt;br /&gt;
*Read existing installation procedure.&lt;br /&gt;
*Run the automatic installer and play with it.&lt;br /&gt;
*Compare the missing things and update the wiki.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Make a troubleshooting section on installation wikipage which should contain possible warnings a user might see and there solution(s).&lt;br /&gt;
*Create a short video tutorial on how to install LimeSurvey.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Wiki editing, creating screen shots, writing documentation, creating videos|| difficult||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; Marketing==&lt;br /&gt;
&lt;br /&gt;
===Outreach: Blog about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
Write an independant article about LimeSurvey on your blog. Explain what are advantages, what are disadavantages of the software - show how to create a first survey and also write about problems are on the way getting there. Motivate people to participate to help use make LimeSurvey better. The article should be in-depth and correct. It should help other to get hooked up without false promises.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Use LimeSurvey to setup your own survey (you can use our demo version for that)&lt;br /&gt;
*Blog about your experience after discussing your article with us.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days|| Writing skills || Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee engagement survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An introduction.&lt;br /&gt;
#Setting up an employee engagement survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee engagement survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee engagement survey.&lt;br /&gt;
*Discuss the employee engagement metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an employee satisfaction survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee satisfaction survey.&lt;br /&gt;
*iscuss the employee satisfaction metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Blog about LimeSurvey (2)===&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
&lt;br /&gt;
- Research how a general basic customer satisfaction survey should look like&lt;br /&gt;
&lt;br /&gt;
- Create it in LimeSurvey&lt;br /&gt;
&lt;br /&gt;
- Write about your experience in setting this up.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Survey Creation, Technical Writing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey to create and distribute a customer satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
Show current and potential LimeSurvey users how they can use LimeSurvey to do customer satisfaction surveys.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an customer satisfaction survey with LimeSurvey.&lt;br /&gt;
#Importing the tokens into the customer satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide a link to the example customer satisfaction survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey and test it.&lt;br /&gt;
*Discuss the customer satisfaction metrics measured with your mentor.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Analyse user feedback and port suggestions to our idea tracker===&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey [http://survey.limesurvey.org/ conducts user feedback surveys] to find out how our users use the software and which features they are missing. We received quite a lot feedback during the last months and a lot of valuable information can be found at the textual feedback. It&#039;s a mixture of praise, suggestions for new features and other useful comments. This needs to be summed up. Also useful suggestions for new features should be ported to [http://ideas.limesurvey.org/ our idea tracker] so we have this on our list for future development.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will give you access to our survey system so you can export the survey data into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list of common complaints, suggested features and the like.&lt;br /&gt;
*Once you are done, order the lists by frequency and present it to your mentor.&lt;br /&gt;
*Your mentor will go through your list and mark those ideas worth porting to the idea tracker.&lt;br /&gt;
*Add ideas to the idea tracker&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Data analysis, Report Writing, Using idea tracker|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Training==&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a custom survey template===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Create a video tutorial showing users how to create a copy of the default template and modify it.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#An overview of the template editor and a description of what each area of the template editor is used for.&lt;br /&gt;
#An explanation of the different screens.&lt;br /&gt;
#Inserting a company logo in to the template.&lt;br /&gt;
#Basic adjustments in the css to modify the appearance of questions.&lt;br /&gt;
#Customizing the survey description page.&lt;br /&gt;
#Customizing the end page.&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a new survey from scratch===&lt;br /&gt;
&lt;br /&gt;
There are several videos around explaining how to create a survey with LimeSurvey. Unfortunately most of the are pretty outdated and old. We would like to have a kick-all video tutorial explaining how to create a survey that immediately will hook up people.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Creation of a survey, with an easy explanation of the concept behind it (Survey-&amp;gt;Question groups-&amp;gt;Questions)&lt;br /&gt;
#Creating the survey, explaining the most important settings&lt;br /&gt;
#Creating question groups and questions plus answers&lt;br /&gt;
#Showing off a number of question types&lt;br /&gt;
#Showing off how a simple condition is created.&lt;br /&gt;
#Activating the survey&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a &amp;quot;Maps&amp;quot; question===&lt;br /&gt;
&lt;br /&gt;
At last years Google Code in a student created an extension to the &amp;quot;short text&amp;quot; question type so it can be used as a &amp;quot;Maps&amp;quot; question type. If this feature is activated at the advanced question settings, the user will be displayed a map at the survey and he/she can place a mark on that map indicating a certain location. The results are then stored a s a text string with lat./long. data.&lt;br /&gt;
&lt;br /&gt;
Unfortunately [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service no real documentation exists] for this type of questions so your task would be to play around with the different settingsm, find out what each setting is used for and then extend the according section at the manual and create a short video tutorial explaining how this question type works.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Explaining what the question can be used for&lt;br /&gt;
#A summary of the most important settings&lt;br /&gt;
#Two sample setups for this question type&lt;br /&gt;
#Showing how the question look slike at the survey&lt;br /&gt;
#Showing how the recorded results wil look like&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service available &amp;quot;Maps&amp;quot; question type settings]&lt;br /&gt;
*Play around with them to find out what each setting does&lt;br /&gt;
*Extend/complete the documentation at our wiki&lt;br /&gt;
*Create a short video tutorial on how to use that question type&lt;br /&gt;
*Submit the documentation and video to your mentor for review.&lt;br /&gt;
*Discuss the results with your mentor and eventually overwork some parts&lt;br /&gt;
*Submit your video to your mentor and complete the codumentation at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create demo surveys for the most important features===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a wide range of features. Some of them are a little complex to set up in a survey. To help new users getting familiar with these feature, we intend to create several sample surveys which users can easily download from our manual and import for testing.&lt;br /&gt;
&lt;br /&gt;
Each survey should contain 8-10 questions, depending on the feature that is demonstrated.&lt;br /&gt;
&lt;br /&gt;
List of sample surveys:&lt;br /&gt;
#Use of [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#Array_Filter_and_Array_Filter_Exclusion array filter and array exclusive option]&lt;br /&gt;
#How to set different types of [http://docs.limesurvey.org/tiki-index.php?page=Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions]&lt;br /&gt;
#Create a quiz using [http://docs.limesurvey.org/tiki-index.php?page=Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments ]and [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier] to show the users answers at the end of the survey.&lt;br /&gt;
#Screen users by making use of [http://docs.limesurvey.org/tiki-index.php?page=Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas]&lt;br /&gt;
#Demonstrate the use of ~10 different [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey question attributes].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Get familiar with Limesurvey by using our [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey demo ]or installing Limesurvey yourself.&lt;br /&gt;
*Read the documentation linked above.&lt;br /&gt;
*Create a first survey and ask your mentor for feedback.&lt;br /&gt;
*Create the rest of the surveys.&lt;br /&gt;
*Create a topic in our forum and ask for some user feedback.&lt;br /&gt;
*Add feedback where useful.&lt;br /&gt;
*Merge all surveys in a big demo survey using group/question import/export while keeping the smaller survey versions.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Creating surveys using Limesurvey, communicate with coomunity|| easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Training: Create a &amp;quot;How to design a &#039;&#039;good&#039;&#039; survey&amp;quot; tutorial===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Our manual describes all available features in detail but we don&#039;t have instructions on how to create a good survey yet, e.g. users might have huge matrix question which are all mandatory at their survey, that&#039;s a no go. Your task is to find out about some basics of survey design by asking google and asking our experienced users at the forum and then collect that data and structure it so we can have a list of issues one should take care of when designing a survey.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a new forum topic explaining your task and asking for user feedback. Ask your mentor to also link this post at www.limesurvey.org and to twitter about it.&lt;br /&gt;
*Ask Google about the important issues when creating an online survey&lt;br /&gt;
*Sum up all information and create a structured document which deals with different parts to take care of.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Port all the details to a new wiki page&lt;br /&gt;
*Add the wiki page at a new tipps &amp;amp; tricks section of our wiki&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Using search engines, writing documentation|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new expression engine===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The enxt Limesurvey version will use a powerful Expression Manager which can be used for conditions, assessments, advanced filterinfg and many more. Since this feature is a little complex, it would be nice to have a video tutorial on how to set up the according expressions for certain features.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Expression manager documentation here: http://docs.limesurvey.org/Expression+Manager and here: http://docs.limesurvey.org/Expression+Manager+HowTos&lt;br /&gt;
*Create a list of the most important features for which the Expression manager can be used.&lt;br /&gt;
*Discuss the list with your mentor and think which parts should be covered at the video tutorial.&lt;br /&gt;
*Create a video tutorial about the most important features. The users should learn how the Expression manager works and how to set up expressions for different features&lt;br /&gt;
*Show the video to your mentor and discuss necessary changes.&lt;br /&gt;
*When you are done, upload the video at Limesurvey&#039;s youtube channel and also add it at the online documentation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Screen Recording, Video and Sound Editing|| hard||twmswhite, Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Research==&lt;br /&gt;
&lt;br /&gt;
===Research: Usability testing===&lt;br /&gt;
&lt;br /&gt;
Usability testing and user input is a great source of ideas for improving your application. The goal of this assignment is to identify usability problems in LimeSurvey and discussing possible solutions for them.&lt;br /&gt;
&lt;br /&gt;
The general steps for this assignment would be:&lt;br /&gt;
#Work with LimeSurvey like a regular user would&lt;br /&gt;
##Set up a new survey&lt;br /&gt;
##Answer the survey at least once&lt;br /&gt;
##Make changes to the survey&lt;br /&gt;
##Use and export the results&lt;br /&gt;
##&amp;amp;hellip; (be creative!)&lt;br /&gt;
#Identify usability problems in LimeSurvey&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#Write a social media post (blog, facebook, twitter) about your work at LimeSurvey, discuss the problems you have found and the ideas your propose to solve them.&lt;br /&gt;
##Tell others about what you have done during this assignment and how awesome LimeSurvey and their dev team is.&lt;br /&gt;
&lt;br /&gt;
For this assignment it is possible to make use of LimeService . LimeService provides free LimeSurvey installs for small users and requires no installation (even though installation could be a usability test in itself! How easy is it to install LimeSurvey). We advice to google for common usability problems before starting this assignment as a source of inspiration.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||None, skills in web development are a plus|| Easy||ttielu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Use Google Analytics to create a report about the common Limesurvey user===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses Google Analytics to gather some basic background information about our users like where they come from, which browser they are using, which pages are visited most and the like. Because Google Analyitcs offers a lot of information we need a summary of the most important details. That&#039;s where you can give a helping hand.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will grant you access to our Google Analytics account so you can play around with the data a little&lt;br /&gt;
*Have a look at the available information and create a list of available data. Mark which data you consider important.&lt;br /&gt;
*Discuss the list and your proposed priorities with your mentor&lt;br /&gt;
*After we have agreed on the information the final report should include, gather the required information and create a report containing a 1 page summary plus 3-4 pages of additional information and charts.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Create a news article for the www.limesurvey.org website summing up your findings.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||writing reports (MS WOrd/Excel)|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Question types===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
Now there are more than 20 question types at Limesurvey and we are planning to extend some of them. Therefore we need to know which question types are used most by our users.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the available question types at http://docs.limesurvey.org/Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Survey related features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
There are several survey related features like [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions], [http://docs.limesurvey.org/Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments] or [http://docs.limesurvey.org/Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas] but we don&#039;t really kniow to what extend they are used.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at [http://docs.limesurvey.org/English+Instructions+for+LimeSurvey&amp;amp;structure;=English+Instructions+for+LimeSurvey the Limesurvey documentation] and make a list of survey related features&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Limesurvey user feedback on templates and GUI design===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
After having ported the code to a PHP framework recently, we are planning to now focus on improving the really outdated GUI. Therefore we need to know what our users think about the current GUI and where we should start working. It&#039;s your task to have a look at the current GUI and think about some GUI related questions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin interface and make some notes about things you like and things you don&#039;t like.&lt;br /&gt;
*Import a test survey containing all question types (we can provide such a survey) and test it using the shipped templates. Create a like/dislike list.&lt;br /&gt;
*Have a look at your lists and think how we can ask other users about the issues you noted. This includes rating questions and open text questions.&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor.&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Limesurvey|| difficult||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Create a report on the &amp;quot;Limesurvey user feedback on templates and GUI design survey&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
One of these surveys includes comments about how we can improve the GUI. There will be lots of text comments so we need to sum them up in a report.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Wait until someone has completed the &amp;quot;Research: Limesurvey user feedback on templates and GUI design&amp;quot; task. There should be at least ~50 responses to that survey&lt;br /&gt;
*Export the survey results and check the text comments.&lt;br /&gt;
*There will be several similar comments like &amp;quot;the icons suck&amp;quot;. Sum them up and create a list about what is top priority.&lt;br /&gt;
*Create a report which should also include the closed questions and write a short summary text (~ 20 sentences)&lt;br /&gt;
*Discuss the finding with your mentor and eventually overwork the report.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey, report writing, data summary|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Icon creation===&lt;br /&gt;
&lt;br /&gt;
As easy as it is sounds icon creation is a demanding task. Icons have to fit to the existing theme and their meaning must be untuitive without being hard on the eye. We want you to create three icons for for LimeSurvey that represent the following entities:&lt;br /&gt;
*Survey&lt;br /&gt;
*Question group&lt;br /&gt;
*Question&lt;br /&gt;
&lt;br /&gt;
The icons must fit to the existing theme and shoudl be create using Inkscape as SVG file.&lt;br /&gt;
#Have a look at our existing icons in the LimeSurvey interface&lt;br /&gt;
#Have a look at our existing icons in SVG format in our Subversion repository at https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/original art&lt;br /&gt;
#Create a couple drafts with a tool of your choice&lt;br /&gt;
#Discuss the drafts with your mentor&lt;br /&gt;
#Create the final icons&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Design, Inkscape|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the token screen:&lt;br /&gt;
*Problem: When switching to the token admin screen you don&#039;t see a list of available tokens. You have to click on the &amp;quot;Display Tokens&amp;quot; icon first.&lt;br /&gt;
*Solution: List all tokens below the &amp;quot;Token Summary&amp;quot; and above the &amp;quot;Token database options&amp;quot;.&lt;br /&gt;
*Problem: After having added a token entry you only see a short &amp;quot;New token was added&amp;quot; message with options to display tokens or add another token.&lt;br /&gt;
*Solution: It would be better to show the confirmation as a pop-up, like it is done after having added answer options or having changed global settings, and directly move on to the &amp;quot;add token entry&amp;quot; page because usually users want to add several token entries one by one.&lt;br /&gt;
*Alternative solution: When adding a token have two radio options above the save button: a) add another token after save (should be default) OR b) display tokens after save.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece, for this task /admin/tokens.php is a good start&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Survey designer workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the survey designer at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the survey designer:&lt;br /&gt;
*Problem: When adding new answer option and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text. For following answer options the text is deleted automatically when clicking into the input field.&lt;br /&gt;
*Solution: Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Problem: When creating a new survey there are options to import or copy a survey. BUT there is a &amp;quot;save&amp;quot; button after the &amp;quot;import/copy survey&amp;quot; button as well. This is irritating because users might click the save button instead and then an error message will show up because no survey title etc. was entered at the previous tabs&lt;br /&gt;
*Solution: Hide &amp;quot;save&amp;quot; button at import and copy tab.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User and rights management workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when adding users and settings rights at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the user management and rights setting screens.&lt;br /&gt;
*Problem: After having added a new user there is a summary screen showing the username and email address. You can either click &amp;quot;continue&amp;quot; to get to the user list summary or click the &amp;quot;set user permissions&amp;quot; button which leads you to the next logical step of setting the permissions for this user (a user without any permissions set doesn&#039;t make much sense).&lt;br /&gt;
*Solution: We should show the summary as a pop uf and automatically redirect the admin to the screen where permissions for the newly added user can be set.&lt;br /&gt;
*Problem: After having set permissions as the next workflow step described below, the user receives a short status update and can only click &amp;quot;continue&amp;quot; which leads him to the user overview.&lt;br /&gt;
*Solution: We should automatically redirect the admin to the user overview and show the status update as a pop-up. We could also think about redirecting him to the screen where template permissions can be set which would be the next logical step.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=We want your ideas!=&lt;br /&gt;
&lt;br /&gt;
What floats your boat? Do you have another idea that gets you excited? Discuss your ideas in our [http://www.limesurvey.org/component/option,com_fireboard/Itemid,105/func,view/catid,11/id,24710/lang,en/ forums], [https://lists.sourceforge.net/lists/listinfo/limesurvey-developers mailing lists] or at #limesurvey on irc.freenode.net.&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=GSoC_Getting_Started How to get started with LimeSurvey]&lt;br /&gt;
&lt;br /&gt;
How to Get Started With LimeSurvey:&lt;br /&gt;
&lt;br /&gt;
- setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2042</id>
		<title>LimeSurvey project ideas for Google Code-in 2011</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_project_ideas_for_Google_Code-in_2011&amp;diff=2042"/>
		<updated>2011-11-23T08:07:15Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome=&lt;br /&gt;
&lt;br /&gt;
Welcome Google Code-in Student aspirants (:razz:)!! Please check if you are an [http://code.google.com/opensource/gci/2010-11/faqs.html eligible candidate] for the GCI program.&lt;br /&gt;
&lt;br /&gt;
This page lists task ideas developed by the LimeSurvey Community. These tend to be areas that will get the most support as tasks since they have been developed by people who know the project and what it needs the most. Good Luck (:biggrin:)&lt;br /&gt;
&lt;br /&gt;
All tasks aim at the development version 2.0a.&lt;br /&gt;
&lt;br /&gt;
=How to claim a task=&lt;br /&gt;
&lt;br /&gt;
All tasks below will be entered in the [http://www.google-melange.com/gci/program/list_tasks/google/gci2011 Google Code-in task tracker] (which is not yet available). You have to be a registered Google Code-In participant to claim a task.&lt;br /&gt;
&lt;br /&gt;
=Task ideas=&lt;br /&gt;
&lt;br /&gt;
==Idea Template==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;This is just a template you can use to add your ideas:&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Code/Documentation/Outreach/Quality assurance/Training/Research/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: &amp;lt;myname&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here comes some text describing the current situation and how Limesurvey will benefit from this task. The description should make clear what this task is about.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Second wave==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;...add your ideas here...&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===Documentation/Translation: (GERMAN) Merge article &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot; and add new/missing parts of english article &amp;quot;The template editor&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+vierundzwanzig vierundzwanzig] &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The english article &amp;quot;The template editor&amp;quot; has both the description for the template editor as well as the description for template styles. In the german part of the documentation this article is seperated into two articles &amp;quot;Vorlagen / Vorlagen Editor&amp;quot; and &amp;quot;Templates   Styles&amp;quot;. For the reason of simplicity and unity both articles should be merged together. If the english article &amp;quot;The template editor&amp;quot; has new/missing parts this parts should be translated and added to the new merged article.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Some steps like...&lt;br /&gt;
*Install Limesurvey or use the online system we provide&lt;br /&gt;
*Analyse the problem&lt;br /&gt;
*Discuss the issue and your proposed solution with your mentor&lt;br /&gt;
*Code/document/translate/... and submit your work&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk/add it to the wiki/...&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X days||some skills the applicants should have|| easy/moderate/difficult||mentorname&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==First wave (already ported to GCi system)==&lt;br /&gt;
&lt;br /&gt;
==Localization==&lt;br /&gt;
&lt;br /&gt;
===Localization: Translate LimeSurvey to your mother language===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey software is available in more than 50 languages - not all of them are completely translated. Check if your language is supported at: http://www.limesurvey.org/translationstatus_v2/&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Check out if your language is already there and if the translation status is below 70% OR if your language does not exist at all.&lt;br /&gt;
*Read the documentation on [[how to update a translation or how to create a new one.|Translating LimeSurvey]]&lt;br /&gt;
*Translate as crazy - check your translation using a local copy of LimeSurvey.&lt;br /&gt;
*Submit your updated/new translation to us.&lt;br /&gt;
&lt;br /&gt;
Updating a translation from &amp;lt;70% to 100%:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Translation|| Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
New translation (at least 50%):&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Translation|| Moderate ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to German.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new German translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Erstellen+einer+neuen+Umfrage current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced qustion attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute update the German translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Frage-Attribute current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Tokens&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the German documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey update the German translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Zugangsschl%C3%BCssel&amp;amp;structure;=Deutsche+Anleitung+f%C3%BCr+LimeSurvey current German version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (GERMAN) Translate the english &amp;quot;Installer&amp;quot; docs page to German===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the German translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the German translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||German and English language|| easy||mot2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;--&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to French.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new French translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Cr%C3%A9er+un+nouveau+questionnaire current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions update the French translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Attributs+des+questions current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Tokens&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the French documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey update the French translation of that wiki page] based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/Invitations&amp;amp;structure;=Instructions+fran%C3%A7aises+pour+LimeSurvey current French version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (FRENCH) Translate the english &amp;quot;Installer&amp;quot; docs page to French===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the French translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the French translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| easy||Shnoulle&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;&amp;lt;strike&amp;gt;-&amp;lt;/strike&amp;gt;---&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Expression Manager&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will contain a powerful &amp;quot;Expression Manager&amp;quot; which replaces conditions and some other features. The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Expression+Manager translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Expression+Manager&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Central Participants Database&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The upcoming Limesurvey 2.0 version will have a new feature called &amp;quot;Central Participants Database&amp;quot; (CPDB). The documentation of this new feature is only available in English yet. Your task is to [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 translate the current wiki page] to Spanish.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Central+participants+database+%28User+panel%29&lt;br /&gt;
*Create a new Spanish translation of this page directly at our wiki and translate the page carefully&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Creating a new survey&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Creating a new survey&amp;quot; page is one of the most important pages at our documentation because it lists all available survey settings. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Reglas+de+evaluaci%C3%B3n current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/Creating+a+new+survey&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|1 day||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Question types&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Question types&amp;quot; page is one of the most important pages at our documentation because it lists all available question types. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Tipos+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Question+types english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Advanced question settings&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Advanced question attributes&amp;quot; page is one of the most important pages at our documentation because it lists all available question attributes which enhance question functionality. Unfortunately the Spanish documentation of this page is really outdated. Your task is to [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas update the Spanish translation of that wiki page] based on the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings&lt;br /&gt;
*Check if it&#039;s worth keeping parts of the [http://docs.limesurvey.org/tiki-index.php?page=Atributos+de+ajuste+de+preguntas current Spanish version]. If so, update the existing page, if not, clear the page and translate the [http://docs.limesurvey.org/tiki-index.php?page=Advanced+question+settings english base version].&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new/updated translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Spanish and English language|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Tokens&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Tokens&amp;quot; page is one of the most important pages at our documentation because feature is used a lot to restrict access to a survey on predefined users. Unfortunately the Spanish documentation of this page doesn&#039;t exist yet. Your task is to create the Spanish translation of that wiki page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey current english wiki page].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english page at http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Translate the page based on the [http://docs.limesurvey.org/Tokens&amp;amp;structure;=English+Instructions+for+LimeSurvey english base version].&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Spanish and English language|| difficult||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Translation: (SPANISH) Translate the english &amp;quot;Installer&amp;quot; docs page to Spanish===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The new installer is one of the most important featres of the new Limesurvey 2.0 version. Once the English instructions page ([http://docs.limesurvey.org/LimeSurvey+project+ideas+for+Google+Code-in+2011#Documentation:_Rewrite_installation_procedure see this idea]) was set up, the Spanish translation of that page has to be created.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the english installer page once it was set up.&lt;br /&gt;
*Create the Spanish translation of this page directly at our wiki.&lt;br /&gt;
*Check if your new translation contains all information of the english base version.&lt;br /&gt;
*Discuss the translation with your mentor&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||French and English language|| moderate||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Usability changes for LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey user interface (like most interfaces) has its kinks - often it is very easy to enhance the usability by just making small changes to the interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey, play around with the interface.&lt;br /&gt;
*Pick a couple things you would like to change to have better usability&lt;br /&gt;
*Discuss the found issues with your mentor&lt;br /&gt;
*Together we will either pick one of your found issues or the mentor will make an suggestion for another change.&lt;br /&gt;
*Code the usability change and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and the mentor&lt;br /&gt;
*If necessary make re-submit patch with discusse changes&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, HTML, CSS, maybe SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement &amp;quot;Embedd all text answers&amp;quot; setting at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently the admin statistics only sum up data. If you want to have a look at text responses in detail, you have to click another button within the summary which opens a new windows.&lt;br /&gt;
&lt;br /&gt;
This is a bad solution if you want to exports results and include the texts because you have to copy them manually. Therefore a new &amp;quot;Embedd all text answers&amp;quot; setting should be introduced so that all text answers will be listed for all corresponding questions. This way this data would also be avialable when exporting the statistics.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with text questions and add some dummy data.&lt;br /&gt;
*Have a look at the data summary and the available export options.&lt;br /&gt;
*Add a &amp;quot;Embedd all text answers&amp;quot; setting.&lt;br /&gt;
*Implement the code to embedd that data and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||PHP, some very basic HTML, SQL|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement Google map at admin statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a &amp;quot;Map&amp;quot; question type which can be used to let the user mark a certain location. The results are stored as lat./long. coordinates at a simply text question. Currently the admin statistics only show the raw coordinates. To improve this, a Google Map should be included at the admin statistics, showing the users&#039; answers at that overview.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a map question and add some dummy data.&lt;br /&gt;
*Have a look at the admin statistics of that question.&lt;br /&gt;
*Implement the code to embedd a Map and mark the users&#039; answers in there and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||PHP, some very basic HTML, (knowledge about Google Maps API or: learning by doing)|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at token overview table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing all the existing users at the token overview. Usability will benefit a lot if those overviews would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the token overview and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Difficult ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement jqgrid at browse response table===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend includes several tabular overviews, e.g. when listing survey results at the browse responses screen. Usability will benefit a lot if this overview would be sortable, searchable and filterable. For this we can use jqgrid.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we&#039;ll hand that to you) and add some test answer data.&lt;br /&gt;
*Have a look at the jqgrid docs at http://www.trirand.com/jqgridwiki/doku.php&lt;br /&gt;
*Implement jqgrid for the browse response table and create a patch&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, maybe a little CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve drag and drop functionality at attribute mapping===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Aniessh&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Central Participant&#039;s Database feature has a special drag and drop functionality for mapping/creating attributes in the token table to the central table and vice versa. The feature is working but needs improvement in the user interface.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey with a token table and add a few dummy people there.&lt;br /&gt;
*Create some attributes at the token level.&lt;br /&gt;
*Create some attributes at the Central Participant Database panel.&lt;br /&gt;
*Copy the previously added dummy people from token table to the central table.&lt;br /&gt;
*You will be presented with a drag and drop screen that will allow you to match the attributes from the central and the token table.&lt;br /&gt;
*Suggest how to improve the user interface.&lt;br /&gt;
*Improve the user interface and create a patch.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 days||Javascript, PHP, HTML, CSS|| Moderate||aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add drag and drop feature to ranking question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey contains a &amp;quot;ranking&amp;quot; question type (see http://docs.limesurvey.org/Question+type+-+Ranking&amp;amp;structure;=English+Instructions+for+LimeSurvey) which isn&#039;t very user friendly when it comes to sorting and it also causes problems when being used by screen readers. Nowadays there are better interfaces for such question types so switching to a drag and drop version is the goal of this coding task.&lt;br /&gt;
&lt;br /&gt;
There is already a [http://docs.limesurvey.org/Workarounds%3A+Manipulating+a+survey+at+runtime+using+Javascript&amp;amp;structure;=English+Instructions+for+LimeSurvey#Drag_and_Drop_Rankings workaround] and a [http://www.partnersinc.biz/surveys//index.php?sid=36981&amp;amp;newtest;=Y&amp;amp;lang;=en demo version] available so what has to be done is porting the code to create a more generic solution and embedding the CSS for the available shipped templates.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a test survey with ranking question types and different question attributes&lt;br /&gt;
*Have a look at the question type within the survey to see what could be improved.&lt;br /&gt;
*Check the workaround linked above and the demo survey to see where we would like to go to.&lt;br /&gt;
*Implement a generic solution to make the ranking question type a little nicer (no DB changes required).&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Javascript, PHP, CSS|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add option to switch between bar chart and pie chart at statistics===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses bar charts for multiple choice questions and pie charts for single choice questions. Often users want to switch to a different chart type so this fixed assignment of certain types should be replaced by a more dynamic system which allows the user to set chart types himself.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - import a test survey with all question types (we can provide one) and add some test data.&lt;br /&gt;
*Have a look at the admin statistics and the charts that are created. Check how we could best offer a choice for the user to set chart types.&lt;br /&gt;
*Discuss your suggestions with your mentor and together create a concept how to deal with the problem.&lt;br /&gt;
*Implement a generic solution.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||PHP, MySQL, a little HTML|| difficult||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Refactor the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. The code however is far from ideal. In order to improve code quality, there are plenty of refactorings required like splitting up long methods, extracting view-related and database-related code from controllers, adding new helper functions, ...&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find a class or method with smelly (bad) code&lt;br /&gt;
*Discuss the code smell with the mentor and make a proposal on how to improve the code&lt;br /&gt;
*Work out the improvement and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen smell)||PHP, CodeIgniter (depending on chosen smell)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Make unit tests for the CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. Now we are using the framework, it is possible to write unit tests for the different classes (domain classes, controllers, helpers, libraries, ...) The goal of this task is to write a unit test for an untested class or method.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download the LimeSurvey CI-branch&lt;br /&gt;
*Find an untested class which could use some testing&lt;br /&gt;
*Discuss the badly tested class/method with the mentor and make a proposal on how to test the code&lt;br /&gt;
*Write tests for class/method and create a patch&lt;br /&gt;
*Discuss your patch with the mentor&lt;br /&gt;
*Check-in your changes into the limesurvey svn trunk.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days (depending on chosen class/method)||PHP, CodeIgniter (depending on chosen class/method)|| Moderate||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring HTML into views : CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, there are still some controllers which have lots of HTML content in them. This task aim for separating this HTML(wherever possible) from controllers and move it to View files. This task will be on controller by controller basis.&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Browse Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Browse Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Browse Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Check Integrity Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Check Integrity Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Check Integrity Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Conditions Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Conditions Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Conditions Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Database Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Database Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Database Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Data Entry Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Data Entry Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Data Entry Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Email Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Email Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Email Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Export Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Export Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Export Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Labels Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Labels Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Labels Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Printable Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Printable Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Printable Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Question Group Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Question Group Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Question Group Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Quotas Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Quotas Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Quotas Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Saved Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Saved Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Saved Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Statistics Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Statistics Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Statistics Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Survey Permission Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Survey Permission Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Survey Permission Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Templates Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Templates Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Templates Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Tokens Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Tokens Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Tokens Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (Translate Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
Translate Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in Translate Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Re-factoring database calls into models (User Groups Controller): CodeIgniter branch===&lt;br /&gt;
&lt;br /&gt;
This year LimeSurvey got ported to the CodeIgniter framework. As CodeIgniter is based on MVC architecture, all database calls should be in served via models and &amp;quot;Active Records&amp;quot; should be used everywhere. This task aim for searching through the&lt;br /&gt;
&lt;br /&gt;
User Groups Controller and moving all database calls to models. (i.e. making new functions in models to serve the purpose and call it in controller instead of using db_execute_assoc()!).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Download LimeSurvey&#039;s CodeIgniter branch&lt;br /&gt;
*Read the Documentation&lt;br /&gt;
*Find outdated database calls in User Groups Controller (db_execute_assoc()).&lt;br /&gt;
*Identify which calls have equivalent methods in models.&lt;br /&gt;
*Port these calls using the existing models.&lt;br /&gt;
*Create or extend the models for the remaining calls.&lt;br /&gt;
*Port the remaining calls using the new models.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Check-in your changes into the LimeSurvey svn trunk.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2-4 days||PHP, CodeIgniter, MySQL|| Moderate||dionet/magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite template editor wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Currently the documentation for the template editor is out of date needs to be brought up to date with the latest version of limesurvey. Cropped screenshots should also be inserted to visually reference the documentation and the software.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the template editor documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite the survey settings page===&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing outdated documentation.&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Design a new structure for the documentation which is easy to follow and well structured.&lt;br /&gt;
*Discuss your planned documentation structure with your mentor.&lt;br /&gt;
*Rewrite the documentation.&lt;br /&gt;
*Insert cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Wiki editing,LimeSurvey|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Create a tutorial about how to replace the logo at a shipped template===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Problem is that some HTML and CSS knowledge is needed to fully style a template and this might be a problem to the common user. Usually replacing the logo at one of the shipped templates is all they need so the goal is to write a step by step tutorial with some screen shots about how to replace the logo.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing documentation about templates and create a new entry at the [http://docs.limesurvey.org/The+template+editor&amp;amp;structure;=English+Instructions+for+LimeSurvey#Tips_amp_Tricks Tipps &amp;amp; Tricks sub-section].&lt;br /&gt;
*Explore limesurvey&#039;s template editor and compare it to the existing documentation.&lt;br /&gt;
*Check the template editor at our demo system and note how the logos are embedded at different templates&lt;br /&gt;
*Write a step by step tutorial including screen shots on how to replace the images and/or change the logo file name at the templates&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
*Discuss your tutorial with your mentor and if necessary overwork some parts&lt;br /&gt;
* Add everything at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Wiki editing, LimeSurvey, HTML|| Easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite statistics wiki page===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers public statistics, which are shown to the user at the end of the survey, as well as more detailed statistics at the admin backend. The [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey current statistics documentation] is outdated and not very well structured. Lots of users don&#039;t know that they can filter data and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the statistics more clear to the user, the documentation should be updated, extended and better structured. A video showing how to set filters and demonstrating other statistic features should be added, too.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import the sample survey at /docs/demosurveys which contains all question types.&lt;br /&gt;
*Enable public statistics for this survey and all questions that are supported by this feature.&lt;br /&gt;
*Fill out the survey ~20-30 times (ask your friends for some help) to create some data to be used by the statistics.&lt;br /&gt;
*Explore the public and admin backend statistics and write down which features are available.&lt;br /&gt;
*Ask your mentor if all features are on your list.&lt;br /&gt;
*Think about a new structure for the wiki page&lt;br /&gt;
*Document each section and describe each feature in detail. Add some nice screenshots where appropriate.&lt;br /&gt;
*Create a short video showing how to set filters and use other important features.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Wiki editing, LimeSurvey, video capture|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation: Rewrite installation procedure.===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey 2.0 has a new automatic installer which makes installation process a cake-walk. Hence, installation procedure needs to be updated explaining each and every step of the installation procedure and possible errors/warnings that a user might see during installation of LimeSurvey and there solutions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Checkout LimeSurvey_CI branch.&lt;br /&gt;
*Read existing installation procedure.&lt;br /&gt;
*Run the automatic installer and play with it.&lt;br /&gt;
*Compare the missing things and update the wiki.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Make a troubleshooting section on installation wikipage which should contain possible warnings a user might see and there solution(s).&lt;br /&gt;
*Create a short video tutorial on how to install LimeSurvey.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Wiki editing, creating screen shots, writing documentation, creating videos|| difficult||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; Marketing==&lt;br /&gt;
&lt;br /&gt;
===Outreach: Blog about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
Write an independant article about LimeSurvey on your blog. Explain what are advantages, what are disadavantages of the software - show how to create a first survey and also write about problems are on the way getting there. Motivate people to participate to help use make LimeSurvey better. The article should be in-depth and correct. It should help other to get hooked up without false promises.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Use LimeSurvey to setup your own survey (you can use our demo version for that)&lt;br /&gt;
*Blog about your experience after discussing your article with us.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days|| Writing skills || Easy ||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee engagement survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An introduction.&lt;br /&gt;
#Setting up an employee engagement survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee engagement survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee engagement survey.&lt;br /&gt;
*Discuss the employee engagement metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey and OrangeHRM to conduct an employee satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
OrangeHRM is a powerful and fully featured Human Resource Management Tool. Help empower open source by showing how two separate open source products can be used together to bring added value to their users.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an employee satisfaction survey with LimeSurvey.&lt;br /&gt;
#Patching OrangeHRM (CustomExport.php and CustomizableCSVExport.php models) to allow the work_email field to be exported.&lt;br /&gt;
#Creating a custom export in OrangeHRM with the fields: firstName, lastName, workEmail.&lt;br /&gt;
#Using the OrangeHRM custom export to get a CSV list for LimeSurvey tokens import.&lt;br /&gt;
#Importing the tokens into the employee satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide links to patched OrangeHRM files and example survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install OrangeHRM.&lt;br /&gt;
*Create the employee satisfaction survey.&lt;br /&gt;
*iscuss the employee satisfaction metrics measured with your mentor.&lt;br /&gt;
*Modify OrangeHRM custom export and generate patches (mentor can provide changes).&lt;br /&gt;
*Test the OrangeHRM custom export and LimeSurvey tokens import.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Blog about LimeSurvey (2)===&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
&lt;br /&gt;
- Research how a general basic customer satisfaction survey should look like&lt;br /&gt;
&lt;br /&gt;
- Create it in LimeSurvey&lt;br /&gt;
&lt;br /&gt;
- Write about your experience in setting this up.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Survey Creation, Technical Writing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Marketing: Create an article on how to use LimeSurvey to create and distribute a customer satisfaction survey===&lt;br /&gt;
&lt;br /&gt;
Show current and potential LimeSurvey users how they can use LimeSurvey to do customer satisfaction surveys.&lt;br /&gt;
&lt;br /&gt;
The article should include:&lt;br /&gt;
#An Introduction.&lt;br /&gt;
#Setting up an customer satisfaction survey with LimeSurvey.&lt;br /&gt;
#Importing the tokens into the customer satisfaction survey.&lt;br /&gt;
#Sending out invitations and reminders.&lt;br /&gt;
#Viewing statistics and exporting results.&lt;br /&gt;
#Provide a link to the example customer satisfaction survey.&lt;br /&gt;
#Article conclusion.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create the customer satisfaction survey and test it.&lt;br /&gt;
*Discuss the customer satisfaction metrics measured with your mentor.&lt;br /&gt;
*Write the article.&lt;br /&gt;
*Submit the article to your mentor for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Survey Creation, Technical Writing, Source Code Patching|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Analyse user feedback and port suggestions to our idea tracker===&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey [http://survey.limesurvey.org/ conducts user feedback surveys] to find out how our users use the software and which features they are missing. We received quite a lot feedback during the last months and a lot of valuable information can be found at the textual feedback. It&#039;s a mixture of praise, suggestions for new features and other useful comments. This needs to be summed up. Also useful suggestions for new features should be ported to [http://ideas.limesurvey.org/ our idea tracker] so we have this on our list for future development.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will give you access to our survey system so you can export the survey data into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list of common complaints, suggested features and the like.&lt;br /&gt;
*Once you are done, order the lists by frequency and present it to your mentor.&lt;br /&gt;
*Your mentor will go through your list and mark those ideas worth porting to the idea tracker.&lt;br /&gt;
*Add ideas to the idea tracker&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Data analysis, Report Writing, Using idea tracker|| Moderate [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (1/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||dionet&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs or GUI design issues at the new Central Participant Database feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It will be available at the upcoming Limesurvey 2.0 alpha release. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing instructions] and the [http://docs.limesurvey.org/Central+participants+database+%28User+panel%29 CPDB documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Using bugtracker, Limesurvey|| Easy ||Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the new Expression Manager feature of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
At the upcoming Limesurvey 2.0 alpha release conditions will be replaced by a powerful Expression Manager (EM). This feature is capable to evaluate all kinds of expressions and it will be used for other feature besides conditions as well.&lt;br /&gt;
&lt;br /&gt;
Since this is a new feature with a very complex logic we have to test it carefully. Therefore it&#039;s your task to create tests and see if everything works as expected.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at our [http://www.limesurvey.org/en/component/content/article/1-general-news/226-new-qcentral-participants-databaseq-feature-is-ready-for-testing testing system details] and the [http://docs.limesurvey.org/Expression+Manager EM documentation].&lt;br /&gt;
*Test this feature by checking each single function and note any weird behavior, error messages or anything else you think is worth being improved.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Using bugtracker, Limesurvey|| Moderate||TMS White&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Admin Backend of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested, there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin feature. Play around with the available features and check if all works as described at the manual. If not, note all details about the problem.&lt;br /&gt;
*Find out which new features were added at Limesurvey 2.0 and check the according sections at the admin panel carefully. Note any weird behavior.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|2 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality Assurance: Find and report 3 bugs at the overworked Survey Engine of the upcoming Limesurvey 2.0alpha version (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
During this years Google Summer of Code we ported the whole Limesurvey code to an MVC framework called codeigniter. This implied a whole bunch of code changes and re-design. Though this feature was carefully tested there might still be some bugs in there and we want you to have a detailed look at this feature to check if you can find any weird behavior, misleading user interface or bugs.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Import a test survey with all question types and most of the additional question attributes (we can provide some test surevys).&lt;br /&gt;
*Check if data for each question type is stored correctly, if conditions work as expected and all other available features listed at our documentation.&lt;br /&gt;
*Note any weird behavior, error messages and the like.&lt;br /&gt;
*Your mentor will go through your list and will discuss the details with you.&lt;br /&gt;
*Add all issues to the bugtracker.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Limesurvey, Using bugracker|| Moderate||magiclko&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Training==&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a custom survey template===&lt;br /&gt;
&lt;br /&gt;
Limesurvey has a template editor which allows users to create and modify templates used when displaying surveys. These templates allow survey administrators to adjust the look and feel of their surveys and brand them as well. Create a video tutorial showing users how to create a copy of the default template and modify it.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#An overview of the template editor and a description of what each area of the template editor is used for.&lt;br /&gt;
#An explanation of the different screens.&lt;br /&gt;
#Inserting a company logo in to the template.&lt;br /&gt;
#Basic adjustments in the css to modify the appearance of questions.&lt;br /&gt;
#Customizing the survey description page.&lt;br /&gt;
#Customizing the end page.&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a new survey from scratch===&lt;br /&gt;
&lt;br /&gt;
There are several videos around explaining how to create a survey with LimeSurvey. Unfortunately most of the are pretty outdated and old. We would like to have a kick-all video tutorial explaining how to create a survey that immediately will hook up people.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Creation of a survey, with an easy explanation of the concept behind it (Survey-&amp;gt;Question groups-&amp;gt;Questions)&lt;br /&gt;
#Creating the survey, explaining the most important settings&lt;br /&gt;
#Creating question groups and questions plus answers&lt;br /&gt;
#Showing off a number of question types&lt;br /&gt;
#Showing off how a simple condition is created.&lt;br /&gt;
#Activating the survey&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end. Your will need to create a script for your video which includes all the steps you will be showing in your video and the dialog associated with each step.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a script with dialog to explain what will be done in the video from start to end.&lt;br /&gt;
*Submit your video script to your mentor for review.&lt;br /&gt;
*Record/Produce each section for your video tutorial.&lt;br /&gt;
*Submit each video to your mentor for review.&lt;br /&gt;
*Merge your video sections into an xvid avi with mp3 audio.&lt;br /&gt;
*Submit your video to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial for creating a &amp;quot;Maps&amp;quot; question===&lt;br /&gt;
&lt;br /&gt;
At last years Google Code in a student created an extension to the &amp;quot;short text&amp;quot; question type so it can be used as a &amp;quot;Maps&amp;quot; question type. If this feature is activated at the advanced question settings, the user will be displayed a map at the survey and he/she can place a mark on that map indicating a certain location. The results are then stored a s a text string with lat./long. data.&lt;br /&gt;
&lt;br /&gt;
Unfortunately [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service no real documentation exists] for this type of questions so your task would be to play around with the different settingsm, find out what each setting is used for and then extend the according section at the manual and create a short video tutorial explaining how this question type works.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
#Explaining what the question can be used for&lt;br /&gt;
#A summary of the most important settings&lt;br /&gt;
#Two sample setups for this question type&lt;br /&gt;
#Showing how the question look slike at the survey&lt;br /&gt;
#Showing how the recorded results wil look like&lt;br /&gt;
&lt;br /&gt;
It will be best to record each video section separately and then join the video at the end.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the [http://docs.limesurvey.org/Question+type+-+Short+free+text&amp;amp;structure;=English+Instructions+for+LimeSurvey#Use_mapping_service available &amp;quot;Maps&amp;quot; question type settings]&lt;br /&gt;
*Play around with them to find out what each setting does&lt;br /&gt;
*Extend/complete the documentation at our wiki&lt;br /&gt;
*Create a short video tutorial on how to use that question type&lt;br /&gt;
*Submit the documentation and video to your mentor for review.&lt;br /&gt;
*Discuss the results with your mentor and eventually overwork some parts&lt;br /&gt;
*Submit your video to your mentor and complete the codumentation at our wiki.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Screen Recording, Video and Sound Editing|| Moderate||Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create demo surveys for the most important features===&lt;br /&gt;
&lt;br /&gt;
Limesurvey offers a wide range of features. Some of them are a little complex to set up in a survey. To help new users getting familiar with these feature, we intend to create several sample surveys which users can easily download from our manual and import for testing.&lt;br /&gt;
&lt;br /&gt;
Each survey should contain 8-10 questions, depending on the feature that is demonstrated.&lt;br /&gt;
&lt;br /&gt;
List of sample surveys:&lt;br /&gt;
#Use of [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes#Array_Filter_and_Array_Filter_Exclusion array filter and array exclusive option]&lt;br /&gt;
#How to set different types of [http://docs.limesurvey.org/tiki-index.php?page=Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions]&lt;br /&gt;
#Create a quiz using [http://docs.limesurvey.org/tiki-index.php?page=Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments ]and [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier] to show the users answers at the end of the survey.&lt;br /&gt;
#Screen users by making use of [http://docs.limesurvey.org/tiki-index.php?page=Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas]&lt;br /&gt;
#Demonstrate the use of ~10 different [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey question attributes].&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Get familiar with Limesurvey by using our [http://docs.limesurvey.org/tiki-index.php?page=Question+attributes&amp;amp;structure;=English+Instructions+for+LimeSurvey demo ]or installing Limesurvey yourself.&lt;br /&gt;
*Read the documentation linked above.&lt;br /&gt;
*Create a first survey and ask your mentor for feedback.&lt;br /&gt;
*Create the rest of the surveys.&lt;br /&gt;
*Create a topic in our forum and ask for some user feedback.&lt;br /&gt;
*Add feedback where useful.&lt;br /&gt;
*Merge all surveys in a big demo survey using group/question import/export while keeping the smaller survey versions.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 Days||Creating surveys using Limesurvey, communicate with coomunity|| easy [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Training: Create a &amp;quot;How to design a &#039;&#039;good&#039;&#039; survey&amp;quot; tutorial===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Our manual describes all available features in detail but we don&#039;t have instructions on how to create a good survey yet, e.g. users might have huge matrix question which are all mandatory at their survey, that&#039;s a no go. Your task is to find out about some basics of survey design by asking google and asking our experienced users at the forum and then collect that data and structure it so we can have a list of issues one should take care of when designing a survey.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a new forum topic explaining your task and asking for user feedback. Ask your mentor to also link this post at www.limesurvey.org and to twitter about it.&lt;br /&gt;
*Ask Google about the important issues when creating an online survey&lt;br /&gt;
*Sum up all information and create a structured document which deals with different parts to take care of.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Port all the details to a new wiki page&lt;br /&gt;
*Add the wiki page at a new tipps &amp;amp; tricks section of our wiki&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Using search engines, writing documentation|| easy||holch&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new expression engine===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The enxt Limesurvey version will use a powerful Expression Manager which can be used for conditions, assessments, advanced filterinfg and many more. Since this feature is a little complex, it would be nice to have a video tutorial on how to set up the according expressions for certain features.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Expression manager documentation here: http://docs.limesurvey.org/Expression+Manager and here: http://docs.limesurvey.org/Expression+Manager+HowTos&lt;br /&gt;
*Create a list of the most important features for which the Expression manager can be used.&lt;br /&gt;
*Discuss the list with your mentor and think which parts should be covered at the video tutorial.&lt;br /&gt;
*Create a video tutorial about the most important features. The users should learn how the Expression manager works and how to set up expressions for different features&lt;br /&gt;
*Show the video to your mentor and discuss necessary changes.&lt;br /&gt;
*When you are done, upload the video at Limesurvey&#039;s youtube channel and also add it at the online documentation.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||Screen Recording, Video and Sound Editing|| hard||twmswhite, Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Research==&lt;br /&gt;
&lt;br /&gt;
===Research: Usability testing===&lt;br /&gt;
&lt;br /&gt;
Usability testing and user input is a great source of ideas for improving your application. The goal of this assignment is to identify usability problems in LimeSurvey and discussing possible solutions for them.&lt;br /&gt;
&lt;br /&gt;
The general steps for this assignment would be:&lt;br /&gt;
#Work with LimeSurvey like a regular user would&lt;br /&gt;
##Set up a new survey&lt;br /&gt;
##Answer the survey at least once&lt;br /&gt;
##Make changes to the survey&lt;br /&gt;
##Use and export the results&lt;br /&gt;
##&amp;amp;hellip; (be creative!)&lt;br /&gt;
#Identify usability problems in LimeSurvey&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#Write a social media post (blog, facebook, twitter) about your work at LimeSurvey, discuss the problems you have found and the ideas your propose to solve them.&lt;br /&gt;
##Tell others about what you have done during this assignment and how awesome LimeSurvey and their dev team is.&lt;br /&gt;
&lt;br /&gt;
For this assignment it is possible to make use of LimeService . LimeService provides free LimeSurvey installs for small users and requires no installation (even though installation could be a usability test in itself! How easy is it to install LimeSurvey). We advice to google for common usability problems before starting this assignment as a source of inspiration.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||None, skills in web development are a plus|| Easy||ttielu&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Use Google Analytics to create a report about the common Limesurvey user===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Limesurvey uses Google Analytics to gather some basic background information about our users like where they come from, which browser they are using, which pages are visited most and the like. Because Google Analyitcs offers a lot of information we need a summary of the most important details. That&#039;s where you can give a helping hand.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*We will grant you access to our Google Analytics account so you can play around with the data a little&lt;br /&gt;
*Have a look at the available information and create a list of available data. Mark which data you consider important.&lt;br /&gt;
*Discuss the list and your proposed priorities with your mentor&lt;br /&gt;
*After we have agreed on the information the final report should include, gather the required information and create a report containing a 1 page summary plus 3-4 pages of additional information and charts.&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Create a news article for the www.limesurvey.org website summing up your findings.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|4 days||writing reports (MS WOrd/Excel)|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Question types===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
Now there are more than 20 question types at Limesurvey and we are planning to extend some of them. Therefore we need to know which question types are used most by our users.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the available question types at http://docs.limesurvey.org/Question+types&amp;amp;structure;=English+Instructions+for+LimeSurvey&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Survey related features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
There are several survey related features like [http://docs.limesurvey.org/Setting+conditions&amp;amp;structure;=English+Instructions+for+LimeSurvey conditions], [http://docs.limesurvey.org/Assessments&amp;amp;structure;=English+Instructions+for+LimeSurvey assessments] or [http://docs.limesurvey.org/Quotas&amp;amp;structure;=English+Instructions+for+LimeSurvey quotas] but we don&#039;t really kniow to what extend they are used.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at [http://docs.limesurvey.org/English+Instructions+for+LimeSurvey&amp;amp;structure;=English+Instructions+for+LimeSurvey the Limesurvey documentation] and make a list of survey related features&lt;br /&gt;
*Think which information might be important and which questions could be asked&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Limesurvey user feedback on templates and GUI design===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
After having ported the code to a PHP framework recently, we are planning to now focus on improving the really outdated GUI. Therefore we need to know what our users think about the current GUI and where we should start working. It&#039;s your task to have a look at the current GUI and think about some GUI related questions.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the Limesurvey admin interface and make some notes about things you like and things you don&#039;t like.&lt;br /&gt;
*Import a test survey containing all question types (we can provide such a survey) and test it using the shipped templates. Create a like/dislike list.&lt;br /&gt;
*Have a look at your lists and think how we can ask other users about the issues you noted. This includes rating questions and open text questions.&lt;br /&gt;
*Discuss the questions and your proposed survey design with your mentor.&lt;br /&gt;
*After we have agreed on the questions we want to ask, set up the survey at our online system and test it carefully.&lt;br /&gt;
*Start the survey and write a short description so we can annunce it at the forums, on twitter at on the Limesurvey homepage.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|5 days||Limesurvey|| difficult||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Create a report on the &amp;quot;Limesurvey user feedback on templates and GUI design survey&amp;quot;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
From time to time Limesurvey runs some surveys itself, we simply use those surveys to find out more about our users. The resulting data tells us a lot about the areas where we have to improve the program and makes it easier to prioritize tasks.&lt;br /&gt;
&lt;br /&gt;
One of these surveys includes comments about how we can improve the GUI. There will be lots of text comments so we need to sum them up in a report.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Wait until someone has completed the &amp;quot;Research: Limesurvey user feedback on templates and GUI design&amp;quot; task. There should be at least ~50 responses to that survey&lt;br /&gt;
*Export the survey results and check the text comments.&lt;br /&gt;
*There will be several similar comments like &amp;quot;the icons suck&amp;quot;. Sum them up and create a list about what is top priority.&lt;br /&gt;
*Create a report which should also include the closed questions and write a short summary text (~ 20 sentences)&lt;br /&gt;
*Discuss the finding with your mentor and eventually overwork the report.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 days||Limesurvey, report writing, data summary|| moderate||Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Icon creation===&lt;br /&gt;
&lt;br /&gt;
As easy as it is sounds icon creation is a demanding task. Icons have to fit to the existing theme and their meaning must be untuitive without being hard on the eye. We want you to create three icons for for LimeSurvey that represent the following entities:&lt;br /&gt;
*Survey&lt;br /&gt;
*Question group&lt;br /&gt;
*Question&lt;br /&gt;
&lt;br /&gt;
The icons must fit to the existing theme and shoudl be create using Inkscape as SVG file.&lt;br /&gt;
#Have a look at our existing icons in the LimeSurvey interface&lt;br /&gt;
#Have a look at our existing icons in SVG format in our Subversion repository at https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/original art&lt;br /&gt;
#Create a couple drafts with a tool of your choice&lt;br /&gt;
#Discuss the drafts with your mentor&lt;br /&gt;
#Create the final icons&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|3 Days||Design, Inkscape|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the token screen:&lt;br /&gt;
*Problem: When switching to the token admin screen you don&#039;t see a list of available tokens. You have to click on the &amp;quot;Display Tokens&amp;quot; icon first.&lt;br /&gt;
*Solution: List all tokens below the &amp;quot;Token Summary&amp;quot; and above the &amp;quot;Token database options&amp;quot;.&lt;br /&gt;
*Problem: After having added a token entry you only see a short &amp;quot;New token was added&amp;quot; message with options to display tokens or add another token.&lt;br /&gt;
*Solution: It would be better to show the confirmation as a pop-up, like it is done after having added answer options or having changed global settings, and directly move on to the &amp;quot;add token entry&amp;quot; page because usually users want to add several token entries one by one.&lt;br /&gt;
*Alternative solution: When adding a token have two radio options above the save button: a) add another token after save (should be default) OR b) display tokens after save.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece, for this task /admin/tokens.php is a good start&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Survey designer workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like the survey designer at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the survey designer:&lt;br /&gt;
*Problem: When adding new answer option and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text. For following answer options the text is deleted automatically when clicking into the input field.&lt;br /&gt;
*Solution: Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Problem: When creating a new survey there are options to import or copy a survey. BUT there is a &amp;quot;save&amp;quot; button after the &amp;quot;import/copy survey&amp;quot; button as well. This is irritating because users might click the save button instead and then an error message will show up because no survey title etc. was entered at the previous tabs&lt;br /&gt;
*Solution: Hide &amp;quot;save&amp;quot; button at import and copy tab.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User and rights management workflow improvements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when adding users and settings rights at which workflow improvements can be added. Often a summary page is shown even if you just made a minor change. Instead we should speed up the workflow and show just a pop-up, just to name a few issues.&lt;br /&gt;
&lt;br /&gt;
This is a list of issues referring to the user management and rights setting screens.&lt;br /&gt;
*Problem: After having added a new user there is a summary screen showing the username and email address. You can either click &amp;quot;continue&amp;quot; to get to the user list summary or click the &amp;quot;set user permissions&amp;quot; button which leads you to the next logical step of setting the permissions for this user (a user without any permissions set doesn&#039;t make much sense).&lt;br /&gt;
*Solution: We should show the summary as a pop uf and automatically redirect the admin to the screen where permissions for the newly added user can be set.&lt;br /&gt;
*Problem: After having set permissions as the next workflow step described below, the user receives a short status update and can only click &amp;quot;continue&amp;quot; which leads him to the user overview.&lt;br /&gt;
*Solution: We should automatically redirect the admin to the user overview and show the status update as a pop-up. We could also think about redirecting him to the screen where template permissions can be set which would be the next logical step.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;TO BE CONTINUED&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
*Problem: ...&lt;br /&gt;
*Solution: ...&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
#Check the described issues using the online system we provide&lt;br /&gt;
#Search for the according code piece&lt;br /&gt;
#Overwork the code to improve the workflow&lt;br /&gt;
#Create a patch file and send it to your mentor for review.&lt;br /&gt;
#Once the mentor accepts your patch he will add it to the current development branch&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Time frame||Skills||Difficulty||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|X Days||PHP, maybe a little HTML and Javascript|| Easy||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=We want your ideas!=&lt;br /&gt;
&lt;br /&gt;
What floats your boat? Do you have another idea that gets you excited? Discuss your ideas in our [http://www.limesurvey.org/component/option,com_fireboard/Itemid,105/func,view/catid,11/id,24710/lang,en/ forums], [https://lists.sourceforge.net/lists/listinfo/limesurvey-developers mailing lists] or at #limesurvey on irc.freenode.net.&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=GSoC_Getting_Started How to get started with LimeSurvey]&lt;br /&gt;
&lt;br /&gt;
How to Get Started With LimeSurvey:&lt;br /&gt;
&lt;br /&gt;
- setting up the development environment, coding standards, and all the other important stuff that you need to know before the real fun begins!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4447</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4447"/>
		<updated>2011-11-21T10:32:53Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Download the data and the syntax file from the browse response screen.&lt;br /&gt;
#Save both of them on the R working directory (use &#039;&#039;getwd()&#039;&#039; and &#039;&#039;setwd()&#039;&#039; on the R command window to get and set it).&lt;br /&gt;
#Enter: &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; on the R command window&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:limesurveyExportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
example (structure of a vv file):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Delete old answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 3: Add new answers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;example&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Step 1: Open file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Step 2: Add new answers (at the end of the document)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;php&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Response ID    Date submitted    Last page    Start language    please vote from 1 to 6 (1 - super, 6 - worst)&lt;br /&gt;
&lt;br /&gt;
id    submitdate    lastpage    startlanguage    token        46492X40X1991&lt;br /&gt;
&lt;br /&gt;
183    09.11.11 11:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
184    09.11.11 11:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
190    09.11.11 11:44    3    de        1&lt;br /&gt;
&lt;br /&gt;
17    10.11.11 12:44    3    de        4&lt;br /&gt;
&lt;br /&gt;
18    24.11.11 14:53    3    de        2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:LimeSurveyImportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; file you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them (use this option for the use case &amp;quot;Adding new responses to the existing responses of a survey&amp;quot;). If you un-check this box, then the original record id&#039;s will be imported (use this option for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Replace the existing record (uses this for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4448</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4448"/>
		<updated>2011-11-17T10:26:13Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Download the data and the syntax file from the browse response screen.&lt;br /&gt;
#Save both of them on the R working directory (use &#039;&#039;getwd()&#039;&#039; and &#039;&#039;setwd()&#039;&#039; on the R command window to get and set it).&lt;br /&gt;
#Enter: &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; on the R command window&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
[[File:limesurveyExportVVen.jpg]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; file you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them (use this option for the use case &amp;quot;Adding new responses to the existing responses of a survey&amp;quot;). If you un-check this box, then the original record id&#039;s will be imported (use this option for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Replace the existing record (uses this for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4449</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4449"/>
		<updated>2011-11-15T13:22:58Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Download the data and the syntax file from the browse response screen.&lt;br /&gt;
#Save both of them on the R working directory (use &#039;&#039;getwd()&#039;&#039; and &#039;&#039;setwd()&#039;&#039; on the R command window to get and set it).&lt;br /&gt;
#Enter: &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; on the R command window&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the responses by entering them manually or copy/paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; file you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them (use this option for the use case &amp;quot;Adding new responses to the existing responses of a survey&amp;quot;). If you un-check this box, then the original record id&#039;s will be imported (use this option for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Replace the existing record (uses this for the use case &amp;quot;Overwriting all responses of the survey&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4450</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4450"/>
		<updated>2011-11-15T13:12:33Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Download the data and the syntax file from the browse response screen.&lt;br /&gt;
#Save both of them on the R working directory (use &#039;&#039;getwd()&#039;&#039; and &#039;&#039;setwd()&#039;&#039; on the R command window to get and set it).&lt;br /&gt;
#Enter: &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; on the R command window&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import responses using &amp;quot;VVImport&amp;quot; make sure to check whether the responses should be added to the existing responses or all responses should be overwritten.&lt;br /&gt;
* If you are trying to import responses from a diffrent 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.&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Editing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
When a vv file has been successfully exported you can use a spreadsheet tool like Microsoft Excel or alternatives to open and edit the file. If you have to choose the column seperator use &amp;quot;Tabulator&amp;quot;. If you are using mutated vowels (like &amp;amp;auml;, &amp;amp;ouml; or &amp;amp;uuml; in the german language) make sure you use &amp;quot;UTF-8&amp;quot; as used character set.&lt;br /&gt;
&lt;br /&gt;
As mentioned before the first two rows of the vv file are headers so you should not change them. 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.&lt;br /&gt;
&lt;br /&gt;
===Adding new responses to the existing responses of a survey===&lt;br /&gt;
&lt;br /&gt;
If you want to add new responses to the survey you can delete every row past row two (the both headers should not be deleted) and add the new responses using one response for each row. You can add the data by writing them into the collums or copy-paste the reponses from e.g. another vv file (be carefull to add the responses only and not the header.)&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure not to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
===Overwriting all responses of the survey===&lt;br /&gt;
&lt;br /&gt;
If you want to overwrite all responses of the survey you can just add the new responses to the end of the file. As mentoind in &amp;quot;Adding new responses to the existing responses of a survey&amp;quot; you can either enter them manually or copy/paste them from another vv file.&lt;br /&gt;
&lt;br /&gt;
You can then import the survey, make sure to override the existing responses (see &amp;quot;Importing a VV survey file&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them. If you un-check this box, then the original record id&#039;s will be imported.&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Ignore the new record&lt;br /&gt;
*Replace the existing record&lt;br /&gt;
&lt;br /&gt;
==How to use VV-Export and VV-Import:==&lt;br /&gt;
&lt;br /&gt;
The VV-Import function is not particularly smart. The spreadsheet being imported has to be massaged into shape so that it matches the new survey.&lt;br /&gt;
&lt;br /&gt;
The idea of VV-Export/VV-Import was to allow import of results from a survey table that had changed. My standard procedure for the VV-Export/Import process is to:&lt;br /&gt;
#Create the new survey&lt;br /&gt;
#Activate the new survey&lt;br /&gt;
#Perform a VV-Export from the _new_ survey (first export)&lt;br /&gt;
#Perform a VV-Export from the _old_ survey (second export)&lt;br /&gt;
#Cut the two top rows from the first export and insert them as the top two rows in the second export.&lt;br /&gt;
#While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.&lt;br /&gt;
#Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)&lt;br /&gt;
#Save it all as a CSV file&lt;br /&gt;
#Perform the VV-Import into the _new_ survey&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4451</id>
		<title>Exporting results</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Exporting_results&amp;diff=4451"/>
		<updated>2011-11-15T12:47:44Z</updated>

		<summary type="html">&lt;p&gt;Steve: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
Once your survey is active you can start browsing responses and export them. To get to the survey response overview click...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
=Export to application (Excel/.csv)=&lt;br /&gt;
&lt;br /&gt;
On top of the browse responses page several export options are listed, beginning with &#039;&#039;export to CSV/application&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
When exporting results to an application there are several filter options which are separated into:&lt;br /&gt;
*&#039;&#039;&#039;General&#039;&#039;&#039;&lt;br /&gt;
** Set a range like export records X to Y&lt;br /&gt;
** Set to export all records OR completed records only OR incomplete records only&lt;br /&gt;
*&#039;&#039;&#039;Questions&#039;&#039;&#039;&lt;br /&gt;
** Set how the heading should look like: Abbreviated heading OR full headings OR question codes&lt;br /&gt;
** Convert spaces in question text to underscores&lt;br /&gt;
*&#039;&#039;&#039;Answers&#039;&#039;&#039;&lt;br /&gt;
** You can either export full answers or convert answer codes Y and N to a defined variable&lt;br /&gt;
*&#039;&#039;&#039;Format&#039;&#039;&#039;&lt;br /&gt;
** Microsoft Word (latin charset)&lt;br /&gt;
** Microsoft Excel (all charsets)&lt;br /&gt;
** CSV File (all charsets)&lt;br /&gt;
** PDF&lt;br /&gt;
*&#039;&#039;&#039;Column Control&#039;&#039;&#039;&lt;br /&gt;
** Set which answers should be exported. All answers in this list are represented by their [http://docs.limesurvey.org/tiki-index.php?page=SGQA+identifier&amp;amp;structure;=English+Instructions+for+LimeSurvey SGQA identifier]&lt;br /&gt;
** Set which &#039;&#039;&#039;&#039;&#039;token&#039;&#039;&#039;&#039;&#039; data should be exported. This option is only available if your survey is &#039;&#039;&#039;&#039;&#039;not anonymous&#039;&#039;&#039;&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
=SPSS Export=&lt;br /&gt;
&lt;br /&gt;
==General==&lt;br /&gt;
&lt;br /&gt;
To export your response data to SPSS go to Responses &amp;amp; Statistics section and click the icon to export to SPSS.&lt;br /&gt;
&lt;br /&gt;
[[File:spss_toolbar.png]]&lt;br /&gt;
&lt;br /&gt;
==Export and filter data==&lt;br /&gt;
&lt;br /&gt;
When exporting data to SPSS there are two filter options. You can select &#039;&#039;&#039;which data&#039;&#039;&#039; should be selected (&#039;&#039;all records/completed records only/incompleted records only&#039;&#039;) and for &#039;&#039;&#039;which SPSS version&#039;&#039;&#039; the export files will be used (&#039;&#039;prior version 16/16 or up&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
SPSS export includes two files:&lt;br /&gt;
# a syntax file (&#039;&#039;survey_xxxx_SPSS_syntax_file.sps&#039;&#039;)&lt;br /&gt;
# and a data file (&#039;&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
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&#039;t do that.&lt;br /&gt;
&lt;br /&gt;
==Import data in SPSS==&lt;br /&gt;
&lt;br /&gt;
Place the two files in the same folder on your drive (example: &#039;&#039;c:\data\survey_xxxx_SPSS_syntax_file.sps&#039;&#039; and &#039;&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
We have two options now:&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
[[File:spss_explorer-screenshot.jpg]]&lt;br /&gt;
&lt;br /&gt;
Now you can just choose Run-&amp;gt;All from the opened window and after some time have your output dataset that you can save as a normal .sav file.&lt;br /&gt;
&lt;br /&gt;
2. Sometimes the easy solution above does not work. Then you can proceed as follows:&lt;br /&gt;
* Open SPSS&lt;br /&gt;
* Choose File-&amp;gt;Open-&amp;gt;Syntax&lt;br /&gt;
* Choose the appropriate file: c:\data\survey_xxxx_SPSS_syntax_file.sps&lt;br /&gt;
* Now the syntax opens.&lt;br /&gt;
* Change the line that reads &#039;&#039;/FILE=&#039;survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039; to include the path where the files are: &#039;&#039;/FILE=&#039;c:\data\survey_xxxx_SPSS_data_file.dat&#039;&#039;&#039;&lt;br /&gt;
* Now mark the whole command text and choose Run-&amp;gt;All from the menu and after a while (please be patient) you have the dataset with all info like questions, labels etc.&lt;br /&gt;
&lt;br /&gt;
=R Export=&lt;br /&gt;
&lt;br /&gt;
Feel free to add more information if you have some!&lt;br /&gt;
&lt;br /&gt;
The freeware software [http://www.r-project.org/ R] is an alternative for SPSS. It is closely linked to the SPSS export in LimeSurvey. Instructions on how to import your dataset in R:&lt;br /&gt;
#Download the data and the syntax file from the browse response screen.&lt;br /&gt;
#Save both of them on the R working directory (use &#039;&#039;getwd()&#039;&#039; and &#039;&#039;setwd()&#039;&#039; on the R command window to get and set it).&lt;br /&gt;
#Enter: &#039;&#039;source(&amp;quot;Surveydata_syntax.R&amp;quot;, encoding = &amp;quot;UTF-8&amp;quot;)&#039;&#039; on the R command window&lt;br /&gt;
&lt;br /&gt;
=VVExport ([[File:exportvv.png]]) and VVImport ([[File:importvv.png]])=&lt;br /&gt;
&lt;br /&gt;
Once you&#039;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.&lt;br /&gt;
&lt;br /&gt;
VVExport and VVImport (the &amp;quot;VV&amp;quot; stands for vertical verification) allow 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 the import the file again into your responses table using the &amp;quot;VVImport&amp;quot; feature.&lt;br /&gt;
&lt;br /&gt;
Things you should be aware of:&lt;br /&gt;
* If you want to import answers using &amp;quot;VVImport&amp;quot; make sure to check whether the answers should be added to the existing answers or all answers should be overwritten.&lt;br /&gt;
* If you are trying to import answers from a diffrent 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.&lt;br /&gt;
&lt;br /&gt;
==Exporting a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A &#039;vv survey file&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Clicking on &amp;quot;Export a VV survey file&amp;quot; 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 &amp;quot;human readable&amp;quot; column heading that details the name of the question/answer field. The second row is the internal PHP/database column name for that response.&lt;br /&gt;
&lt;br /&gt;
You should not modify the first two rows of this spreadsheet if you want to be able to &amp;quot;import&amp;quot; the data back into LimeSurvey at a later point.&lt;br /&gt;
&lt;br /&gt;
==Importing a VV survey file==&lt;br /&gt;
&lt;br /&gt;
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 deactivated the survey when you exported the data you will need to activate the survey in the normal way when doing this.&lt;br /&gt;
&lt;br /&gt;
Then, from the browse screen, choose the &amp;quot;Import a VV Survey file&amp;quot; icon.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Import a VV Survey File&amp;quot; screen needs you to choose the &amp;quot;vvexport&amp;quot; you are importing. If you choose to &amp;quot;Exclude Record IDs&amp;quot; the records will be imported and brand new Record ID&#039;s will be generated for them. If you un-check this box, then the original record id&#039;s will be imported.&lt;br /&gt;
&lt;br /&gt;
There are a range of options you can choose that tell LimeSurvey how to deal with double or multiple entries.&lt;br /&gt;
*Report an error (and skip the new record).&lt;br /&gt;
*Renumber the new record&lt;br /&gt;
*Ignore the new record&lt;br /&gt;
*Replace the existing record&lt;br /&gt;
&lt;br /&gt;
==How to use VV-Export and VV-Import:==&lt;br /&gt;
&lt;br /&gt;
The VV-Import function is not particularly smart. The spreadsheet being imported has to be massaged into shape so that it matches the new survey.&lt;br /&gt;
&lt;br /&gt;
The idea of VV-Export/VV-Import was to allow import of results from a survey table that had changed. My standard procedure for the VV-Export/Import process is to:&lt;br /&gt;
#Create the new survey&lt;br /&gt;
#Activate the new survey&lt;br /&gt;
#Perform a VV-Export from the _new_ survey (first export)&lt;br /&gt;
#Perform a VV-Export from the _old_ survey (second export)&lt;br /&gt;
#Cut the two top rows from the first export and insert them as the top two rows in the second export.&lt;br /&gt;
#While leaving the first two rows unchanged, cut and paste the columns below so that they are now in the right place according to the first two rows.&lt;br /&gt;
#Once all the data is in the correct spot, delete the 3rd and 4th row (ie: the headings from the second export)&lt;br /&gt;
#Save it all as a CSV file&lt;br /&gt;
#Perform the VV-Import into the _new_ survey&lt;br /&gt;
&lt;br /&gt;
=Other export options=&lt;br /&gt;
&lt;br /&gt;
==Export a single response==&lt;br /&gt;
&lt;br /&gt;
If you want to export an individual response, you can do it in 3 ways:&lt;br /&gt;
&lt;br /&gt;
1. Login to limesurvey admin backend, choose your survey, goto &amp;quot;Edit survey settings&amp;quot; -&amp;gt; &amp;quot;Notification and data management&amp;quot; and make sure you receive basic email notifications.&lt;br /&gt;
&lt;br /&gt;
Every time someone has completed a survey, you will receive an email with a link: &amp;quot;Click the following link to see the individual response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will take you to a page with a button above the data saying &amp;quot;Export this response&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. Login to limesurvey admin backend, choose your survey and &amp;quot;Browse responses for this survey&amp;quot;. Click on &amp;quot;Display responses&amp;quot; and the id number you want to export in the left column. Then you can click on &amp;quot;Export this survey&amp;quot; above the data.&lt;br /&gt;
&lt;br /&gt;
3. Login to limesurvey admin backend, choose your survey and &amp;quot;Export results to application&amp;quot;. In the last field above &amp;quot;Export data&amp;quot; you can choose which entry you want to export.&lt;br /&gt;
&lt;br /&gt;
==Match Responses From Different Surveys (longitudinal survey)==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The steps to implementing this are as follows:&lt;br /&gt;
&lt;br /&gt;
1. Create the survey&lt;br /&gt;
&lt;br /&gt;
2. Make sure the survey is non-anonymous and uses tokens. To create a non-anonymous survey:&lt;br /&gt;
&lt;br /&gt;
a) Click on the edit survey button:&lt;br /&gt;
&lt;br /&gt;
[[File:editsurvey.png]]&lt;br /&gt;
&lt;br /&gt;
b) Then under the Notification &amp;amp; data management tab select &amp;quot;No&amp;quot; for Anonymous answers:&lt;br /&gt;
&lt;br /&gt;
[[File:make_private.png]]&lt;br /&gt;
&lt;br /&gt;
3. Activate the survey.&lt;br /&gt;
&lt;br /&gt;
When you activate the survey, click on the &amp;quot;switch to closed-access mode&amp;quot; button to create the token table:&lt;br /&gt;
&lt;br /&gt;
[[File:switch_to_closed.png]]&lt;br /&gt;
&lt;br /&gt;
4. Populate the tokens table with whatever method you wish (follow the instructions found at the [[Tokens]] page ).&lt;br /&gt;
&lt;br /&gt;
5. Export the survey results and make sure you include the token information.&lt;br /&gt;
&lt;br /&gt;
To export click &#039;&#039;browse results&#039;&#039;...&lt;br /&gt;
&lt;br /&gt;
[[File:browse_results.png]]&lt;br /&gt;
&lt;br /&gt;
...and then &#039;&#039;export&#039;&#039;:&lt;br /&gt;
&lt;br /&gt;
[[File:export2.png]]&lt;br /&gt;
&lt;br /&gt;
Remember to choose one or more elements from the token table to associate with the survey responses:&lt;br /&gt;
&lt;br /&gt;
[[File:export_tokens.png]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Problems &amp;amp; Solutions=&lt;br /&gt;
&lt;br /&gt;
==Excel==&lt;br /&gt;
&lt;br /&gt;
===Modifying responses in Excel prior to Import===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Edit .csv with Excel===&lt;br /&gt;
&lt;br /&gt;
In general &#039;&#039;&#039;&#039;&#039;we do not recommend to use Excel to edit the exported .csv files&#039;&#039;&#039;&#039;&#039; 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):&lt;br /&gt;
&lt;br /&gt;
System Control|Region- Languageoptions|Regional Settings, customize...|Tab Numbers|Digit grouping symbol| replace ; with ,&lt;br /&gt;
&lt;br /&gt;
===Workaround to edit .csv files with Excel===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Export a question similar to what you would like to reuse as .csv file&lt;br /&gt;
* Open the CSV file in a rawtext editor&lt;br /&gt;
* Copy the part that has the answers to Excel, and parse it with Text to Columns or equivalent.&lt;br /&gt;
* Use the talent of Excel to allow pasting text in columns to paste in 20, 50, 100 answers, as you wish&lt;br /&gt;
* Save the file as Excel CSV, which will likely have no quotes.&lt;br /&gt;
* Open this file in the editor, and Select All, Copy&lt;br /&gt;
* Go back to the file you opened in 2)&lt;br /&gt;
* Paste over the answers there&lt;br /&gt;
* Save AS, with a different name, maybe one that you can remember for reuse&lt;br /&gt;
* Import this file.&lt;br /&gt;
&lt;br /&gt;
===Excel - export limited to 255 columns===&lt;br /&gt;
&lt;br /&gt;
Due to limitations in Excel (versions lower and equal to 2003), LS 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].&lt;br /&gt;
&lt;br /&gt;
Although newer spreadsheets (Excel &amp;gt;= 2007, OpenOffice) can display more than 255 columns, the internal module used by LimeSurvey still can&#039;t export more than 255 columns.&lt;br /&gt;
&lt;br /&gt;
Two workarounds are however possible, use one of the following solutions:&lt;br /&gt;
* Either export to CSV and import in your spreadsheet&lt;br /&gt;
* Or use multiple exports (selecting at most 250 columns at a time), then merge the exported results&lt;br /&gt;
&lt;br /&gt;
===Excel/.csv - export fails===&lt;br /&gt;
&lt;br /&gt;
If you are unable to export your data to excel or into a .csv file please try to clear your browser cache and cookies.&lt;br /&gt;
&lt;br /&gt;
==SPSS export==&lt;br /&gt;
&lt;br /&gt;
===General steps===&lt;br /&gt;
&lt;br /&gt;
To import the LimeSurvey response data please use the following steps:&lt;br /&gt;
#Click on the &#039;Export to SPSS&#039; icon.&lt;br /&gt;
#From the select boxes select which responses you want to export and your SPSS version.&lt;br /&gt;
#Download both files, the .sps (SPSS syntax command file) and .dat file (data file)&lt;br /&gt;
#Open the .sps file with SPSS by opening SPSS, then select &#039;Choose another type of file&#039; and select the downloaded .sps file.&lt;br /&gt;
#Now an editor opens inside SPS where you can edit the commands in that file. Look for the line that starts with &#039;/FILE=...&#039;&lt;br /&gt;
#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=&#039;c:\temp\survey_(xxxx)_SPSS_data_file.dat&#039;&lt;br /&gt;
#Now select all commands inside the editor by pressing CTRL-A.&lt;br /&gt;
#From the SPSS menu select Run/All.&lt;br /&gt;
#Be patient, it will take some time to import all data and labels. Check the status bar for the progress.&lt;br /&gt;
#Done!&lt;br /&gt;
&lt;br /&gt;
===Possible error messages in SPSS===&lt;br /&gt;
&lt;br /&gt;
====ERROR. command name:Get Data====&lt;br /&gt;
&lt;br /&gt;
If you receive the error message &#039;&#039;ERROR. command name:Get Data. 2267 Unexpected Token missing.&#039;&#039; please edit the forth line of your syntax file so it points to the absolute path of the data file like&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;C:\spss\Data\limesurvey\SPSS\survey_35276_SPSS_data_file.dat&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Error: &amp;quot;Text value unmappable in the current server locale&amp;quot;====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt;Open SPSS. Go to Edit &amp;gt; Options &amp;gt; Character encoding for data and syntax. Change the option to &amp;quot;unicode&amp;quot;.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey data can now be exported to SPSS 16 without any problem.&lt;br /&gt;
&lt;br /&gt;
===Define the scale to use for your variable by setting a question attribute===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==VV Export/Import==&lt;br /&gt;
&lt;br /&gt;
===VV - Problems with vv import===&lt;br /&gt;
&lt;br /&gt;
If you have difficulties importing a vv file, try a Tab-delimited file and it should work fine.&lt;br /&gt;
&lt;br /&gt;
==Other problems and solutions==&lt;br /&gt;
&lt;br /&gt;
===Copying responses into a different survey (using tokens)===&lt;br /&gt;
# Create new survey, add a dummy response, export the response file, open in Excel. This creates the format for the new import file.&lt;br /&gt;
# Export the responses from the old survey, including tokens, open in Excel.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# Save as .txt file.&lt;br /&gt;
# Use VVImport to import the new data into the new survey.&lt;br /&gt;
# 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 &amp;quot;2009-12-01!&lt;/div&gt;</summary>
		<author><name>Steve</name></author>
	</entry>
</feed>