to use limesurvey as a customer survey tool.

a customer database is synchonising with limesurvey.

so new users appear in this table,

for this we need to log in and send these new customers a survey.

Currently, LSRC (LimeSurvey Remote Control) only supports .CSV files as templates.

It would be great to be able to support LSS/LSG/LSQ files on top of CSVs

This would allow me (and other users) to use an exported structure from a complex survey in v1.90+, modify it at will, and import it to create a modified version of the survey.

We detect a need in our user population (admins and survey creators) to print individual answers to a survey. For example an evaluation survey where the admin would like to print an answer record of 1 person or all the persons who filled in the survey.

Could you have a survey editor, much like you have a template editor?

I find it impossible to alter question/label set sizes and the placement on the survey (Left or right, top corner, etc, not question order)

Also, Could we edit multiple questions at the same time without exporting to excel first?

I believe the user should be able to customize the exported data layout, inc adding their own images/text to the template.

I dont believe the current exported template caters for many people or a wide variety of survey types.

I would personally like to be able to export templates for Word, PDF and Excel last (Excel less important in my eyes).

The editable templates should include both data results and graphs view.

I think it would be useful to be able to record and export the survey start language for multi-lang surveys, much like it is now possible to record the time-stamp or IP address. So if a survey was accessed with something like "http://www.mysite.com/surveys//index.php?sid=11111&newtest=Y&lang=fr", the "fr" would be in the exported data.

This would allow the data to be filtered by language.

A related idea would be to allow filtering by start language in the Statistics panel.

I have a question1 of type M. A test person is able to write an additional answer into the text box.
In question2 of the type F (array flexible labels) are all answers of question1 but not the answer from the text box. Now I want the test person to be able to rate his/her answer as well.

Make Limesurvey survey content available offline on the iPad or on the Android platform.
This will help boost usability of Limesurvey by people wishing to collect face to face data with customers, as an alternative to collecting hte data on-line, but hte database would be identical, and can be used to extend the reach of hte surveying method.

Some of the questions in my survey have images. I then export full survey responses and it is hard to understand the questions / responses without the images being exported too.

With a larger organisation and more people to collaborate on creating surveys, it would be a convenience to have the ability to support survey versioning.

The main problem with Lime survey is that groups and questions have all different IDs. If you copy a survey, the survey ID will change (and this is normal) but all the question IDs and the group IDs will also change.

This way of working makes Lime more difficult to integrate with outside applications. It also prevents having features like a bank of questions which one could pick into.

Example: I am passing company name parameter from another application (my ERP for instance) to a given question in one survey. I will use the SGQA Identifier which will be for instance 12345X1X1001.
Now, if I duplicate the survey into another one, and simply need to change two or 3 questions, lime will necessarily rename the survey ID (which is normal), but will also change the group ID and all question ID. What I passed to 12345X1X1001 will now need to be passed to 54321X2X1002 for instance. This means that from the external application, I must maintain a different map per survey - which is time consuming.

If Lime would not automatically increment the group and question numbers, passing (and retrieving) parameters would be far easier because only the survey ID would need to be changed. This would mean that the company name of all of my surveys could be passed to DDDDDX1X1001 with DDDDD being the survey ID to point to. In that situation, I would be able to copy the map of a survey to the next and simply change the mapping for questions which have truly changed versus the original survey copy.

I understand there might not be an easy way of achieving such purpose, at least I wanted to place that rationale in the pool of ideas as it is important for Lime to be integrable with other tools. I believe its current structure is a barrier towards that objective.

It would appear when you export and import, it does not import token attributes, yet these are included in the exported data?

We need to do both web-based and paper surveys. We would like to export surveys to paper and then import/scan survey results back into LimeSurvey

CSV export of data from LimeSurvey works for simple manipulation of data.

Triple-s survey interchange standard: http://www.triple-s.org/ was designed to allow exchange of complete survey structures and design between survey tools.

This feature would allow surveys and survey data to be easier exported and used in other survey products and tools.

In response to forum post #34111, I would like to be able to create a list of question codes and their matching SGQA identifiers. I have been using a long, laborious manner of creating Access (from MySQL) and Excel tables (from the LimeSurvey Administation screen) and stitching them together in one Excel table. Sometimes I end up with more SGQA fields than question code fields, even after allowing for the first few fields at the front of the table.

We do a lot of analyzing of data and it would be much more efficient if there were a simpler manner.

For clarification, here is an example of what I am looking for:

SatWRes 78787X1X3
FirstName 78787X1X4

Thanks!

tfj

I have a standard survey which I call template.
I export this each time and import it again to create a new survey and rename the imported survey.

In the 'Template Survey' I have an attribute setup in the tokens section called 'Occupation'.

When I export my 'Template Survey' structure, and view this in excel, I can see the token attribute 'Occupation'.

When I create a new survey and import 'Template Survey' and give this a new name, it does not import the token attribute 'Occupation'.

This would save alot of time for repetitive surveys / standard templates.

Ever since some users reported problems reaching a small survey hosted on a slicehost 256 VPS, I have been paranoid about optimizing limesurvey performance.
To day I run all surveys from a dedicated 8GB monster, but I still see mysql can be tuned in different ways.
But it is difficult to realistically simulate 500 users using a full feature survey.

To make the initial stucturing of a survey faster, it would be very helpful to be able to import a mindmap as the basic survey structure.

Level 1 Branches would be sections, level two answers. We could even go so far as to design standardised icons to identify the question types. The text attachment to a node would serves as the description of the question...

What do you think?

J

The response export options are very limited at this time. Yes, there are many options but the mostly give very hard to read exports.

For example, there is the export to program option, which lets you export responses to Word, Excel or PDF format. If you have several dual scale array questions, such a Word export becomes illegible.

The same goes for the 'view single response'. When you are in the 'view responses' screen, there is a magnifying glass icon for each response which lets you zoom in on that response. But also that response is almost illegible.

Additional token attribute fields are great, but please add some validation:

- on import, the additional attribute fields should be created automatically; if not, give a warning

- when using additional attribute fields as placeholders for replacements (e.g. email), there should be a warning plus abort the sending procedure in the cast that the attribute field does not exist in the database

- additional attribute fields should be recreated when importing surveys