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

[Bug 7162] New: Factorize code for order cancellation
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '15

12 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7162 Bug #: 7162 Summary: Factorize code for order cancellation Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: julian.maurice(a)biblibre.com ReportedBy: julian.maurice(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Some code was duplicated, in the following patch all is now in a new file cancelorder.pl. It takes a 'referrer' parameter so it can easily be called from any page of Koha, and then redirect to it when it finish. Confirmation for cancellation is now done in this page (not in javascript). Add possibility to give a reason for cancellation (or other things, this is saved in aqorders.notes) DelOrder is modified to take two new parameters: - delete_biblio: if '1', try to delete biblio - reason: text to add to aqorders.notes (this note isn't show anywhere since there is no place to view cancelled orders, but another patch will add this feature). basket.pl and parcel.pl links to this page. -- 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 135

[Bug 11641] New: ILS-DI: Some more work for HoldTitle and HoldItem
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '15

10 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11641 Bug ID: 11641 Summary: ILS-DI: Some more work for HoldTitle and HoldItem Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This report is a follow-up on report 8918. This still needs some attention: 1) HoldTItle and HoldItem do not check for double reserve requests of a patron where Koha does. 2) The mandatory request_location parameter of HoldTitle does not seem to be used. Same for needed_before_date and pickup_expiry_date. 3) Also: needed_before_date, pickup_expiry_date in HoldItem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 12041] New: Improve Koha::Cache
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '15

10 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12041 Bug ID: 12041 Summary: Improve Koha::Cache 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: robin(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Koha::Cache can be improved to fall back more reliably, to handle complex data types, and so on. This is necessary to allow caching of things properly under plack. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 11924] New: warning about hold when item checked in at wrong library
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '15

08 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11924 Bug ID: 11924 Summary: warning about hold when item checked in at wrong library 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: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This was received via email: ------------- I guess what I'm seeing as the problem is this: 1. PatronX places an item on hold for pickup at Library A. 2. Library B sends a copy of the item to Library A. 3. The item is checked in at Library A and Koha switches the status of the item to "Item is waiting for PatronX at Library A." 4. A staff member at Library A hands the item to PatronX and, for whatever reason, the item does not get checked out to PatronX. 5. PatronX uses the item and then returns it to Library C. 6. Staff at Library C checks in the item and Koha does nothing. When you look at the item record it says "Item is waiting for PatronX at Library A." Koha does not change the status of the item, it does not display a "Route to Library A" message, it does not change the holding location. Koha does nothing even though the item does not belong at Library C in any way shape or form. Yes, there is a procedure problem here. At step 4 the staff member at Library A screwed up and let PatronX leave the library building with an item that had not been checked out. What I'd like Koha to do is to give the staff at Library C some kind of alert when step 6 is reached so that staff at Library C know that the item is supposedly on hold at Library A. Since Koha doesn't do _anything_ at checkin, if this kind of mistake is made the error created by staff at Library A can be further complicated if staff at Library C are as inattentive as staff at Library A. So my question is, when an item that is supposed to be on hold and waiting for pickup at one branch gets checked in at a different branch, can Koha display some kind of a message? I really think that it ought to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 12165] New: Add description of charges (bug 2546) to Bootstrap OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '15

06 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12165 Bug ID: 12165 Summary: Add description of charges (bug 2546) to Bootstrap OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr It looks like we forgot to fix the bootstrap templates in bug 2546: Copying test plan from the other bug: The descriptions for charges are stored in English in the DB (accountlines.description). So they are not translatable. This patch removes the descriptions automatically added and generates the string in the template. Test plan: 1/ Execute the updatedatabase entry. 2/ Verify in the following pages the description is consistent: - members/pay.pl?borrowernumber=XXXX - members/boraccount.pl?borrowernumber=XXXX - opac-account.pl 3/ Launch the translate script and update the po files in order to translate the new strings. 4/ Verify the strings are translated in the interface. The database bits for this are done, we only need to update the templates. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 6254] New: can't set patron privacy by default
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6254 Bug #: 6254 Summary: can't set patron privacy by default Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Patrons AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you do a bulk patron import you can choose a privacy setting for your patrons, but when you create a new patron you can't. Many libraries want the default to be 'Never' and have the patrons opt in - while others want the patrons to choose to opt-out instead. Given this librarians should be able to set the default per patron or patron category and then never be allowed to edit that once it's set (in order to let the patron have control over the preference). -- 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 60

