| | 29 | Until Bossa has good web-based administration tools, |
| | 30 | you'll need to examine and modify the MySQL database directly, |
| | 31 | using the command-line tool 'mysql', |
| | 32 | or a web-based interface such as [http://www.phpmyadmin.net/ phpMyAdmin]. |
| | 33 | |
| | 34 | The Bossa tables are as follows: |
| | 35 | |
| | 36 | bossa_app: |
| | 37 | || field name || type || meaning || |
| | 38 | || id || integer || row ID, assigned by MySQL || |
| | 39 | || create_time || integer || row creation time || |
| | 40 | || name || varchar(255) || short name (internal use; no spaces) || |
| | 41 | || user_friendly_name || varchar(255) || user-visible name (spaces OK) || |
| | 42 | || long_jobs || tinyint || nonzero if user can have > 1 active job || |
| | 43 | || start_url || varchar(255) || name (relative to project URL) of start script || |
| | 44 | || deprecated || tinyint || nonzero if deprecated (don't show) || |
| | 45 | || info || text || information (typically encoded in JSON) such as the criteria for which users to issue jobs to || |
| | 46 | |
| | 47 | bossa_job: |
| | 48 | || field name || type || meaning || |
| | 49 | || id || integer || row ID, assigned by MySQL || |
| | 50 | || create_time || integer || row creation time || |
| | 51 | || name || varchar(255) || a unique name for this job || |
| | 52 | || app_id || integer || ID of bossa_app || |
| | 53 | || info || text || job-specific info (file names etc.) typically JSON-encoded || |
| | 54 | || batch || integer || batch number (use to group jobs) || |
| | 55 | || time_estimate || integer || number of seconds this job is likely to take || |
| | 56 | || time_limit || integer || give up if not completed after this number of seconds || |
| | 57 | || more_needed || tinyint || nonzero if more completed instances of this job are needed || |
| | 58 | || npending || integer || number of pending instances || |
| | 59 | || nsuccess || integer || number of successfully completed instances || |
| | 60 | || nsuccess_needed || integer || required number of successfully completed instances || |
| | 61 | |
| | 62 | bossa_job_inst: |
| | 63 | || field name || type || meaning || |
| | 64 | || id || integer || row ID, assigned by MySQL || |
| | 65 | || create_time || integer || row creation time || |
| | 66 | || job_id || integer || ID of bossa_job || |
| | 67 | || user_id || integer || ID of user || |
| | 68 | || finish_time || integer || time when finished, or zero || |
| | 69 | || info || text || outcome info (usually JSON-encoded) || |
| | 70 | |
| | 71 | bossa_app_user: |
| | 72 | || app_id || integer || ID of bossa_app || |
| | 73 | || user_id || integer || ID of user || |
| | 74 | || info || text || description of the user's skill or ranking at a given app, typically JSON-encoded || |
| | 75 | |