Zeno,
> Probaly not a pure CCL but something very similar to the present opac > queries that are so: > > idx=ti,phr > &q=red+winter > &op=and > > &idx=au,wrdl > &q=white > &op=and > > &idx=kw > &op=and > > &idx=kw > > &sort_by=call_number_asc&do=Search > If we're using that we could just as easily use PQF internally, with a lookup table to convert indexes to bib-1 attributes. Also, to clarify for those who might not be familiar with the terms, CCL is ISO 8777 ( http://www.indexdata.com/yaz/doc/tools.html#CCL ). It is a standard for specifying queries in a single, non-tokenized string. So this would be an example CCL query: > ti,phr:"red winter" and au,wrdl:white Notice how ambiguous that query becomes if you enter without the quotes (which users often don't enter): >ti,phr:red winter and au,wrdl:white Where should the system be looking for the word "winter"? Consider this even more charming example: > ti:snow white and rose red and au:wrede I'm not sure any commentary is necessary, but the book I'm looking for with that query is actually entitled "Snow White and Rose Red" by Patricia C. Wrede. If we use CCL, this record *may* match that search: TITLE: Snow white AUTHOR: Wrede, Patricia C. PUBLISHER:Rose red productions In order to handle real-life input, Koha uses an implied keyword index. Much better to use a tokenized query and convert it internally into equally non-ambiguous syntaxes handled by Zebra and Solr. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) [email protected] (web) http://www.cpbibliography.com/
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
