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

[Mimi Yin]

BACKGROUND
https://bugzilla.osafoundation.org/show_bug.cgi?id=5403
There have been some questions about how to deal with Items that have  
been Trashed and then are resurrected as a result of an Import/ 
Subscribe.

Scenario:
1. I subscribe to the Office calendar with read-write privileges.
2. I Trash an event I added to the office calendar from My calendar.  
Movie night: The Natural History of Porcupines and Skunks. (which is  
a GREAT movie btw). This event is also on my Work calendar and on my  
Movies calendar.
3. This is where I get stuck, I can't think of a good reason for Step  
3. Jeffrey and Morgen please step in if you can think of one.
4. Somehow, I end up re-importing this event into my Chandler either  
via a file import OR sharing subscription.

What does Chandler do?
1. Keep the event in the Trash, thereby removing it from the  
collection you just subscribed to OR whichever collection you chose  
as the destination of your file import; OR
2. Remove the event from the Trash so that it can show up in the  
collections; OR
3. Option 2 PLUS Restore the event to all the collections it used to  
belong to: Work, Movies, My, Office. (This is what we do if the user  
hand-removes an item out of the Trash. When we have UNDO, this will  
be what we do when the user hits Cmd/Ctrl-Z after Trashing an item.)

PROPOSAL
I think there is a difference between the user explicitly dragging an  
item out of the Trash and Chandler removing an item out of the Trash  
as a result of the user re-importing that item via Collection import.

The user may not even be aware that items have been removed from the  
Trash, because the user isn't really thinking in terms of unique  
identifiers.

So it would be like: You have a text file on your desktop. You put it  
into the Trash.

Then you go up to some file server and pull down the text file again  
onto your desktop.

I would expect that the text file I trashed would still be in the  
Trash + I'd have a new version of the text file on my desktop.

Since we have unique identifiers in Chandler, we can automatically  
reconcile the items in the Trash and the items in the Import. But I  
don't think we should unify the behavior that results from:
1. Importing/Subscribing to an item that has been put in the Trash; AND
2. The user explicitly removing an item from the Trash or undoing  
Trashing an item

While the underlying implementation semantics are the same (item gets  
taken out of Trash), for the user, the context/reasons for removing  
the item from the Trash are completely different. (ie. the user may  
not even be aware that an item has been restored from the Trash as a  
result of Importing or Subscribing)

So I think the right thing to do is to have the Import and Subscribe  
behave in accordance with Jeffrey's A proposal, which corresponds to  
Proposal #2 above: Remove the item from the Trash, but don't restore  
it to all the collections it used to be a member of.

And stick with the B proposal, which corresponds to Proposal #3  
above: Remove the item from the Trash and restore it to all the  
collections it used to be a member of, for when users explicitly  
remove an item from the Trash or undo Trashing an item.

Mimi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060315/f097836f/attachment.html