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

[Bug 12979] New: Price formatting should only be defined at one place
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '15

01 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12979 Bug ID: 12979 Summary: Price formatting should only be defined at one place Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org git grep Number::Format will show you the places where the currency format is defined. This formatting should only be defined in the new module Koha::Number::Price. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 13093] New: Allow/Don't allow holds on items with set statuses
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '15

01 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13093 Bug ID: 13093 Summary: Allow/Don't allow holds on items with set statuses 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 It would be helpful if there was more consistency between statuses regarding holds. The LOST category does not allow holds. The DAMAGED category has a global preference to allow/don't allow holds. The NOTFORLOAN category allows you to set a positive or negative value to indicate if it is holdable or not. For us, it would be great if we ditched the AllowHoldsOnDamagedItems preference and made LOST, DAMAGED, and NOTFORLOAN the same, where you to set a positive or negative value to indicate if it is holdable or not. (Hey, look at that! Someone is requesting a preference be removed!) Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 11297] New: Add support for custom PQF attributes for Z39.50 server searches.
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '15

01 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11297 Bug ID: 11297 Summary: Add support for custom PQF attributes for Z39.50 server searches. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: fcapovilla(a)live.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 23144 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=23144&action=edit Add support for custom Z39.50 attributes for Z39.50 servers. For some Z39.50 servers, some PQF attributes are required for the server to return results to searches. For example, the BANQ server (catalogue.banq.qc.ca) requires "@attr 4" to always be set. No results are returned without this attribute. For this server, we simply enter "@attr 4=1" in the "Attributes" field added by this patch, and the server then returns results correctly. This patch can also be used to force PQF attributes in all searches to a specific Z39.50 server in order to override the server's default values. Sponsored-by: CCSR ( http://www.ccsr.qc.ca ) -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 12188] New: fines duplicated after changing dateformat
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '15

01 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12188 Bug ID: 12188 Summary: fines duplicated after changing dateformat Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 27948 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=27948&action=edit fines duplicated hi, I changed sys pref dateformat to put dd/mm/aaaa and after cron of overdues, fines were duplicated (see attachment). I think a bug is on date on description of charges or on cron? Someone noticed it? Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 12151] New: remove remaining uses of the Perl smartmatch operator
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '15

