Subject:
|
Re: News search function reactivated (was: News search function temporarily disabled)
|
Newsgroups:
|
lugnet.admin.general, lugnet.off-topic.geek
|
Date:
|
Wed, 3 Jan 2001 14:11:53 GMT
|
Viewed:
|
10220 times
|
| |
|
|
In lugnet.admin.general, Dan Jezek writes:
> Wow! So you have terms for the ampersand options in a URL? My standpoint
> on this would be to put everything in a form and kill 2 birds with 1 stone -
> not having to think of how to name URL terms (unless you enjoy doing that)
> and having the search more user-friendly (not everyone will remember the
> options or find it easy to edit the URL).
Ya, exactly -- first name the URL components carefully and then put a user-
friendly level on top of it. Best of both worlds.
> No, I meant having the option to pick between what I want the results to be
> sorting on. Dejanews has a great power search:
>
> http://www.deja.com/home_ps.shtml
>
> which includes the option to sort by relevance, subject, forum, author and
> date. That's how I would like to see the sort options here.
Ah, I see. Yeah, that could be helpful in certain cases, if you're scouring
tons of results! I've needed to look things up on Deja.com, so I know what
you mean.
> But knowing
> that you most likely don't have the resources that dejanews has and how
> flawlessly Lugnet runs on the current setup, I'm satisfied with editing the
> URL for now :-)
There's an alternate form that avois the &qs= thingie, so you don't have to
edit the URLs:
http://news.lugnet.com/admin/general/?n=8613
> It could be done. Include another version of jump.cgi into the 5 more, 10
> more... on the search results page and log the number of results returned,
> the IP address and the query subject.
These don't actually run through jump.cgi. But they're already logged by
httpd anyway. (That's how the jump.cgi logging is implemented as well.)
> Then run an average, min, max query
> grouped by all 3 fields. Sounds complicated, depends on how badly you want
> to see the results. I wouldn't want to go through the process of
> implementing that but would really like to see the results :-)
Hmm, it's all there now, except for logging the number of results produced.
I guess it could be as simple as open for append, flock, print, and close on
a filehandle inside of the search page...lemme think about it. Analyzing the
results and making a graph would be a snap with gnuplot.
I think it would be especially fun to compare the graph now to the way it was
(would have been) before the change...but alas, that data was never captured
for the old query engine and it's too late now.
--Todd
|
|
Message is in Reply To:
45 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
