November 2014 - Koha-bugs - lists.koha-community.org

[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 12461] New: Add patron clubs feature
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12461 Bug ID: 12461 Summary: Add patron clubs feature Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This features would add the ability to create clubs which patrons may be enrolled in. It would be particularly useful for tracking summer reading programs, book clubs and other such clubs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 8483] New: Borrower reading history should include deleted items
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8483 Priority: P5 - low Change sponsored?: --- Bug ID: 8483 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Borrower reading history should include deleted items Severity: enhancement Classification: Unclassified OS: All Reporter: robin(a)catalyst.net.nz Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha When showing a borrower's reading history, it'd be good to be able to include the deleted items also, as we have that information available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 9004] New: Talking Tech doesn't account for holidays when calculating a holds last pickup date.
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9004 Priority: P5 - low Change sponsored?: --- Bug ID: 9004 Assignee: koha-bugs(a)lists.koha-community.org Summary: Talking Tech doesn't account for holidays when calculating a holds last pickup date. Severity: enhancement Classification: Unclassified OS: All Reporter: kyle(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Notices Product: Koha The Talking Tech outbound script adds the ReservesMaxPickUpDelay to the waitingdate of a reserve to calculate its last pickup day. However, this day may fall on a holiday. In this case, the last day to pick the item up should be pushed to the next open day. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 12633] New: SQLHelper replacement - C4::Members
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12633 Bug ID: 12633 Summary: SQLHelper replacement - C4::Members Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: yohann.dufour(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The module C4::Members depends on module C4::SQLHelper. However, the module SQLHelper is obsolete, so the calls for InsertInTable, UpdateInTable and SearchInTable have to be replaced by the use of the module DBIx::Class. -- You are receiving this mail because: You are watching all bug changes.

1 65

[Bug 10163] New: batch-mod items tool fails on files over 1000 lines long
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10163 Bug ID: 10163 Summary: batch-mod items tool fails on files over 1000 lines long Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com CC: m.de.rooy(a)rijksmuseum.nl if you attempt to upload a file with more than 1000 lines, you get an error... ---------------------------------------- Batch item modification - Too many items (1001): not displaying each one individually. Return to batch item modification ---------------------------------------- looking that the code its obvious that the intended behavior is to not display the items, yet still allow the items to be edited this functionality seems broken -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 11343] New: The max number of items to process in a batch is hardcoded
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11343 Bug ID: 11343 Summary: The max number of items to process in a batch is hardcoded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The maximum number of item records to process in a batch is 1000. This value is hardcoded in the code. It should be store in a syspref. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 11490] New: Deleting Batch Items
by bugzilla-daemon＠bugs.koha-community.org 18 Dec '15

18 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11490 Bug ID: 11490 Summary: Deleting Batch Items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org This discovery is made based off an enhancement being worked on in bug 11343. It has been discovered that when patch 11343 is in place, if I set the new syspref MaxItemsForBatch to 2, and then try to do a batch delete of 3 items, it won't show the 3 items because of the limit, but it will still allow me to delete beyond the limit. I have concern that even without this patch, staff can delete beyond the hard coded 1000 item limit. Can anyone confirm this issue? Christopher -- You are receiving this mail because: You are watching all bug changes.

1 7

[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