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

[Bug 7292] New: new permission for claims
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '14

09 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7292 Bug #: 7292 Summary: new permission for claims Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions AssignedTo: claire.hernandez(a)biblibre.com ReportedBy: claire.hernandez(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7163 "new permission for claims: the librarian can have a permission ""claim for all"". Without this permission, he can claim only on basket he is a ""user"" of " (BibLibre MT6542) -- 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 60

[Bug 11375] New: Patron permission names are untranslatable
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11375 Bug ID: 11375 Summary: Patron permission names are untranslatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Patron permimssions (eg. "superlibrarian", "reserveforothers", etc) and their explanations are not translatable. These strings come from installer/data/mysql/en/mandatory/subtag_registry.sql and installer/data/mysql/en/mandatory/userpermissions.sql -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 12211] New: Wrong home link in bootstrap opac-auth
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12211 Bug ID: 12211 Summary: Wrong home link in bootstrap opac-auth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In bootstrap opac-auth.tt, the link to "Home" in breadcrumbs leads to #, it should lead to opac-main.pl like in all other pages. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 10893] New: Location facet not working in UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10893 Bug ID: 10893 Summary: Location facet not working in UNIMARC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mathieu.saby(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Location facet in UNIMARC is void. In the code, it is build on 995$c, while location is store in 995$e (see record.abs). M. Saby -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 12432] New: Saved reports tabs not working
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12432 Bug ID: 12432 Summary: Saved reports tabs not working Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: Windows Status: NEW Severity: major Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: koha(a)jsense.co.uk QA Contact: testopia(a)bugs.koha-community.org In release 3.14.05.000 the tabs on the Saved Reports page worked correctly but after upgrading to 3.16.00.000 the tabs stop working. Visually the tabs change but the table of reports is not filtered. There are no errors reported in the browser console. IE version 11.0.9600.17107 Chrome version 35.0.1916.153 m -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 11885] New: Inconsistent HTML in MARC Details
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11885 Bug ID: 11885 Summary: Inconsistent HTML in MARC Details Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 25770 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=25770&action=edit Make MARC Details tab HTML consistent In Catalog > MARC Details, the HTML in the different tabs is slightly inconsistent and doesn't differentiate different elements, making CSS styling complicated or impossible: * tab 0 has <p class="subfield_line"> whereas all the other tabs have just <p> * all other tabs wrap the subfield character in <b> tags, except for tab 0 * the MARC tag title is a single div with the tag, the indicators and the field description. Attached patch folds all the tab outputs into a single TT BLOCK, which is then reused. It also marks the separate parts of the tag title in their own spans. The output should be nearly identical to previous behaviour, minus a dash from the tag title descriptions - it was used to separate the tag from the description. The description can now be styled separately from the tag itself, so the dash can be added with CSS, if necessary. To test: 1) Look at some MARC details in the staff client, noting the contents of each tab. 2) Install patch 3) Compare the MARC details output to what was shown in step 1. Should be the same, minus a dash in each of the tag title descriptions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 11624] New: Impossible to style MARC display via CSS
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '14

08 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11624 Bug ID: 11624 Summary: Impossible to style MARC display via CSS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It's impossible to style the MARC display field number, indicators, and the descriptions via CSS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 12450] New: Closing libraries for the summer
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '14

07 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12450 Bug ID: 12450 Summary: Closing libraries for the summer Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Currently, there is no way to close a library in Koha for a specified period of time. A good example for this is when we have public schools closed for the summer. We should not be able to place holds on their items or use their location as a pickup location. Right now, we have to do several things to accomplish this. First, we have set the default rule for the closed library to "No holds allowed". Next we have to remove the library from all staff pickup locations listed with jquery: $("#pickup option[value='SILVERHILL'],select[name='pickup'] option[value='SILVERHILL']").hide(); Then we have to do the same for the OPAC: $("option[value='SILVERHILL']").hide(); But then we also have to warn the patron that they can't pick up at their library, and then change the default to another library. Otherwise, it will still set their library as the pickup location, even though the choice is hidden in the list: if($("select[name='branch'] :selected").val() =="SILVERHILL") { alert("Your home branch is closed for the summer. Please select a different pickup location."); $("select[name='branch'] option:contains('Wallace Library')").prop("selected",true); }; If we don't change the default selection and the patron places the hold with their library as the pickup location, the hold ends up in limbo. It doesn't show on a queue anywhere! It isn't necessary, but should be done for the staff side as well. Right now we don't, because the pickup location defaults to the logged in library. Our closed libraries would not be logged in at this time. But, ideally it should be done to prevent issues. Ideally, I would like to see a setting in the libraries or calendars that would do all of this. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 12365] New: Notes for rules
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '14

04 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12365 Bug ID: 12365 Summary: Notes for rules Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 I would LOVE to see a notes field for each branch (or default) under smart-rules.pl, if not a note field for each individual rule. Often we are combing through rules (and settings for that matter), and come across something we are not sure why we set a particular way. Not all branches have the same workflow or methods, and therefore have a rule set for what they need. However, when we come across that setting months or years later, we have to go through huge discussions as to why it was set, and if we need that setting. This would help save a LOT of time, if we could make notes somewhere about it. Maybe just a notes table, where we could link to the rule, and if there is a note about the rule, a link called "notes" appears next to it that will display a popup window with the note. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 9864] New: systematic searching error : can't call method "raw"
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '14

04 Dec '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9864 Bug ID: 9864 Summary: systematic searching error : can't call method "raw" Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: koha(a)univ-lyon3.fr Launching a Search, whether on opac or intranet and whatever index is used get the following error : "Can't call method "raw" on an undefined value at /home/kohabac/src/C4/Search.pm line 496" -- You are receiving this mail because: You are watching all bug changes.

1 13