Re: A counter productive conversation about search. - Mailing list pgsql-www

From Dave Page
Subject Re: A counter productive conversation about search.
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C890@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Re: A counter productive conversation about search.  ("John Hansen" <john@geeknet.com.au>)
Responses Re: A counter productive conversation about search.
List pgsql-www

> -----Original Message-----
> From: John Hansen [mailto:john@geeknet.com.au]
> Sent: 29 August 2006 08:52
> To: Dave Page; Joshua D. Drake; PostgreSQL WWW
> Subject: RE: [pgsql-www] A counter productive conversation
> about search.
>
> Dave Page Wrote:
>
> > That should be fixable by tweaking weighting values, however
> > last time I suggested that I got shot down.
>
> Not so much shot down, but that it isn't possible. (at least
> not without rewriting code)
>
> Siteweights are for sites, not for parts of a site.

Yeah, I was thinking of Mnogosearch where a server can include
subsections so you can do things like:

ServerWeight 100
Server http://www.postgresql.org/docs/8.1/
ServerWeight 50
Server http://www.postgresql.org/docs/7.4/

I did get shot down as well though - iirc it was Oleg who was
essentially saying that the search engine should not have any knowledge
of the site beyond what it crawled.

> However, if you browse to the documentation you want to
> search first, then only that part of the website will be searched.
>
> Example:
>
> Go to http://www.postgresql.org/docs/8.1/static/index.html
> and search for 'create index'
>
> http://search.postgresql.org/www.search?ul=http%3A%2F%2Fwww.po
> stgresql.org%2Fdocs%2F8.1%2Fstatic%2F%25&fm=on&cs=utf-8&q=create+index

Yeah.

/D

pgsql-www by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: [pgsql-advocacy] Getting better Google search results
Next
From: Robert Treat
Date:
Subject: Re: No PWN on planetpostgresql.org