Changeset 2317 for pykota/trunk/TODO

Timestamp:

06/15/05 22:46:47 (19 years ago)

Author:

jerome

Message:

Big database changes.
Severity : From now on, existing datas have to be migrated
using the appropriate script if needed. LDAP users will need
to use the new schema. Beginning tomorrow, the code will be in
experimental quality instead of stable quality.

Files:

• pykota/trunk/TODO (modified) (3 diffs)

pykota/trunk/TODO

@@ -48 +48 @@
                 these values, and PyKota processes the job as usual.
           
-        - Add a table listing all the allowed billing codes. Unknown
-          billing codes should produce an action which is configurable
-          (reject the job being the default). The billing codes table
-          will contains total pages and cost, and life time pages
-          and cost => speedup for LDAP, and allows people to cleanup
-          the printing history in any case. A tool to manage the
-          table of billing codes must be written, but this will
-          be easy.
-          
-        - Pass-through mode for printers : history correctly filled (including
-          job size) but no impact on user's page counter or account
-          balance : this is meant to be a temporary situation for
-          a printer to be in pass-through mode, for example during
-          an exam where the faculty pays for the printouts and we
-          don't want our users to complain about their credits being
-          "eaten" for mandatory printouts.
-          
         - Allow several levels of administrative priviledges by allowing
           files like ~pykota/pykotadmin.someusername.conf (readonly by
@@ -71 +54 @@
           in PyKota's database !
         
-        - Add a "printing denied" indicator on user print quota entries,  
-          to temporarily forbid an user to print on a particular printer.
-          
-        - Maybe per user "denyduplicates" : my 5 years old daughter 
-          just prints again when the printer is off...
-          Maybe not needed anymore since denyduplicates now allows
-          an external command to decide if the job should be allowed
-          or denied.
-          
-        - Now that the job size is ALWAYS precomputed, add a 
-          MaxJobSize attribute to users and groups (printers as
-          well, maybe ?) to limit each job's size if needed.
-          
-        - Add precomputed job size (and price) to the history for
-          controlling purpose.
-          
         - Try to talk to education based distribution coordinators
           (SambaEdu, SkoleLinux, K12LTSP, ...) to see how to
@@ -100 +67 @@
         
         - Price and statistics per page format.
-        
-        - Add a description field to users/groups.
         
         - Allow the admin to choose an action to take when the database