[Koha-bugs] [Bug 7518] searches with quotation marks don't work

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Jun 30 10:23:37 CEST 2014


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7518

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #42 from David Cook <dcook at prosentient.com.au> ---
(In reply to Jared Camins-Esakov from comment #12)
> (In reply to comment #11)
> > (In reply to comment #10)
> > CCL syntaxe for an exact match is 'exact' after the index ; it means phrase
> > structure and complete field.
> > The use of double quotes for exact match is a Google search engine behavior.
> > I can be very usefull, but maybe hard to manage in actual C4::Search.
> 
> Very hard (read: impossible) if we want to keep using CCL2RPN. Fortunately,
> there's a better way! Bug 9239 introduces a new query parser that uses
> quotes for phrases.

As Jared has mentioned, I think the use of double quotes to signify a
phrase/exact search would also be difficult to do while using CCL2RPN.

However, as some people have mentioned, it seems that Koha has had this ability
in the past...

This is, in part, because the default Koha search is a kw,wrdl search (i.e. a
Word list search on the Keyword index). 

"The structure attribute values Word list (6) is supported, and maps to the
boolean AND combination of words supplied. The word list is useful when
Google-like bag-of-word queries need to be translated from a GUI query language
to PQF."
Source: http://www.indexdata.com/zebra/doc/querymodel-rpn.html

In other words, doing a regular search for "professional responsibility" would
not do a phrase search. Rather, it would do a search like this: "professional"
AND "responsibility". In some cases, this will return the exact same results as
a phrase search would, but technically speaking it's not the same because
proximity and order of the words to each other doesn't take place in a "Word
list" type search.

The other reason why it seemed that we had this functionality in the past is
probably due to conflicting system preferences which accidentally turned off
QueryWeightFields. 

Truncation and QueryWeightFields really do not play well together. I am
endeavouring to fix that. I'll open other bugs to fix that though...

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list