[cle-release-team] [sakai-pmc] Proposal: Add Delegated Access as a Sakai core tool

[Bryan Holladay]

Could you add the link to the email archive (or the tool)?  The only tool I
can think of is the one that allows you to modify the realm permission
templates and existing sites.  If that's the one, then they are not related
in any way other than they both work with Sakai.


On Tue, Dec 10, 2013 at 4:06 PM, Berg, Alan <A.M.Berg at uva.nl> wrote:

>  Hi fellow hard workers,
>
> I like Bryans proposal. I was just wondering if there is any comparison
> with the work of the Spanish that was also recently mentioned on the dev
> list. Are these complimentary tools or does this contrib tool take
> precedence due to its maturity.
>
> Regards,
>            Alan
>
>
> Alan Berg
>
> Innovation working group
> On the use of ICT in Education & Research
> University of Amsterdam
>      ------------------------------
> *From:* sakai-pmc-bounces at collab.sakaiproject.org [
> sakai-pmc-bounces at collab.sakaiproject.org] on behalf of Bryan Holladay [
> holladay at longsight.com]
> *Sent:* 10 December 2013 21:30
> *To:* Sakai Development (sakai-dev at collab.sakaiproject.org);
> sakai-pmc at collab.sakaiproject.org;
> cle-release-team at collab.sakaiproject.org
> *Subject:* [sakai-pmc] Proposal: Add Delegated Access as a Sakai core tool
>
>   *Proposal*
>
> Add Delegated Access as a Sakai core tool
>
>
>  *Rationale*
>
> Sakai doesn't have a verbose administration feature set and requires
> institutions to grant too much or too little access for users who shouldn't
> have full administrative privileges.  Delegated Access allows
> administrative users to choose who can access which sites and which
> permissions they have and tools they can view.  Site access through
> Delegated Access doesn't effect Sakai performance and doesn't show up in
> the site's membership list.  Only step required for an institution to start
> using Delegate Access is to add site properties (or leverage existing site
> properties) to describe the hierarchy.
>
> Delegated Access is a contrib tool, currently in use at a number of
> institutions including Columbia (2 years in production) (I wish I had a
> list of all production instances!  I know of at least 10 others, but I
> don't want to post them w/o permission).  This tool has been proven to
> handle scalability as well as functionality.  It is built off of wicket and
> the hierarchy tool and is running in both Oracle and MySql production
> instances.  It is highly customizable with several sakai.properties to
> taylor the tool to your specific use case. [1]
>
> Delegated Access is currently deployed on the nightly+experimental server
> [2].
>
> Delegated Access is currently maintained by Bryan Holladay and supported
> by Longsight. Longsight will continue to support this application and hope
> the community will adopt it as a standard for delegating access to
> departmental administrators.
>
>
>  *Vote*
>
> Read the rationale above. A material objection (indicated by a -1 and
> accompany reasoning) raised by a Sakai PMC member will block this proposal.
>  Other opinions are welcome, indeed encouraged. Silence equals consent.
> Discussion should be on the sakai-dev list unless of a private nature in
> which case I am happy to correspond off list. Objections must be received
> before Tuesday 17th December 2013 (one week from now).
>
>
>  *Links*
>
>
>  1. https://confluence.sakaiproject.org/display/DAC/Delegated+Access+Tool
>
> 2. http://nightly2.sakaiproject.org:8085/portal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131210/d9d9f122/attachment-0001.html