User Manual for Inquisit's Decision Board Analysis Task


___________________________________________________________________________________________________________________	

								DECISION BOARD ANALYSIS - Template
___________________________________________________________________________________________________________________

Script Author: Katja Borchert, Ph.D. (katjab@millisecond.com) for Millisecond Software, LLC
Date: 11-05-2014
last updated:  02-21-2022 by K. Borchert (katjab@millisecond.com) for Millisecond Software, LLC

Script Copyright © 02-21-2022 Millisecond Softwaree

___________________________________________________________________________________________________________________
BACKGROUND INFO 	
___________________________________________________________________________________________________________________
This script implements a simple Decision Board Task modelled after the one described in:

Mustafa, N., Ahsan, K. & Kingston, P. (2012). Intelligent Survey Software using Decision Board 
Analysis Technique for Recruitment Process in UK. WSEAS TRANSACTIONS on
INFORMATION SCIENCE and APPLICATIONS, 9, 220-229.

NOTE: The purpose of this script is to provide sample code to build your own decision board.
By default, this script runs with a limited number of tabs and applicants (2).

___________________________________________________________________________________________________________________
TASK DESCRIPTION	
___________________________________________________________________________________________________________________	
Participants are asked to make fictional hiring decisions of 2 (script default) applicants.
For each applicant, participants view a decision board: a board of tabs 
(e.g. 'resume') that -when clicked upon- open up pop-up windows with additional information. 
When participants have gathered enough information about one applicant, they can click on a tab 'decision'
to (a) decide whether to hire this applicant (yes/no) (b) state the reasons for the hiring decision and
(c) give a confidence rating for their hiring decision.
The order of applicants is randomly determined

___________________________________________________________________________________________________________________	
DATA FILE INFORMATION 
___________________________________________________________________________________________________________________
The default data stored in the data files are:

(1) Raw data file: 'decisionboardanalysis_raw*.iqdat' (a separate file for each participant)

build:								The specific Inquisit version used (the 'build') that was run
computer.platform:					the platform the script was run on (win/mac/ios/android)
date, time: 						date and time script was run 
subject, group: 					with the current subject/groupnumber
session:							with the current session id

blockcode, blocknum:				the name and number of the current block (built-in Inquisit variable)
trialcode, trialnum: 				the name and number of the currently recorded trial (built-in Inquisit variable)
										Note: trialnum is a built-in Inquisit variable; it counts all trials run; even those
										that do not store data to the data file such as feedback trials. Thus, trialnum 
										may not reflect the number of main trials run per block.
									
response:							the participant's response (for mouse input: mouse response; for keyboard response: scancode)
latency: 							the response latency in ms

block.dba.sumlatency:					time participant spent on current decisionboard (in ms)
firsttab:								first tab checked out by participant for current applicant
count_firstname:						counts number of times participant clicked on first name tab
time_firstname:							sums up the time (in ms) participant spent on first name info
(same for all the remaining info trials)

radiobuttons.hiredecision.response:		stores the hiring decision for the last viewed applicant
textbox.reasons.response:				stores the reasons for the hiring decision for the last viewed applicant
radiobuttons.confidence.response:		stores the confidence rating for the hiring decision for the last viewed applicant
viewingorder:							the order in which all the information tabs are viewed for the current applicant


(2) Summary data file: 'decisionboardanalysis_summary*.iqdat' (a separate file for each participant)

inquisit.version: 						Inquisit version run
computer.platform:					the platform the script was run on (win/mac/ios/android)
startdate:							date script was run
starttime:							time script was started
subjectid:							assigned subject id number
groupid:							assigned group id number
sessionid:							assigned session id number
elapsedtime:						time it took to run script (in ms); measured from onset to offset of script
completed:							0 = script was not completed (prematurely aborted); 
									1 = script was completed (all conditions run)
									

quit:								0 = participant did not quit; 1 = participant did quit

//APPLICANT1:
applicant1:							the itemnumber of first applicant (e.g. here:1 = Hans; 2 = Gretel -> item.firstnames)

time_decisionboard1:				the time (in ms) spent on the Decision board for the first applicant

firsttab1:							first tab checked out by participant1
Firsttab2:							first tab checked out by participant2

count_firstname1:					counts the number of times participan clicked on the first name info tab for applicant 1
count_lastname1:					counts the number of times participan clicked on the last name info tab for applicant 1
count_dateofbirth1:					counts the number of times participan clicked on the date of birth info tab for applicant 1
count_gender1:						counts the number of times participan clicked on the Gender info tab for applicant 1
count_appliedposition1:				counts the number of times participan clicked on the applied position info tab for applicant 1
count_currentemployment1:			counts the number of times participan clicked on the current emloyment info tab for applicant 1
count_coverletter1:					counts the number of times participan clicked on the Coverletter info tab for applicant 1
count_resume1:						counts the number of times participan clicked on the Resume info tab for applicant 1

time_firstname1:					time (in ms) the participan spent on the first name info for applicant 1
time_gender1:						time (in ms) the participan spent on the last name info for applicant 1
time_dateofbirth1:					time (in ms) the participan spent on the date of birth info for applicant 1
time_gender1:						time (in ms) the participan spent on the first name info for applicant 1
time_appliedposition1:				time (in ms) the participan spent on the applied position info for applicant 1
time_currentemployment1:			time (in ms) the participan spent on the current employment info for applicant 1
count_coverletter1:					time (in ms) the participan spent on the Coverletter info for applicant 1
values.time_resume1:				time (in ms) the participan spent on the Resume info for applicant 1

hiredecision1:						stores the hiring decision for applicant1
reasons1:							stores the reasons for the hiring decision for applicant1
confidence1:						stores the confidence rating for the hiring decision for applicant1


wiewingorder1: 						the order in which all the information tabs are viewed for applicant1 and applicant2

(same for applicant2)

___________________________________________________________________________________________________________________	
EXPERIMENTAL SET-UP 
___________________________________________________________________________________________________________________
This script provided decision boards for 2 applicants. The order of the applicants is randomly determined
(Editable Lists -> list.applicantindex)

___________________________________________________________________________________________________________________	
STIMULI
___________________________________________________________________________________________________________________	
This script runs with generic stimuli provided by Millisecond Software.
Check section EDITABLE CODE -> Editable Stimuli for item set-up

___________________________________________________________________________________________________________________	
INSTRUCTIONS 
___________________________________________________________________________________________________________________
see section EDITABLE CODE -> Editable Instructions for more info