Petrus,
I'm certain this script won't handle incrementing fines daily. That
is handled by a cron job.
I also would like to see the fines incremented daily. I saw mention of
such a feature in the Koha 3 install I have here, but couldn't find the
corresponding cron job.
In my Koha 2.2 install I
Actually, this script only handles the rule creation part of it, not
the rule usage. However, I did have an idea (not yet implemented, but
I will soon) for fixing those as well.
The rules are documented as follows:
>* same branch and same borrower category, itemtype *
>* same branch and
Message: 1
Date: Tue, 19 Feb 2008 10:18:19 -0600
From: "Galen Charlton" <[EMAIL PROTECTED]>
Subject: Re: [Koha-devel] Issuing Rules
To: Jesse <[EMAIL PROTECTED]>
Cc: Koha Development Mailing List
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO
Hi,
On 2/18/08, Jesse <[EMAIL PROTECTED]> wrote:
> My little script (attached, along with a template for the default set)
> is actually a replacement for issuingrules.pl. Instead of having a
> massive table with two cells for every combination of itemtype and
> category code, there is now just one
On Feb 18, 2008 8:29 AM, C W Nel <[EMAIL PROTECTED]> wrote:
>
>
> Thanks Jesse
>
> Did you perhaps fix the chargeperiod problem? If you enter 1,7,7 the last 7
> disappears and is not written into the issuingrules table. (Ver2.2.9)
My little script (attached, along with a template for the default s
Thanks Jesse
Did you perhaps fix the chargeperiod problem? If you enter 1,7,7 the last 7
disappears and is not written into the issuingrules table. (Ver2.2.9)___
Koha-devel mailing list
Koha-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/koha
I have been doing a lot of work recently on issuing rules in Koha; I
have made a new, much nicer issuing rules screen am working on making
issuingrules fallback better. I have working production code if anyone
is interested, and templates for the default and NPL template sets.
--
Jesse
C.W. --
Please report what version of Koha you are using.
--joe atzberger
On Jan 24, 2008 11:13 AM, C W Nel <[EMAIL PROTECTED]> wrote:
> I have noticed that the chargeperiod is not written into the
> issuingrules table.
>
> I first thought that it just is not displayed correctly, but it
> seem
I have noticed that the chargeperiod is not written into the
issuingrules table.
I first thought that it just is not displayed correctly, but it
seems to be ignored in issuingrules.pl.
I had to force it in with sql.
Is this a known issue?
___
Koha-dev
Cindy Murdock a écrit :
Hi Paul,
While you're revisiting the issuing rules, you might want to consider
moving renewalsallowed and possibly rentalcharge from itemtypes to
issuingrules. It would allow for more flexibility in large library
systems. Or maybe a syspref to control whether these f
Ryan Higgins a écrit :
one more request:
change default branch to '*', so that all 'defaults' are handled the same way.
this makes local modifs to the circ subs much easier to manage.
for those currently running '2.9x', a simple
UPDATE issuingrules set branchcode='*' where branchcode=''; shoul
one more request:
change default branch to '*', so that all 'defaults' are handled the same way.
this makes local modifs to the circ subs much easier to manage.
for those currently running '2.9x', a simple
UPDATE issuingrules set branchcode='*' where branchcode=''; should suffice.
I have a sys
Hi Paul,
While you're revisiting the issuing rules, you might want to consider
moving renewalsallowed and possibly rentalcharge from itemtypes to
issuingrules. It would allow for more flexibility in large library
systems. Or maybe a syspref to control whether these fields are defined
in ite
Thanks Joshua,
in the following days I'll try to connect to the GIT repository and
upload our code so anyone can use it.
Best regards,
--
Ernesto Silva.
Coordinador de Desarrollo Web y Sistemas Abiertos
Centro de Procesamiento de Datos
Universidad ORT Uruguay.
E-mail: [EMAIL PROTECTED]
Tel:
Hi Ernesto,
Thanks for giving us some indication about your preferences for
issuing rules, and also the information about what you've developed
inhouse. Now that the official Koha project runs Git, it will be much
easier for your team to contribute select features, and also manage
a local repo tha
Hi,
I've read the message and I do agree. I just want to mention some of
our own developments.
We have 2 types of items in case of biblios representing books. We have
"room" and "common" items; "common" items use the standard issuing rules
but "room" items cannot be on loan during working
I would like to place what little influence I have in favor of this
idea. I am one of those who had trouble with the way issuing rules
workes in 2.2. I have gone as far as implementing something very
similar to this already in my install.
I will add that, as I recall, there are two places in the
Hello world,
We are reviewing Koha for 3.0 Release & Joshua pointed something
important: the way issuingrules worked in koha 2.2.
In Koha 2.2, the way it works is :
- you define the rules depending on itemtype / patron category / branch
- you have "wildcard" that means "all of them". For examp
18 matches
Mail list logo
