Thanks for your answers,
Yes, its true that with boolen queries things are much easier...
+(query1) +(query2) should do an and
or
(query1) (query2) should do an or
and this does not need a special ability to parse the queries
I like the dismax approach, I think is interesting but then to
: To do so I need to store the results as a filter, with a given name, so
: the user can use it later on. But I need to store this in disk, as I can
: not trust on the cache or the web session.
: The user should then indicate that the query that is doing now has a
: filter (a previous query) and
Joan,
What you're after is something custom at a layer above Solr, not
something that really fits as something built into Solr.
For example, I've implemented "saved searches" in both Collex www.nines.org/collex> and Flare (it's a proof-of-concept in Flare,
saved only in Rails session scope)
I would like to store the results of a query someway,. Then after the
user analyzes some of the documents (and he/she can take some days to
do it), the user can try to make a query refinement over the previous
result, getting a subset of it.
To do so I need to store the results as a filter, w
On 3/27/07, Joan Codina <[EMAIL PROTECTED]> wrote:
I'm using solr, to build a search engine, and it works great!!
Thanks for the job,guys!
Glad it is working for you.
but...
I need to build a searcher that must allow to perform a "search process"
for a collection of documents. And this se
