Project Implicit Knowledge Base

To help increase retention within studies, it is advisable to incorporate guidepost pages that orient your participants to where they are in the study and what they are doing.  Use them to do things like:

• thank your participants for participating
• tell them how long the next phase of your study will take
• remind them that they will receive feedback at the end of the study. 

If you have a guidepost at the very beginning of your study, it should double as a realstart page.

In an effort to more effectively monitor study completion rates, all studies should have a “realstart” task that occurs directly after the consent page. This allows researchers to determine what percentage of people who make it past the consent page actually complete the study. There are two options for incorporating a realstart task into your study:

1) The basic realstart page is an html page that you can use to have a welcome screen or general overview of the task they are about to complete (e.g. Here’s what happens first: _____. It will take about 3 minutes).

Every study must begin with a startpage. This page launches the session and checks to see if the computer has an updated Flash player. There are two startpages that you can choose to employ:

This page will cover ways to integrate social media into your studies.  Right now the example will cover how to add a Facebook link with IAT feedback and a twitter link.  These are only recommended to be used on the final debriefing page, to avoid social network effects.  A sample demo task debriefing 2 is included below.

First off, make sure that your file is a .jsp, renaming the .html to .jsp if you need to.  Include the following at the top of the file:

<%@page import="java.util.*,java.net.*, org.uva.*" errorPage="/research/ShowError.jsp"%>

This page covers what you need to make data be encrypted before being sent to the database, as well as how to later decrypt the data.  You might want to do so in cases where the data you collect is confidential, especially if you are running measures on a demo study, since many people will access to the data.  There are several steps.

1.  Generate your encryption keys:

You can disable a study in the expt.xml file by adding the disable="URL" attribute to the study.  Anyone who tries to take the study will instead be sent to the URL that you specify.  Using this can be an advantage for private link studies, where you want people clicking the link after the study has ended to get a page telling them that the study is expired.  For example, to send someone trying to take your study to a more important study:

<Study id="Demo.Skin" datagroup="std" disable="http://humanoralien.com">

A new feature is ready for testing by lab members- a study progress bar.  This bar will appear at the top of the window as participants take the study, showing how much they have completed.  You can also set the weight of each task.  The weight will determine how much the bar will go up after the participant completes the task.  So if you have 100 total weight and the participant completes a 8 weight task, the progress bar will increase by 8%.  Just change your expt.xml file to use

<Task id="startpage">/common/en-us/html/InstructionsProgressBar.jsp</Task>

You can use the <Done> tag in your study expt.xml file to show that all important manipulations / measures have been completed by the participant.    Do so by adding <Done/> to the map, as follows:

<Map>

<Task id="startpage"/>

<Task id="iata"/>

<Done/>

<Task id="debriefing1"/>
<Task id="debriefing2"/>

</Map>

(1) Raw data from all Project Implicit DEMO, INTL, FEATURED TASK, PIMH, and ATTITUDES 1.0 and 2.0 datasets are available for use within Project Implicit labs (Nosek, Banaji, Greenwald, Teachman, Nock, Ratliff, Bar-Anan, Smith).  Any uses should be supervised by the PI of that laboratory.  PI's assume responsibility for communicating uses with each other to avoid conflicting uses.