[sakai2-tcc] New feature - Soft deletion of sites

[John Bush]

yeah I think the use case is more admin folks deleting a myws site as a one
off to fix something or another, not the users themselves.
Probably didnt describe that clearly, you want me to enter jira so this
doesnt get lost?

Not sent with my iphone.
On Aug 1, 2011 5:04 PM, "Steve Swinsburg" <steve.swinsburg at gmail.com> wrote:
> Hi John,
>
> A normal user can't delete their own my workspace. I get:
>
> Alert: Your Workspace may not be deleted with this tool.
>
> However what you propose sounds like a sensible modification since My
Workspace sites are automatically regenerated with content intact.
>
> cheers,
> Steve
>
>
> On 02/08/2011, at 8:22 AM, John Bush wrote:
>
>> I have one question about this. We have a local mod to do soft
>> deletes, which seems fairly similar to this, although it doesn't do
>> the final purging. One thing we've noticed is that it causes some
>> issues with myworkspaces. A lot of times folks delete myworkspaces
>> via the UI in order to have them recreated with new configuration (new
>> tools, etc). With the introduction of a soft delete, since the
>> myworkspace aren't really deleted, they aren't regenerated. This
>> causes people some confusion. We were considering making myws sites a
>> special case, where they are always hard deleted. Right now we are
>> getting around this with manual sql calls that perform the hard
>> delete.
>>
>> Has there been any testing with your work around myws sites? Do you
>> see an issue here for your work ?
>>
>> On Tue, Feb 1, 2011 at 6:04 AM, Steve Swinsburg
>> <steve.swinsburg at gmail.com> wrote:
>>> Hi all,
>>>
>>> I have just finished work on a set of patches that allow sites to be
softly deleted, and then later purged from the system after a given grace
time.
>>> https://jira.sakaiproject.org/browse/SAK-19952
>>>
>>> The way it works is thusly:
>>>
>>> A maintainer of a site deletes that site. If soft deletes are enabled,
the user receives a message about this instead of the normal message. The
site is then, for all intents and purposes, deleted. It does not show in any
lists and users cannot navigate to it. However the site still exists and is
completely intact with all content and user lists. Users with the
appropriate permission (site.visit.softly.deleted) can manually navigate to
the url. They get a message that the site is due to be purged, but can still
act on the site, perhaps retrieving content.
>>>
>>> Normal users of a softly deleted site cannot access the site at all.
>>>
>>> After a configured grace period, a Quartz job purges softly deleted
sites from the system.
>>>
>>> In addition, another permission is added, site.del.softly.deleted. This
allows users with this permission to issue another removeSite call, perhaps
from a webservice or similar, and that will manually purge the site from the
system.
>>>
>>> Some screenshots are in the JIRA.
>>>
>>> I invite you to review this and let me know if you think it is something
that could be voted on for inclusion. It does touch a few areas, and part of
it requires mods deep into the Kernel SQL, so feedback would be great.
>>>
>>> regards,
>>> Steve
>>>
>>> N.B. The client I wrote this for has kindly allowed me to contribute
this to the community.
>>> _______________________________________________
>>> sakai2-tcc mailing list
>>> sakai2-tcc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>
>>
>>
>>
>> --
>> John Bush
>> 602-490-0470
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110801/2be3a447/attachment-0001.html