[sakai2-tcc] VOTE: Functionality Changes for 2.9: Soft Delete

Matthew Jones jonespm at umich.edu
Fri Aug 19 09:52:50 PDT 2011


+1

I can still see users emailing support to get their site back even after the
gracetime is passed. Maybe it should be longer than 30 days by default.
(Maybe ~90 days?) Otherwise it's a useful cleanup feature.

On Fri, Aug 19, 2011 at 12:29 PM, Seth Theriault <slt at columbia.edu> wrote:

>
> +1.
>
> Seth
>
> Beth Kirschner wrote:
>
> > Having not received any further discussion, I'd like to open this issue
> for a vote, with the voting OPEN until Friday, August 19th at 23:59 UTC.
> >
> > As a reminder, this is a public, on-list vote with a "+1" signifying
> approval. Per our governance documents, a -1 vote must be accompanied by a
> detailed explanation. A single -1 vote based on a material objection will
> block action. However, -1 blocking votes can be overridden by a 2/3 majority
> roll call vote of active TCC members.
> >
> > - Beth
> >
> > On Aug 9, 2011, at 5:23 PM, Beth Kirschner wrote:
> >
> >>
> >> At the LA Project Coordination Meetings the following functionality
> changes were proposed for the 2.9 release: Inclusion enhancement for soft
> delete of sites & resources. I'd like to put it to a vote next week, but
> please share any concerns or questions now. I've pasted previous comments
> below.
> >>
> >> Thanks,
> >> - Beth
> >>
> >>
> >>> Begin forwarded message:
> >>>
> >>>> From: John Bush <john.bush at rsmart.com>
> >>>> Date: August 1, 2011 10:07:54 PM EDT
> >>>> To: Steve Swinsburg <steve.swinsburg at gmail.com>
> >>>> Cc: "sakai2-tcc at collab.sakaiproject.org Committee" <
> sakai2-tcc at collab.sakaiproject.org>, John Bush <john.bush at rsmart.com>
> >>>> Subject: Re: [sakai2-tcc] New feature - Soft deletion of sites
> >>>>
> >>>> ah then that might just handle it, nice, maybe just a test case then
> >>>>
> >>>> Not sent with my iphone.
> >>>>
> >>>> On Aug 1, 2011 7:06 PM, "Steve Swinsburg" <steve.swinsburg at gmail.com>
> wrote:
> >>>>> It's been a while since I worked on this, but I thought I built in a
> provision where admin users can issue another delete on a softly deleted
> site, and then it is purged immediately. And the soft delete is only for
> normal users (and they don't get the ability to do the extra delete)
> >>>>>
> >>>>> File a Jira so we can track it.
> >>>>>
> >>>>> cheers,
> >>>>> Steve
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 02/08/2011, at 11:59 AM, John Bush wrote:
> >>>>>
> >>>>>> 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
> >>
> >>
> >
> > _______________________________________________
> > sakai2-tcc mailing list
> > sakai2-tcc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >
> >
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110819/ec99bb1a/attachment-0001.html 


More information about the sakai2-tcc mailing list