| 33 | | - Add a table listing all the allowed billing codes. Unknown |
| 34 | | billing codes should produce an action which is configurable |
| 35 | | (reject the job being the default). The billing codes table |
| 36 | | will contains total pages and cost, and life time pages |
| 37 | | and cost => speedup for LDAP, and allows people to cleanup |
| 38 | | the printing history in any case. A tool to manage the |
| 39 | | table of billing codes must be written, but this will |
| 40 | | be easy. |
| | 33 | |
| | 34 | - Add a new external hook to allow the overwriting of the job's ticket |
| | 35 | (mainly username and billing code) at startup time : |
| | 36 | |
| | 37 | 1 - hook is launched and can do whatever it wants, like asking |
| | 38 | the user for username+password or billing code |
| | 39 | |
| | 40 | 2 - hook prints any (or all) of : |
| | 41 | |
| | 42 | USER:some_username |
| | 43 | BILLING:some_billingcode |
| | 44 | DENY |
| | 45 | |
| | 46 | if hook doesn't print anything, job processed as usual. |
| | 47 | if DENY, job is rejected. |
| | 48 | |
| | 49 | 3 - if billing code or username is invalid, and if PyKota |
| | 50 | is configured to loop in this case, hook is launched |
| | 51 | again, otherwise job is rejected. |
| | 52 | |
| | 53 | 4 - if billing code and/or username is valid, the job's |
| | 54 | billing code and/or username are overwritten with |
| | 55 | these values, and PyKota processes the job as usual. |
| | 56 | |
| | 57 | - Add a table listing all the allowed billing codes. Unknown |
| | 58 | billing codes should produce an action which is configurable |
| | 59 | (reject the job being the default). The billing codes table |
| | 60 | will contains total pages and cost, and life time pages |
| | 61 | and cost => speedup for LDAP, and allows people to cleanup |
| | 62 | the printing history in any case. A tool to manage the |
| | 63 | table of billing codes must be written, but this will |
| | 64 | be easy. |
