Post by andre on Apr 7, 2023 6:33:52 GMT
Dear All,
we have a video-rating task where we use 3 questions on a page, something like:
page: begin
l: video1
t: youtube
q: Watch the video
- <youtube ID>
l: rating1
t: radio
q: please rate
- option1
- option2
l: rating2
t: range
q: please rate
- question1
page: end
And then we have in total 60 videos presented in the above way.
We encapsulated all these video presentation between randomization: begin and randomization: end
And while it indeed keeps the pages together and randomises the videos (and keeps the question on the same page), it also randomises outside the scope between randomization: begin and randomisation: end
For example, we have some demographic questions as well (outside the randomisation scope), and it might happen that a couple of videos are presented before the question for age (first question in the survey, not included in the randomisation), then age comes, then again some videos, then the question for gender, etc.
Is this a bug, a known limitation, or are we (hopefully) simply doing something wrong?
Best wishes,
Andre
we have a video-rating task where we use 3 questions on a page, something like:
page: begin
l: video1
t: youtube
q: Watch the video
- <youtube ID>
l: rating1
t: radio
q: please rate
- option1
- option2
l: rating2
t: range
q: please rate
- question1
page: end
And then we have in total 60 videos presented in the above way.
We encapsulated all these video presentation between randomization: begin and randomization: end
And while it indeed keeps the pages together and randomises the videos (and keeps the question on the same page), it also randomises outside the scope between randomization: begin and randomisation: end
For example, we have some demographic questions as well (outside the randomisation scope), and it might happen that a couple of videos are presented before the question for age (first question in the survey, not included in the randomisation), then age comes, then again some videos, then the question for gender, etc.
Is this a bug, a known limitation, or are we (hopefully) simply doing something wrong?
Best wishes,
Andre