01 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12151 Bug ID: 12151 Summary: remove remaining uses of the Perl smartmatch operator 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The Perl smartmatch operator has been marked as experimental as of Perl 5.18. As the syntax and interpretation of it is therefore subject to change, current uses of it should be removed. This is especially the case when running under Perl 5.18, as by default use of experimental constructs generates warning messages. The following source files contain the ~~ operator: C4/Search.pm: unless ( $data ~~ @used_datas ) { misc/translator/translate: if ( $cmd !~ /create/ && $lang && not $lang ~~ $installer->{langs} ) { opac/opac-search.pl: if ( $sort ~~ @allowed_sortby ) { tools/batchMod.pl: unless ( $field_to_update->subfield($subfield->[0]) ~~ $subfield->[1] ) { The following source files contain the given construct, which also uses smartmatch: C4/Serials.pm: given ($num_type) { reports/acquisitions_stats.pl: given ($_) { reports/acquisitions_stats.pl: given ($podsp) { reports/acquisitions_stats.pl: given ($rodsp) { reports/acquisitions_stats.pl: given ($process) { reports/borrowers_stats.pl: given ($line) { reports/borrowers_stats.pl: given ($column) { reports/borrowers_stats.pl: given ($i) -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 12268] New: Subject Broader Narrower Related terms and Query Parser and Exploded Terms issues
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12268 Bug ID: 12268 Summary: Subject Broader Narrower Related terms and Query Parser and Exploded Terms issues 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Just a couple things I want to point out... 1) su-na already exists in the CCL config as an alias for something other than "narrower term" for a subject: Subject-name-personal 1=1009 su-na 1=1009 2) If QueryParser is turned off, using su-br and su-rl queries will cause Zebra errors, because these aliases aren't defined in ccl.properties. The QueryParser dynamically adds them (and su-na) using a callback which adds them to the aliases defined in the config loaded from queryparser.yaml, I believe. To get around this, we could probably add "su-br" and "su-rl" as aliases to subject. We should probably also rename the existing su-na to something like su-nap so it doesn't get confused with the "su-na" for narrower terms during a query... 3) Even when the QueryParser is turned on, if you do a search for "Subject and Broader/Narrower/Related Terms" in advanced search, you'll always get a search that appends "wrdl" to the end of the alias. Unfortunately, QueryParser doesn't use "wrdl", so it falls back to using a non-QueryParser query, which creates the Zebra errors mentioned in Problem #2. 4) Advanced search with "more options" causes QueryParser to fail. It seems to be that "limit=" gets added onto the query string and that this is causing QP to fall back to non-QP. My guess is it's related to "Audience", "Content", "Format", or "Additional content types for books/printed materials", as these seem to be the only limits added when "expanded_options=1". 5) Advanced search includes a lot of "wrdl" suffixes which will cause QueryParser to fail. (E.g. su,wrdl; se,wrdl; au,wrdl; cpn,wrdl; cfn,wrdl; pn,wrdl; pb,wrdl; pl,wrdl;) I've tried out some of these indexes without the wrdl suffice while NOT using QueryParser, and they seem to work fine. I think we could get rid of these suffixes from the advanced search. 6) QueryParser also seems to ignore repeated indexes in a query... Example: kw:law || su:bulldozer || kw:test 22 results kw:test || su:bulldozer || kw:law 3 results It should give the exact same results... 7) If you try to use the "Search also for broader subjects" link from the search results and you don't have authorities, you'll get a database authorities unavailable error. Not the end of the world. But maybe we should hide these links if the Koha DB doesn't contain any authorities, since they'll never ever work and will just confuse users. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 7683] New: stat wizrad :cataloging
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7683 Priority: P5 - low Change sponsored?: --- Bug ID: 7683 Assignee: gmcharlt(a)gmail.com Summary: stat wizrad :cataloging QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: stephane.delaye(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: Reports Product: Koha In the cataloguing wizard, add the following lines that can be used as row/column/filter: * status * item creation date (range with dynamic calendar) * item suppresion date (range with dynamic calendar) * origin : items.materials - authorized value list "origin" 995$s * Domaine : 995$t items.statisticvalue "domain" av list Adds options for distinct biblionumber count on title and items. Add 3 options (radio buttons) - Titles count "COUNT (biblionumber)" - Counting of copies "COUNT (ItemNumber)" (current behavior) - Counting of copies deleted "COUNT (deleteditems.itemnumber)" - Add to selected row or column + filter combo: - items.notforloan - items.materials - items.statisticvalue For each of these fields, retrieve the label and the code value allowed in the grid cataloging default. If no MARC field is mapped to the field in question, it does not show this line in the wizard. If the MARC field is associated with a legal value, it displays a dropdown list for the filter, if a text field. - Add to selected row or column + filter on a date range - Items.dateaccessioned (create Date) - Deleteditems.timestamp (date deleted) (Only if the third option (eg count. Del.) Is selected) -- You are receiving this mail because: You are watching all bug changes.

1 146

[Bug 9537] New: Add a list of the patches that have been applied to a koha installation
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9537 Bug ID: 9537 Summary: Add a list of the patches that have been applied to a koha installation Classification: Unclassified 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: egpetridis(a)yahoo.com CC: gmcharlt(a)gmail.com I wonder if it would be useful to add a tab in the home, about koha section, displaying a list patches that have been applied to the specific koha installation, similar to the list of pearl modules. This could prove handy when trying to ascertain why a bug that doesn't exist in the main distribution manifests itself in some git derivative or other. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 7397] New: Patron search from Checkout tab does 'contains' instead of 'starts_with' search
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7397 Bug #: 7397 Summary: Patron search from Checkout tab does 'contains' instead of 'starts_with' search Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com When searching for a patron using the Checkout tab, instead of the main Patron search, inexact searches (those returning more than 1 hit) do a 'contains' search instead of a 'starts_with' search (as one would expect from the Patron search module's behaviour). The result is many, many more results than one would otherwise expect. The call to Search() in circ/circulation.pl seems to be malformed given the documentation for how C4::Members::Search works. -- 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 5

[Bug 11211] New: Move calculation code out of C4::Calendar
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '15

30 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11211 Bug ID: 11211 Summary: Move calculation code out of C4::Calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Blocks: 8133 Koha::Calendar should contain all of the calendar calculation code, and C4::Calendar should only have admin subs. Created to slim down bug 8133. -- You are receiving this mail because: You are watching all bug changes.

1 74