[WG: Sakai QA] [DG: User Experience] User Experience] why aseparate step to join sites?

Stephen Marquard stephen.marquard at uct.ac.za
Fri Jul 24 08:43:01 PDT 2009


Sakai 2 permits visiting without being a site member through use of the .auth role, which can have its own set of permissions.

.auth = anyone who is logged in
.anon = anyone at all (even not logged in).

So all of the use cases are supported by the Sakai 2 authz scheme. It mostly just requires some changes in Site Info and the portal to support this correctly.

Regards
Stephen 
 
>>> John Norman <john at caret.cam.ac.uk> 7/24/2009 5:37 PM >>> 
There is a Sakai 2 and a Sakai 3 dimension here too. In the scenario  
mentioned by Hattie where a member of staff is going to a site only to  
see a specific piece of content, that content will more easily be  
shared with groups beyond the site membership - making "join"  
unnecessary /for this use case/.

The implications of a "joinable" site are that the owners want to  
allow a wide group of people to be able to choose whether they become  
members of a site. In this situation it is logical that they should be  
able to visit the site without restriction (but also without a / 
requirement/ to join) and then should be presented with an opportunity  
to join once there together with some information about what  
difference it would make if they join (e.g. receive site  
notifications, ability to post announcements, etc.). Another nice  
option might be an invitation - a bit like a Google Calendar meeting  
invitation - that can be accepted in the invitation.

The options for Sakai 2 are different I think, due to the way access  
controls are linked to site membership.

John




More information about the sakai-qa mailing list