Please help us help you and fill where relevant:
LimeSurvey version:  6.12.3+250331
Own server or LimeSurvey Cloud: Own
Survey theme/template: fruity_twentythree
==================

Hi,
We've set up a simple customer satisfaction survey on an Android tablet. The tablet is secured in kiosk mode and the browser is set to refresh the start page every 10 minutes just in case.

Now the problem is, every refresh of the survey start page generates an incomplete response.

Perhaps, that's got something to do with the JS snippets we've used on the survey start page. There, the test person is asked to tap on one of three smileys using the touch screen. We wanted to hide the submit button so the following code has been used:

<script type="text/javascript" charset="utf-8">

    $(document).ready(function(){
        $('#ls-button-submit').hide();
        $('#question{QID} input[type="radio"]').on('click', function() {
        $('#ls-button-submit').trigger('click');
        });
    });  
</script>

Any ideas? My apologies if this appears to be a dumb question - layman at work...

This is usual behaviour.
When a new survey is started a new record in the answer table is created.
Your script doesn't affect this.

But what is the real problem?
You can remove the incompletes in the response table from time to time, and you will export only complets at the end of the survey.

Or you can create a small script (php) on your server to delete incomplete responses and call it with a cron job.

Joffm 
 

Thanks a lot for your reply!

I still find it odd that a record is created just because the page is loaded without any user interaction whatsoever.

But anyway: the issue is that we have numerous such terminals and each of them creates a response every ten minutes. So, this adds up to a load of unwanted data.

The php script you suggest might be a work around. However, we have other surveys on the server as well and add terminals continuosly. So we'd have to edit the script regularly and manually add the survey IDs.

I still find it odd that a record is created just because the page is loaded without any user interaction whatsoever.

Because for Limesurvey there was an interaction. Someone "clicked the link" or "someone opened the survey".

But anyway: the issue is that we have numerous such terminals and each of them creates a response every ten minutes. So, this adds up to a load of unwanted data.

In your scenario each terminal can generate max. 144 of unwanted data sets. I don't find that a big issue. Now in your scenario, as you seem to have a lot of terminals, this might be a bit more work. But then, I don't see a big issue. The empty responses take up almost nothing in the database. Cleaning this once a month should be more than enough. And exporting only the completed responses should work fine.

What you could do: Create a splash page that you put BEFORE the Limesurvey survey. For example with the smilies. Then when the respondent clicks, pass the chosen smiley to Limesurvey via the URL and save it into the Limesurvey survey.

But then, it seems like this smiley page is the only page? I don't know why I get this impression. In this case: Why not just a simple script that counts the smilies and writes it into a database. I think Limesurvey is not necessary in such a scenario.

Thanks for your suggestions!

In your scenario each terminal can generate max. 144 of unwanted data sets. I don't find that a big issue.

As this is an ongoing survey, just 50 terminals lead to over 2,5 mio. useless entries p.a.

But then, it seems like this smiley page is the only page? I don't know why I get this impression.

Actually, it's not a one-pager. If the users click on a "not happy" smiley, they get to give more detailed feedback.

 

As this is an ongoing survey, just 50 terminals lead to over 2,5 mio. useless entries p.a.

That's why you would delete them on a regular basis.

Actually, it's not a one-pager. If the users click on a "not happy" smiley, they get to give more detailed feedback.

Then I think you could implement a fairly simple solution that probably avoids the empty responses:

Create the page with the smilies outside of Limesurvey and link each smiley with a survey url (all have the same URL, just with a different variable passed on to Limesurvey). This variable can be read into Limesurvey an via Expression Manager/script fill a hidden question (so you replicate the smiley question with a list(radio) type question for example and set the response via expression script to this hidden question. This way you can do the reload to this external page and not directly the survey. So the database entries in Limesurvey will only happen if someone clicks on a smiley.

Okay, cheers!
Perhaps I'll try the splash page proposal.