<?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=Aniesshsethh</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=Aniesshsethh"/>
	<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/Special:Contributions/Aniesshsethh"/>
	<updated>2026-08-13T12:30:49Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2056</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2056"/>
		<updated>2012-11-06T18:52:52Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Design a new LimeSurvey Template (Part 1, 2, 3)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: gautamgupta&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Design a new good-looking template for LimeSurvey front-end in HTML5/CSS3. Go creative!&lt;br /&gt;
&lt;br /&gt;
One template counts for 3 tasks. This is part &#039;&#039;N&#039;&#039;/3 of the task. Please claim the tasks in order.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the template system.&lt;br /&gt;
*Start with the designing process, discuss the design with a mentor&lt;br /&gt;
*Finalize the design&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| TBD&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi,[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2057</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2057"/>
		<updated>2012-11-06T18:45:11Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Design a new LimeSurvey Template (Part 1, 2, 3)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: gautamgupta&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Design a new good-looking template for LimeSurvey front-end in HTML5/CSS3. Go creative!&lt;br /&gt;
&lt;br /&gt;
One template counts for 3 tasks. This is part &#039;&#039;N&#039;&#039;/3 of the task. Please claim the tasks in order.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the template system.&lt;br /&gt;
*Start with the designing process, discuss the design with a mentor&lt;br /&gt;
*Finalize the design&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| TBD&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi,[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2058</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2058"/>
		<updated>2012-11-06T18:43:32Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Design a new LimeSurvey Template (Part 1, 2, 3)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: gautamgupta&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Design a new good-looking template for LimeSurvey front-end in HTML5/CSS3. Go creative!&lt;br /&gt;
&lt;br /&gt;
One template counts for 3 tasks. This is part &#039;&#039;N&#039;&#039;/3 of the task. Please claim the tasks in order.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the template system.&lt;br /&gt;
*Start with the designing process, discuss the design with a mentor&lt;br /&gt;
*Finalize the design&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| TBD&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi],[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi,[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2059</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2059"/>
		<updated>2012-11-06T18:37:25Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Design a new LimeSurvey Template (Part 1, 2, 3)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: gautamgupta&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Design a new good-looking template for LimeSurvey front-end in HTML5/CSS3. Go creative!&lt;br /&gt;
&lt;br /&gt;
One template counts for 3 tasks. This is part &#039;&#039;N&#039;&#039;/3 of the task. Please claim the tasks in order.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the template system.&lt;br /&gt;
*Start with the designing process, discuss the design with a mentor&lt;br /&gt;
*Finalize the design&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| TBD&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi,[http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Google_Code-in_2012&amp;diff=1982</id>
		<title>LimeSurvey Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Google_Code-in_2012&amp;diff=1982"/>
		<updated>2012-11-06T11:36:19Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &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; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Please note that we are currently applying for Google Code-in and are not accepted yet. Please watch our [http://www.limesurvey.org] for news if we are accepted.&amp;lt;/span&amp;gt; &amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=General information=&lt;br /&gt;
&lt;br /&gt;
Google has been continuously supporting Open Source Projects and students coming together since 2005 through its &#039;&#039;Google Summer of Code Programs&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Now Google Code-in 2012 has been announced and is &#039;&#039;on&#039;&#039;!&lt;br /&gt;
&lt;br /&gt;
LimeSurvey will apply as a mentoring organization and is hopeful and excited about he opportunity to participate in Google Code-in 2012. We plan to give students an excellent environment and platform to &#039;&#039;&#039;learn&#039;&#039;&#039; and most importantly to have &#039;&#039;&#039;fun&#039;&#039;&#039; (:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
The LimeSurvey community, at the same time, will benefit by students&#039; participation and their fresh eyes and ideas.&lt;br /&gt;
&lt;br /&gt;
==Google Code-in program information==&lt;br /&gt;
&lt;br /&gt;
Google Code-in is a great contest both for Open Source organizations like LimeSurvey as well as young students because it gives a platform where several small tasks on Open Source Projects are done by students and in return get rewarded by Google.&lt;br /&gt;
&lt;br /&gt;
There&#039;s a lot more information available in Google&#039;s Code-in [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page FAQ] and [http://code.google.com/opensource/gci/2012/index.html home page]. You can also join the [http://groups.google.com/group/gci-discuss Google Code-In discussion group] to get feedback or ask questions about Google Code-in.&lt;br /&gt;
&lt;br /&gt;
The time-line can be found [http://www.google-melange.com/gci/events/google/gci2012 here].&lt;br /&gt;
&lt;br /&gt;
==LimeSurvey specific information==&lt;br /&gt;
&lt;br /&gt;
Welcome to the LimeSurvey Community (:biggrin:). LimeSurvey is an open source survey engine that allows people to create and deploy surveys (from marketing to academic to engineering applications). LimeSurvey is written in PHP and used by many high profile organizations including [https://wiki.ubuntu.com/ServerTeam &#039;&#039;&#039;Ubuntu Server Team&#039;&#039;&#039;], [http://foundation.gnome.org/ &#039;&#039;&#039;GNOME Foundation&#039;&#039;&#039;] and [http://www.vorarlberg.at/ &#039;&#039;&#039;Office of the Austrian Vorarlberg State Government&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
LimeSurvey is loved and used by many universities, students, medical institutes, non-profit organizations, marketing companies and more around the world for many years. Even in the 2004 &#039;&#039;&#039;U.S. presidential election&#039;&#039;&#039;, the [http://www.verifiedvoting.org/article.php?id=5207 &#039;&#039;&#039;Verified Voting Foundation&#039;&#039;&#039;] used PHPSurveyor (as LimeSurvey was then known) to gather data about voting irregularities. Sourceforge provides LimeSurvey as a free application for open source projects and LimeSurvey keeps turning up in new places.&lt;br /&gt;
&lt;br /&gt;
It&#039;s loved because it is free, flexible and constantly improving - and that because it has a dedicated and committed team of voluntary developers who love the challenge and satisfaction of using and building such a tool - since 2003 over the whole lifespan of the project [http://gitstats.limesurvey.org/ we did 6 commits per day on average].&lt;br /&gt;
&lt;br /&gt;
LimeSurvey is widely used. It has been directly downloaded over &#039;&#039;&#039;140,000 times&#039;&#039;&#039; in the last 12 months alone, and is also distributed as a package in the &#039;&#039;&#039;Ubuntu Linux Distribution&#039;&#039;&#039;, and included as a pre-installed application in many standard Web Hosting packages (such as &#039;&#039;&#039;Fantastico&#039;&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
LimeSurvey is recognized as a leader in its field of application. On November 29, 2007 LimeSurvey won the &#039;&#039;1st prize award&#039;&#039; at the &#039;&#039;Les Troph&amp;amp;eacute;es du Libre &#039;&#039; contest in the category Corporate Management. In 2008 LimeSurvey was nominated in the category Best Project for the Enterprise in the SourceForge.net &#039;&#039;&#039;Community Choice Awards 2008&#039;&#039;&#039;. After that LimeSurvey was successful in being selected for three consecutive years as a mentoring organization for the Google Summer of Code in 2009-2011 which we are very proud of.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey was ported in the Google Summer of Code 2011 by students to use the CodeIgniter framework - however CodeIgniter suddenly put up a strange licensing model on their framework so we made another switch to the &#039;&#039;&#039;Yii PHP framework&#039;&#039;&#039; - so to make it modular and obey the MVC approach. In October 2012 this port was finished and a stable version 2.0 was released. However large parts of the code still need to be re-factored to smooth out the way for the future.&lt;br /&gt;
&lt;br /&gt;
It&#039;s a perfect opportunity for a Google Code-in student like yourself to get involved early in a project that has a strong history and an even stronger future. Our community is welcoming and fun and our core developers (all volunteers) have a long history and alot of experience they would like to share.&lt;br /&gt;
&lt;br /&gt;
==Google Code-in student aspirants==&lt;br /&gt;
&lt;br /&gt;
Please visit our [http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+Project+Ideas+for+Google+Code-in+2012 ideas page] and see if any idea interests you. If you have an idea of your own, then develop it. If any idea excites you, and you want to implement that feature , see how you can [#|get started] on it. Come and join us on the [http://www.limesurvey.org/en/community-services/live-chat IRC channel on Freenode (#limesurvey)] and talk about what you would like to do.&lt;br /&gt;
&lt;br /&gt;
==LimeSurvey mentors==&lt;br /&gt;
&lt;br /&gt;
The following core member are looking forward to mentor students during the Code-in contest:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&amp;lt;center&amp;gt;&#039;&#039;&#039;Mentor Name&#039;&#039;&#039;&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;&#039;&#039;&#039;Nick&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Denis Chenu&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;shnoulle&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Menno Dekker&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;mdekker&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Diogo Gon&amp;amp;ccedil;alves&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;dionet&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Marcel Minke&amp;lt;/center&amp;gt; &amp;lt;center&amp;gt;[http://docs.limesurvey.org/tiki-index.php?page=UserPage Mazi||Mazi]&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Sam Mousa&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;sammousa&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Tony Partner&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;tpartner&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Carsten Schmitz&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;c_schmitz&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Aaron Smith&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;ajs&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;center&amp;gt;Aniessh Sethh&amp;lt;/center&amp;gt;||&amp;lt;center&amp;gt;aniesshsethh&amp;lt;/center&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Our ideas page==&lt;br /&gt;
*[http://docs.limesurvey.org/tiki-index.php?page=LimeSurvey+Project+Ideas+for+Google+Code-in+2012 Google Code-in Ideas Page]&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2061</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2061"/>
		<updated>2012-11-03T12:54:13Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2062</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2062"/>
		<updated>2012-11-03T12:54:00Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2063</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2063"/>
		<updated>2012-11-03T12:50:57Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for Central Participants Database attribute mapping screens===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to suggest some new designs with the help of mockups to improve the attribute map screen. We are looking for some out of the box thinking as to how best this UI can be made to handle 100&#039;s of attribute mappings which is quite difficult with the current UI.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Have a look at the attribute map screen and try to map large number of attributes to understand the problem associated with the current UI.&lt;br /&gt;
*Analyse the problem and think how to improve the UI.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create drafts of the new UI and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2064</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2064"/>
		<updated>2012-11-03T12:43:57Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature - Participant Import Export and attribute map===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - CSV Import/Export===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Training: Create a video tutorial on how to use the new Central Participant Database Feature - Other Features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various features mentioned in what the video should include&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2065</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2065"/>
		<updated>2012-11-03T12:36:07Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Central Participant Database Feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants.Your task is to create video tutorials showing how to use this new feature.&lt;br /&gt;
&lt;br /&gt;
The Video should include:&lt;br /&gt;
*How to use Central panel by showing the user how to import/export the participants from central database to token table and vice versa&lt;br /&gt;
*The attribute map feature of CPDB&lt;br /&gt;
*Different type of attributes that can be created by CPDB with multilingual support&lt;br /&gt;
*Share Feature with user edit rights of CPDB&lt;br /&gt;
*Different ways in which the user can import/export participants using the CSV&lt;br /&gt;
*The Blacklist feature of CPDB&lt;br /&gt;
*User id editable feature of CPDB&lt;br /&gt;
&lt;br /&gt;
It might 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 http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a video tutorial about using the Central Participant Database and it&#039;s various 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;
===Documentation : Change the screenshots of documentation and improve it to depict changed icons and new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of participants. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2066</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2066"/>
		<updated>2012-11-03T12:15:07Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots of documentation to depict changes icons/new features===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of surveys. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2067</id>
		<title>LimeSurvey Project Ideas for Google Code-in 2012</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=LimeSurvey_Project_Ideas_for_Google_Code-in_2012&amp;diff=2067"/>
		<updated>2012-11-03T12:14:05Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Welcome Google Code-in Student aspirants!=&lt;br /&gt;
&lt;br /&gt;
Please check first if you are an [http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions eligible candidate] for the GCI program. This page lists task ideas developed by core developers and the LimeSurvey community. This way we get a great mix of &#039;most-wanted&#039; solutions from the users and the developers.&lt;br /&gt;
&lt;br /&gt;
We wish good luck to you and we hope that this contest will be alot of fun for all of us(:biggrin:) !&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div class=&amp;quot;simplebox&amp;quot;&amp;gt; &amp;lt;span style=&#039;color:#C00&#039;&amp;gt;Important:&amp;lt;/span&amp;gt; All tasks will have to be implemented based on [https://github.com/LimeSurvey/LimeSurvey/tree/2.1 the development version 2.1 available on github] . &amp;lt;/div&amp;gt;&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/homepage/google/gci2012 Google Code-in task tracker] (which will be available once the contest has officially started). 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;
==Task category: Code==&lt;br /&gt;
&lt;br /&gt;
===Code: Remove &amp;lt;center&amp;gt; tags from LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
In LimeSurvey there are still a couple places where the obsolete  &amp;lt;center&amp;gt; tag is used. These need to be replaced with proper HTML &amp;amp; CSS.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Create a small 1-question survey.&lt;br /&gt;
*Use a proper tool to search for &amp;lt;center&amp;gt; tags in the source code.&lt;br /&gt;
*Remove each of these tags and replace them with proper HTML and CSS (CSS preferred)&lt;br /&gt;
*Important: Test if the appearance of your replacement matches the old behaviour&lt;br /&gt;
*Create a gitHub pull request and submit the pull request link for review.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML, CSS|| Moderate||c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add styled error message to pre-installer failure===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After uploading LimeSurvey to a web server, normally the installer will run when the public url is requested. In the case that a specific directory (tmp/runtime) on the server is not writable the installer can not start. Currently just a single line describing the error is shown, this should be replace by an HTML page in the design of the installer.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Analyze the problem (if you have problems reproducing please contact your mentor)&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;
*Issue a git pull request&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP,HTML||mdekker&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Implement ajax popup dialog at token overview table when adding a survey participant===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey admin backend already supports jqgrid features for the token overview screen. But when adding a new token entry, a new page is used which is old fashioned and could be far more user friendly when switching to a jQuery popup dialogue. That&#039;s what we need your help with!&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&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;
*Look at the current dialog when adding a token. This one should appear in a jQuery popup dialog instead. After the record was added, the new record should be shown first in the grid (grid needs to re-sorted by ID descending) so that the user automatically sees the new entry on top.&lt;br /&gt;
*When editing a record current inline editing is used - this has to be changed to using the popup dialog, too.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, PHP, HTML, some CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to main Limesurvey admin menu elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;main admin page&#039;&#039;&#039;, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for this screen and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs to Limesurvey token administration elements===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;token administration page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related views for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add unique CSS IDs for all elements at Limesurvey&#039;s &amp;quot;Browse responses&amp;quot; screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For having more options to fully customize the Limesurvey admin interface and to hide certain elements at a customized layout, all Limesurvey admin menu elements (buttons, drop downs, text elements and so on) should be assigned their own, unique CSS ID.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Have a look at the HTML of the Limesurvey admin interface.&lt;br /&gt;
*Create a list of elements on the &#039;&#039;&#039;browse response page&#039;&#039;&#039; and all pages linked there, sorted by &amp;quot;buttons&amp;quot;, &amp;quot;texts&amp;quot;, &amp;quot;...anything else...&amp;quot; that need to be changed.&lt;br /&gt;
*Discuss the list with your mentor to check if all admin interface elements are listed&lt;br /&gt;
*Edit the related view for these screens and assign each element it&#039;s unique ID&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|HTML and CSS|| c_schmitz, Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Improve work flow of the &amp;quot;send invitation/reminder&amp;quot; feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Currently, when sending email invitations or reminders, you don&#039;t see the scope of concerned data sets (some have already received an invitation/reminder, some might have opted out, some might have a missing token/email address). The user sees the list of email receivers AFTER having sent the emails which is not that good. Your task is to present these details up front.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the &amp;quot;send email invitation/reminder&amp;quot; feature and note the single work flow steps when sending these emails.&lt;br /&gt;
*The work-flow should be changed so that when clicking &amp;quot;send email invitations/reminders&amp;quot;, a list of people who will receive the email is created up front so the user can look into the details.&lt;br /&gt;
*By default a checked checkbox is shown in front of each listed user who will receive an email .&lt;br /&gt;
*A button &amp;quot;send emails to selected users&amp;quot; is placed on top.&lt;br /&gt;
*Furthermore, you should add a &amp;quot;list people who will NOT receive the email&amp;quot; link below which shows this different list when being clicked (default = hidden). That second list of users who will NOT receive an email contains users sorted by status like&lt;br /&gt;
**&amp;quot;invitation already received&amp;quot; (invitations) / &amp;quot;max number of reminders already sent&amp;quot; (reminders)&lt;br /&gt;
**&amp;quot;missing token&amp;quot;&lt;br /&gt;
**&amp;quot;missing email&amp;quot;&lt;br /&gt;
**&amp;quot;opted out&amp;quot;&lt;br /&gt;
** anythingh else you can think of&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add a &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
A check for duplicate token data already exists for the CSV import feature. This is not sufficient because user A might import data from a CSV file and user B might add token data later manually, which might lead to duplicate entries. That&#039;s why we need a new function which is called by clicking a certain icon on the admin screen. Here is what this new function should do:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function which is used when importing token data from a CSV file.&lt;br /&gt;
*Talk to your mentor where at the admin interface a new icon for the duplicate token check can be added and how it might look like. Afterwards, add the icon and link to the new feature.&lt;br /&gt;
*Create a new view which is shown after the button was clicked. This view should contain columns the user wants to check for duplicates. We need at least:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script should check the whole token data for duplicates.&lt;br /&gt;
*Extend the current view to show the duplicates below the filter options described above. It should include a tabular overview similar to the standard token list which lists only duplicate entries. If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name&lt;br /&gt;
*For each data set, mark the according cell where duplicate data was found with a red border.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Add sorting and edit/delete token functionality to &amp;quot;Check for duplicates&amp;quot; function at the token admin screen===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Important: This task can only be executed if task &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; is completed. Don&#039;t start to work on this before that or your work will be most likely futile.&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Add a &#039;Check for duplicates&#039; function at the token admin screen&amp;quot; task was completed, a next step is to add some additional functionality to the screen which lists the duplicates. Here are the details:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Create a simple test survey and create a token table which is filled with 2-3 test data sets.&lt;br /&gt;
*Have a look at the ducplicate check function it supports checking for duplicates based on:&lt;br /&gt;
**First name&lt;br /&gt;
**Last name&lt;br /&gt;
**Email&lt;br /&gt;
**Token&lt;br /&gt;
*For each column ticked at this screen, the script checks the whole token data for duplicates.&lt;br /&gt;
*Your task is to extend the current view which lists the duplicates: If only &amp;quot;email&amp;quot; was selected previously, the overview should be sorted by email, if only &amp;quot;last name&amp;quot; was checked, it should be sorted by last name and so on. If several filters were clicked, the data should be sorted by last name.&lt;br /&gt;
*Add buttons and a function to delete and edit a certain data set at the table of duplicate entries. These features already exist at the standard token overview, so no need to re-invent the wheel.&lt;br /&gt;
*Discuss the patches with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, MySQL, HTML, jQuery, CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Check for valid question code when adding/editing a question===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Limesurvey 1.92 we have a great new feature called [[Expression Manager|Expression Manager]] which requires unique question codes and disallows certain chars to be used. Currently, there is no check at question code input if the entered question code is valid. So this is your task.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - create a small survey of 3-4 questions and assign them valid and non-valid question codes.&lt;br /&gt;
*Valid question codes may NOT&lt;br /&gt;
**start with a number&lt;br /&gt;
**contain dots&lt;br /&gt;
**use spaces&lt;br /&gt;
**ADD MORE RESTRICTIONS HERE&lt;br /&gt;
*Assign a JavaScript/jquery function to the question code fields which takes care of different validations:&lt;br /&gt;
**When adding or editing a question code, the validation function should check the code syntax for issues listed above and show a message like &amp;quot;Invalid question code&amp;quot; right to the field.&lt;br /&gt;
**Another check should check the input against a list of existing question codes (this has to be generated on page load) and show an error like &amp;quot;Question code already used at question #123 (&#039;How old are you?&#039;)&amp;quot;&lt;br /&gt;
*Input should be validated at runtime when the user inputs the characters&lt;br /&gt;
*The question code input field should use a red border as long as it is invalid input. When the input is valid, a green border and a message like &amp;quot;Valid question code&amp;quot; should be used.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|Javascript/jQuery, HTML, some PHP and MySQL|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Create unit tests===&lt;br /&gt;
&lt;br /&gt;
Now that we are using a PHP 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;
*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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||mrp001&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 87 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in tokens_dynamic.php, Questions.php, ParticipantAttributeNames.php, Groups.php , update_helper.php and Answers.php. (There are about be about 6 of themin these files). Also do 4 more from updatedb_helper.php (so in total you have to do 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU3===&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if tasks ARI1 and ARI2 are completed. Do NOT start to work on this before that or your work will most likely be futile.LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 73 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU4===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU3 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 63 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU5===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU4 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 52 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU6===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU5 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 41 of them, you need to do only 11 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU7===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU6 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 30 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU8===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU7 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 20 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;update() calls to use the model instead - Task ARU9===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: This task can only be executed if task ARU8 is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the update() commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;update&amp;quot; in updatedb_helper.php (There are about be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in InstallerController.php and common_helper.php (should be about 10 of them)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from Adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in import_helper.php (There are about be about 17 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in updatedb_helper.php (There are about be about 14 of them, you need to do only 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in ParticipantAttributeNames.php, Participants.php, ParticipantShares.php and Survey_url_paramenters.php (In total there should be 10 of these)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;insert() calls to use the model instead - Task ARI5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). As a first step the INSERT commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be claimed if task ARI1 to ARI4 are completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;insert&amp;quot; in importhelper.php (about 7 occurences) and update_db_helper (about 4 occurences)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in InstallerController.php, tokens.php, exportresults_helper.php, Answers.php, Groups.php, Label.php, Labelsets.php and ParticipantAttributeNames.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in Participants.php (about 14 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand()-&amp;gt;select() calls to use the model instead - Task ARS3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand).These SELECT query commands have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand()-&amp;gt;select&amp;quot; in ParticipantShares.php, Participant_attribute.php, Questions.php, Surveys_languagesettings.php, User.php (about 9 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO1===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in RegisterController.php, Statistics_userController.php, checkintegrity.php, conditionsaction.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO2===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database.php, export.php and surveyadmin.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO3===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in surveypermission.php, tokens.php, index.php (about 11 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO4===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in common_helper.php (about 25 occurences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO5===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in export_helper.php (10 occurences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO6===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Survey_Common_Action.php, frontend_helper.php, activate_helper.php (10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO7===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in database_helper.php, exportresults_helper.php, em_manager_helper.php (about 10 occurrences in total)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO8===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 45 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO9===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 25 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO10===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 21 occurrences in total, you need to do only 10)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO11===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in Save.php, Conditions.php, Questions.php, Survey_links.php, Survey_permissions.php, Tokens_dynamic.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO12===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in CommentCheckQuestion.php, CommentListQuestion.php, ListQuestion.php, RadioArrayQuestion.php, RankingQuestion.php, SelectQuestion.php, TextArrayQuestion.php (about 10 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO13===&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in label_helper.php, User.php, User_groups.php, CheckQuestion.php (about 11 occurrences )&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO14===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO8 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 35 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO15===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 24 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO16===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO15 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in import_helper.php (about 13 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO17===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO14 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in statistics_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Code: Convert createCommand($query) calls to use the model instead - Task ARO18===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT NOTE: This task can only be executed if task ARO10 is completed. Do NOT start to work on this before that or your work will most likely be futile because you duplicate someone elses work. &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey has been plainly ported from adodb to CodeIgniter to Yii and so many of our database queries are still direct SQL commands (CDBCommand). These queries (which are written in plain SQL) have to be changed to use the model (CActiveRecord) instead (to ensure data integrity)&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Search for occurrences of &amp;quot;createCommand($&amp;quot; in updatedb_helper.php (about 15 occurrences in total, you need to do only 11)&lt;br /&gt;
*Replaces these with calls to the related ActiveRecord models instead - and don&#039;t forget test each by running the related application parts.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, Yii, SQL||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Documentation &amp;amp; Training==&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;
&#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 offers 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 as 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 settings, 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 looks like at the survey&lt;br /&gt;
*Showing how the recorded results will look like&lt;br /&gt;
&lt;br /&gt;
It might 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Conditions===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;conditions&#039;&#039;&#039;.&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 and focus on documentation about conditions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions which use the Expression Manager to define conditions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for conditions at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for conditions at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different conditions.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Assessments===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;assessments&#039;&#039;&#039;.&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 and focus on documentation about assessments and learn how to store assessment data at equation questions.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions and assessment values which uses the Expression Manager to store assessment results and sum up assessment scores.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, sum() function, ...) when using the Expression Manager for assessment results at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for assessments at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different questions and assessments.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [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 video tutorial on how to use the new Limesurvey Expression Manager - Piping===&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;
Since version 1.92 Limesurvey offers a powerful [[Expression Manager|Expression Manager]] which can be used for conditions, assessments, piping 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 correct expressions when using &#039;&#039;&#039;piping&#039;&#039;&#039;.&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 and focus on documentation about piping.&lt;br /&gt;
*Create a simple sample survey with 4-5 questions if which the first question answers can be used for piping at later questions.&lt;br /&gt;
*Make a list of what to watch out for (syntax, variable naming, ...) when using the Expression Manager for dynamic texts at Limesurvey.&lt;br /&gt;
*Create a video tutorial about using the Expression Manager for dynamic texts at Limesurvey. The users should learn how the Expression manager works and how to set up expressions for different dynamic texts.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screen Recording, Video and Sound Editing|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation : Change the screenshots used in http://docs.limesurvey.org/Central+participants+database to depict new icons used in Yii===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Since Version 2 Limesurvey offers a new feature Central Participant Database which is a central database of participants which can be shared between surveys and hence helps in easy management of surveys. However , since the documentation was first written there has been many UI changes and this task requires you to add new screenshots depicting the changes, also there has been new features added such as overwriting attribute values even if participant is already present in token table of that particular survey, you need to update that too.&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/Central+Participants+Database&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Checkout and install the 2.10 branch of LimeSurvey&lt;br /&gt;
*Take new screenshots and update http://docs.limesurvey.org/Central+participants+database&lt;br /&gt;
*Show the documentation to your mentor and discuss necessary changes.&lt;br /&gt;
*Make the changes and complete the task&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Screenshot Editing|| [http://docs.limesurvey.org/UserPage+aniesshsethh Aniessh Sethh]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Survey Creation, Technical Writing, Source Code Patching|| Machaven&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Update the Limesurvey glossary===&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;
Sometimes you stumble upon a Limesurvey feature and don&#039;t know about any details. Since Limesurvey offers have quite a wide range of features, we have created an alphabetical list of keywords like &#039;&#039;assessments, conditions, label sets, quotas, ...&#039;&#039; with 2-3 sentences to describe each feature will help a lot. With the new Limesurvey 2 release, some new features are available which are not listed at the [[LimeSurvey Glossary|Limesurvey glossary]] yet.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Do some research about new features at Limesurvey 1.92 and 2.0. Google is your friends and you should find some forum topics about this as well.&lt;br /&gt;
*Also have a look at the english manual and check which features exist there: http://docs.limesurvey.org/English+Instructions+for+LimeSurvey but are not listed at the glossary&lt;br /&gt;
*Make a list of 8-10 new glossary keywords and show it to your mentor.&lt;br /&gt;
*Create a user accout at www.limesurvey.org. Once done, click on the &amp;quot;documentation&amp;quot; link at the menu to be redirected to the wiki. You should already be logged in there and can edit pages now.&lt;br /&gt;
*Add the new keywords together with a feature description of 2-3 sentences and if possible link to the according english manual pages.&lt;br /&gt;
*Ask others at our forum (or other places) to add missing features.&lt;br /&gt;
*Discuss the updated glossary entries with your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Rewrite the survey settings page===&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 Limesurvey 2 the survey settings are split up into multilingual &amp;quot;text elements&amp;quot; and &amp;quot;general settings&amp;quot;. There are some new settings available, too, so the documentation needs an update.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Read the existing [[Creating a new survey|outdated documentation]].&lt;br /&gt;
*Check how the settings are structured at Limesurvey 2 (we can provide you with login data to our test system).&lt;br /&gt;
*Compare the current structure to the existing documentation.&lt;br /&gt;
*Rewrite the documentation including inserting cropped screenshots where needed.&lt;br /&gt;
*Submit your documentation for review by your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey|| [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: 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;
The documentation of the Limesurvey database layout is oudated (see http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development). Your task is to have a look at the current layout, update the documentation and the table description.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Have a look at http://docs.limesurvey.org/LimeSurvey+1.8+database+layout+documentation&amp;amp;structure;=LimeSurvey+development&lt;br /&gt;
*Download and install Limesurvey 2&lt;br /&gt;
*Install phpmyadmin: http://www.phpmyadmin.net/home_page/downloads.php&lt;br /&gt;
*Have a look at the current database layout and compare it to the outdated docs.&lt;br /&gt;
*Update the old document, list missing tables and columns, mark dependencies and keys, write a short description on what each table is used for.&lt;br /&gt;
*If you have problems to find it please get in touch with us on IRC. #limesurvey@freenode.org (http://www.limesurvey.org/en/community-services/live-chat)&lt;br /&gt;
*Discuss the work with your mentor&lt;br /&gt;
*Add your file at our wiki (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 and navigate to the page you want to update).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Documentation, Excel, database design||Mazi, c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a video tutorial on how to use filters at the Limesurvey statistics===&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 offers detailed statistics at the admin backend. Unfortunately, lots of users don&#039;t know that they can [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data filter data] and limit statistics to certain questions only.&lt;br /&gt;
&lt;br /&gt;
To make the filtering more clear to the user, a video showing how to set filters and demonstrating other statistic features should be added.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create a simple 5-6 question survey.&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 statistics and play around with the filter options.&lt;br /&gt;
*Create a short video showing how to set different filters for a survey and how to do cross tabulation.&lt;br /&gt;
*Show the video to your mentor&lt;br /&gt;
*Embed the video at the [http://docs.limesurvey.org/tiki-index.php?page=Statistics&amp;amp;structure;=English+Instructions+for+LimeSurvey#Filtering_data statistics wiki page].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, LimeSurvey, video capture [http://docs.limesurvey.org/tiki-index.php?page=UserPage+Mazi Mazi]&lt;br /&gt;
&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Document Limesurvey 2 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;
*Download Limesurvey 2&lt;br /&gt;
*Read [[Installation|existing installation procedure]].&lt;br /&gt;
*Run the automatic installer in English and create a nice screenshot of every single step.&lt;br /&gt;
*Make a list of required user inouts for each step.&lt;br /&gt;
*Add the single steps [http://docs.limesurvey.org/Installation&amp;amp;structure;=English+Instructions+for+LimeSurvey#Run_the_installation_script to the wiki]. Add a screenshot for each step and describe each user input so the user will know exactly what to put in there.&lt;br /&gt;
*Write down any error/warning you see during installation or while playing around with it.&lt;br /&gt;
*Fill the [http://docs.limesurvey.org/tiki-index.php?page=Installation+FAQ&amp;amp;no;_bl=y#During_Installation_Limesurvey_2.0_and_above_ troubleshooting section] on the installation FAQ wikipage with all possible warnings a user might see and the solution(s).&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Documentation &amp;amp; Training: Create a new wiki page for setting default answers===&lt;br /&gt;
&lt;br /&gt;
At Limesurvey 1.92 we extended the feature for setting default answers to questions. This isn&#039;t documented well, there needs some work to be done:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Create an account at www.limesurvey.org which can also be used to edit [http://docs.limesurvey.org our wiki].&lt;br /&gt;
*Add a note to [http://docs.limesurvey.org/Adding+answers+or+subquestions&amp;amp;structure;=English+Instructions+for+LimeSurvey the old documentation] that the feature was extended at Limesurvey 1.92 and later and link to the new wiki page&lt;br /&gt;
*Create a new wiki page (or ask your mentor to do it) called &amp;quot;Setting default answers&amp;quot;.&lt;br /&gt;
*We will provide you with a login to a Limesurvey system which contains a survey with all available question types. Check each question type if it supports the default answers feature. Note all supported question types and add the list to the wiki page.&lt;br /&gt;
*Write some introductory text what default answers can be used for.&lt;br /&gt;
*Have a look at the [http://www.limesurvey-consulting.com/pre-filling-a-text-field-at-limesurvey-1-92-using-default-answers-and-expression-manager-2/ Pre-filling a text field at Limesurvey 1.92 using default answers] blog post and port the example to the wiki.&lt;br /&gt;
*Search the forum for examples how to set default answers to a hidden question and what it can be used for. Add this to the wiki page as well.&lt;br /&gt;
*Referring to the above, also search for how default answers for hidden questions can be used for [[Quotas|quotas]].&lt;br /&gt;
*Show the new wiki page to your mentor for discussion.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Wiki editing, creating screen shots, writing documentation|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Outreach &amp;amp; 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;
We will provide you with username/password for a Limesurvey 2.0 system. We advice to google for common usability problems before starting this assignment as a source of inspiration.&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 and create a list:&lt;br /&gt;
##What was good/lacking in LimeSurvey?&lt;br /&gt;
##What was easy/hard to do?&lt;br /&gt;
#For each issue on your list, think how we could improve Limesurvey to make it more user friendly.&lt;br /&gt;
#Create a summary (0.5 - 1 page) of your findings.&lt;br /&gt;
#Discuss possible solutions to these usability problems with your mentor&lt;br /&gt;
#For each issue identified as a usability problem create a feature request at our [http://ideas.limesurvey.org/ idea tracker].&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|None, skills in web development are a plus|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Ask Limesurvey users which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Limesurvey website needs a refurbishing and we also think that the site structure should change. In order to find out which information is too hidden or generally missing, we need you to do some investigation:&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirement is that you have not worked with Limesurvey before. Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*Download and install the software and create a simple survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*Make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Your list should include 6-10 different kind of informations you were looking for and related problems about finding them.&lt;br /&gt;
*Looking at the list and thinking of your requirements, make suggestions on how to improve our website and manual&lt;br /&gt;
*Discuss the list and your proposed solutions with your mentor&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Post your finding at the forums at www.limesurvey.org to start a discussion with others. Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, a little computer knowledge to set up Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Sum up forum discussion about which information is missing or hard to find at the Limesurvey website===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This task can only be executed if task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
At task &amp;quot;Ask Limesurvey users which information is missing or hard to find at the Limesurvey website&amp;quot; we present a summary of information that might be hard to find on our website. This is to be discussed at the forums (the forum topic should already exist if previous task is done). We hope to have a lengthy discussion with our users and then need a summary of the most mentioned problems.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Think you want to do a survey to register people for an event and want to use Limesurvey. Go to www.limesurvey.org as a start and from there search for the information you need.&lt;br /&gt;
*You don&#039;t need to download and install the software and create a survey, just think of each step needed until you have successfully set up a survey asking for &amp;quot;Name&amp;quot;, &amp;quot;Email&amp;quot;, &amp;quot;Gender&amp;quot;, &amp;quot;Age&amp;quot; and two more useful questions of your choice.&lt;br /&gt;
*While searching the website/manual for the required information, make notes which information you were looking for (like &amp;quot;Where can I download the software?&amp;quot;, &amp;quot;Where are the installation instructions?&amp;quot;, &amp;quot;Where do I find tutorials?&amp;quot;,...) and if it was difficult to find them.&lt;br /&gt;
*Hand the notes to your mentor.&lt;br /&gt;
*Go to the forum topic which discusses the hard to find information. Join the discussion with your findings.&lt;br /&gt;
*Once this topic has received more than 20 replies, start scanning the details&lt;br /&gt;
*Write a short summary which includes the problems you noticed and possible solutions.&lt;br /&gt;
*Provide your mentor with the link.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|writing reports, community interaction|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Create a short survey about most used 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] and we want to know to what extend they are used. So let&#039;s create a survey and ask for these details.&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 about which information might be important and which questions could be asked&lt;br /&gt;
*Think how one can best ask for some free text feedback for certain features.&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Research: Analyse Limesurvey usage - Write a summary about the &amp;quot;most used Limesurvey features&amp;quot; survey===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea posted by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: This task can only be started after the &amp;quot;Create a short survey about most used features&amp;quot; task was completed!&lt;br /&gt;
&lt;br /&gt;
Once the &amp;quot;Create a short survey about most used features&amp;quot; task was completed and there are at least 50 answers to the survey, we need a clever person to analyse the details and write a summary&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Have a look at the &amp;quot;Create a short survey about most used features&amp;quot; at our online system (we will provide you with username/password)&lt;br /&gt;
*Export the survey data to an application of your choice or use the existing analysis features&lt;br /&gt;
*For each Limesurvey feature, write a short text about the usage and positive/negative comments.&lt;br /&gt;
*After you have done the analysis of each feature, write a summary which points to the features which have received most negative comments&lt;br /&gt;
*Write a short description about what you did related to this task so we can use it when presenting the results to our community.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Limesurvey|| Mazi&lt;br /&gt;
|}&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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Writing skills || c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;German&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native German speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://de.wikipedia.org/wiki/LimeSurvey German Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the German Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native German speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Spanish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Spanish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://es.wikipedia.org/wiki/LimeSurvey Spanish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Spanish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Spanish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;French&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native French speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://fr.wikipedia.org/wiki/LimeSurvey French Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the French Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native French speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Italian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Italian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://it.wikipedia.org/wiki/LimeSurvey Italian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Italian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Italian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Polish&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Polish speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pl.wikipedia.org/wiki/LimeSurvey Polish Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Polish Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Polish speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Portuguese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Portuguese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://pt.wikipedia.org/wiki/LimeSurvey Portuguese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Portuguese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Portuguese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Romanian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Romanian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ro.wikipedia.org/wiki/LimeSurvey Romanian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Romanian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Romanian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Russian&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Russian speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://ru.wikipedia.org/wiki/LimeSurvey Russian Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Russian Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Russian speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Outreach: Update the &#039;&#039;&#039;Chinese&#039;&#039;&#039; Wikipedia article about LimeSurvey===&lt;br /&gt;
&lt;br /&gt;
We have recently updated the English Wikipedia article about Limesurvey. Unfortunately, other language versions are quite outdated, so time to get this updated as well.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Requirements: You should speak English well to understand the content of the English Wikipedia article AND you need to be a native Chinese speaker.&lt;br /&gt;
*Open the [http://en.wikipedia.org/wiki/LimeSurvey English Wikipedia article about Limesurvey].&lt;br /&gt;
*Open the [http://zh.wikipedia.org/wiki/LimeSurvey Chinese Wikipedia article about Limesurvey] and compare both. Probably most of the article needs an update.&lt;br /&gt;
*Update the Chinese Wikipedia article.&lt;br /&gt;
*Show the updated Wikipedia article to your mentor.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|English language, native Chinese speaker, Wikipedia editing || Mazi&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Quality Assurance==&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Unify wording in the application===&lt;br /&gt;
&lt;br /&gt;
By today LimeSurvey has over 3000 text strings that need to be translated for every language we support. However we know that some of these strings are very similar and could be unified so it is less work for our translators.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Create an account on http://www.limesurvey.org, log in once and then login at http://translate.limesurvey.org&lt;br /&gt;
*Choose any translation, sort by original strings and find strings that seem to be very similar and can be unified.&lt;br /&gt;
*Change the source code and unify these strings there. (should be at least 20 strings)&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Quality assurance: Correct English texts in the application.===&lt;br /&gt;
&lt;br /&gt;
There are still several English texts in the application which are spelled wrong or have wrong casing. Most of this can be found in the English to English translation&lt;br /&gt;
&lt;br /&gt;
They need to be corrected in the source.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Set [[Google Code-In development environment quick-setup|up your LimeSurvey development environment]] (if not has already happened)&lt;br /&gt;
*Open the English to English translation at http://translate.limesurvey.org/projects/limesurvey2/en/default&lt;br /&gt;
*Find each string in the LimeSurvey source and correct it using the &#039;translation&#039; - please also obey our [http://docs.limesurvey.org/Coding+guidelines&amp;amp;structure;=LimeSurvey+development#Localization localization guidelines] for this.&lt;br /&gt;
*Submit a gitHub pull request.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP||Carsten Schmitz (c_schmitz)&lt;br /&gt;
|}&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 of the last month into MS Word, Excel or what else you like.&lt;br /&gt;
*Go through all the textual user feedback and create a list summing up 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Data analysis, Report Writing, Using idea tracker|| [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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&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 (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 last years Google Summer of Code a cool new feature called &amp;quot;Central Participant Database&amp;quot; was coded. It is available since Limesurvey 2.0. 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 [http://docs.limesurvey.org/Central+Participants+Database CPDB documentation].&lt;br /&gt;
*We will provide you with access to a Limesurvey 2 test system. Upload a simple survey (we can provide samples) and add token data to the survey.&lt;br /&gt;
*Also add data to the CPDB feature.&lt;br /&gt;
*Test this feature by checking features like&lt;br /&gt;
**creating users&lt;br /&gt;
**importing/exporting participants&lt;br /&gt;
**adding attributes&lt;br /&gt;
**moving people and attributes to surveys&lt;br /&gt;
**moving people and attributes from the token screen to CPDB&lt;br /&gt;
*On your list 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Using bugtracker, Limesurvey|| Aniessh&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==User interface==&lt;br /&gt;
&lt;br /&gt;
===User interface: Token section workflow improvements===&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;
There are some sections at the Limesurvey admin backend like the token part at which workflow improvements can be added, e. g. 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;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a import a simple survey and add 2-3 token entries.&lt;br /&gt;
*Search the code for the snippet which is called when a user calles the token admin screen.&lt;br /&gt;
*Change the code so that a user is automatically directed to the list of tokens.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Improve &amp;quot;Add answer options&amp;quot; GUI===&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, e. g. when adding new answer options and clicking into the answer text field, you have to manually delete the &amp;quot;Some example subquestion&amp;quot; text (For further answer options the text is deleted automatically when clicking into the input field.).&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install Limesurvey 2, create a simple survey and add a &amp;quot;list radio&amp;quot; question. You are then asked to add answer options.&lt;br /&gt;
*Search the code for the snippet which is called when a user adds answer options.&lt;br /&gt;
*Add some Javascript to automatically delete the text once a user clicks into the input field.&lt;br /&gt;
*Discuss the patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|PHP, maybe a little HTML and Javascript|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User management workflow improvement (1/2)===&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 at which workflow improvements can be added, e. g. after having added a new user there is a summary screen showing the username and email address. You can then 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). This work flow can be improved by removing the step in between.&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the summary screen with username and email address.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: User rights management workflow improvement (2/2)===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea added by: Mazi&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
NOTE: This task can only be executed if task &amp;quot;User rights management workflow improvement (1/2)&amp;quot; is completed. Do NOT start to work on this before that or your work will most likely be futile.&lt;br /&gt;
&lt;br /&gt;
There are some sections at the Limesurvey admin backend like when setting user rights at which workflow improvements can be added, e. g. after having added user rights there is a summary screen showing &amp;quot;User permissions were updated successfully.&amp;quot;. Only following option is to click the &amp;quot;continue&amp;quot; button which leads him to the user overview. This work flow can be improved by showing the feedback as a pop up and redirecting the user to the next step of setting template rights&lt;br /&gt;
&lt;br /&gt;
Task Steps:&lt;br /&gt;
*Install LimeSurvey - Add a new user and add user rights to check the work flow details.&lt;br /&gt;
*Search the code for the snippet which is responsible of showing the &amp;quot;User permissions were updated successfully.&amp;quot; summary.&lt;br /&gt;
*Change the code so that the summary is shown as a pop up (see pop up when renaming a survey for example) and lead the user directly to the admin screen where template permissions for the newly added user can be set.&lt;br /&gt;
*Discuss the new work flow and patch with your mentor and ask for feedback.&lt;br /&gt;
*Submit a github pull request.&lt;br /&gt;
*Done!&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Skills||Mentor&lt;br /&gt;
|-&lt;br /&gt;
|PHP, HTML and maybe Javascript and CSS|| c_schmitz&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===User interface: Create mockups for integrating export results screens into one feature===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea by: mdekker&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
LimeSurvey currently offers response export in three different screens: export to application, export to Spss and export to R. We wish to make this only one screen, based on export to application where the export to Spss and R should be added. The problem is those exports require two downloads and should show a little help text when selected and possibly have other selections that are mandatory.&lt;br /&gt;
&lt;br /&gt;
Think of a way to merge the three screens into one while keeping it logical for the end user. The actual coding of the change is not part of this task.&lt;br /&gt;
&lt;br /&gt;
Task steps:&lt;br /&gt;
*Use the online demo and check the export to application, export to R and export to SPSS screens&lt;br /&gt;
*Do a test export to check the different work-flow and note all steps involved.&lt;br /&gt;
*Analyse the problem and think how to best merge the three features on one screen.&lt;br /&gt;
*Discuss the issues and your proposed solution with your mentor&lt;br /&gt;
*Create three drafts of an overworked and merged export screen and add some description of the user interacting with the screens.&lt;br /&gt;
*Discuss the work with your mentor.&lt;br /&gt;
*Create a feature request in our bugtracker describing the change and attach your images + description.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|Image editing||mdekker, Mazi&lt;br /&gt;
|}&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 &amp;amp; Training/Outreach &amp;amp; Research/Quality assurance/User interface: Some descriptive task description===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Idea 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;
|Recommended skills||Mentor(s)&lt;br /&gt;
|-&lt;br /&gt;
|some skills the applicants should have|| name of the mentor&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>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3070</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3070"/>
		<updated>2011-08-23T01:47:13Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participant information to a central table that is independent of any token table. It&#039;s major advantages are :&lt;br /&gt;
* The central table acts as a backup so in case a user creates a new survey he would not have to go through the trouble of exporting it&#039;s participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* Users will only need to add the participants to the central table and then the same can be added to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , the owners can choose to share his participants with others and also set access rights for the shared users.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is an advanced attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display participant&amp;amp;rsquo;s grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export all participants to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist control&lt;br /&gt;
&lt;br /&gt;
7) Global participant&amp;amp;rsquo;s settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute control&lt;br /&gt;
&lt;br /&gt;
9) Share panel&lt;br /&gt;
&lt;br /&gt;
10) Panel summary&lt;br /&gt;
&lt;br /&gt;
==Home==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes the user back to the administrator panel.&lt;br /&gt;
&lt;br /&gt;
==Information==&lt;br /&gt;
&lt;br /&gt;
This screen shows the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display participant&amp;amp;rsquo;s grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Below is the screenshot of the same.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation bar&lt;br /&gt;
&lt;br /&gt;
8)  Share participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to survey&lt;br /&gt;
&lt;br /&gt;
10) Total count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
12) Subgrid&lt;br /&gt;
&lt;br /&gt;
===Add participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click the participant and after editing you can press enter and any changes done will be saved to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in any token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well all token tables, but his responses are not deleted.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system including his responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV you are presented with a dialog box asking you to mark the additional attributes which you want to import. There is also an option for filtering the attributes. It will display all the attributes in the central table (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV option works under either of the two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
It will export all or selected participants depending on your filtering criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export the file as central_&#039;the current time stamp&#039;.csv .&lt;br /&gt;
&lt;br /&gt;
===Advance search===&lt;br /&gt;
&lt;br /&gt;
This is yet another major feature of the Central Panel. It is a powerful feature which not only filters through the participants but also through additional attributes (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two levels of search that you can do.&lt;br /&gt;
&lt;br /&gt;
1) Single search&lt;br /&gt;
&lt;br /&gt;
2) Combined search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition by using a plus sign next to the previous condition and remove a condition by using a minus sign in front of it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This not only filters the participants in the grid but also those in the database that are not yet loaded, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination which allows the you to see the first X number of entries ( chosen by the you) and then load more if required. To control this we have pagination control option in the navigator bar.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down menu you can select the number of entries to be loaded and with navigation buttons you can navigate sequentially and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of entries that visible per page. Also the searching and sorting of grid are not dependent on the records visible in the grid at any particular time but are done on the whole central table.&lt;br /&gt;
&lt;br /&gt;
===Share participant===&lt;br /&gt;
&lt;br /&gt;
This is another important feature of the Central Participants Database. You can share your participants with other users. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with whom you want to share.You can also set whether the user sharing your participant can edit those participants. If you set it no they will get an access denied error when trying to edit those shared entries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t mean you have selected all the participants on the filtered participants from the database.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will only offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that are going to exported. Besides that, there is also a check box, that if checked, will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total count===&lt;br /&gt;
&lt;br /&gt;
Number of participants out of total participants is displayed at the right of the navigator.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented the concept subgrid in the main grid that shows all the attributes in the system and also allows you to edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. It also shows the links to the surveys to which the participant is added to. In case the participant is not added to atleast one survey, this subgrid is not diplayed. When you expand the subgrid, all of the attributes in the system show up, but that doesn&#039;t means all the attribute values for that participant are saved in the database. Only when you add some value, that attribute value is saved for that particular participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This supports files with only *.csv extension. The rest of the settings are similar with what we have for &amp;quot;import CSV&amp;quot; under tokens. As in &amp;quot;add to survey&amp;quot; option we also have a drag and drop control over the attribute here. This feature scans all the headings in the CSV and shows them . You can map the attribute to an already existing central attribute or choose to create a new one.&lt;br /&gt;
&lt;br /&gt;
Steps to import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and specify associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to those in the central table or create a new attribute. New attributes created will be of text box type but can be changed later.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it to process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export all==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has access to.&lt;br /&gt;
&lt;br /&gt;
== Global participant&amp;amp;rsquo;s settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted, as it&#039;s the user id associated with the participant which decides the ownership of the participant. For this there setting in the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, you can edit the user name field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the owner name field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the Central Participants Database. The attribute control in the token system allows  to add only the attribute of text type, which reduces complexity, but when you have to add a large number of attribute values, it becomes very tiring to type the exact same value, for example &#039;male&#039;, repeatedly. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop down&lt;br /&gt;
&lt;br /&gt;
2) Text box&lt;br /&gt;
&lt;br /&gt;
3) Date picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing. For drop down , you will need to add possible values. Also, the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visibility right here by using the  check box. The visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advanced editing, such as adding of drop down values and adding multilingual languages, you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add the attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the specific value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant. Please note that this panel shows only the shared participants owned by that particular user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:sharepanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the &amp;quot;Can Edit&amp;quot; field is editable for the user. The can edit field as explained earlier determines whether to allow the shared participant to be editable by the sharer or not.Just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, only it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the toolbar.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3071</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3071"/>
		<updated>2011-08-23T01:45:58Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participant information to a central table that is independent of any token table. It&#039;s major advantages are :&lt;br /&gt;
* The central table acts as a backup so in case a user creates a new survey he would not have to go through the trouble of exporting it&#039;s participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* Users will only need to add the participants to the central table and then the same can be added to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , the owners can choose to share his participants with others and also set access rights for the shared users.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is an advanced attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display participant&amp;amp;rsquo;s grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export all participants to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist control&lt;br /&gt;
&lt;br /&gt;
7) Global participant&amp;amp;rsquo;s settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute control&lt;br /&gt;
&lt;br /&gt;
9) Share panel&lt;br /&gt;
&lt;br /&gt;
10) Panel summary&lt;br /&gt;
&lt;br /&gt;
==Home==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes the user back to the administrator panel.&lt;br /&gt;
&lt;br /&gt;
==Information==&lt;br /&gt;
&lt;br /&gt;
This screen shows the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display participant&amp;amp;rsquo;s grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Below is the screenshot of the same.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation bar&lt;br /&gt;
&lt;br /&gt;
8)  Share participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to survey&lt;br /&gt;
&lt;br /&gt;
10) Total count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
12) Subgrid&lt;br /&gt;
&lt;br /&gt;
===Add participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click the participant and after editing you can press enter and any changes done will be saved to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in any token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well all token tables, but his responses are not deleted.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system including his responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV you are presented with a dialog box asking you to mark the additional attributes which you want to import. There is also an option for filtering the attributes. It will display all the attributes in the central table (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV option works under either of the two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
It will export all or selected participants depending on your filtering criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export the file as central_&#039;the current time stamp&#039;.csv .&lt;br /&gt;
&lt;br /&gt;
===Advance search===&lt;br /&gt;
&lt;br /&gt;
This is yet another major feature of the Central Panel. It is a powerful feature which not only filters through the participants but also through additional attributes (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two levels of search that you can do.&lt;br /&gt;
&lt;br /&gt;
1) Single search&lt;br /&gt;
&lt;br /&gt;
2) Combined search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition by using a plus sign next to the previous condition and remove a condition by using a minus sign in front of it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This not only filters the participants in the grid but also those in the database that are not yet loaded, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination which allows the you to see the first X number of entries ( chosen by the you) and then load more if required. To control this we have pagination control option in the navigator bar.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down menu you can select the number of entries to be loaded and with navigation buttons you can navigate sequentially and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of entries that visible per page. Also the searching and sorting of grid are not dependent on the records visible in the grid at any particular time but are done on the whole central table.&lt;br /&gt;
&lt;br /&gt;
===Share participant===&lt;br /&gt;
&lt;br /&gt;
This is another important feature of the Central Participants Database. You can share your participants with other users. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with whom you want to share.You can also set whether the user sharing your participant can edit those participants. If you set it no they will get an access denied error when trying to edit those shared entries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t mean you have selected all the participants on the filtered participants from the database.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will only offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that are going to exported. Besides that, there is also a check box, that if checked, will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total count===&lt;br /&gt;
&lt;br /&gt;
Number of participants out of total participants is displayed at the right of the navigator.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented the concept subgrid in the main grid that shows all the attributes in the system and also allows you to edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. It also shows the links to the surveys to which the participant is added to. In case the participant is not added to atleast one survey, this subgrid is not diplayed. When you expand the subgrid, all of the attributes in the system show up, but that doesn&#039;t means all the attribute values for that participant are saved in the database. Only when you add some value, that attribute value is saved for that particular participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This supports files with only *.csv extension. The rest of the settings are similar with what we have for &amp;quot;import CSV&amp;quot; under tokens. As in &amp;quot;add to survey&amp;quot; option we also have a drag and drop control over the attribute here. This feature scans all the headings in the CSV and shows them . You can map the attribute to an already existing central attribute or choose to create a new one.&lt;br /&gt;
&lt;br /&gt;
Steps to import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and specify associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to those in the central table or create a new attribute. New attributes created will be of text box type but can be changed later.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it to process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export all==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has access to.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted, as it&#039;s the user id associated with the participant which decides the ownership of the participant. For this there setting in the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, you can edit the user name field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the owner name field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the Central Participants Database. The attribute control in the token system allows  to add only the attribute of text type, which reduces complexity, but when you have to add a large number of attribute values, it becomes very tiring to type the exact same value, for example &#039;male&#039;, repeatedly. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop down&lt;br /&gt;
&lt;br /&gt;
2) Text box&lt;br /&gt;
&lt;br /&gt;
3) Date picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing. For drop down , you will need to add possible values. Also, the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visibility right here by using the  check box. The visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advanced editing, such as adding of drop down values and adding multilingual languages, you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add the attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the specific value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant. Please note that this panel shows only the shared participants owned by that particular user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:sharepanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the &amp;quot;Can Edit&amp;quot; field is editable for the user. The can edit field as explained earlier determines whether to allow the shared participant to be editable by the sharer or not.Just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, only it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the toolbar.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3072</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3072"/>
		<updated>2011-08-23T01:40:26Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participant information to a central table that is independent of any token table. It&#039;s major advantages are :&lt;br /&gt;
* The central table acts as a backup so in case a user creates a new survey he would not have to go through the trouble of exporting it&#039;s participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* Users will only need to add the participants to the central table and then the same can be added to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , the owners can choose to share his participants with others and also set access rights for the shared users.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is an advanced attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export all participants to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes the user back to the administrator panel.&lt;br /&gt;
&lt;br /&gt;
==Information==&lt;br /&gt;
&lt;br /&gt;
This screen shows the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Below is the screenshot of the same.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
12) Subgrid&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click the participant and after editing you can press enter and any changes done will be saved to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in any token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well all token tables, but his responses are not deleted.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system including his responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV you are presented with a dialog box asking you to mark the additional attributes which you want to import. There is also an option for filtering the attributes. It will display all the attributes in the central table (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV option works under either of the two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
It will export all or selected participants depending on your filtering criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export the file as central_&#039;the current time stamp&#039;.csv .&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is yet another major feature of the Central Panel. It is a powerful feature which not only filters through the participants but also through additional attributes (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two levels of search that you can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition by using a plus sign next to the previous condition and remove a condition by using a minus sign in front of it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This not only filters the participants in the grid but also those in the database that are not yet loaded, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination which allows the you to see the first X number of entries ( chosen by the you) and then load more if required. To control this we have pagination control option in the navigator bar.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down menu you can select the number of entries to be loaded and with navigation buttons you can navigate sequentially and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of entries that visible per page. Also the searching and sorting of grid are not dependent on the records visible in the grid at any particular time but are done on the whole central table.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another important feature of the Central Participants Database. You can share your participants with other users. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with whom you want to share.You can also set whether the user sharing your participant can edit those participants. If you set it no they will get an access denied error when trying to edit those shared entries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t mean you have selected all the participants on the filtered participants from the database.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will only offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that are going to exported. Besides that, there is also a check box, that if checked, will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
Number of participants out of total participants is displayed at the right of the navigator.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented the concept subgrid in the main grid that shows all the attributes in the system and also allows you to edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. It also shows the links to the surveys to which the participant is added to. In case the participant is not added to atleast one survey, this subgrid is not diplayed. When you expand the subgrid, all of the attributes in the system show up, but that doesn&#039;t means all the attribute values for that participant are saved in the database. Only when you add some value, that attribute value is saved for that particular participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This supports files with only *.csv extension. The rest of the settings are similar with what we have for &amp;quot;import CSV&amp;quot; under tokens. As in &amp;quot;add to survey&amp;quot; option we also have a drag and drop control over the attribute here. This feature scans all the headings in the CSV and shows them . You can map the attribute to an already existing central attribute or choose to create a new one.&lt;br /&gt;
&lt;br /&gt;
Steps to Import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and specify associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to those in the central table or create a new attribute. New attributes created will be of text box type but can be changed later.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it to process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export All==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has access to.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted, as it&#039;s the user id associated with the participant which decides the ownership of the participant. For this there setting in the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, you can edit the user name field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the owner name field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute Control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the Central Participants Database. The attribute control in the token system allows  to add only the attribute of text type, which reduces complexity, but when you have to add a large number of attribute values, it becomes very tiring to type the exact same value, for example &#039;male&#039;, repeatedly. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop Down&lt;br /&gt;
&lt;br /&gt;
2) Text Box&lt;br /&gt;
&lt;br /&gt;
3) Date Picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing. For drop down , you will need to add possible values. Also, the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visibility right here by using the  check box. The visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advanced editing, such as adding of drop down values and adding multilingual languages, you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add the attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the specific value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share Panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant. Please note that this panel shows only the shared participants owned by that particular user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:sharepanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the &amp;quot;Can Edit&amp;quot; field is editable for the user. The can edit field as explained earlier determines whether to allow the shared participant to be editable by the sharer or not.Just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel Summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, only it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the toolbar.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3074</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3074"/>
		<updated>2011-08-22T20:38:09Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participant information to a central table that is independent of any token table. It&#039;s major advantages are :&lt;br /&gt;
* The central table acts as a backup so in case a user creates a new survey he would not have to go through the trouble of exporting it&#039;s participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* Users will only need to add the participants to the central table and then the same can be added to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , the owners can choose to share his participants with others and also set access rights for the shared users.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is an advanced attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export All&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes the user back to the administrator panel.&lt;br /&gt;
&lt;br /&gt;
==Information==&lt;br /&gt;
&lt;br /&gt;
This screen shows the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Below is the screenshot of the same.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
12) Subgrid&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click the participant and after editing you can press enter and any changes done will be saved to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in any token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well all token tables, but his responses are not deleted.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system including his responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV you are presented with a dialog box asking you to mark the additional attributes which you want to import. There is also an option for filtering the attributes. It will display all the attributes in the central table (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV option works under either of the two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
It will export all or selected participants depending on your filtering criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export the file as central_&#039;the current time stamp&#039;.csv .&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is yet another major feature of the Central Panel. It is a powerful feature which not only filters through the participants but also through additional attributes (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two levels of search that you can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition by using a plus sign next to the previous condition and remove a condition by using a minus sign in front of it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This not only filters the participants in the grid but also those in the database that are not yet loaded, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination which allows the you to see the first X number of entries ( chosen by the you) and then load more if required. To control this we have pagination control option in the navigator bar.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down menu you can select the number of entries to be loaded and with navigation buttons you can navigate sequentially and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of entries that visible per page. Also the searching and sorting of grid are not dependent on the records visible in the grid at any particular time but are done on the whole central table.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another important feature of the Central Participants Database. You can share your participants with other users. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with whom you want to share.You can also set whether the user sharing your participant can edit those participants. If you set it no they will get an access denied error when trying to edit those shared entries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t mean you have selected all the participants on the filtered participants from the database.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will only offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that are going to exported. Besides that, there is also a check box, that if checked, will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
Number of participants out of total participants is displayed at the right of the navigator.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented the concept subgrid in the main grid that shows all the attributes in the system and also allows you to edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. It also shows the links to the surveys to which the participant is added to. In case the participant is not added to atleast one survey, this subgrid is not diplayed. When you expand the subgrid, all of the attributes in the system show up, but that doesn&#039;t means all the attribute values for that participant are saved in the database. Only when you add some value, that attribute value is saved for that particular participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This supports files with only *.csv extension. The rest of the settings are similar with what we have for &amp;quot;import CSV&amp;quot; under tokens. As in &amp;quot;add to survey&amp;quot; option we also have a drag and drop control over the attribute here. This feature scans all the headings in the CSV and shows them . You can map the attribute to an already existing central attribute or choose to create a new one.&lt;br /&gt;
&lt;br /&gt;
Steps to Import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and specify associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to those in the central table or create a new attribute. New attributes created will be of text box type but can be changed later.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it to process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export All==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has access to.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted, as it&#039;s the user id associated with the participant which decides the ownership of the participant. For this there setting in the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, you can edit the user name field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the owner name field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute Control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the Central Participants Database. The attribute control in the token system allows  to add only the attribute of text type, which reduces complexity, but when you have to add a large number of attribute values, it becomes very tiring to type the exact same value, for example &#039;male&#039;, repeatedly. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop Down&lt;br /&gt;
&lt;br /&gt;
2) Text Box&lt;br /&gt;
&lt;br /&gt;
3) Date Picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing. For drop down , you will need to add possible values. Also, the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visibility right here by using the  check box. The visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advanced editing, such as adding of drop down values and adding multilingual languages, you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add the attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the specific value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share Panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant. Please note that this panel shows only the shared participants owned by that particular user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:sharepanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the &amp;quot;Can Edit&amp;quot; field is editable for the user. The can edit field as explained earlier determines whether to allow the shared participant to be editable by the sharer or not.Just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel Summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, only it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the toolbar.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3075</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3075"/>
		<updated>2011-08-22T20:35:13Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participant information to a central table that is independent of any token table. It&#039;s major advantages are :&lt;br /&gt;
* The central table acts as a backup so in case a user creates a new survey he would not have to go through the trouble of exporting it&#039;s participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* Users will only need to add the participants to the central table and then the same can be added to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , the owners can choose to share his participants with others and also set access rights for the shared users.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is an advanced attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export All&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes the user back to the administrator panel.&lt;br /&gt;
&lt;br /&gt;
==Information==&lt;br /&gt;
&lt;br /&gt;
This screen shows the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Below is the screenshot of the same.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
12) Subgrid&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click the participant and after editing you can press enter and any changes done will be saved to the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in any token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well all token tables, but his responses are not deleted.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system including his responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV you are presented with a dialog box asking you to mark the additional attributes which you want to import. There is also an option for filtering the attributes. It will display all the attributes in the central table (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV option works under either of the two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
It will export all or selected participants depending on your filtering criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export the file as central_&#039;the current time stamp&#039;.csv .&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is yet another major feature of the Central Panel. It is a powerful feature which not only filters through the participants but also through additional attributes (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two levels of search that you can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition by using a plus sign next to the previous condition and remove a condition by using a minus sign in front of it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This not only filters the participants in the grid but also those in the database that are not yet loaded, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination which allows the you to see the first X number of entries ( chosen by the you) and then load more if required. To control this we have pagination control option in the navigator bar.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down menu you can select the number of entries to be loaded and with navigation buttons you can navigate sequentially and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of entries that visible per page. Also the searching and sorting of grid are not dependent on the records visible in the grid at any particular time but are done on the whole central table.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another important feature of the Central Participants Database. You can share your participants with other users. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with whom you want to share.You can also set whether the user sharing your participant can edit those participants. If you set it no they will get an access denied error when trying to edit those shared entries.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t mean you have selected all the participants on the filtered participants from the database.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will only offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that are going to exported. Besides that, there is also a check box, that if checked, will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
Number of participants out of total participants is displayed at the right of the navigator.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented the concept subgrid in the main grid that shows all the attributes in the system and also allows you to edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. It also shows the links to the surveys to which the participant is added to. In case the participant is not added to atleast one survey, this subgrid is not diplayed. When you expand the subgrid, all of the attributes in the system show up, but that doesn&#039;t means all the attribute values for that participant are saved in the database. Only when you add some value, that attribute value is saved for that particular participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This supports files with only *.csv extension. The rest of the settings are similar with what we have for &amp;quot;import CSV&amp;quot; under tokens. As in &amp;quot;add to survey&amp;quot; option we also have a drag and drop control over the attribute here. This feature scans all the headings in the CSV and shows them . You can map the attribute to an already existing central attribute or choose to create a new one.&lt;br /&gt;
&lt;br /&gt;
Steps to Import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and specify associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to those in the central table or create a new attribute. New attributes created will be of text box type but can be changed later.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it to process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export All==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has access to.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted, as it&#039;s the user id associated with the participant which decides the ownership of the participant. For this there setting in the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, you can edit the user name field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the owner name field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute Control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the Central Participants Database. The attribute control in the token system allows  to add only the attribute of text type, which reduces complexity, but when you have to add a large number of attribute values, it becomes very tiring to type the exact same value, for example &#039;male&#039;, repeatedly. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop Down&lt;br /&gt;
&lt;br /&gt;
2) Text Box&lt;br /&gt;
&lt;br /&gt;
3) Date Picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing. For drop down , you will need to add possible values. Also, the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visibility right here by using the  check box. The visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advanced editing, such as adding of drop down values and adding multilingual languages, you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add the attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the specific value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share Panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant. Please note that this panel shows only the shared participants owned by that particular user.&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the &amp;quot;Can Edit&amp;quot; field is editable for the user. The can edit field as explained earlier determines whether to allow the shared participant to be editable by the sharer or not.Just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel Summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, only it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the toolbar.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3076</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3076"/>
		<updated>2011-08-22T17:51:44Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export All&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
11) Subgrid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click on the row on which you want to edit and after editing you can press enter and any changes you have done will be saved on the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV the user is presented with a dialog box asking him to mark the additional attributes which he wants to import. There is also a nice filter for filtering the attributes. It will display all the attributes (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV will work under two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
When you are done filtering it will export all the filtered results otherwise it will export all the participants visible to that user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export with the file name as central_&#039;the current time stamp&#039;.&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is another major feature of Central Panel. It has a powerful search which not only filters through the participant but through additional attributes as well (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two level of searches that an administrator can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition using a plus sign next to the previous condition and remove the condition using a minus sign&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This search not only filters attributes in the grid but also from the database, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination in the grid which allows the user to see the first X entries ( chosen by the user) and then load more if required by him. To control this we have a pagination control in the navigator bar&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down you can select the entries to be loaded and with navigation buttons you can navigate and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of eateries visible per page. Also the search and sorting of grid are not dependent on the records visible in the grid at any particular time but are independent of them.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another most important feature of CPDB. You can share the participants among other users in the LimeSurvey installation. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with who you want to share. You can also set as to whether the participant that you are sharing can be edited by the user with whom you are sharing. If you set it to no, user with whom you have shared will get a access denied error.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants and rest of the participants are loaded when requested, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t meant you have selected all the participants on the second and the third page as well.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that you are going to export. Besides that there is also a check box that if checked will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants to. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
The navigator in the right also displays the number of participants out of the total participants.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented subgrid in the main grid that shows all the attributes in the system and also edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. The subgrid also shows the links to the surveys to which the participant is added to. In case the participant is not added to any survey this subgrid hides itself. When you expand the subgrid all the attributes in the system show up, but that doesn&#039;t mean that you have saved all the attribute values for that participant in the database. Only when you add some value that attribute is saved for that particular attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This feature is similar to as we have in tokens.This supports files with only *.csv extension. The rest of the settings are similar with what we have for import CSV under tokens. As in add to survey we also have a drag and drop control over the attribute here. This feature all the headings in the CSV and show them . The user can map the attribute to already existing central attribute or choose to create new one.&lt;br /&gt;
&lt;br /&gt;
Steps of Import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to the one in the central table or create new. New attributes will be created text box type which can changed later&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export All==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has rights for.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted as it&#039;s the user id associated with the participant which decides the ownership of the participant. For which there is a setting the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, the user can edit the user field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the user id field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute Control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the CPDB. The attribute control in the current system allows only to add the attribute of only text type, which this reduces complexity but when you have to add a large number of attribute values, it becomes very difficult to type in the exact same value, for example &#039;male&#039; a large number of times. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop Down&lt;br /&gt;
&lt;br /&gt;
2) Text Box&lt;br /&gt;
&lt;br /&gt;
3) Date Picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing attributes. For drop down you will need to add values. Also the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visible right here by just checking the visible check box. the visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advance editing such as adding of drop down values and adding multilingual languages you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the possible value.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editcommonsetting.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share Panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant . Please note that this panel shows only the shared participant by that particular user.&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the can_edit field is editable for the user. The can edit field as explained earlier determines as to whether to allow the shared participant to be editable with the sharer or not. You don&#039;t need to double click or something, just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel Summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, just that it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the panel and it gives general information about the CPDB.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3077</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3077"/>
		<updated>2011-08-22T17:42:37Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:ParticipantPanel.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export All&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
11) Subgrid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click on the row on which you want to edit and after editing you can press enter and any changes you have done will be saved on the server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:deleteParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV the user is presented with a dialog box asking him to mark the additional attributes which he wants to import. There is also a nice filter for filtering the attributes. It will display all the attributes (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV will work under two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
When you are done filtering it will export all the filtered results otherwise it will export all the participants visible to that user.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:exporttoCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It will export with the file name as central_&#039;the current time stamp&#039;.&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is another major feature of Central Panel. It has a powerful search which not only filters through the participant but through additional attributes as well (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two level of searches that an administrator can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advanceSearch.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition using a plus sign next to the previous condition and remove the condition using a minus sign .&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:advancesearchmultiple.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This search not only filters attributes in the grid but also from the database, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination in the grid which allows the user to see the first X entries ( chosen by the user) and then load more if required by him. To control this we have a pagination control in the navigator bar&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:navBar.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the drop down you can select the entries to be loaded and with navigation buttons you can navigate and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of eateries visible per page. Also the search and sorting of grid are not dependent on the records visible in the grid at any particular time but are independent of them.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another most important feature of CPDB. You can share the participants among other users in the LimeSurvey installation. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with who you want to share. You can also set as to whether the participant that you are sharing can be edited by the user with whom you are sharing. If you set it to no, user with whom you have shared will get a access denied error.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:shareParticipant.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants and rest of the participants are loaded when requested, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t meant you have selected all the participants on the second and the third page as well.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtoSurvey.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:direct-all.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that you are going to export. Besides that there is also a check box that if checked will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants to. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributemap.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addtosurveysummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
The navigator in the right also displays the number of participants out of the total participants.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented subgrid in the main grid that shows all the attributes in the system and also edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. The subgrid also shows the links to the surveys to which the participant is added to. In case the participant is not added to any survey this subgrid hides itself. When you expand the subgrid all the attributes in the system show up, but that doesn&#039;t mean that you have saved all the attribute values for that participant in the database. Only when you add some value that attribute is saved for that particular attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:subgrid.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:editattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This feature is similar to as we have in tokens.This supports files with only *.csv extension. The rest of the settings are similar with what we have for import CSV under tokens. As in add to survey we also have a drag and drop control over the attribute here. This feature all the headings in the CSV and show them . The user can map the attribute to already existing central attribute or choose to create new one.&lt;br /&gt;
&lt;br /&gt;
Steps of Import&lt;br /&gt;
&lt;br /&gt;
1) Select a file to import and associated settings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:importCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
2) Map the attributes in the CSV to the one in the central table or create new. New attributes will be created text box type which can changed later&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeMapCSV.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example screenshot I have created a new attribute age and mapped sex with the attribute in the central table.&lt;br /&gt;
&lt;br /&gt;
3) Wait for it process and show the summary.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:CSVsummary.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clicking ok will redirect you to the display participants screen showing the newly imported participants.&lt;br /&gt;
&lt;br /&gt;
== Export All==&lt;br /&gt;
&lt;br /&gt;
This feature is for simplicity of the user. The user can click on it and can download all the participants that he has rights for.&lt;br /&gt;
&lt;br /&gt;
== Global Participant&amp;amp;rsquo;s Settings==&lt;br /&gt;
&lt;br /&gt;
For security purposes the editing of user id is restricted as it&#039;s the user id associated with the participant which decides the ownership of the participant. For which there is a setting the main CPDB panel which can be changed only by the super administrator. If the setting is set to yes, the user can edit the user field in the display grid.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:userideditable.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When you double click on the row, you can see a drop down in the user id field where the list of all users in the system are listed and you choose which one to give participant rights to.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:displayparticipantedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Attribute Control==&lt;br /&gt;
&lt;br /&gt;
This is yet another advance feature of the CPDB. The attribute control in the current system allows only to add the attribute of only text type, which this reduces complexity but when you have to add a large number of attribute values, it becomes very difficult to type in the exact same value, for example &#039;male&#039; a large number of times. To overcome this problem we have introduced three different attribute types :&lt;br /&gt;
&lt;br /&gt;
1) Drop Down&lt;br /&gt;
&lt;br /&gt;
2) Text Box&lt;br /&gt;
&lt;br /&gt;
3) Date Picker&lt;br /&gt;
&lt;br /&gt;
You can choose either of the attribute types and associated UI will be presented to you while editing attributes. For drop down you will need to add values. Also the attribute control has multilingual support.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeControl.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see there are already two existing attributes in the system. You can set their visible right here by just checking the visible check box. the visibility will determine as to whether the attributes should be visible in the main grid or not.&lt;br /&gt;
&lt;br /&gt;
For adding a new attribute you just have to click on the plus sign and another row will pop up allowing you to put in basic details and saving the attribute.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:addingattribute.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can save the attribute by using the save button or by pressing enter after entering the attribute name.&lt;br /&gt;
&lt;br /&gt;
For deleting an attribute in the system just click on the delete button next to the edit button. Clicking the delete button will not only delete the attribute but also the associated values.&lt;br /&gt;
&lt;br /&gt;
For advance editing such as adding of drop down values and adding multilingual languages you need to click on the edit button. On clicking the edit button you will see something like this.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:attributeadvanceedit.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For adding a new language you can click on the plus sign and a new tab will pop up and you can add attribute name in that language there.&lt;br /&gt;
&lt;br /&gt;
You can also add drop down values by selecting the drop down attribute type&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[File:commonsettings2.png]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can edit the possible values of the drop down by clicking on the edit button or clicking on the value itself as it supports inline edit similar to what we have in the grid. Delete button is for deleting the possible value.&lt;br /&gt;
&lt;br /&gt;
[[File:editcommonsetting.png]]&lt;br /&gt;
&lt;br /&gt;
As you can see in the screenshots, the entire attribute properties can be edited here.&lt;br /&gt;
&lt;br /&gt;
== Share Panel==&lt;br /&gt;
&lt;br /&gt;
The share panel shows all the information related to the shared participant . Please note that this panel shows only the shared participant by that particular user.&lt;br /&gt;
&lt;br /&gt;
This panel shows values like&lt;br /&gt;
&lt;br /&gt;
1) First Name&lt;br /&gt;
&lt;br /&gt;
2) Last Name&lt;br /&gt;
&lt;br /&gt;
3) E-Mail&lt;br /&gt;
&lt;br /&gt;
4) Shared With&lt;br /&gt;
&lt;br /&gt;
5) Owner&lt;br /&gt;
&lt;br /&gt;
6) Date Added&lt;br /&gt;
&lt;br /&gt;
7) Can Edit&lt;br /&gt;
&lt;br /&gt;
All this information is for viewing/sorting purposes only and only the can_edit field is editable for the user. The can edit field as explained earlier determines as to whether to allow the shared participant to be editable with the sharer or not. You don&#039;t need to double click or something, just clicking on the check box will make an AJAX call and save the changes on the server.&lt;br /&gt;
&lt;br /&gt;
== Panel Summary==&lt;br /&gt;
&lt;br /&gt;
Panel summary is same as information, just that it is loaded when the CPDB panel is opened and it can be accessed again by using the information icon in the panel and it gives general information about the CPDB.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3078</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3078"/>
		<updated>2011-08-22T13:29:54Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:ParticipantPanel.png]]&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
