There have been many forum posts recently asking how to use Expression Manager (EM) and other new features available in Version 1.92+. We have found the best way to learn is to explore working demos.

So, we have updated the documentation to provide easy access to 9 new surveys that test all of the EM and new 1.92 features. For each, we describe which features the survey demonstrates, and provide representative screen shots plus a link to download the survey so that you can import and play with it yourself. The main features demonstrated include:

• Relevance - with support for more powerful conditional logic than is available via the 1.91+ Conditions editor.
• Group-level Relevance - if the same conditions apply to all questions in a group, you no longer have to apply them to each question (as was true in 1.91+) - simply specify the relevance at the group-level.
• Cascading Relevance - this never worked perfectly in 1.91+. Now it does. And, you don't need to specify all of the conditional logic for cascaded questions - they will automatically inherit the conditions from any questions upon which they depend.
• Piping / Tailoring - easier, more powerful ability to insert answers and question metadata than the old {INSERTANS:xxx} syntax.
• Conditional Micro-Tailoring - you can dynamically change sentences, such as "Mr." vs. "Mrs.", or "child" vs. "children" based upon prior questions (even ones on the same page). You can even conjugate verbs and decline nouns based upon the gender and/or number of your subjects.
• Equations - there is a new Equation question type that lets you do complex calculations and store them in the database, all without needing custom JavaScript (thus, this is more powerful and flexible than 1.91+ Assessment functionality).
• Conditional Validation - traditional validation, like regular expressions, min/max numbers of answers, min/max individual values, and min/max/equals summed values are more robustly supported, with tailored message and CSS styling rather than pop-up messages. Moreover, you can use equations so that your min/max criteria are based upon prior answers. Additionally, these traditional validation styles work for many more question types.
• (Sub)-Question Level Validation - for most question types, you can now use complex expressions to validate either individual answers or the collection of answers. This lets you do things like ensure that answers are in descending order; specify the maximum responses on a row; or even call external functions to validate the response.
• Better International Support - you can now use the comma as a radix separator (decimal point) in all question types that require numerical input, plus be sure that the data will be properly stored in the database.
• Qcode Naming - when you do tailoring, you need to know the proper naming of your variables. One of the surveys includes samples of every question type so you can see how variables should be named.
• Tailoring using Question Metadata - there are now 16 "dot notation" suffixes available for each question. These let you easily access question metadata (e.g. text, relevance, number, IDs) and answer metadata (e.g. the value stored in the database, the value shown, or the assessment value). One of the surveys has tables showing (for all question types), the values generated for each of these dot notation suffixes.

The LimeSurvey project is looking for volunteers who would like to help in an Open Source project on a long-term base :-). We have three positions that need to be filled, all of which require only little/none coding experience, but require about 10 hours of work every week.

Translations Community Manager

The translation community manager takes care of translators and translations. The important part of this is to make translations of the application and the documentation alot better by motivating existing and new translators, give incentives to translate, look for new tools to make translations better in general. You should be an experienced LimeSurvey user.

Incident Manager

The incident manager takes care of incidents in the LimeSurvey project in general, be it with the application or the website. He monitors new bug reports, does a first filtering, ask the reporters for details and tries to reproduce the issue. After the incident proves to be a really issue he assigns these to coders or translators. He reports to the project lead and if escalates things if a general problem seems to show up.

Documentation Manager

The documentation manager takes care of everything documentation related. He works together with the translations manager, as translations a re a big part of the documentation. He also makes sure that documentation is well structure and organized. If needed he will restructure or rewrite existing documentation. He will also look for ways to get the community involved with the documentation so in general it gets better.

If you are interested in any of these volunteer positions, please This e-mail address is being protected from spambots. You need JavaScript enabled to view it with the following details:

• Which position are you interested in and why?
• Short CV
• Details of your past experience with LimeSurvey and past involvement with the LimeSurvey community

Thank you for reading. if you have any questions please let us know.

The LimeSurvey team is pleased to announce the release of 1.92 RC4, which can be downloaded now.

This release resolves over 50 issues reported about 1.92 RC3. It also adds a new set of CSS classes available within templates so that you can tailor how you display the different types of validation messages. You can find more details about this in our documentation wiki.

Unless any truly major issues are discovered with 1.92 RC4, we are planning to release 1.92 stable on February 27th.  So, please test out this version and report any bugs you find via the bug tracker.