[thelist] Destroy and search - Update

[Chris Hayes]

1) I'm respondinding in a new reply as I can't remember if I committed the 
sin of just replying to a post and changing the subject, something I'm used 
to amongst my Outlook Express friends

2) I worked out a solution, and it's quite simple:

Using Verity as the search engine, I index a batch of poems in Collection A. 
I then merge this collection with Collection B (initially blank)

I delete the poems.

Come the next batch of poems I repeat the process, overwriting Collection A 
with the new batch, and merging that with Collection B.

Collection B is the master collection containing all the indeces of poems 
received over time, Collection A is temporary.

It works.

If anyone knows if and how I can do this with MSSQL full text catalogues, or 
if as suggested these catalogues actually contain the entire , intact poems 
I'd appreciate the feedback.

Until them I'm going with Verity.

Have fun, I lurve you guys.

Chris

> ----- Original Message ----- 
> From: "Shawn K. Quinn" <skquinn at speakeasy.net>
> To: <thelist at lists.evolt.org>
> Sent: Saturday, October 29, 2005 12:12 AM
> Subject: Re: [thelist] Destroy and search
>>> If not, maybe the situation explained will make things clearer.  The
>>> client
>>> is happy for me to hold this data temporarily but not to retain it.  I
>>> want
>>> users to be able to search this data after it has gone.
>>
>> I could be missing something here, but I don't think this is possible.
>> Either you have the data or you don't. I don't see how there's a middle
>> ground where you have just enough data for the users to search but not
>> enough to reconstruct the original.
>>
>> Without knowing more about the exact circumstances and reasoning that
>> your client doesn't want you retaining the data, it's difficult if not
>> impossible to suggest ideas.
>
> Say it's copyright poetry, and for legal reasons I can't retain the poem.
>
> What I can do is index keywords related to a poem ID so it is searchable
> although I don't actually store the poem anywhere.
>
> This is the avenue I'm exploring but I certainly don't want to reinvent 
> the
> wheel, I don't want to write an bespoke search engine.