[[File:displayParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
11) Subgrid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager. For editing the added participant you can simply double click on the row on which you want to edit and after editing you can press enter and any changes you have done will be saved on the server.&lt;br /&gt;
&lt;br /&gt;
[[File:addParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
[[File:deleteParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Reload Grid===&lt;br /&gt;
&lt;br /&gt;
It simply reloads the grid from the server.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV the user is presented with a dialog box asking him to mark the additional attributes which he wants to import. There is also a nice filter for filtering the attributes. It will display all the attributes (visible/non-visible).&lt;br /&gt;
&lt;br /&gt;
The export to CSV will work under two conditions :&lt;br /&gt;
&lt;br /&gt;
1) Export filtered&lt;br /&gt;
&lt;br /&gt;
2) Export All&lt;br /&gt;
&lt;br /&gt;
When you are done filtering it will export all the filtered results otherwise it will export all the participants visible to that user.&lt;br /&gt;
&lt;br /&gt;
[[File:exporttoCSV.png]]&lt;br /&gt;
&lt;br /&gt;
It will export with the file name as central_&#039;the current time stamp&#039;.&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is another major feature of Central Panel. It has a powerful search which not only filters through the participant but through additional attributes as well (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two level of searches that an administrator can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
[[File:advanceSearch.png]]&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition using a plus sign next to the previous condition and remove the condition using a minus sign .&lt;br /&gt;
&lt;br /&gt;
[[File:advancesearchmultiple.png]]&lt;br /&gt;
&lt;br /&gt;
This search not only filters attributes in the grid but also from the database, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Navigation Bar===&lt;br /&gt;
&lt;br /&gt;
To decrease load time of the grid we have used pagination in the grid which allows the user to see the first X entries ( chosen by the user) and then load more if required by him. To control this we have a pagination control in the navigator bar&lt;br /&gt;
&lt;br /&gt;
[[File:navBar.png]]&lt;br /&gt;
&lt;br /&gt;
Using the drop down you can select the entries to be loaded and with navigation buttons you can navigate and also use the text box to go to a certain page. Please note that the number of pages will reduce as you increase the number of eateries visible per page. Also the search and sorting of grid are not dependent on the records visible in the grid at any particular time but are independent of them.&lt;br /&gt;
&lt;br /&gt;
===Share Participant===&lt;br /&gt;
&lt;br /&gt;
This is another most important feature of CPDB. You can share the participants among other users in the LimeSurvey installation. You just have to select the participants you want to share and click on share. A modal box will open up which will allow you to select the user with who you want to share. You can also set as to whether the participant that you are sharing can be edited by the user with whom you are sharing. If you set it to no, user with whom you have shared will get a access denied error.&lt;br /&gt;
&lt;br /&gt;
[[File:shareParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) all participants in current search&lt;br /&gt;
&lt;br /&gt;
2) all participants&lt;br /&gt;
&lt;br /&gt;
3) only the participant&#039;s that I have selected&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants and rest of the participants are loaded when requested, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t meant you have selected all the participants on the second and the third page as well.So when exporting you are presented with the above mentioned three options which will be visible/invisible to you as per the present scenario.&lt;br /&gt;
&lt;br /&gt;
[[File:addtoSurvey.png]]&lt;br /&gt;
&lt;br /&gt;
For example if you have not selected any row and haven&#039;t done any search it will not show you any option and will offer you to add all the participants in the grid and so on...&lt;br /&gt;
&lt;br /&gt;
[[File:direct-all.png]]&lt;br /&gt;
&lt;br /&gt;
The title of the dialog box will show you the number of participants that you are going to export. Besides that there is also a check box that if checked will take you to the token table of the survey to which you are adding the participants.&lt;br /&gt;
&lt;br /&gt;
After clicking next you will be taken to the attribute map page.&lt;br /&gt;
&lt;br /&gt;
The attribute map page has three columns and uses advance drag and drop functionality. The first column shows all the attributes that are present in the central table. The second column gives space to the user to create new attributes. The third column shows the attributes in the token table to which the user is adding participants to. The user is free to choose to either create a new attribute in the token table to copy new values to or map the values from the attribute in the central table to the token table.&lt;br /&gt;
&lt;br /&gt;
[[File:attributemap.png]]&lt;br /&gt;
&lt;br /&gt;
After you have mapped all the attributes, you can click on continue and after processing the participants a summary page will show up that will tell you how many participants were successfully copied, after which if you have asked for redirection you will be redirected to the token table table or else you will be redirected to the central grid.&lt;br /&gt;
&lt;br /&gt;
[[File:addtosurveysummary.png]]&lt;br /&gt;
&lt;br /&gt;
===Total Count===&lt;br /&gt;
&lt;br /&gt;
The navigator in the right also displays the number of participants out of the total participants.&lt;br /&gt;
&lt;br /&gt;
===Hide/Show grid===&lt;br /&gt;
&lt;br /&gt;
Simply hide or show the grid.&lt;br /&gt;
&lt;br /&gt;
===Subgrid===&lt;br /&gt;
&lt;br /&gt;
For editing of attributes in the system we have implemented subgrid in the main grid that shows all the attributes in the system and also edit them. The main grid shows only the visible attributes, the rest of the attributes are available here and only fetched when required. The subgrid as the main grid allows inline editing of attributes and also sorting. The subgrid also shows the links to the surveys to which the participant is added to. In case the participant is not added to any survey this subgrid hides itself. When you expand the subgrid all the attributes in the system show up, but that doesn&#039;t mean that you have saved all the attribute values for that participant in the database. Only when you add some value that attribute is saved for that particular attribute.&lt;br /&gt;
&lt;br /&gt;
[[File:subgrid.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:editattribute.png]]&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This feature is similar to as we have in tokens.This supports files with only *.csv extension. The rest of the settings are similar with what we have for import CSV under tokens.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3079</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3079"/>
		<updated>2011-08-21T20:46:32Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:ParticipantPanel.png]]&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
