Chris Hostetter wrote:
1) if you've got full text search, why would you even want KWIC?
Well, KWIC is a way to present the full text search results so that they
can be easily read.
2) your description of how you'd want the results ordered is extrmely
confusing to me ... can you give a simple concrete example of some
documents / queries / result-doclists that you would want to see?
If you go to http://tkb.mydns.jp:8899/exist/rest/db/new/tkb.xq you will
see what I currently have. Just click search to search for the example,
or maybe delete the last character so that you get more results (this is
not released yet, so don't be surprised if it breaks...).
You will see the search term highlighted in the middle, context is
available from the blue arrow to the right. The display would be much
more useful for the users, if this could be sorted on the characters
following the hit (ignoring punctuation). Another option would be to
sort on the characters previous to the hit. But in this case, the
sorting has to be reversed, so that if I have:
ABCD<hit>FGHI
the sort-key would be constructed as DCBA for this case.
I know that this can be done by post-processing the results on the
client (which is what Erik suggested offline), but if I get thousands of
hits, that would be very slow, so I am looking for other ways. Erik
also said that down the road there might be a sort function that could
be called, which is what I would need here.
Cheers,
Christian
--
Christian Wittern
Institute for Research in Humanities, Kyoto University
47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN
