[Deploying Sakai] OAE Administration functions
oliver at media.berkeley.edu
Sat Sep 10 05:42:57 PDT 2011
I'm not entirely clear on what you're asking for, John. Dawn offered a
very brief elaboration of each requirement, but did not, AFAICT, offer
any justifications. As Eli points out, more than one item in the UCB
list overlaps with Dawn's.
I may again be misinterpreting, but outside of the ability to add/remove
a user from a group, I'm not sure which of the items involves doing
something "to" the user. Presumably, becoming a "superuser" will allow a
top level admin a great deal of latitude in that regard.
Perhaps others will disagree, but based on experience, most of the
requirements captured on this thread thus far seem like basic
capabilities necessary to supporting a system like OAE across an enterprise.
On 9/10/11 1:21 AM, John Norman wrote:
> I missed this in the list move. I would like to encourage Berkeley to
> explain reasons as Dawn did, because I'm not sure we want too many
> things to be done to the user by an admin. On the other hand, I would
> add to the list (and I believe it is in the specs) the ability to
> delegate admin powers within a certain scope of the site and the way
> to do something on behalf of another user for certain roles beyond
> administrator (TA acting for professor, Secretary acting for Head of
> On 2 Sep 2011, at 17:43, Eli Cochran wrote:
>> Our Director of Operations just sent me an email this morning
>> stressing his need for Administrative tools. He summed it up with the
>> following list which overlaps Dawn's list rather nicely.
>>> As admin, I want to be able to look up a user's account information
>>> As admin, I want to be able to see a user's login history
>>> As admin, I want to be able to become a particular user
>>> As admin, I want to be able to see a user's group memberships
>>> As admin, I want to be able to add/remove user from a group
>>> As admin, I want to be able to email a specific user
>>> As admin, I want to be able to see how many users are currently online
>> - Eli
>> On Aug 14, 2011, at 10:36 PM, Calvert, Dawn 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
>>> • 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.
>>> Charles Sturt University
>>> | ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | ONTARIO
>>> | ORANGE | SYDNEY | WAGGA WAGGA |
>>> 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.
>>> LEGAL NOTICE
>>> 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 <http://www.peqab.ca>
>>> Consider the environment before printing this email.
>> ...... .... ... .. . . . . . . . . . .
>> Eli Cochran
>> project manager, CalCentral project
>> Educational Technology Services, U.C. Berkeley
>> production mailing list
>> production at collab.sakaiproject.org
>> <mailto:production at collab.sakaiproject.org>
>> TO UNSUBSCRIBE: send email to
>> production-unsubscribe at collab.sakaiproject.org with a subject of
> John Norman
> Director - CARET
> University of Cambridge
> john at caret.cam.ac.uk <mailto:john at caret.cam.ac.uk>
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the production