[[File:displayParticipants.png]]&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager.&lt;br /&gt;
&lt;br /&gt;
[[File:addParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
[[File:deleteParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is another major feature of Central Panel. It has a powerful search which not only filters through the participant but through additional attributes as well (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two level of searches that an administrator can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
[[File:advanceSearch.png]]&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition using a plus sign next to the previous condition and remove the condition using a minus sign .&lt;br /&gt;
&lt;br /&gt;
[[File:advancesearchmultiple.png]]&lt;br /&gt;
&lt;br /&gt;
This search not only filters attributes in the grid but also from the database, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
When exporting to CSV the user is presented with a dialog box asking him to mark the additional attributes which he wants to import. There is also a nice filter for filtering the attributes. It will display all the attributes (visible/non-visible.&lt;br /&gt;
&lt;br /&gt;
===Add to survey===&lt;br /&gt;
&lt;br /&gt;
Add to survey can be done at three levels :&lt;br /&gt;
&lt;br /&gt;
1) All Filtered Participants&lt;br /&gt;
&lt;br /&gt;
2) Manually Participants&lt;br /&gt;
&lt;br /&gt;
3) All Participants in the Grid&lt;br /&gt;
&lt;br /&gt;
As we know that the grid loads only the requested participants and rest of the participants are loaded when requested, thus ensuring minimum loading time for the user. So when you select a page on the grid (using multi-select or single select )that doesn&#039;t meant you have selected all the participants on the second and the third page as well.So when exporting you are p&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This feature is similar to as we have in tokens.This supports files with only *.csv extension. The rest of the settings are similar with what we have for import CSV under tokens.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3080</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3080"/>
		<updated>2011-08-19T01:31:39Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:ParticipantPanel.png]]&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
[[File:displayParticipants.png]]&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager.&lt;br /&gt;
&lt;br /&gt;
[[File:addParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
[[File:deleteParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;br /&gt;
&lt;br /&gt;
===Advance Search===&lt;br /&gt;
&lt;br /&gt;
This is another major feature of Central Panel. It has a powerful search which not only filters through the participant but through additional attributes as well (visible and non-visible). This feature is also integrated with the grid.&lt;br /&gt;
&lt;br /&gt;
There are two level of searches that an administrator can do.&lt;br /&gt;
&lt;br /&gt;
1) Single Search&lt;br /&gt;
&lt;br /&gt;
2) Combined Search&lt;br /&gt;
&lt;br /&gt;
[[File:advanceSearch.png]]&lt;br /&gt;
&lt;br /&gt;
You can add a complex condition using a plus sign next to the previous condition and remove the condition using a minus sign .&lt;br /&gt;
&lt;br /&gt;
[[File:advancesearchmultiple.png]]&lt;br /&gt;
&lt;br /&gt;
This search not only filters attributes in the grid but also from the database, so it is an extensive search.&lt;br /&gt;
&lt;br /&gt;
===Export to CSV===&lt;br /&gt;
&lt;br /&gt;
[some changes left]&lt;br /&gt;
&lt;br /&gt;
==Import from CSV==&lt;br /&gt;
&lt;br /&gt;
This feature is similar to as we have in tokens.This supports files with only *.csv extension. The rest of the settings are similar with what we have for import CSV under tokens.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3081</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3081"/>
		<updated>2011-08-19T00:30:05Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:ParticipantPanel.png]]&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information Screen( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;br /&gt;
&lt;br /&gt;
==Home Screen==&lt;br /&gt;
&lt;br /&gt;
Participant&#039;s Panel is a separate panel in the LimeSurvey administrator toolbar, so this icon takes back the user to the administrator panel&lt;br /&gt;
&lt;br /&gt;
==Information Screen==&lt;br /&gt;
&lt;br /&gt;
This screen shows the summary of the Central Database by giving the statistics of Central Database. This gives the summary of&lt;br /&gt;
&lt;br /&gt;
1) Total Participants in central table&lt;br /&gt;
&lt;br /&gt;
2) Participants Owned by you&lt;br /&gt;
&lt;br /&gt;
3) Participants Shared with you&lt;br /&gt;
&lt;br /&gt;
4) Participants you have shared&lt;br /&gt;
&lt;br /&gt;
5) Blacklisted Participants&lt;br /&gt;
&lt;br /&gt;
6) Total attributes in the central table&lt;br /&gt;
&lt;br /&gt;
==Display Participant&amp;amp;rsquo;s Grid==&lt;br /&gt;
&lt;br /&gt;
This is the main asset of the Participant&#039;s Panel. This is where you can perform majority of central Panel&#039;s operations, such as adding, deleting , exporting, adding to survey etc.&lt;br /&gt;
&lt;br /&gt;
Let me show you a screenshot of the same and explain each of the feature.&lt;br /&gt;
&lt;br /&gt;
[[File:displayParticipants.png]]&lt;br /&gt;
&lt;br /&gt;
Explaination of the screenshot is given below&lt;br /&gt;
&lt;br /&gt;
1)  jqGrid header&lt;br /&gt;
&lt;br /&gt;
2)  Add Participant&lt;br /&gt;
&lt;br /&gt;
3)  Delete Participant&lt;br /&gt;
&lt;br /&gt;
4)  Reload Grid&lt;br /&gt;
&lt;br /&gt;
5)  Export to CSV ( Advanced )&lt;br /&gt;
&lt;br /&gt;
6)  Advance Search&lt;br /&gt;
&lt;br /&gt;
7)  Navigation Bar&lt;br /&gt;
&lt;br /&gt;
8)  Share Participant&lt;br /&gt;
&lt;br /&gt;
9)  Add to Survey&lt;br /&gt;
&lt;br /&gt;
10) Total Count&lt;br /&gt;
&lt;br /&gt;
11) Hide/show grid&lt;br /&gt;
&lt;br /&gt;
Now I will explain each of the features&lt;br /&gt;
&lt;br /&gt;
===Add Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily add individual participant using the plus sign in the grid pager.&lt;br /&gt;
&lt;br /&gt;
[[File:addParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
===Delete Participant===&lt;br /&gt;
&lt;br /&gt;
You can easily mark a single participant to delete or you can choose all the participants in the grid to be deleted. There are three possible conditions when deleting a participant.&lt;br /&gt;
&lt;br /&gt;
[[File:deleteParticipant.png]]&lt;br /&gt;
&lt;br /&gt;
The explanation of the three conditions is&lt;br /&gt;
&lt;br /&gt;
1) Delete Participant(s) from central participants panel only&lt;br /&gt;
&lt;br /&gt;
2) Delete Participant(s) from central panel and token tables&lt;br /&gt;
&lt;br /&gt;
3) Delete Participant(s) from central panel,token tables and all associated responses&lt;br /&gt;
&lt;br /&gt;
The first option deletes the participant from the central panel only, if the participant is in the token table, he/she will not be removed.&lt;br /&gt;
&lt;br /&gt;
The second option deletes the participant from central as well as token table, but the responses are kept.&lt;br /&gt;
&lt;br /&gt;
The third option deletes all traces of that participant from the system included responses.&lt;br /&gt;
&lt;br /&gt;
In all the three options the links created for the purpose of maintaining history related to a particular participant are also deleted.&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3082</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3082"/>
		<updated>2011-08-18T18:35:29Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;br /&gt;
