Hi Erik and Will,
Thanks for the suggestions! The *:* is exactly what I was after for question
#1. I was not aware of that syntax.
I would like to be able to save the query itself, however, the users may decide
to pick only some of the documents, all of them and unselect some, etc. The
point of the system is to pick a set of document identifiers that will then be
submitted to another separate system (not Solr based) for processing. For
example, image that each document describes a "prospect". You want to search
all prospects in the system and then create your own "list" of prospects that
you want to send direct mail to. You select these prospects and upload their
ids into a system that will create labels, print envelops, etc.
In a relational database, I could just have these two sample tables:
create table SavedLists
(
userID int not null,
listID int not null,
dateCreated datetime,
listName nvarchar,
listDescription nvarchar
)
create SavedListProspects
(
listID int not null,
prospectID int not null /* this is the id that would come from Solr */
)
The SavedtListsProspects table would contain the relationship between the list
and the prospects in it.
Thanks,
Av
----- Original Message ----
From: Erik Hatcher <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Tuesday, May 22, 2007 9:09:13 AM
Subject: Re: Interesting Practical Solr Question
On May 22, 2007, at 10:07 AM, Will Johnson wrote:
> 2) Each document will be shown to the user with a check box next to
> it.
> I want to user to be able to select certain documents and "save" their
> ids some where else. This is not a problem. However, I also want to
> give
> the user an ability to say "Select All Documents". This would need to
> save the ids of ALL documents found with user's given query and query
> filter (based on the facets that they selected). This list could
> potentially contain over 10,000 documents. Question: How to easily and
> quickly grab the IDs of all these documents?
>
> Why not just save the query itself instead of the id's? if you're
> worried about new docs showing up that weren't available when the user
> saved the docs you could always filter them by a 'createdtime' field
> that gets set when you index the docs.
Ah, good idea with the createdtime! I like it.
> 3) Once the user saves the list, I want them to be able to do further
> searches by do a "negative union" with the set of ids they already
> saved. So for example, if they already saved 1000 ids into one of
> their
> lists, they would need to be able to get results from Solr that match
> their query but are NOT in the set of 1000 ids that they already
> saved.
> Is this possible?
>
> Even more reason to save the queries and not the id's. then its
>
> (query1expr) NOT (query2expr)
But in the use case mentioned, the user is collecting specific
documents not necessarily all of them.
Erik
____________________________________________________________________________________
Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/
