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

[Bug 7340] New: emailLibrarianWhenHoldIsPlaced enhancement
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7340 Bug #: 7340 Summary: emailLibrarianWhenHoldIsPlaced enhancement Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: spl(a)metrocast.net QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com This preference currently results in an email to the librarian whenever a hold is placed, even if the hold is placed by staff. I think it would be good to add a preference that excludes those holds, limiting emails to instances where holds are patron-initiated. -- 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 3

[Bug 7183] New: consistency of displays
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7183 Bug #: 7183 Summary: consistency of displays Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: paul.poulain(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 There is no consistency for most displays in Koha. Sometimes, patron information is displayed John, Doe +123 45 67 89, New York sometimes Doe, John, New York Adult Sometimes <b>John Doe</b> Adult, New York ... Template Toolkit can help us having a consistent display: we should define basic objects and how they are displayed is managed in a specific include, ensuring consistency. A first list of objects: * biblio * biblio+item (location, without availability, like what is displayed in item bulkmodification, cart,...) * biblio+item (location and availability like what is displayed in circulation/hold pages) * patron -- 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 1

[Bug 7782] New: Inconsistency in management of holds on checkout, patron detail, and holds pages
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7782 Priority: P5 - low Change sponsored?: --- Bug ID: 7782 CC: gmcharlt(a)gmail.com Assignee: oleonard(a)myacpl.org Summary: Inconsistency in management of holds on checkout, patron detail, and holds pages QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Circulation Product: Koha Created attachment 8438 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8438&action=edit Proposed interface for the checkout and patron detail pages' list of holds The lists of holds on a patron's checkout and detail pages are consistent with each other, but different from the list of holds displayed for a paticular title. I think there are some features of the title's holds list which could be added to the circ and patron detail page, and some possible improvements to all of them. The option of choosing "yes or no" is non-standard in Koha. It would be more consistent to offer the user a column of checkboxes for marking individual lines for deletion. To the checkout and patron detail pages' list of holds I would also add a single "delete" link corresponding to the "X" icon on the title's hold list page. The redirect will have to be modified to return the user to the appropriate page. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 5504] New: No pickup library if IndependentBranches
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5504 Summary: No pickup library if IndependentBranches Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests 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 If the libraries have chosen to be Independent Branches then there should be no reason to show the 'pickup library' option on the holds interface. This is also true if the library doesn't allow holds from other branches. -- 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 3

[Bug 7040] New: Public note should show when placing item level holds in staff
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7040 Bug #: 7040 Summary: Public note should show when placing item level holds in staff Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/reserve/request.pl?biblionumber=43 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 5911 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5911 screenshot When placing holds in staff the public note is not shown in the item table for placing item level holds. The public note should show there as it does in other places like check out/check in and detail pages. -- 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 3

[Bug 5800] New: Hold Policy "home library only" incompatible with CircControl "patron home library"
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '15

20 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5800 Bug #: 5800 Summary: Hold Policy "home library only" incompatible with CircControl "patron home library" Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com If a branch's Hold Policy for an item (or default) is configured to only allow holds for patrons belonging to that branch (value = 1), and the CircControl system preference is set to PatronHomeLibrary, the Holds Policy breaks. The holds policy from the patron's home library is used, which, unless it's set to deny ALL holds, will let them place a hold on any item at any library, regardless of that libraries Hold Policy. The root of the problem is using _GetCircControlBranch to generate the $branchcode used for determining the Hold Policy. Unfortunately, using $item->{homebranch} universally would not always work for libraries who want the item's current holding branch to set the policies. -- 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 7688] New: Change subscriptions numbering pattern and frequencies
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '15

17 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7688 Priority: P3 Change sponsored?: --- Bug ID: 7688 Assignee: julian.maurice(a)biblibre.com Summary: Change subscriptions numbering pattern and frequencies QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: julian.maurice(a)biblibre.com Hardware: All Status: ASSIGNED Version: master Component: Serials Product: Koha Created attachment 8110 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8110&action=edit 'New subscription' page This development made by BibLibre improve management of numbering patterns and frequencies for subscriptions. It add the possibility to create (and of course edit and delete) numbering patterns and frequencies in two new pages. When you create a new subscription (or edit an existing one) you can change easily the numbering pattern (and the frequency) with a drop-down list. It also change the way the prediction pattern is calculated. It's no more calculated client-side, but server-side, with a Perl script called by ajax. That way it is more consistent because the Perl script use the same functions Koha use to determine the next serial number. (see screenshot attached) -- You are receiving this mail because: You are watching all bug changes.

1 149

[Bug 5279] New: Add option to limit label item search by homebranch
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '15

16 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5279 Summary: Add option to limit label item search by homebranch Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 For larger libraries with many branches, it would be helpful to have the option to limit the item search by homebranch. -- 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 7012] New: limit to available not limiting anymore
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Bug #: 7012 Summary: limit to available not limiting anymore Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When I limit to only available items in the OPAC it doesn't appear to be limiting anymore. -- 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 6

[Bug 7041] New: Sort >1000 search results with sortmax parameter in zebra config file
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7041 Bug #: 7041 Summary: Sort >1000 search results with sortmax parameter in zebra config file Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: m.de.rooy(a)rijksmuseum.nl QAContact: koha-bugs(a)lists.koha-community.org By default, zebra does not sort more than 1000 records (search results). You can increase this number by adding the sortmax parameter in zebra-biblios.cfg. Putting this value in Koha's zebra config file will make this default value visible and make it easier to increase it if one prefers that. This patch therefore adds the default of 1000 to zebra-biblios.cfg. Does not change any Koha/Zebra behavior. If you want to test it, look for a search in your catalog with >1000 results. Look at the order of the records. Now apply the patch and copy the zebra-biblios.cfg to your zebra directory. Increase sortmax, reindex and search again. If you increased sortmax above the number of hits, you should see a difference in sort order now. -- 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 11