Hello,

I would like to use LimeSurvey on mTurk and I need a way to generate a unique code (randomly) in the end message, that would be saved in the survey results preferably. In order to get paid, participants can then type in the code in mTurk and I would know that they have actually finished the survey.

Any help would be appreciated as I have not found good info on this problem

Best,

Hi ,
there are 2 old great posts about this topic (using differents ways)... here (using Expression Manager) and there (using chance.js)

Hi,

thanks a lot. If I could have just a bit of your time since I am a total beginner. I have seen this SAVEDID option but I am not sure to what it relates to. Is this an option that is choosable or is it something that I need to have coded for. Plus, how would this ID be shown to the participants at the end?

All the best,

"SAVEDID" is the respondant ID. It's a unique number (incremental, start is #1) for a survey but if you have several survey it's not so unique. You can print it at the end using the placeholder {SAVEDID}

...but if you have several survey it's not so unique.

You can combine it with the survey ID.

Thanks to all.

If anybody else stumbles on this, I've managed to produce a random string of digits using the code already mentioned in one of the linked pages above.

{if(!is_empty(PIN),PIN,1*rand(357382, 908173))}

"PIN" is the name of your question group or just the questions (this can obviously be anything you want to name it). For me, as is per usual in mTurk, it was important to have a six digit number so I just basically said the rand() function to randomise between two six digit numbers (they can also be anything really). Not the most elegant solution but it works.

Hope it helps.

You are aware that the same code could appear more than once, right? Ok, the chance is low, but it is there...

Yes, absolutely, but I'm starting the study in one day, so I'm willing to accept the risk. Plus, the, admittedly low chance of reoccurrence is worth it as I plan on some 100 - 200 participants.

Do you have a way of ensuring that it never repeats?

Best,

Do you have a way of ensuring that it never repeats?

Incorporate the SAVEDID as Ben suggests.

The problem with the SAVEDID is it can be 1, 2, 3 (even more) digits, so an advanced equation is required to match the required length...
Using time() & rand () with 6 digits, an option is: (IMHO, with 200 participants, the probability of duplicate PIN outputs, may be the same than for of a sudden meteor shower on the server)

The problem with the SAVEDID is it can be 1, 2, 3 (even more) digits

You can pad it with zeros depending on the length.

But if you have a fixed length code randomly generated number and then join the saved id at the end it should be fine. At least if you don't care that the final code could be anything from 7 to 9 digits long. But you will know that everything after the sixth digit is the savedid.