[Bug 11634] New: Allow renewal of item with unfilled holds if other available items can fill that hold
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11634 Bug ID: 11634 Summary: Allow renewal of item with unfilled holds if other available items can fill that hold 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The current holds behavior in Koha allows a situation like this: - Patron A has an item currently checked out. - Patron B places a hold on the next available copy of that title. - Then Patron A will not be able to renew his item, even if there are other available copies of that title that could potentially fill Patron B's hold. Since this seems unfair to Patron A, we should allow renewal of items even if there are unfilled holds, but those holds could all be filled with currently available items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 60

[Bug 11232] New: Retrieve facets from Zebra
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11232 Bug ID: 11232 Summary: Retrieve facets from Zebra Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At Kohacon, a few of us (Jared, Paul P, Tomas, myself, and possibly others) looked at using Zebra's native facetting. After a bit of trial and error, in the final 15 minutes of the hackfest, we were able to get it working using queries in YAZ(high fives all around), but I'm not sure if anyone has followed up on that work (as I've been on holiday). I don't see any existing bug reports for adding this functionality to Koha, but I think it would be preferable to how we build facets at the moment (hence this bug). This method should be: 1) faster (since it is pulling the facets from the search results using indexes rather than iterating through every record); 2) more comprehensive (it is based on the full result set and not just the first 50 or so results [depending on your sysprefs]); 3) able to build facets for control fields and the leader (since it pulls data using indexes, we should be able to easily build facets for publication year, record type, etc.). In terms of customizability (bug 10891), it might be more difficult to change on the fly. This is because we need to explicitly define each facet index in our configuration files for Zebra. I'll need to look over my notes and do a few more experiments, but I'm quite certain this is the case. While we could add a mechanism for allowing users to specify which facets to retrieve and display (probably a good idea), we couldn't do the same for the static XML config file. So we would need to either include all the indexes in the XML config file or mark it as a place for local changes. I'm not sure about the cost/benefit of telling Zebra that every index could be used as a facet. I don't imagine it would be too much of a cost though, since the list of facets would be fed to Zebra on start up and not runtime. -- As I said, I'm not sure if anyone is working on the native facetting at the moment. I would like to but I'll have to look at my workload and chat to my boss. I'll be happy to post my notes in a comment tomorrow on how to get it to work. The config is slightly different for DOM and GRS1 but it works well for both. -- You are receiving this mail because: You are watching all bug changes.

1 125

[Bug 6590] New: Removing hyphens from isbn and issn when cataloging a biblio
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '15

03 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6590 Bug #: 6590 Summary: Removing hyphens from isbn and issn when cataloging a biblio Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: juan.sieira(a)xercode.es QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com By removing hyphens from isbn and issn in marcxml and marc, it makes possible search for a isbn or issn with or without them. When a search of an isbn, or issn is made, it has to remove them too. -- 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 9096] New: Subscription Fee for patrons
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '15

02 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9096 Bug ID: 9096 Summary: Subscription Fee for patrons Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: mpprasanth75(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Please include a filed to enter subscription fees details in the patron enrolment section.I am from Kerala India.Working with public library affiliated to Kerala State Library Council.We are collecting subscription fee from our members every month.That fees entering and updated status for a member is required to every members circulation page.Now Koha only enrolment fee only thats for one time payment but in subscription fee is charging every month.Please necessary to do this matter. Regards Prasanth 09961858865 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3