|
 |
 |
Test Pilot |  |
||||||||
|
Test Pilot Enterprise Manual |
||||||||||||
Test Pilot assessments and assessment indices may be secured from general access with a list of authorized participants. This means that unless the participant is using an authorized id, they would be prevented from accessing the assessment or assessment index. Assessments may have a private list. Assessment indices may contain shared lists which one or more assessments may share. Finally, Test Pilot administrators may define public participant lists which may be used in any assessment or assessment index in the Test Pilot network. This allows the administrator to maintain, if desired, a set of centralized participant lists usable by any author.
Public user lists are created and maintained by the Test Pilot administrator and usable by any author in the Test Pilot network. New Public User List To create a new public user list, simply enter a name for the list in the space provided and click the Create button. Deleting Public User Lists To delete a public user list, check the enable deletion checkbox and click the appropriate Delete button. Any consumers of the deleted list will have new empty (open access) lists assigned to them. Editing Public User Lists The public user list is edited as any user list. Controls to rename or export the list are initially displayed:
To export a tab-delimited copy of the list, simply click the Export button. To rename the list, enter the new name in the space provided and click the Rename button. Next, a list of users is presented. The list is sorted by name or id as determined by the Name/ID popup menu:
Following the list of users is an editing area where you may make new entries or change or delete existing entries. Clicking on any existing entry in the list will cause the information about that entry to be presented in the editing area. Depending upon your server authentication architecture a password editing box may or may not be displayed. Consider the following sample editing area resulting from clicking on the name Kennedy above.
When changing an existing entry, the password is never shown and will remain unchanged unless a new entry is made in the empty password box. As for the remaining fields, you may simply make changes and then click the Update Entry button to record the changes. The ID field may not be changed. If you have an incorrect ID, delete the entry and create a new one. To create a new entry, click the New Entry button, fill in the appropriate fields and click Update Entry. There is no limit to the size of a user list. Entries are displayed 100 at a time. To delete an entry, click on the id in the user list to have the entry displayed in the editing area. Then, check the enable deletion checkbox and finally click the Delete Entry button. You may also import a list of participants from either a file stored on the Test Pilot server or from a list pasted into a space provided.
Test Pilot assumes a tab or comma delimited ASCII file of users listed one per line such as what might be created by ALL common database, spreadsheet, word processor or text editing programs. You will need to tell Test Pilot the order of the fields in your data by entering numbers as appropriate in the spaces provided. If the information is in a server file in the format recognized by version 3 of Test Pilot, simply click the v3 format checkbox. Import from a Field - If you paste the user information into the field provided, be sure to click the button to indicate that you are importing from a field. Import from a File - If you are importing from a file, be sure to click the button to indicate that you are importing from a file. For security purposes, Test Pilot imports from files located in the web server's current directory as defined by the URL used to access the index management options. If you used http://SERVER/servlet/TestPilot4/tests/joe/mytest.tp4?manage then Test Pilot uses the joe subdirectory of the tests subdirectory of the web server's document root directory. Enter the name of the ASCII file in the selected directory which contains the user information and click the Import button. The files MUST have an extension of .txt or .tpj. Be sure to remove the file after importing to avoid any privacy or security issues. About the Fields Each user should be assigned a unique id and a password which will be associated with their name and e-mail entries. The fields are defined as follows: id - this is an arbitrary string of one or more characters; spaces, commas, tabs or nonprinting characters are not allowed. It is this id which must be entered in security challenges when they appear. password - this is an arbitrary string of one or more characters; spaces, commas, tabs or nonprinting characters are not allowed. It is this password which must be entered in security challenges when they appear. Depending on your server architecture, the password may or may not be presented for editing. name - this is an arbitrary string of one or more characters; spaces, commas, tabs or nonprinting characters are not allowed. This name will be associated with the id and listed on reports and links where appropriate. e-mail - this should be a valid internet e-mail address including an account id, an @ sign and a domain name which together form an e-mail address for the participant. It is to this e-mail address that notifications and other messages automatically generated by the Test Pilot program may be sent. |
|
||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
