[Design] [Cosmo] [Proposal] Fwd: [service-dev] Account deletion

[Mimi Yin]

Moving this thread over to the design list.

The issues are:
1. How do we provide a way for users to delete Hub accounts.
2. And when they delete those accounts, do we just delete all the  
collections/items in those accounts?

RE: 1: We could add a [Terminate Account] button in the bottom left- 
hand corner of the 'Settings' dialog. That would mean moving the  
[Close] button (which is currently in the left-hand corner] to the  
right-hand side, next to [Save].

[Terminate Account]					[Close] [Save]

RE: 2: When the user clicks [Terminate Account] we close the Settings  
dialog and pop-up a 2nd dialog.

===
Terminate Account
-----
You have <#> collections created or published by your account. Would  
you like to leave any of them on Chandler Hub so that others can  
continue to access them?

[   ] Select all
	[   ] xxxxx
	[   ] xxxxx
	[   ] xxxxx

									[Cancel]	[Terminate Account]
===

Clicking [Terminate Account] takes you to confirmation page:

===
Account terminated!

The following collections were deleted along with your account:
	xxx
	xxx
	xxx
The following collections were left on Chandler Hub:
	xxx
	xxx
	xxx
===

Questions? Comments?

Mimi

Begin forwarded message:

> From: "Brian Moseley" <bcm at osafoundation.org>
> Date: November 27, 2007 1:05:20 PM PST
> To: "Chandler Hub" <service-dev at osafoundation.org>
> Subject: Re: [service-dev] Account deletion
> Reply-To: Chandler Hub <service-dev at osafoundation.org>
>
> On Nov 26, 2007 1:38 PM, Jared Rhine <jared at wordzoo.com> wrote:
>
>> For reference, Hub users have no advertised mechanism to remove their
>> accounts; we just added "delete collection" functions.  There is a
>> backend "delete account" operation supported, which I assume deletes
>> the account record, all collections owned by that account, and all
>> items not present in at least one other collection.
>
> it actually deletes any item owned by the account as well, regardless
> of how many collections the item belongs to ("hard delete").
>
> in our data model, when you add an item to a collection, you are
> literally creating an association between the existing item and a new
> collection. therefore, user B can't claim that he's "copying" user A's
> item.
>
>> So, where do we stand?  Do I just run the Cosmo CMP "delete account"
>> operation for anyone who asks, but leave it manual operation (ie, you
>> have to send us email)?  Do we provide user affordances for this?  Do
>> we modify any existing algorithms to preserve data in the event of
>> account removal?  Or perhaps deprecate the idea of "account removal"
>> and just set and support some sort of "not active" flag, preserving
>> all their items and collections for subscriptions/copies.
>
> i think we should allow a user to click a link or button to deactivate
> or delete his account. i don't have any particular opinion about
> whether we should hard or soft delete his items, although if we
> implemented an actual copy operation for items, then the question
> would become moot.
> _______________________________________________
> service-dev mailing list
> service-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/service-dev

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