- Posts: 2
- Thank you received: 0
Need help with relevance equation
I've set up a relevance equation for all my question groups using a yes/no question - this works fine using the equation
consent == 'Y'
However for a couple of groups I want to add a second condition in the equation using answers from a radio list, ie.
consent == 'Y' AND uniplans == 'No'
However this doesn't seem to work and the survey just jumps to the end in preview. The problem I'm having (I think) is identifying the answer values. I'm used to analysing secondary data in SPSS and just assumed that LimeSurvey would default to sequential values for labels - in my above example for the question 'uniplans' 'yes' would be 1, 'no' would be 2 and so on.
What have I got wrong: the equation or the value LS is expecting for 'uniplans'?
This is what i get in the answers section when I check logic for the 'uniplans' question:
A-1 A1 [VALUE: 0] Yes
A-2 A2 [VALUE: 0] No
A-3 A3 [VALUE: 0] Do not know
A-4 A4 [VALUE: 0] Prefer not to say
(Should VALUE be set for each answer?)
what you have to enter in your relevance equation is the code, so
the code of "No" in the uniplans question is "A2"
this means your relevance equation should be:
consent == 'Y' AND uniplans == 'A2'
No, you get the codes you entered in the anwer options.
example for the question 'uniplans' 'yes' would be 1, 'no' would be 2 and so on.
Obviously you just used the default values "A1", "A2", "A3, ...
Why do you use a relevance equation for all groups with "consent=='Y'"?
What happens if a respondent answers "No"?
Is he screenouted? Just use a quota. Then all "No"s are gone and you do not need a relevance equation for "Yes".
is not very helpful.
the web-based version of LimeSurvey through my institution.
Which version is it?
Volunteers are not paid.
Not because they are worthless, but because they are priceless
I'd already set up a zero quota for no responses to 'consent' (which is a question indicating informed consent has been given). I thought I would play it safe and add the relevance equation.
So, that's two things your post taught me. Three including discovering the fact I'm using Version 2.73.1+171220