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

[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 12568] New: Improve visibility of successful renewal via opac
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12568 Bug ID: 12568 Summary: Improve visibility of successful renewal via opac Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, when a patron renews an item via the opac, the only feedback the patron receives when a renewal is successful is an updated value for the due date of the item. This subtle indication of success may go unnoticed by some patrons. We should add a more prominent way to indicate an item was renewed successfully. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 12571] New: Add ability to customize SIP2 screen messages
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12571 Bug ID: 12571 Summary: Add ability to customize SIP2 screen messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We should add the ability to apply a regular expression to screen messages for the SIP2 server. This would allow libraries to not only customize the screen messages the patron sees, but can also allow screen messages to be translated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[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 13373] New: Update Polish web installer sample data files
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '15

04 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13373 Bug ID: 13373 Summary: Update Polish web installer sample data files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: rkopaczka(a)afm.edu.pl Reporter: rkopaczka(a)afm.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There's polish web installer files, but it seems that they are very outdated, and this may cause problems after install. I'll try to update it, and translate some of it. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 13644] New: Paging Javascript breaks links with anchor
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '15

03 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13644 Bug ID: 13644 Summary: Paging Javascript breaks links with anchor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I have a library asking me to put a link to the items tab of the MARC detail page on the normal detail page, so they can see the additional fields we have defined more easily. Trying to do this, turned up an oversight in the Javascript for the site paging. In order for a link with an anchor # to work, the anchor needs to be last on the link, but the browser.js will but the searchid= parameter at the end, so the link is broken. What needs to be done is to add the params directly after the other params and leave the #anchor at the end. http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=koha-tmpl/intrane… I have found no existing link that gets broken yet, but we could still fix this to make sure everywhere this script is used the links are created correctly. Example: Created link: https://staff.kopac.bsz-bw.de/cgi-bin/koha/catalogue/MARCdetail.pl?biblionu… Working link: https://staff.kopac.bsz-bw.de/cgi-bin/koha/catalogue/MARCdetail.pl?biblionu… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 13651] New: Provision for monthly library fee
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '15

03 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13651 Bug ID: 13651 Summary: Provision for monthly library fee Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dear Developers, Many public libraries charge monthly subscription fee (e.g. INR 30 per month)for patrons. We would like to see a provision for charging monthly fee in coming version. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 13659] New: "stack smashing detected", when Zebra indexing a subfield with a very long (1000+) word
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '15

03 Feb '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13659 Bug ID: 13659 Summary: "stack smashing detected", when Zebra indexing a subfield with a very long (1000+) word Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org I encountered this when migrating another library group to Koha: *** stack smashing detected ***: /usr/bin/zebraidx terminated After a long search using the rebuild_zebra_sliced.sh I managed to isolate the culprit to a MARCXML Record with a subfield consisting of a single word with a length of ~1000 characters. A fix for this issue is to sanitate the marc-records to not contain such silly words. -- You are receiving this mail because: You are watching all bug changes.

1 3

[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