&lt;br /&gt;
This new feature allows the administrator to store the participants to a central table that is independent of any token. The major advantages of allowing this is  :&lt;br /&gt;
* The participants are backed up, so if a user wants to backup the participants without having to go through the trouble of exporting his participants to a CSV file and then importing them back into a new survey.&lt;br /&gt;
* The user need not have to import CSV to each specific survey , he/she just needs to add the survey to the central table and then can add to as many surveys as he wants.&lt;br /&gt;
* In case of multiple users , one user can choose to share his participants with others and also set if he wants it to be editable with the shared user or not.&lt;br /&gt;
&lt;br /&gt;
Along with this, there is a advance attribute control and several other features.&lt;br /&gt;
&lt;br /&gt;
=The participants panel management tools=&lt;br /&gt;
&lt;br /&gt;
[[File:ParticipantPanel.png]]&lt;br /&gt;
&lt;br /&gt;
1) Home Screen&lt;br /&gt;
&lt;br /&gt;
2) Information ( Summary of CPDB )&lt;br /&gt;
&lt;br /&gt;
3) Display Participant&amp;amp;rsquo;s Grid&lt;br /&gt;
&lt;br /&gt;
4) Import from CSV&lt;br /&gt;
&lt;br /&gt;
5) Export to CSV&lt;br /&gt;
&lt;br /&gt;
6) Blacklist Control&lt;br /&gt;
&lt;br /&gt;
7) Global Participant&amp;amp;rsquo;s Settings&lt;br /&gt;
&lt;br /&gt;
8) Attribute Control&lt;br /&gt;
&lt;br /&gt;
9) Share Panel&lt;br /&gt;
&lt;br /&gt;
10) Panel Summary&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
	<entry>
		<id>https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3083</id>
		<title>Central Participant Database</title>
		<link rel="alternate" type="text/html" href="https://www.limesurvey.org/manual/index.php?title=Central_Participant_Database&amp;diff=3083"/>
		<updated>2011-08-18T17:14:25Z</updated>

		<summary type="html">&lt;p&gt;Aniesshsethh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
=Introduction=&lt;/div&gt;</summary>
		<author><name>Aniesshsethh</name></author>
	</entry>
</feed>