Here is how searching and indexing works.
i. LISTSERV fully processes and prepares 100,000 match results, in the requested sort order.
ii. LISTSERV returns the first 100 to WA (I think this used to be 50).
iii. WA returns 100 matches to browser, with previous/next navigation.
i. If possible (this depends on the search), LISTSERV fully processes and prepares only the 100 match results that it is going to return. These are the 100 items that would come on
top if LISTSERV were to process all 100,000 matches in the requested sort order.
ii. LISTSERV returns 100 matches to WA.
iii. WA returns 100 matches to browser, with previous/next navigation.
This is for 16.5 and 16.0/2017a. Older versions handled ordering differently.
Sites like Amazon have gotten people used to searching for just “knife” and finding the nakiri knife they always dreamed of among the first 5 matches because matches are sorted based on past purchases, browsing history, and a host of other
private data that we don’t even know about, but that is very effective in predicting what we want to see. LISTSERV collects no such data, so if you could search for “email” in LSTSRV-L, the message you are looking for would be very unlikely to be among the
first 5. LISTSERV returns the equivalent of 10 Google pages’ worth of results and you can paginate for more but, if you value your time, you just have to narrow your search.
Anyway, there is nothing in the HPO search function that is more limiting than in Classic.
Eric
To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1