Return-Path: 
 <users-return-18378-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D1E6696D8
	for <apmail-jackrabbit-users-archive@minotaur.apache.org>;
 Tue,  6 Dec 2011 09:28:53 +0000 (UTC)
Received: (qmail 44257 invoked by uid 500); 6 Dec 2011 09:28:41 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 42303 invoked by uid 500); 6 Dec 2011 09:28:18 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:users@jackrabbit.apache.org>
List-Id: <users.jackrabbit.apache.org>
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Received: (qmail 42223 invoked by uid 99); 6 Dec 2011 09:27:47 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 09:27:47 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=5.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of christian.stocker@liip.ch
 designates 207.126.144.135 as permitted sender)
Received: from [207.126.144.135] (HELO eu1sys200aog113.obsmtp.com)
 (207.126.144.135)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Dec 2011 09:27:42 +0000
Received: from mail-ey0-f170.google.com ([209.85.215.170]) (using TLSv1) by
 eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP
	ID DSNKTt3f+J7GLGXGW9mINGvQdOqwKqvWtT80@postini.com;
 Tue, 06 Dec 2011 09:27:21 UTC
Received: by mail-ey0-f170.google.com with SMTP id o13so582375eaa.15
        for <multiple recipients>; Tue, 06 Dec 2011 01:27:20 -0800 (PST)
Received: by 10.213.29.1 with SMTP id o1mr2154214ebc.79.1323163639758;
        Tue, 06 Dec 2011 01:27:19 -0800 (PST)
Received: from pri7.local (77-58-253-248.dclient.hispeed.ch. [77.58.253.248])
        by mx.google.com with ESMTPS id v3sm69041096eej.7.2011.12.06.01.27.17
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 06 Dec 2011 01:27:18 -0800 (PST)
Message-ID: <4EDDDFF3.8090601@liip.ch>
Date: Tue, 06 Dec 2011 10:27:15 +0100
From: Christian Stocker <christian.stocker@liip.ch>
Organization: Liip AG
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: users@jackrabbit.apache.org
CC: dev@jackrabbit.apache.org
Subject: Re: Boosting newer documents
References: 
 <CA+ivXSaAynE7Z8n8+58pg=Hd3KBDNGyeNngd0L8=BVYGQDZO+A@mail.gmail.com>
 <CAB-0WTAe-kOPZT9DpZ84wr9o5njm1a+NNETbpq0DpGfaK6c1cQ@mail.gmail.com>
 <A0D56A8C-2193-46F5-934D-010F68C2D3B5@pooteeweet.org>
In-Reply-To: <A0D56A8C-2193-46F5-934D-010F68C2D3B5@pooteeweet.org>
X-Enigmail-Version: 1.3.3
OpenPGP: id=0748D5FE;
	url=http://gpg-keyserver.de/pks/lookup?op=get&search=0xC2BAFBC30748D5FE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi all

(crossposting to dev, since it's a potential feature improvement)

After digging into the code, it looks like we have to add a possibility
to specify not only a fixed boost number, but maybe also be able to
specify a method in the indexing.xml, which gets called when a Document
is inserted (like in
http://stackoverflow.com/questions/4724451/boost-fresh-documents-with-lucene/4737138)
or even add our own Scoring like in
http://www.lucenetutorial.com/advanced-topics/scoring.html

Before we dig more into this: Would this be the correct way? Is this
even possible in Jackrabbit without having to change too much? Or is
there an easier way to give "newer" Documents more weight than older once?

Greetings and thanks for any hint

chregu

On 02.12.11 18:08, Lukas Kahwe Smith wrote:
> 
> On Dec 2, 2011, at 18:03 , Alex Parvulescu wrote:
> 
>> Hi,
>>
>> you are probably referring to a sort, rather than a boost, right?
>>
>> if 2 documents rank the same for a search, sorting by the date would get
>> you what you need.
> 
> 
> no .. we actually want to boost.
> with "ORDER BY score, date" the date would only be a tie breaker.
> 
> we really want to significantly boost the score of any document that is more recent.
> the use case is a news site, where in most cases people will not care about content from a year ago if there is content about the same topic from a week ago.
> 
> regards,
> Lukas Kahwe Smith
> mls@pooteeweet.org
> 
> 

-- 
Liip AG  //  Feldstrasse 133 //  CH-8004 Zurich
Tel +41 43 500 39 81 // Mobile +41 76 561 88 60
www.liip.ch // blog.liip.ch // GnuPG 0x0748D5FE