: 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
I don't read Japanese so i'm really not sure what I'm looking at. I see hte search term highlighted, but I don't know enough about the langauge to really understand what is special about hte order of the results... : 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. That still doesn't really answer a fairly fundemental question i've been trying to understand: *why* would having the results in that order be much more useful to for the users? what are you going to do if the term input more then once in a single document? : 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. SOlr can sort your results on any indexed, single value, field - but for something like this you'd need to write your own plugin to do the sorting. Note that your plugin would basically need to do the same thing you currently do on the client, the only real speed performance gain would be in reducing the amount of data sent over the wire. -Hoss
