- Posts: 9
- Thank you received: 0
- Forum
- English support forums
- Can I do this with LimeSurvey?
- Individual survey question for a number survey participants
Individual survey question for a number survey participants
- ConstantinTU
-
Topic Author
- Offline
- New Member
-
I am currently working on a customer survey on the LimeSurvey web platform and I'm fairly new to this. Couldn't find anything regarding my problem.
Does the survey platform provide a solution in which it is possible to create an individual question with a varying number of answer options for each survey participant? This should be best done by importing an Excel customer list, as the customer base is in the four-digit range. Is it also possible (from the customer's point of view), after the successful completion of the survey, to access and edit it again at a later point in time?
Thank you for your help
Cheers
Constantin
Does the survey platform provide a solution in which it is possible to create an individual question with a varying number of answer options for each survey participant? This should be best done by importing an Excel customer list, as the customer base is in the four-digit range.
Not quite sure if I understand. Are you referring to a loop, e.g. someone has 3 children, so he gets 3 questions (one for each child), the next one has 5 children, so gets 5 questions?
Or, in a specific question you will show/hide answer options for a respondent, depending on the pre-defined relevance for this specific person?
Both are possible, but solutions are obviously different, e.g. there is no real loop option. You would have to create the maximum number of questions that you would expect.
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
- ConstantinTU
-
Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 0
thank you for your answer. Yes, I think my question was to general. I'll try to explain it with an example.
So lets say we have specific information about each of our customers stored in a company internal database. The individual question for the customers should be like this:
If customer A opens the survey he is asked to select one of the specific information data we have from our database.
So customer A would be able to select in a dropdown menu:
"CustomerAData XX1"
"CustomerAData XX2"
"CustomerAData XX3"
-> customer B would be able to select:
"CustomerBData YY1"
"CustomerBData YY2"
"CustomerBData YY3"
"CustomerBData YY4"
-> customer C would be able to select:
"CustomerCData ZZ1"
"CustomerCData ZZ2"
and so on...
I also put those examples in the attachments.
Right now I would have to create an individual survey for each customer if I'm not mistaken. Problem with that is the big amount of customers we have.
Thank you very much
The customer data for each customer are totally different, right? Or could "CustomerBData YY1" be the same as "CustomerAData XX1" (to be clearer: are they from the same list or are they really just for each customer).
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
- ConstantinTU
-
Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 0
Ok awesome, thanks. I will check that out.You could store this information in a custom token attribute I guess.
The customer data for each customer are totally different, right? Or could "CustomerBData YY1" be the same as "CustomerAData XX1" (to be clearer: are they from the same list or are they really just for each customer).
You are correct. The data for each customer is completly different. Each data set consists partly of an individual identification number.
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
Depending on one ATTRIBUTE the drop down is populated.
www.limesurvey.org/forum/development/114...ute_5%7D-on-question
Regards
Joffm
Volunteers are not paid.
Not because they are worthless, but because they are priceless
- ConstantinTU
-
Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 0
Your suggestions with the tokens really helped me out. I got it to work how I wanted.
Sadly…
…about 90 max. I got it now working with 65 tokens (which I can live with). But there I ran into the next problem. I cannot create so many sub questions for each scenario. This will be massive.holch wrote: How many of those number can there be per customer as maximum?
Just for clarification what I mean.
The sub questions for each customer and scenario are the same. So this should be easy, but I want the customer to answer each dataset at one point in time.
Lets say,
Customer A would be able to select in a dropdown menu:
"CustomerAData XX1"
"CustomerAData XX2"
"CustomerAData XX3"
.
.
.
"CustomerAData XX65"
Customer A selects "CustomerAData XX1". The next question appears and asks for for information in a multible short text question type. There are up to 26 fields for each data set, in this case for "CustomerAData XX1".
... more questions follow.
So everything is great until this point.
When the customer has finished those questions for "CustomerAData XX1" he is supposed to scroll up again to the first question and select "CustomerAData XX2". Then he should answer those same questions again just for the dataset "CustomerAData XX2". And so on until he reaches the end of the list in the first question.
Is that even possible with so many tokens(max. 65 dropdown options)? Or does the participant need to restart the survey?
Thank you
Best,
Constantin
So there are customers that have up to 90 of those codes???? You expect them to fill in 90x 65? Your whole thing is extremely confusing.
I just don't get what you are actually trying to do. Can you give a graphic example that explains a little bit better what you are trying to do? I have the feeling that you are over complicating things.
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
sorry, either I am too tired to understand your explanation or too ...
And reading this I fear that you will reach the MySQL limit of columns.
Really?
Only CustomerA with 65 options, each answered in the first question with multiple short text question (up to 26 fields) will use 1690 columns which is more than possibleAnd so on until he reaches the end of the list in the first question.
So you should revise your survey structure.
Are the questions to your customers really so different? How will you compare the answers of different customers?
Maybe you can use "micro-tayloring" or resart the survey by end-url with a certain parameter 65 times.
So the best would be you provide a sample survey (*.lss)
Joffm
Volunteers are not paid.
Not because they are worthless, but because they are priceless
This means you would have to built 65x those 26+ subquestions. This would be a minimum of 1690 columns and most probably means you would run into the column limit of MySQL, which should be around 1000, give and take.
I guess you are better off to create one survey only for one code and give the respondent 65 surveys to fill. Then you just pass the code via token attribute into the survey.
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
- ConstantinTU
-
Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 0
You are correct that's the idea behind it.holch wrote: Let's take the worst case scenario: the client A who has codes from "CustomerAData XX1" to "CustomerAData XX65", or in other words, this client A has to go through the loop 65 times. And for each of these loops there is a minimum of 26 subquestions and there might be more to follow, as you mentioned.
Yes I'm afraid this will happen.Joffm wrote: Only CustomerA with 65 options, each answered in the first question with multiple short text question (up to 26 fields) will use 1690 columns which is more than possible
attached a sample (*.lss)
It's a kind of looping through your 65 datasets.
Add to the survey-URL a parameter "dsno" for "DataSet number".
so the url is something like:
https://www.myServer.com/limesurvey/index.php/[SurveyID]?token=1111&dsno=1
In your survey you grab the dsno.
Then there is the "multiple short text" question about documents.
In the question text enter the equation
{if(dsno==1,"Name of Dataset 1",if(dsno==2,"Name of Dataset 2",if(dsno==3,"Name of Dataset 3",...)))}
At the end change the dsno to dsno+1.
And in the end-url you link to the same survey (now with the same token and the new Dataset number)
https://www.myServer.com/limesurvey/index.php/[SurveyID]?token={TOKEN:TOKEN}&dsno={dsno}
At the end (dataset number = 65) empty the end-url or set a quota=0 on dataset number.
So you get 65 records in your answer table for each participant.
That's an idea to avoid problems with the column limits.
Best regards
Joffm
P.S. Are there always 65 datasets? In your survey I saw conditions up to 90, or so.
Volunteers are not paid.
Not because they are worthless, but because they are priceless
I finished my idea.
First there is a "global" survey with some general questions which links to a second survey.
This second survey contains only the two questions about documents and plans for one dataset and afterwards links to itself to ask the same questions for the next dataset.
So you will get one record of the participant in the global survey and 65(?) records for each participant in the second survey.
Of course it is easy to extend.
Here a short (quick and dirty) video
www.youtube.com/embed/MObiXhVLODw
Regards
Joffm
Volunteers are not paid.
Not because they are worthless, but because they are priceless
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.