Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard

From: Richard Huxton <dev(at)archonet(dot)com>
To: Robert Bernier <robert(dot)bernier5(at)sympatico(dot)ca>
Cc: pgsql-www(at)postgresql(dot)org
Subject: Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard
Date: 2006-08-02 19:12:44
Message-ID: 44D0F92C.7030507@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Robert Bernier wrote:
> On Wednesday 02 August 2006 13:33, Robert Treat wrote:
>>> ASPSeek can as well (they're called stopwords) but it won't help in this
>>> case because even if we don't ignore IN et al. it'll still match
>>> virtually every page.
>> What would be nice would be to have a first level of human specified
>> keywords that return specific information, above and beyond the general
>> search. This could operate similarly to rtfm_please on irc or my rtfmbot
>> on AIM. This way when someone searches on something like IN, we can say
>> "you're probably looking for this --> link" If there are general search
>> results, we could show them after the pre-spelected links.
>
>
> Could a set of links be returned, somewhere on the page, that would always
> refer to one or more keywords when a single word is used as the search
> criteria?

Could we not just score the index more highly than other pages?
http://www.postgresql.org/docs/8.1/static/bookindex.html

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message anil maran 2006-08-02 19:26:12 latin-1 to utf8 in python
Previous Message Robert Bernier 2006-08-02 17:57:28 Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard