| 16 Jul 10:40

user reports

Hello,

 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.

 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?

 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?

Best regards,
Elio Coutinho
Hello,

 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
(Continue reading)

Jerome Alet | 16 Jul 10:58
Gravatar

Re: user reports

On Wed, Jul 16, 2008 at 09:44:30AM +0100, Élio Coutinho wrote:
> 
>  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)
(Continue reading)

| 16 Jul 11:54

Re: user reports

OK, thanks! I'm looking forward to get that release.

Elio
| 16 Jul 13:48

Re: user reports

I've just realized that I can use posthook, and the information on these
variables

PYKOTAJOBSIZE
PYKOTAPRICEPERPAGE
PYKOTABALANCE
PYKOTATITLE
PYKOTAPRINTERHOSTNAME

to feed my own user report table. Thank you for such a versatile product!

Elio
Jerome Alet | 16 Jul 13:53
Gravatar

Re: user reports

On Wed, Jul 16, 2008 at 12:48:43PM +0100, Élio Coutinho wrote:
> I've just realized that I can use posthook, and the information on these
> variables
> 
> PYKOTAJOBSIZE
> PYKOTAPRICEPERPAGE
> PYKOTABALANCE
> PYKOTATITLE
> PYKOTAPRINTERHOSTNAME
> 
> to feed my own user report table. Thank you for such a versatile product!

I knew this would be useful some day ;-)

bye

Jerome Alet


Gmane