>
> > What do people think about allowing a item-type level 'not-for-hold'
> > checkbox,
> > and a item-type level hold-fee (that overrides the patron-type level
> > hold-fee)
> >
> >
> The development version of Koha allows hold policies to be set up
> by branch and itemtype (and soon, patron ty
2009/5/25 Eric Bégin
> Hi Mason,
>
> I think this is a good idea and must be implemented.
>
> I would make that part of the circulation & fines rules. This would
> allow us to set it per item types and per patron categories.
>
> I know Nahuel is working on something similar at the moment. He is
Hi Mason,
I think this is a good idea and must be implemented.
I would make that part of the circulation & fines rules. This would
allow us to set it per item types and per patron categories.
I know Nahuel is working on something similar at the moment. He is
adding the number of renewals to
Bonjour peoples
I am about to do some development work to add item-type level hold-
fees, and item-type level 'not-for-hold' restrictions in koha3
the reasons?
1) Currently in koha3, an item's reserve-fee (aka hold-fee) is set
per patron-type - not per item-type,
which is not ideal for li
Hi All,
I'm wondering if anyone ever wanted events in Koha? Events may be like
onpatronremove, onbibliosave, onbiblionew etc... For example if one
wants to check spelling and marc-correctness of the record before it is
saved to the database one could put either 'default' or home-made perl
scri
Le Thu, 21 May 2009 11:05:33 +0100,
MJ Ray a écrit :
> Nahuel ANGELINETTI wrote:
> > MJ Ray a écrit :
> > > Why shouldn't we revalidate the rights at the user checkout event?
> >
> > The problem is, if the user have a reserve on a biblio record(not a
> > specific item), we don't know how to cou
