[Deploying Sakai] OAE Administration functions

Clay Fenlason clay.fenlason at et.gatech.edu
Mon Aug 15 05:34:46 PDT 2011

I think the immediate question is going to be not whether this is
needed, but rather: which items currently on the list would you want
to take out in order to make room for it? A treatment which takes into
account those tradeoffs would be helpful.


On Mon, Aug 15, 2011 at 1:36 AM, Calvert, Dawn <DCalvert at csu.edu.au> wrote:
> A question that has popped up a couple of times is the need for an admin/ support type interface and whether this should be on the Y2 plan.
> Are any other pilot institutions thinking similarly...
> The interface would allow features like:
> •       Become user (so you can see what the user sees)
> •       Superuser (ie, ability to see any site, add widgets, manage any permissions, etc etc)
> •       System usage (how many current sessions, system load, memory etc)
> •       System wide messaging (e.g. ability to push a popup to all users saying we are gonna stop the server in 20mins)
> •       Job scheduler (ability to kick off code at certain times)
> •       A way to add pilot tools/widgets as that wouldn’t be normally accessible by logging in as a coordinator.
> Comments before the this weeks URG would be useful.
> Regards,
> Dawn
> Charles Sturt University
> Give Generously - Support Young Australians
> You can help young Australians to go to University and succeed in their studies by giving generously to the Charles Sturt University Foundation. To find out more or to make a donation go to the Foundation web site http://www.csu.edu.au/special/foundation. Australian donations are tax deductible.
> This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.
> Charles Sturt University in Australia  http://www.csu.edu.au  The Chancellery, Panorama Avenue, Bathurst NSW Australia 2795  ABN: 83 878 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B (ACT)
> Charles Sturt University in Ontario  http://www.charlessturt.ca 860 Harrington Court, Burlington Ontario Canada L7N 3N4  Registration: www.peqab.ca
> Consider the environment before printing this email.

More information about the production mailing list