Methods to verify Subject ID with Inquisit Lab


Author
Message
lakeside
lakeside
Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)Guru (6.6K reputation)
Group: Forum Members
Posts: 34, Visits: 121
Hi again,

Are there clever (or brute force) mechanisms available to ensure the respondent has entered a Subject ID that verifies against an external ID pool with Inquisit Lab? We are considering writing our own application that requests the Subject ID and Group ID, verifies them against those found in a database, and then passes the SID/GID to the command shell to open Inquisit. On a similar note, I noticed when we batch several tasks together, the user is prompted before every task for a SID/GID. As we want to link the NC data to survey data, this introduces a lot of opportunities for mistyped SIDs.

Thanks!

Tags
Dave
Dave
Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)Supreme Being (966K reputation)
Group: Administrators
Posts: 11K, Visits: 74K
That would be one way to do it. I'd probably prefer a different approach using string functions (see the functions reference in the documentation). Simple example:

<values>
/ validsids = "Alice,Bob,"
</values>

<expt>
/ stop = [!contains(values.validsids,script.subjectid)]
/ blocks = [1=myblock]
</expt>

<block myblock>
/ trials = [1=mytrial]
</block>

<trial mytrial>
/ stimulusframes = [1=mytext]
/ validresponse = (57)
</trial>

<text mytext>
/items = ("Blurb...")
</text>

In the real world, you'll need more elaborate / robust  validation logic, but you get the idea.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search