Tasks for 2.5.0 have been completed. We're nearing the end of the QA cycle and A lot of general regression testing has been going on for the past few months - the changes have likely been reviewed via this method of testing

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

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.

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.

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.