[Design] [Last call] Bug 5403: Re-importing/Re-subscribing to a Trashed item

[Morgen Sagen]

On Apr 6, 2006, at 10:26 AM, Alec Flett wrote:

> Mimi Yin wrote:
>> 2. Is there a way for us to over-write the "version" of the item  
>> that's in the Trash with the "version" of the Item that's coming  
>> in on re-Import/re-Subscribe? In other words, the Item in the  
>> Trash has a bunch of stuff on it that says what SmartCollections  
>> it was a member of before it was Trashed. the Item in the re- 
>> Import/re-Subscribe doesn't?
>>
> This is a tricky case because it means we have to distinguish  
> between "overwriting" an item that's in the trash, vs.  
> "overwriting" an item that's in another collection.
>
> Personally I think all of this is totally feasible, and I think it  
> would be nice to keep items from magically reappearing after they  
> have been trashed, but the more special cases we have, the more  
> bugs it will expose or create in other places where the trash comes  
> into play. We just have to decide if this is a case where improving  
> the experience for this case is worth potentially strange behavior  
> (bugs) in other trash-related cases.
>
> Here's my vote: we start with the simpler option that morgen  
> proposed - that when something comes out of the trash, that it gets  
> restored to all collections (since that has very few edge cases in  
> the code, and much of that is already implemented) and see if the  
> magically-reappearing-items issue actually bothers people?  
> Personally this is the kind of thing that I could imagine shipping  
> even 1.0 with and waiting until we have a wider audience to  
> complain about it...:)
>
> Alec

+1:  I agree with everything Alec said.

~morgen