Re: pykota Digest, Vol 63, Issue 7

If you require a user to authenticate against a directory in order to  
view their print history, then you may be interested in PrintAgent : http://www.lucidsystems.org/printingworks/printagaent

> >
> >  I'm in the process of migrating our windows based printing  
> account system
> > to pykota. On the present system, each user can access his  
> printing reports,
> > and check how his balance was debited for his printings, or how it  
> was
> > increased by his deposits. You can find an example on the image in
> > attachment. Notice that for each printing the resulting balance is  
> shown,
> > which allows the user to easily understand why they deposited 100,  
> and the
> > balance was increased to 95 only.
>
> Actually the "printquota.cgi" CGI script can provide part of these
> informations. If you want more you can either use the dumpykota  
> command
> line tool or the dumpykota.cgi CGI script (this one is currently  
> broken
> in the latest development tree), but of course you won't be able
> to display data which is not already present in the database (see  
> below)
>
> >  Looking at the pykota database, it seems that there is no  
> information on
> > the resulting balance, at the time the job was printed. Is this  
> correct, or
> > am I missing something?
>
> You're right.
>
> >  I suppose I could do the math and trace back the balance, but I  
> would have
> > more confidence that no one has fiddled with the database, if the  
> balance
> > were to be recorded on each transaction.
> >
> >  Would it be possible to record this information?
>
> Yes. This feature is planned for the next stable release.
> (and if you are wondering, I hope it will be out by the end of the  
> year)
>
> bye
>
> Jerome Alet
>