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

[Bug 12189] New: Untranslatable page title in print slip template
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '14

11 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12189 Bug ID: 12189 Summary: Untranslatable page title in print slip template Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr printslip.pl includes this line: title => "Print Receipt for $borrowernumber", ...meaning the page title is untranslatable. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 9378] New: Translations don't apply?
by bugzilla-daemon＠bugs.koha-community.org 11 Aug '14

11 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9378 Bug ID: 9378 Summary: Translations don't apply? Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: frederic(a)tamil.fr Translations don't appear to apply unless more than one is selected in the I18N/L10N preferences AND the selection bar is enabled (OPAC and Intranet affected) To replicate: 1.Install a second language (I've tested with both en-GB and fr-FR) using '/misc/translate/translate install xx-XX' 2. Enable just one language other than 'en' in the I18N system preferences. 3. Refresh the OPAC or Staff Client page and the new language should take effect, but it doesn't? The only way around this that I've found is to enable multiple translations AND in the OPAC the 'allow patrons to select' option and then manually select a language. Anyone else experiencing this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11564] New: Sorting any search on a date column fails!
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11564 Bug ID: 11564 Summary: Sorting any search on a date column fails! 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It appears that any attempt to sort a search on a date column fails. The two date columns that can be searched on are publication date and acquisition date. Video: http://screencast.com/t/yaRfaqA7mW2r I've also reproduced this on master. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 12257] New: Suggestions management displays all librarians as "Unknown"
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12257 Bug ID: 12257 Summary: Suggestions management displays all librarians as "Unknown" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If you inspect the filter pulldowns for suggested, accepted, or managed by, all the users are listed as "Unknown" instead of his or her name. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 11585] New: pubdate index not working well in UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11585 Bug ID: 11585 Summary: pubdate index not working well in UNIMARC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Without Queryparser, pubdate index is not searchable in unimarc. the query "pubdate:1925" in simple search box gives 0 results, even if we have a book of 1925. It is working well with Queryparser activated. M. Saby -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 12431] New: Relevance does not work properly when using QueryParser
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12431 Bug ID: 12431 Summary: Relevance does not work properly when using QueryParser Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, when using QueryParser, relevance will only work for keyword queries. queryparser.yaml either needs to be updated to include more weighted relevance mappings, or QueryParser needs a mechanism to add relevance to queries beyond the limited support it currently has. More information available here: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 11293] New: QueryParser date filters do not handle full dates well
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11293 Bug ID: 11293 Summary: QueryParser date filters do not handle full dates well 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The date filter callback for handling date filters does not handle full dates correctly. For example, * pubdate(2011-) signifies searching for records published on or after 2011 * pubdate(-1997) signifies searching for records published before or on 1997 * pubdate(1997-1999) signifies searching for records published in the applicable range However, since the hyphen is used to split elements of the range, the parsing does not currently handle full dates, e.g.: * acqdate(-2013-11-21) (items acquired on or before 2013-11-21) * acqdate(2013-01-01-2013-02-26) (items acquired during the specified range As a consequence, when QueryParser is enabled, using the acquisition date filters in the labels add-items-to-batch search form does not work. This likely accounts for the difficulty that Owen had when attempting to test the patch for bug 11222. For example, the QP query "acqdate(-2013-11-29)" gets sent to Zebra as @attrset Bib-1 @and @attr 2=4 @attr 1=Date-of-acquisition @attr 4=4 -2013-11 @attr 2=2 @attr 1=Date-of-acquisition @attr 4=4 29 when what was meant was: @attrset Bib-1 @attr 1=Date-of-acquisition @attr 4=5 @attr 2=2 2013-11-29 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 10831] New: QueryParser requires that defaultSortField and defaultSortOrder be set to non-NULL values
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10831 Bug ID: 10831 Summary: QueryParser requires that defaultSortField and defaultSortOrder be set to non-NULL values 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If QueryParser is enabled, the system preferences defaultSortField/defaultSortOrder (and their OPAC kin OPACdefaultSortField/OPACdefaultSortOrder) should not be set to NULL values. Otherwise, for searches where the sort order is not explicitly specified (e.g., searches made from the staff and OPAC global search box), the search can fail. This is due to several slightly questionable coding constructs collaborating in the confusion of both the user and the developer: [1] If a default sort order is not set, catalogue/search.pl and opac/opac-search.pl can end up setting the @sort_by array to (undef). This is because of the construct @sort_by = $cgi->param('sort_by'); If the sort_by CGI parameter is not passed, the result is not an empty array, it's an array containing one element whose value is undef. [2] The following code in C4::Search::parseQuery in turn uses @sort_by to add QP modifiers: if ( scalar(@sort_by) > 0 ) { my $modifier_re = '#(' . join( '|', @{ $QParser->modifiers } ) . ')'; $query =~ s/$modifier_re//g; foreach my $modifier (@sort_by) { $query .= " #$modifier"; } } If the query is "history", the modified version becomes "history #" ... which in turn results in a query that will not make sense to Zebra. One solution is to push through a DB update that extends the fix for bug 8012 to set the system preferences to sensible default values (probably relevance descending) if they're currently NULL. Note, by the way, that this means that the bug manifests itself only in databases old enough to have been created before the patch for bug 8012 was pushed. Another part of the solution, however, ought to be make the code in question a little more robust. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 12430] New: Truncation disables relevance ranking (when not using QueryParser)
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 Bug ID: 12430 Summary: Truncation disables relevance ranking (when not using QueryParser) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Scenario: 1) NOT using QueryParser 2) Using truncation (either by explicitly using * in the query or when 'QueryAutoTruncate' is set to 'automatically') Result: 1) Search results ARE ordered by biblionumber ascending and NOT by relevance -- This appears not to be an issue when using QueryParser as it seems to parse queries much better than the traditional...method. However, quite a major issue for those not using QueryParser, as everyone likes relevant searches. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 11353] New: Searches with QueryParser activated are broken if an Uppercase is used in the index name
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '14

10 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11353 Bug ID: 11353 Summary: Searches with QueryParser activated are broken if an Uppercase is used in the index name Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: major 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 I tried to search "Title:xxxx" with Queryparser activated Result on screen of staff interface: No results match your search for 'pqf=@attr 2=102 @or @or @attr 1=1016 @attr 5=1 @attr 4=6 "Title:xxxx" @attr 9=20 @attr 2=102 @attr 5=1 @attr 4=6 "Title:xxxx" @attr 9=34 @attr 2=102 @attr 5=1 @attr 4=6 "Title:xxxx"' in Ma bibliothèque Catalog. Mathieu -- You are receiving this mail because: You are watching all bug changes.

1 2