On Sunday, July 7, 2002, at 08:20 PM, Jim Cole wrote:
>> Is it possible to configure ht://dig to return documents ONLY if there >> are >> three or more occurrences of the search term (or phrase) in the >> document? > > I am not aware of any configuration setting that allows this sort > of functionality. I seem to recall reading that the databases are > structured in a manner that makes it non-trivial to obtain > per-document word frequencies. This is not entirely true, but close enough. Basically, you'd still have to retrieve all the documents anyway, and then you'd have to filter the search results carefully. You certainly could code in such a restriction (i.e. while it's doing the scoring, it counts the number of word occurrences), but the key word there at the moment is *code*. Since no one else has really asked for this, it's not high on any of the active developers' lists. >> If there was a way we could limit results via the config file as >> above, this >> should ensure the results are a little more relevant, without us >> having to >> constantly fine-tune or list. Is there a better way to do this? > > Have you checked through the weight related attributes to see if > there is anything there that might help you. In particular, there > are a lot of *_factor attributes that allow you to adjust the Todd, you also mention using 3.2.0b4 snapshots. All of the scoring for 3.2 is done in htsearch, so you can quickly and easily change the factors and adjust the rankings. No reindexing is needed. If you find weightings that you like better, we'd be interested to know them. Regards, -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
