Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates
 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <43FC7C21-99A9-4E07-8855-1533F340C783@wandisco.com>
References: 
 <CAKoya91s5mpxCfaF9jdsUOumPinxLDfVa_Ry8UzXp4BhZzVwdQ@mail.gmail.com>
	<CAHM0gnj7RgUJBxJX=xPSDNtuC=o8hUg3y-U655=jHFZDg5kzuA@mail.gmail.com>
	<CAKoya91M9+ZemWJ7_YtAxmU7taetZmcqnpUApT=PWcaCaXZjSQ@mail.gmail.com>
	<CAHM0gngFdT56VsyG2sz=JCYC3gvw0EjZdVP3HGpMhOq9vPm8Bg@mail.gmail.com>
	<51308FC5.8060709@wandisco.com>
	<CAKoya925UJQ6BFfYrsoS1BCQmJa3nceLLBFD7jPZvPvFbdKoXA@mail.gmail.com>
	<B1308A66-E7FA-4F8F-B3B6-4CAFC220FE51@gmail.com>
	<CAHM0gngVWWNXcsA8+yXYCnat1nLGWV_P6PvXOkWPoEp80HrfVQ@mail.gmail.com>
	<CAKoya93gn4P2_qVceHM7Z=Wh1Zmmzy+MMKD8216X72KP-QbwEw@mail.gmail.com>
	<CAGMZAuOS5DUcDbmiK8Ex3GNnnZWrAE_BK-ukPwkn34-JY3fBVQ@mail.gmail.com>
	<43FC7C21-99A9-4E07-8855-1533F340C783@wandisco.com>
Date: Thu, 21 Mar 2013 10:35:49 -0500
Message-ID: 
 <CAGMZAuNJ9qQ9bagi9Lzdg1czVgrNt-sUe6bhh+wER1-UtUYrEA@mail.gmail.com>
Subject: Re: Query Builder (Search / Custom Query)
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 3/20/13, Joe Dreimann <joachim.dreimann@wandisco.com> wrote:
> On 20 Mar 2013, at 20:53, Olemis Lang <olemis@gmail.com> wrote:
>> On 3/20/13, Joachim Dreimann <joachim.dreimann@wandisco.com> wrote:
>> [...]
>>> On 14 March 2013 19:47, Andrej Golcov <andrej@digiverse.si> wrote:
>> [...]
>>>> We can set default product filter based on active product and use
>>>> global search if user navigates directly to global search url - I
>>>> think, Olemis suggested something like this.
>>>
>>> I believe search should always be global unless the user chooses
>>> otherwise.
>>
>> what does this mean exactly ? Let's focus on the following situation .
>> User reads let's say a wiki page in product P and searches for word W
>> by using search input box in the header . In your opinion is there any
>> value for getting results from other projects , even potentially not
>> provide any result for the active project ?
>
> Yes.
[...]

My point is somehow similar to this :

http://sourceforge.net/p/allura/tickets/?source=navbar

In there you'll find focused product-specific Search Tickets box and
broad Search box in body header . So user will choose search scope
explicitly . The only difference being that our proposal for focused
search (by default) should span over multiple resources (not just
tickets) . That means that I basically agree with you on user intents
within product boundaries . OTOH I disagree on not to limit the
(default) scope of search to active product . Systematically leading
the user out of product boundaries is not a good practice afaict

PS: I actually don't know whether the search box at the top is really
part of Allura of a SF.net specific add-on .

-- 
Regards,

Olemis.