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

[Bug 10956] New: Series of OPAC searches can cause a browser crash
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10956 Bug ID: 10956 Summary: Series of OPAC searches can cause a browser crash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In my tests this series of OPAC searches will result a browser crash (Firefox) or an endlessly loading tab (Chrome): 1. Perform a keyword search which will return a good number of results. 2. Click on a title in those results which will have a good number of works by that author. 3. Click on the author link on the detail page to perform a search by author. 4. Click on a facet on the author search results page (I tested by clicking on a library facet). 5. Click on a title in the refined search results. I've tested this procedure with XSLT on and off, with OpacBrowseResults on and off, and with EnableOpacSearchHistory on and off. I get the same results in both themes. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 10749] New: patron permissions typos
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10749 Bug ID: 10749 Summary: patron permissions typos Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Home > Patrons > Set permissions for {staff member}, it says "edit_patronsPerform batch modifivation of patrons" which should be "edit_patronsPerform batch modification of patrons" It also says "budget_add_delAdd and delete budgets (but cant modify budgets)" which should be "budget_add_delAdd and delete budgets (but can't modify budgets)" -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 12407] New: phone label or data switched
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12407 Bug ID: 12407 Summary: phone label or data switched Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 28785 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=28785&action=edit enter data See attached image. You enter date in the secondary and other phone fields on the patron form and it shows next to the opposite label on the patron record. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 11354] New: NewItemsDefaultLocation Override in Cataloging
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11354 Bug ID: 11354 Summary: NewItemsDefaultLocation Override in Cataloging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: library(a)stas.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The value of NewItemsDefaultLocation indiscriminately sets the location of a new item to this value. That is, when adding a new item, no matter what the cataloger sets for 952$c, the record defaults to the preference value, even if 952$c is not null. The matter is trivial, because one can easily just edit the item after the addition, and the edit sticks. It would be nice, however, for the NewItemsDefaultLocation value to only be applied to a new record when 952$c is null. If non-null, the default should not be applied. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 11111] New: The basket group is not display on the parcel page
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '14

25 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11111 Bug ID: 11111 Summary: The basket group is not display on the parcel page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 10724 adds the search by basket group on the parcel page but does not display it the the table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 12505] New: Variable aqorders.listprice from 'Tools' - 'Notices and Slips' Does not work
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '14

24 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12505 Bug ID: 12505 Summary: Variable aqorders.listprice from 'Tools' - 'Notices and Slips' Does not work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: simith.doliveira(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The variable aqorders.listprice shows aqbooksellers.listprice value instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 5304] New: Too many post find queries for items
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '14

24 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5304 Summary: Too many post find queries for items Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: srdjan(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 C4::Items::GetItemsInfo(): When the items resultset is returned from the search, lots of additional queries are requested for each item in order ti get extra data. This makes large resultsets extremely slow to return. Proposed solution: Rewrite items query so it returns all relevant data at once -- 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 31

[Bug 10345] New: Copy number should be incremented when adding multiple items at once
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '14

24 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10345 Bug ID: 10345 Summary: Copy number should be incremented when adding multiple items at once Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: m.de.rooy(a)rijksmuseum.nl When adding multiple items in cataloguing, the copy number is not incremented for the generated additional items. To test: - Add new items to any of your records - Make sure you enter a copy number - Choose "Add multiple copies" - Enter number of items to be generaded - Click Add - Verify copynumber is empty for all generated items except the first -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 8735] New: Expire holds waiting only on days the library is open
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '14

22 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8735 Priority: P5 - low Change sponsored?: --- Bug ID: 8735 CC: gmcharlt(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Expire holds waiting only on days the library is open Severity: enhancement Classification: Unclassified OS: All Reporter: kyle(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Hold requests Product: Koha There is a problem with expiring reserves. Let us say an items has two holds placed on it, and is set to waiting for the first hold. This hold is then canceled for waiting too long, yet it will remain sitting on the holds shelf until a librarian either returns it to the shelf, or sets it too waiting for the next person in line to get it. During the interim, the item will appear to be available for checkout. This is not a problem most of the time, as the holds expire late at night and the librarians will take care of it in the morning, but over a holiday weekend, it is possible that an item will remain in this state for days at a time. We can fix this situation by adding a system preference to decide of waiting holds should be canceled on holidays, or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 71

[Bug 11852] New: Scripted processes
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '14

22 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11852 Bug ID: 11852 Summary: Scripted processes 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Here is a lofty wish... I wish Koha could have the ability to have scripted processes. For example. We don't have holds waiting automatically expire (meaning it wasn't picked up, not to be confused with a patron set expiration on the request), simply for the sake that we don't want available items on the hold shelf unless it has been processed. For us, this means, after 7 days waiting without being picked up, we pull the item, we go into the patron account the item was waiting for and put a message on the account that the item was not picked up. We then cancel the hold and check the item in to trigger the next hold or transfer back to the home library. It would be a dream to be able to create link to a script that would do all of this. For example, we would have a link in the Circulation menu to a script called "Process expired holds". We then scan the item, and the script puts the "Not picked up" message in the patron account, cancels the existing hold for that patron, and checks the item in to trigger the next hold or transfer on that item. I could see this working if there were a way to pass on these tasks to Koha like events. Maybe through URLs. I don't know. But, it would be wonderful in streamlining processes. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1