Feedback on KinoSearchPlugin

-- DavidGuest - 07 Apr 2008

Thank you David for sharing this plugin with the TWikiCommunity!

Tiny feedback: I am not sure if %%NOP%KINOSEARCH{'Search String' format='Formatting string'}% gets escaped properly. Usually we write %<nop>KINOSEARCH{'Search String' format='Formatting string'}% to escape a TWiki variable.

-- PeterThoeny - 07 Apr 2008

Hi David,

great stuff. I am really happy, that someone uses the KinoSearchAddOn and implements additional things around it. I will test your staff as soon as I find some time for it.

A very interssesing thing would be to implement also the various handlers so that the index is updated after each change. This way the index would always be in step and the update index script would be obsolet.

-- MarkusHesse - 08 Apr 2008

I thought of the indexing thing but hadn't delved deep enough into the code to figure out how to make it work.

-- DavidGuest - 08 Apr 2008

Use the afterSaveHandler() in your plugin to trigger an update of the index on the topic being saved. If indexing is slow consider using a queue where you push the web.topicname, and a daemon that indexes topics pushed to the queue.

-- PeterThoeny - 09 Apr 2008

Impressive! I did a little testing with version 1.1 and want to confirm that text in newly attached documents and also in new topics can immediately after saving be found by the indexing kinosearch. So it looks like the kinosearch update script is getting superfluous with this plugin.

I didn't really get yet what to do with the %KINOSEARCH{'Search String' format='Formatting string'}% part. Could you elaborate a little bit about it or provide examples?

I created the topic QuakTopic putting just the word Quaaaaaak! into it. When searching for it using kinosearch the result was found when using Quaaaaaak! or Quaaaaaak but stopped to find the topic when just looking for Quaaaaaa. Did I miss something or is there an issue?

Thank you, Ingo

-- IngoKappler - 17 Apr 2008

The KINOSEARCH variable is to be used to add the results into any page as you would do with the inbuilt SEARCH variable. It allow for the output to be formatted. I will try and add an example at some point.

The problem with Quaa... is a limitation of the kinosearch utility. It does not do wildcard seraches. So it will only match on full words or words with a common root.

-- DavidGuest - 19 Apr 2008

Thanks for clarifying. I knew about the regex limitation in kinosearch but didn't realize that it already applies to something like a "simple" *. What do you mean by "common root" if Quaaaaaa isn't part of the root of Quaaaaaak!.

I hope this doesn't already get too much off topic here.

-- IngoKappler - 21 Apr 2008

Basically it only works with real words. So if you search for "promote" it should also match on "promotion". But a search for "new" will not match on "news" as these are two different words.

http://www.rectangular.com/kinosearch/docs/stable/KinoSearch/Analysis/Stemmer.html

-- DavidGuest - 21 Apr 2008

Thanks. I had a short look around the kinosearch pages and found that they are working on kind of trailing wildcard search, so probably at some future point kinosearch may be enhanced in that direction: http://www.rectangular.com/kinosearch/docs/devel/KinoSearch/Docs/Cookbook/WildCardQuery.html

-- IngoKappler - 21 Apr 2008

Nice plugin! The %KINOSEARCH% variable is exremely useful. However, saving is very slow now, so it would be good to do the indexing in the background, or - as an intermediate measure - add a configuration option not to do the indexing.

-- StephanMatthiesen - 01 May 2008

Since I have installed this plugin my "Find more extensions" in the configure does not work any more. My browser only shows the loading-indicator but loads nothing. There are no error messages. I have no idea what is wrong.

-- MathiasReiche - 13 Aug 2008