Please help us help you and fill where relevant:
LimeSurvey version: 6.3.4
Own server or LimeSurvey Cloud: own
Survey theme/template: fruity
==================
(Write here your question/remark)

Hello,

I wanted to know if there is some way I can implement two things in my surveys:

• Tracking the count of DKs - for example if out of 10 question 5 or more are answered with DK, the respondent will be shown some warning message
• Tracking the answering time of each question or question group and if the average time is under let's say 5 secs the respondent gets shown some warning message

I'm guessing there will need to be some hidden questions involved, as for the message I was wondering if it could be shown as a pop up message or it will have to be a regular text type question.

I would appreciate any guidance on this,

Thanks in advance,

Kind regards,

1. Yes, count the DK.
If all DK have the same code, (99),
{countif(99,Q1,Q2,Q3,.)}
2. Equation to store the time at the start of each group.
Always calculate the differences to know the ised time of the previous group.

But everything depends on the structure of your survey.

Nest you show a realistic example (lss export)

Joffm 
 

Thank you for your quick reply!

I'm attaching a dummy survey in which I added question types I use most often.

Would like to see how the counting DKs hidden question would get implemented to trigger a pop up notification?

Thank you for the help, 

Kind regards,

Nadica.

From a respondent point of view:

These "quality checks" can be annoying, when the quality checks for the survey itself haven't been done.

What I often see are surveys that are not very well made, that "force" respondents basically to answer "DK", because the survey designer did not take into account all profiles out there.

Happens to me quite a lot, where for certain questions you basically need to answer DK, because otherwise you would basically give a false answer. The answer option you need might not be there, or the question has been asked wrong, etc.

So before implementing these quality checks, make sure to look at your survey from all sides, so you don't "penalize" honest respondents, because of flaws in the survey. Not saying that this is your case, I am just saying that a lately see a lot of surveys that are not very well made.

Years ago it was quite common to do pre-tests with real respondents before sending surveys out, just to check if the survey makes sense, if it covers all scenarios, etc. You hardly see this anymore and it shows.

Hi,

I fully agree with @holch, but if you want to do this, here an option.
To count the DKs  (BTW I renamed these long QuestionCodes and set all DKs to '99')
{sum(countif('99',that.Q2a.NAOK,that.Q2c.NAOK),intval(Q2b_99.NAOK=="Y"))}

To show this with something like a popup you may use a bootstrap alert.
[url] getbootstrap.com/docs/5.3/components/alerts/ [/url]



But this is up to you.
Mabe something like this
And I won't discuss this further in English.

Joffm

BTW:
Can't you revise your conditions?
With numerical codes instead of text it is much shorter:
Qinviteincentive: Qinvitation.NAOK != 'Y
Qage: Qinvitation.NAOK != 'N'  or Qinviteincentive.NAOK != 'N'
Demographics: Qage.NAOK >1

 

Thanks for sharing your thoughts! I totally understand your frustration when surveys aren't well-designed. In our case, most of our surveys are designed to gather general opinions that can be answered by a wide range of people, so we aim to make them as inclusive and straightforward as possible. We rarely ask for specialized knowledge, which is why we try to avoid situations where respondents would need to choose 'DK.' However, I appreciate your point about pre-testing, and it's something we'll definitely keep in mind for the future to improve the experience for everyone.

Thank you Joffm for your explanation!

I'm not very well-versed in JS, I appreciate your help. This should be enough to get me started.

We rarely ask for specialized knowledge, which is why we try to avoid situations where respondents would need to choose 'DK.'

It is often not about special knowledge. But often none of the answer options fit my specific case. So I basically have to answer DK, because if I would click any other answer, it would be wrong and give a wrong impression in the results, if you know what I mean.

It was just a side note as I don't know how you guys work. It's just I am seeing this all the time.