January 2012 - Koha-bugs - lists.koha-community.org

[Bug 6896] New: searching an acq date finds due date instead
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6896 Bug #: 6896 Summary: searching an acq date finds due date instead Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org In searching for 09-05-2011 acquisition date, I get items due on 09-05-2011. It looks like somehow the date due is getting dumped into the acqdate search index. What these search results appear to be saying is that my system doesn't have any items that are shown as acquired on 2011-09-05. The results should be empty, but the checked out items are showing instead. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 7025] New: C4::Items depends on C4::Reserves (which in turn depends on C4::Items...)
by bugzilla-daemon＠bugs.koha-community.org 11 Jul '14

11 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7025 Bug #: 7025 Summary: C4::Items depends on C4::Reserves (which in turn depends on C4::Items...) Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org C4::Items uses a single subroutine from C4::Reserves, CheckReserves(), in a single on of it's subroutines, GetItemsInfo(). The only data exported is in the field "count_reserves" which gives the reserve status. This in turn is only used in opac/opac-detail.pl to display "on hold" in the holdings table if the item is currently waiting on the holds shelf to be picked up. There are no other uses of this information. We can remove CheckReserves() from GetItemsInfo(), and add a different call in opac/opac-details.pl to get whether the particular item is on hold or not. This will remove a circular dependency, likely speeding up the overall code (as we won't need to load all of C4::Reserves every time we load C4::Items). -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 5757] New: Checking in a waiting item again does not trigger hold prompt.
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5757 Summary: Checking in a waiting item again does not trigger hold prompt. Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 If an item has already been made "waiting" (reserves.found = 'F'), checking in that item again will not trigger the hold prompt. It should trigger the prompt headed "Hold Found (item is already waiting)." -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 1

[Bug 5552] New: circ dates in the past
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5552 Summary: circ dates in the past Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/circ/circulation.pl OS/Version: All Status: NEW Severity: major Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Created attachment 2918 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2918 error box with due date When you choose a due date in the past a box appears asking you to confirm the date. This box should have a calendar icon and a date format tip like all other date boxes in Koha to prevent big mistakes. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 4

[Bug 5847] New: Manage Staged MARC Records stuck at 0% if isbn matching rule selected.
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5847 Bug #: 5847 Summary: Manage Staged MARC Records stuck at 0% if isbn matching rule selected. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P1 Component: MARC Bibliographic record staging/import AssignedTo: gmcharlt(a)gmail.com ReportedBy: kmkale(a)anantcorp.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com If we try to use ISBN match rule while importing a staged batch, the Manage Staged MARC Records gets stuck at 0%. I can see a www-data owned background job running but the browser is stuck at 0% and no entries in the db. Tried leaving it overnight with no progress. Tried with firefox and chrome. Same MARC file is imported fine without using the ISBN match rule. The same marc records file imports fine with bulkmarcimport.pl utility even with the -isbn option. Sadly the bulkmarcimport.pl lacks the option to still add items even while ignoring a biblio if a isbn match is found. See attached screenshot for rules used during this import. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 4

[Bug 7441] New: search results showing wrong branch?
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '14

03 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7441 Bug #: 7441 Summary: search results showing wrong branch? Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com When you search in the OPAC it shows you the HOME branch on the location in XSLT (see here: http://screencast.com/t/m870Mr8Wm) but if you click through to the detail page it shows you the CURRENT BRANCH in the holdings table which is very confusing to patrons. I don't know what's the right solution - home or holding branch, but they should be the same in both places for the patron's sake. If you do the same search in the staff client you see the right branch info on the search results and on the detail page. Nicole -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 83

[Bug 7058] New: GetMemberDetails must die!
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7058 Bug #: 7058 Summary: GetMemberDetails must die! Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org The GetMemberDetails subroutine is insanely inefficient, and is used throughout Koha's code. In many cases, GetMember is more than sufficient (please see my rant on bug 5179). This report shall serve as the meta-report for all attempts to eliminate unnecessary calls get GetMemberDetails. Please file separate bug reports for specific instances, and list them as "blocking" this report. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 5

[Bug 5179] New: GetMember and GetMemberDetails should be combined
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '14

25 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5179 Summary: GetMember and GetMemberDetails should be combined Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In Members.pm, GetMember and GetMemberDetails do almost the same thing. This common behaviour should be combined so that changes to this kind of thing don't have to happen in multiple places. Aiming for 3.4. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 2

[Bug 6617] New: table of contents not printing right if entered right
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '14

22 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6617 Bug #: 6617 Summary: table of contents not printing right if entered right Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4682 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4682 table of contents in 505$a If you're entering the table of contents in a series of $t and $r subfields (in the 505) then it doesn't print the table of contents to the OPAC or staff client right. A formatted table of contents looks like this (505$a): What is a mashup? / Darlene Fichter -- Behind the scenes : some technical details on mashups / Bonaria Biancu -- Making your data available to be mashed up / Ross Singer -- Mashing up with librarian knowledge / Thomas Brevik A slash after the title and before the author and a double dash in between the chapters. See the screenshots to see what I mean. The / should probably be entered by the cataloger, but the double dash should be entered by the template and the contents should show with XSLT turned on even if it's not in the $a only. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 48

[Bug 6918] New: can't place holds on 'on order' items with AllowOnShelfHolds off
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '14

19 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6918 Bug #: 6918 Summary: can't place holds on 'on order' items with AllowOnShelfHolds off Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com I don't think this was always the case (but I might be wrong). If AllowOnShelfHolds is set to 'don't allow' then patrons cannot place holds on items that are marked 'on order' (not for loan=-1). Technically items on order are not on the shelf and should be allowed to be placed on hold. This may require a preference for people to say whether they want to allow holds on 'on order' items and/or what the not for loan value is for 'on order' since there is nothing stopping the user from changing the value from -1 to something else. The easy fix is just to make the system allow holds on items with -1 for notforloan like I think it was before. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 29