[horde] What to do when removing user

[Mike Bydalek]

I don't think it 100% necessary to remove *all* data that a deleted user
created, due to your shared calendar example alone.  Perhaps what could be
done is to generate a list of everything that user owns, from calendars, to
tasks, to turba contacts, and allow the user to select what items to delete.
Everything else that isn't selected (ie. Kept) could then be changed
ownership to either a designated admin, or the person who deleted the user.

Deleting all the user data isn't even an option in my option.  In my example
alone, if I delete 1 user, I could completely mess things up by deleting
several shared calendars, tasklists, etc.

Hope this helps and is what you are looking for in terms of feedback.

-Mike

> -----Original Message-----
> From: Jan Schneider [mailto:jan at horde.org] 
> Sent: Sunday, June 27, 2004 4:23 AM
> To: Horde::Horde
> Subject: [horde] What to do when removing user
> 
> 
> We are going to implement the application specific methods 
> that get called when a user gets removed from Horde.
> 
> The correct thing to do was to remove *all* data this user 
> created, but this might also involve shared resources, like 
> in Kronolith for example complete shared calendars or single 
> events in shared calendars.
> 
> So the question is, should we do the "correct" thing or 
> should we handle this differentely, more graceful, whatever 
> that means?
> 
> Jan.
> 
> --
> Do you need professional PHP or Horde consulting? 
> http://horde.org/consulting.php
> -- 
> Horde mailing list - Join the hunt: 
> http://horde.org/bounties/#horde Frequently Asked Questions: 
> http://horde.org/faq/ To unsubscribe, mail: 
> horde-unsubscribe at lists.horde.org
>