Main || CreateWizard || Status || Tasks ... instStatus|| descriptor|| parameters|| modules||

### The Instrument Creation Wizard

### What needs to be done/ has been done?

For the instrument...

Create, or modify, an instrument (details) This wizard will guide you through the many steps of creating a dSurvey instrument. You can create a new instrument, or modify an existing instrument. Note that this wizard supports a subset of the myriad dSurvey options -- advanced administrators might find it more convenient to use the various create and modify instrument options in the main menu.
Create new instrument. | `with a 1-word name of:` `and in the (1-word) project:`
or
Modify existing instrument. | List of current instruments

#### Specify features of this instrument ...

Description: |

What type of instrument: |
Lab session | Field session | Open-ended
Lab session: A controlled group of participants, who start and end at the same time (with no entry or exit). For example, 10 participants in computer lab, spending an hour and engaging in 20 rounds of an auction. These can be highly dynamic, with administrator control of just what is seen when (thus, the administartor is actively monitoring the entire session). Field session: A less-tigntly controlled group of participants, who start and start at the same time but may come and go within that time period. For example, 30 participants who are at their homes, and visit a site once a day over the course of a week -- so that each day can be considered a round -- but all participants are not logged on at the same time. These may be moderately complex (with responses depending on other participants actions), but are typically not subject to intense administrator control (that is, the administrator is not actively monitoring the session). Open-ended session: An open-ended survey, with participants joining and leaving in a more-or-less random fashion. For example, 100 particpants joining over the course of a month, and spending 5 minutes answering a few questions. These are typically fairly simple, with limited dynamic interactions (the administrator is not actively monitoring the session).

How to assign participant-specific data: |
None | Order of joining | By name
None: No participant-specific data. Order of joining: Partcipant specific data is specified in the `reference` data file for this instrument. Participants will be assigned data from a row in this data file as they join. Thus, the first row is used to assign participant-specific values to the first participant to join a session, the second row for the second participant to join, etc. Note that rows are cycled through: if N rows are specified in the reference data file, then the N+1 participant will get the first row, etc. By name: Participants will be asked to provide their name. This name will be compared against entries (in the session-specific `allowedUsers` file), and if a match is found will be assigned the indicated row in the `reference` data file. Note that in addition to a name, you can require a password (in the `allowedUsers` file).

Unique names? | Require Password Default Password:
Unique Names: If you want to require every participant to have a unique name, check this box. Note that when a participant joins a session, he is always asked to provide a `name`. This name can be used in the instrument. It is also used with `By name assiginment of participant data`. To allow more than one user to have the same name, do not check this. Require Password: Check this box if you want to require participants to enter a password. If you check this, you should choose a default password (if you don't, the default password will be `1`). Default password: Specify the default password. This is ignored if the Require password check box is not checked. Note that if you are assigning participant data By name, you can override this default password on a participant specific basis.

Get contact info? | Get a nickname? | Max participants:
Get contact info: If this box is checked, participants will be asked to provide contact informatin (such as an e-mail address) when he joins the session. Get nickname: If this box is checked, participants will be asked to provide a nickname when joining the session. This nickname can be used in the instrument (as an alternative to the `name` that is always requested). Max participants: You can specify the maximum number of participants allowed to join this session. If you do not want to impose a maximum, leave this box empty.

Messages: |
No messages | Notes only | Messages to admin | Messages to anyone
None: Messages are disabled -- participants can't send messages, the administartor can't send messages, and the note creator is not available. Notes only: Participants can not send messages, but they can create notes that can be viewed at any time. The administrator can send messages to any participant (or to several at the same time). Maessages to admin: Participants can send messages to the administartor, but not to other participants. The administrator can send messages to any participant (or to several at the same time). Messages to anyone: Participants will be able to send messages to any participant (as well as to the administrator). The administrator can send messages to any participant (or to several at the same time).

### Create data files for this instrument ... ()

- General parameters
- Participant specific parameters
- Allowed users
  To modify allowedUsers, chose By name method of assigning participant specific data

Notes: | By default, the general and participant specific parameters for this instrument will be used whenever a session is created that uses this instrument. Of course, once you create a session, you can always customize these parameters. You chose to assign participant data By name -- that means when you create a session that uses this instrument, you must specify the allowed users (and specify, for each allowed user, what record to use from the participant specific parameters). When you create a session, you can require all participants to enter a password -- which can be the same for everyone, or can be participant specific.

### General parameters for ... ()

Enter the number of general parameters to specify ... |

### Reference parameters for ... ()

Enter the number of reference records to specify ... |
Enter the number of reference parameters to specify ... |

### Use CSV for reference data

You can type, or cut and paste, CSV values into the text box
? Variable order: ID first, followed by comma-seperated values for the variables

- Each row (in the text box) is treated as a new record
- Values should be seperated with commas
- You can use quoted (") to include commas -- but the entire string must be quoted.
  Example:`1,2,"dog,cat",4` would yield 4 elements with `dog,cat` the third element).
- You must include the `reference id` as the first value in each row.
- You can specify a subset of the records. Non-specified records (records rows will not be modified).

### Allowed users for ... ()

Enter the number of allowed user records to specify ... |

### ? Modules for ... ()

- Click on the to remove a module
- You can edit a module by clicking on the Module name
- Or, you can add a module

Create a new module...

Status messages: