koha-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-bugs] [Bug 748] New: Modfy loan length according to borrower categ


From: bugzilla-daemon
Subject: [Koha-bugs] [Bug 748] New: Modfy loan length according to borrower category
Date: 15 Mar 2004 18:28:40 -0000

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=748

           Summary: Modfy loan length according to borrower category
           Product: Koha
           Version: CVS
          Platform: PC
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Circulation
        AssignedTo: address@hidden
        ReportedBy: address@hidden
         QAContact: address@hidden


It would be nice to control loan length based on the category of borrower, as
well as the type of item.  That way, staff or teachers could keep items longer
than 'regular' borrowers.

One way to do this might be to add a "loanlengthfactor" column to either the
borrowers table or the categories table.  If staff could keep items twice as
long as other borrowers, then the loan length factor would be '2'.  If a loan
was meant to be (almost) permanent, the loan length factor could be '99'.  If
the normal loan period was two weeks, but children's librarians can keep things
three weeks, then the factor would be '1.5', etc.  While the sticky due date
already makes such things possible, it would still be nice to have this
automatically calculated by borrower category.

Circ2.pm would need to retrieve the loan length factor from the appropriate
table.  Then in the issuebook function in Circ2.pm, insert a line (after current
line 771) that recalculates the loan length based on the loan length factor --
like $loanlength=$loanlength*($patroninformation->{'loanlengthfactor'}).

I notice also that there is some hard-coding of borrower categories in Circ2.pm
(starting at line 614).  Perhaps my simple suggestion could be made more complex
to handle this as well.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]