Overview
EvalCGI is part of EvalSuite, an integrated package of evaluation and assessment software. EvalCGI is concerned with data collection and managing the submission process. Other components complete the feedback loop as shown in the illustration on the right (EvalToolkit for data management and EvalFolio for results reporting). Together these programs create an easy to use, efficient environment for collection of evaluation data, analysis, and reporting.
Please be aware that EvalCGI is a large program with many features. This documentation only covers the basics. For more information contact Richard Rathe at rrathe@ufl.edu.
Basic Terminology
There are two general form types: evaluations and exams (aka assessments). Evaluations involve response scales that do not have an expected correct answer. For example:
Contrast this with the classic multiple-choice question, which typically has one correct or preferred answer. Exams are collections of scored items that yield a numerical record of performance.
There are three types of users: takers, subjects, and admins. Takers are those allowed to submit a form. A proxy is a taker who submits data on behalf of another.
Forms may concern a single theme, or multiple subjects may be evaluated with a single generic form.
Admins have ownership of a collection of forms contained within a directory. A small number of admins may have superuser status for the entire installation.
| Term | Definition |
| evaluation | A form primarily focused on scaled input (ie, no correct answers). |
| exam | A form primarily focused on scored input (ie, a multiple choice quiz). |
| taker | Someone who submits a form. |
| subject | Someone (or thing) that is the focus of an evaluation. |
| admin | An administrator for a group of forms. |
| superuser | An administrator for the entire system. |
| proxy | A taker who submits a form on behalf of a subject (ie, taker and subject are flipped). |
| access spec | A simple formula that defines takers and subjects for a form. |
Files and Directories
The basic building blocks are files and directories. Files are generally plain (ASCII) text. Related files are grouped together in directories. (It is important to note that administrative access is granted at the directory level.) Form layout is represented by a simple markup language called ETX (short for evaluation text). These file names end in the '.etx' extension. The 'off' suffix indicates an inactive form.
There are several additional files created by the system as users submit data. Evaluation data files end in '.evl'. Exam data files end in '.exm'. The suffix 'pub' suffix indicates a data file that has been made available (published) via EvalPub. Free text data (comment) files end in '.cmt'. The system keeps track of who has submitted data in reference files ending in '.ref'. Finally, the system creates lock files (.lok) to ensure data integrity. These files may be deleted if desirable to help cut down on clutter.
Access control list files (.acl) define takers, subjects, and admins. These files are merely lists of unique identifiers for users and other entities within the system.
| Type | Definition |
| .etx | Evaluation TeXt files define evaluation forms. |
| .evl | Evaluation (scaled) data file. |
| .exm | Exam (scored) data file. |
| .cmt | Comment (free text) data file. |
| .ref | Reference file to keep track of submissions. |
| .lok | File locking semaphore file. |
| .acl | Access Control List file. |
| .dir | Directory configuration file. |
| .bak | A backup file. |
| .html | Standard HTML file. |