Re: search results not sorted with 'cl'

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19837
interpreted = N
texte = The best match for a search takes into account all search criteria not just the close to parameter (i.e. keywords matched etc.). I wouldn't rely on this to always sort in a numeric direction. If you are explicitly stating a sort direction, and it doesn't seem to be doing it, try adding a hidden field name=allhit value=1. Sorting only takes place with similarly ranked results. Adding this forcess all matches to have the same ranking.John.At 02:40 PM 9/8/98, you wrote: >Hi > >I am doing a search for cl (close to value) this works fine in finding the >correct records but my results are not sorted in the correct order ie: the >closest first. They are just random. > >If I do a couple of (unconnected) searches on the same page, just >increasing the 'close to value' the order is different each time. > >In the online documents is says: >Note: if you do not specify a sort order explicitly, then WebCatalog >assumes you want the results sorted by best match, meaning that the >records which match the most search terms will be shown at the top of the >list. > >Does this not work with closest to? > >Paul Willis > > Associated Messages, from the most recent to the oldest:

    
  1. Re: search results not sorted with 'cl' (John Hill 1998)
  2. search results not sorted with 'cl' (Paul Willis 1998)
The best match for a search takes into account all search criteria not just the close to parameter (i.e. keywords matched etc.). I wouldn't rely on this to always sort in a numeric direction. If you are explicitly stating a sort direction, and it doesn't seem to be doing it, try adding a hidden field name=allhit value=1. Sorting only takes place with similarly ranked results. Adding this forcess all matches to have the same ranking.John.At 02:40 PM 9/8/98, you wrote: >Hi > >I am doing a search for cl (close to value) this works fine in finding the >correct records but my results are not sorted in the correct order ie: the >closest first. They are just random. > >If I do a couple of (unconnected) searches on the same page, just >increasing the 'close to value' the order is different each time. > >In the online documents is says: >Note: if you do not specify a sort order explicitly, then WebCatalog >assumes you want the results sorted by best match, meaning that the >records which match the most search terms will be shown at the top of the >list. > >Does this not work with closest to? > >Paul Willis > > John Hill

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Decrypting a user password (2000) Additional Subtotals (1999) Re:2nd WebCatalog2 Feature Request (1996) name of file (2002) Weird Math and SV (1997) Copyright ? (1997) HELP WITH DATES (1997) Unanswered trigger questions ... (2003) [shownext max=?] armed (1997) Re:Emailer and encryption (1997) Details of shipping - Totalqty calculations (1997) Bug or syntax error on my part? (1997) RequiredFields notes ... (1997) [WebDNA] cookie expiration date (2015) Add to a field (1998) [searchString] (1997) [Sum] function? (1997) Checking for WebCatalog Version (2000) [WebDNA] Old Problem, the exclamation point (2014) HELP WITH DATES (1997)