|
[
Permlink
| « Hide
]
Seth Theriault added a comment - 16-Jul-2007 21:05
Attached patch works tested against 2.4.x
Zhen can probably merge this in -
But just want to clarify. There are 2 entry boxes on the add participants page - one for account ids and one for email address based guest accounts. Does this allow an email address in the first box (currently not allowed)? There is also a prohibition of certain domains in the 2nd box for email addresses, sakai.property controlled. So for example, with this patch, I guess someone could put in jleasia@umich.edu in the first box, which is for account names, and not be able to put jleasia@umich.edu in the second box, which is for guest accounts, which here can't have @umich.edu. I think it's a useful change, just want to see if we need to change the text on the page or something to make it clear what is going on. Example from our local version attached. We don't allow @uct.ac.za in guest emails, but I could add myself using my Sakai account email address (stephen.marquard@uct.ac.za) in the box, rather than specifying a username (as these are numeric, almost nobody knows other people's usernames offhand).
This is a revision of the screen that UCB is about to implement. We have had a *lot* of confusion and problems as a result of implementing this patch without a concomitant UI change.
Our users don't seem to have had difficulties with the UI.
A twist in the tale (looking at UCB's reference to official email addresses) is that in our configuration, users can change their account email address. This defeats adding someone by their official address (because they're using another one, e.g. gmail). So what we ideally want to be able to do is check against an alternate authoritative / canonical source, e.g. the email address from the system mutable profile, that the user cannot change. We haven't implemented this yet, however. It does look like UCT altered the instructional text, though. By referencing the UI, I was largely endorsing John's suggestion that the text be changed to make explicit the differences between the two boxes.
BTW, "official email address" is not entirely accurate here. You have to maintain a private ,berkeley.edu domain address (not necessarily @berkeley.edu), but you can also optionally list and expose another of your choosing. Those addresses can be used to add campus participants, too. The LDAP entry is made unique by an otherwise meaningless (to the user) numerical string, the LDAP UID. Ugh. Josh's patch has been merged in r35117.
UI has also been changed according to UCB's mockup. The demo sakai.properties file has been changed to reflect the configuration variable changes. Institutions need to adjust those variables accordingly. Thanks, - Zhen |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
Modify WS Setup to allow for adding participants via email address
