April 2008 - Koha-bugs - lists.koha-community.org

[Bug 1742] Items on Issue show in Pending Holds report
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1742 galen.charlton(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #6 from galen.charlton(a)liblime.com 2008-04-08 11:57 ------- Darrell's patch resolves this bug, so I'm closing. Russel, if you disagree, please feel free to reopen with a new test case. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2004] statistics wizards don't work with item-level itypes
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2004 galen.charlton(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from galen.charlton(a)liblime.com 2008-04-08 11:45 ------- I have prepared a patch and sent it to you separately to review - please advise ASAP if it does the trick. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1828] Edit Details link for expired member in circulation.pl incorrect
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1828 oleonard(a)myacpl.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Priority|P5 |PATCH-Sent Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2004] New: statistics wizards don't work with item-level itypes
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2004 Summary: statistics wizards don't work with item-level itypes Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: blocker Priority: P3 Component: Reports AssignedTo: galen.charlton(a)liblime.com ReportedBy: rch(a)liblime.com QAContact: koha-bugs(a)lists.koha.org The statistics wizards do not work with item-level itypes. Also, they need to be able to limit on other item fields, most notably location and ccode. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2003] New: Circulation page offers no information on why checkouts are blocked
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2003 Summary: Circulation page offers no information on why checkouts are blocked Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: Circulation AssignedTo: chris(a)bigballofwax.co.nz ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha.org The circulation screen needs to offer more detailed information about why a patron is blocked from checking out. For instance: if a patron has more outstanding fines than the noissuescharge system pref allows, that patron will be blocked from checking out. But the warning on the circ screen is the same as before their outstanding fines exceeded the limit: "Fines: Patron has Outstanding fines." The page might also give a similar message about overdues, "Overdues: Patron has ITEMS OVERDUE," with the same weight as the fines warning. The template needs to be able to determine which warning message relates to the reason for the block on the patron's account and offer relevant information: "Outstanding fines exceed <noissuescharge>. Checkouts blocked." ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2002] OPAC holds listing doesn't show in-transit status
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2002 ------- Comment #2 from oleonard(a)myacpl.org 2008-04-08 06:29 ------- Created an attachment (id=227) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=227&action=view) Screenshot of opac-user.pl, lacking in-transit status for "Odd one out" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2002] OPAC holds listing doesn't show in-transit status
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2002 ------- Comment #1 from oleonard(a)myacpl.org 2008-04-08 06:28 ------- Created an attachment (id=226) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=226&action=view) Screenshot of circulation.pl, correctly showing the in-transit status ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2002] New: OPAC holds listing doesn't show in-transit status
by bugzilla-daemon＠pippin.metavore.com 08 Apr '08

08 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2002 Summary: OPAC holds listing doesn't show in-transit status Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: critical Priority: P3 Component: OPAC AssignedTo: jmf(a)liblime.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha.org opac-user.pl does not correctly show the in-transit status of an item. In comparison, circulation.pl shows this status correctly. Starting at line 314 of opac-user.tmpl:    Item waiting at <b> </b> <input type="hidden" name="pickup" value="" />  Item waiting to be pulled from <b> </b>   Item in transit to <b> </b> <input type="hidden" name="pickup" value="" />   Item waiting to be pulled  ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2001] New: unAPI doesn't work without public-facing zebra server running on port 9998
by bugzilla-daemon＠pippin.metavore.com 07 Apr '08

07 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2001 Summary: unAPI doesn't work without public-facing zebra server running on port 9998 Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: OPAC AssignedTo: jmf(a)liblime.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha.org unAPI doesn't work without public-facing zebra server running on port 9998: [15:29] <kados> my $url = "http://$baseurl:9998/biblios?version=1.1&operation=searchRetrieve&query=$id&startRecord=1&maximumRecords=20&recordSchema=$format"; [15:29] <kados> it assumes a public-facing zebra server running on port 9998 [15:31] <kados> with minor modifs I could get it working with both public-facing and socket servers ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2000] New: separation of issuing & fines rules breaks defaults propagation
by bugzilla-daemon＠pippin.metavore.com 07 Apr '08

07 Apr '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2000 Summary: separation of issuing & fines rules breaks defaults propagation Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: blocker Priority: P3 Component: Circulation AssignedTo: chris(a)bigballofwax.co.nz ReportedBy: rch(a)liblime.com QAContact: koha-bugs(a)lists.koha.org I've submitted a patch for Circulation.pm that reproduces GetLoanLength's issuingrule determination in a new fcn: GetIssuingRule(). This is intended to replace Overdues.pm's GetIssuingRules(), which ignores both defaults and branches. However, this reveals a bug: By separating the interfaces for Issuing and Fines, the following condition arises: (1) set any branch, any borrower category, and just default fines for itemypes. (2) set Issuing rule for specific branch, specific categorycode. This creates an entry with null fine that overrides the intended default behavior for the fines interface. >From the state of current code, I don't imagine that any currently live/testing 3.0 installs are actually using the Fines Rules interface outside of Sanop , so I suggest a simple fix: If fines are used, require that smart-rules.pl is the issuingrules interface. Else, allow use of issuingrules.pl. and, remove finesrules.pl Thoughts ? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0