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

[Bug 8436] New: Add branch limit on checkexpiration.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8436 Priority: P5 - low Change sponsored?: --- Bug ID: 8436 CC: colin.campbell(a)ptfs-europe.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Add branch limit on checkexpiration.pl Severity: enhancement Classification: Unclassified OS: All Reporter: claire.hernandez(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Serials Product: Koha This limit is available only if user is superlibrarian or has the permission 'superserials'. Otherwise, only subscriptions that are linked to the working branch are shown. (BibLibre stetienne/ft/MT6725) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 11678] New: Gather print notices: send files by email
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11678 Bug ID: 11678 Summary: Gather print notices: send files by email Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 11603 allows to generate 3 types of files: html, csv and ods. This patch will add a --email parameter in order to send the generated files by email. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 13098] New: Item lost multiple times by the same patron will create only be charged once
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13098 Bug ID: 13098 Summary: Item lost multiple times by the same patron will create only be charged once Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 If a patron loses an item and is charged a lost fee, returns the item, and loses it again, the patron will not be charged a new lost fee! Steps to reproduce: 1) Check out item with a replacement fee to a patron 2) Mark the item as lost 3) Note the lost fee, write it off 4) Return the item 5) Check out item to the patron a second time 6) Mark the item as lost a second time 7) Note there is no second lost item fee -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15128] New: Add ability to limit the number of open purchase suggestions a patron can make
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15128 Bug ID: 15128 Summary: Add ability to limit the number of open purchase suggestions a patron can make Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries are finding that some patrons have a tendency to "spam" the purchase suggestions with dozens of requests at a time. It would be nice if we could limit the number of purchase suggestions a patron can place that are neither Accepted or Rejected. Idea: 1) Add new system preference "MaxOpenSuggestions" 2) Modify opac-suggestions.pl to count the number of suggesions the patron has that are not Accepted or Rejected 3) If that count has reached the number specified in MaxOpenSuggestions, deny the ability to place another suggestion with the message: "You have reached your limit of suggestions you can place at this time. Once the library has processed those suggestions you will be able to place more" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 14919] New: Reserves history for patron
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14919 Bug ID: 14919 Summary: Reserves history for patron 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On patron page, librarians have access to patron's circulation history and Notices history. One our library wants to see the holds history too. We have some data in table old_reserves, so it should be posible to show it somehow. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15122] New: Allow styling the Items available for loan -list in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15122 Bug ID: 15122 Summary: Allow styling the Items available for loan -list in OPAC search results Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org When you search the OPAC, the search results lists the "Items available for loan", with a list of all the branches where that particular item is available. The branches in that list cannot be styled separately at all. The list should have span class with the branch short name, and the count of items in that branch should also have a class or a tag to allow styling that separately from the branch name, for example: Items available for loan: Centerville(1) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15088] New: Note in koha-remove help that --keep-mysql is how you remove instances with remote databases
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15088 Bug ID: 15088 Summary: Note in koha-remove help that --keep-mysql is how you remove instances with remote databases Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If you try to remove a Koha instance that is using a remote database, it will fail and the sysadmin will feel sad. We already provide a mechanism by which we don't touch the mysql bits (--keep-mysql), it might be nice to explain in the help that using this will allow a sysadmin to remove the front-end of Koha and remove the remote database independently, at a later (or previous) time. I don't think we need a different option, maybe the existing one needs a different name... I'm not really sure. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 15121] New: runreport.pl cronjob ought to let you specify multiple addresses
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15121 Bug ID: 15121 Summary: runreport.pl cronjob ought to let you specify multiple addresses Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Just in case more than one person needs to receive a copy of a report. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14627] New: GetAuthorisedValueByCode does not handle undef intelligently
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14627 Bug ID: 14627 Summary: GetAuthorisedValueByCode does not handle undef intelligently Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org GetAuthorisedValueByCode is used in many places throughout Koha, many of the fields being looked up are nullable but if passed undef the routine proceeds to prepare and execute a meaningless query it should check the passed value and proceed with random behaviour -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 15118] New: Accidental Branch transfer on hold is not handled gracefully.
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '15

03 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15118 Bug ID: 15118 Summary: Accidental Branch transfer on hold is not handled gracefully. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is accidentally transferred to another branch after it fills a hold, the item will be checked in as 'local use' at the second branch, but will show as being held at the original branch. To reproduce: Place a hold for item X at branch ABC Check item X in at branch ABC, thereby filling the hold. Check the item in at branch DEF. This will produce a message like Hold found: ... Hold for ... Hold at ABC This will also give the following check in message: Check in message Not checked out Local use recorded Viewing the item's status will now show that the item's location is DEF, but the item is waiting for pickup at ABC. The expectation is that a branch transfer should have been created to send the item back to ABC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0