[Portfolio] [Building Sakai] scaling for university-wide portfolio

Stephen Marquard stephen.marquard at uct.ac.za
Thu Aug 13 07:40:51 PDT 2009

I can't comment on the portfolio aspect at all, but from the users + groups side, the underlying services are OK with lots of users in a site and lots of groups.

We have a site of 25K+ users, and have sites (of around 1500 users) with 120+ groups.

However, it does somewhat depend on the tool. Any tool that iterates through the groups one-by-one to do some particular operation (rather than using the more efficient API calls to do things like find out which groups a user belongs to) may run into performance problems.

>>> Charles Hedrick <hedrick at rutgers.edu> 8/13/2009 4:33 PM >>> 
Rutgers is in the process of building a portfolio for all of our  
undergrads. This is 10-50K users (depending upon whether we break them  
up into cohorots) in a site. But it also can end up with thousands of  
groups in a site. We're likely to have to use groups to define  
advisors and programs.

Has anyone tried very large sites? Can anyone guess how large numbers  
of groups in a site will work?

The complexity in our planning is that we're likely to be using a  
single portfolio for many purposes. We have all kinds of special  
programs, many of which in the long term will want to look at how  
their program is working, and also provide advise to students. But we  
want all of the activities of these prograrms to show up in a single  
portfolio, since (1) we think it's not practical for students to have  
more than one portfolio for their "general" life at the University,  
and (2) we want the possibility of doing broader assessment of student  

In the short run, I'm looking at creating a process for students to  
submit items for review. It will give them a list of groups they're a  
member of and the reviewers in those groups. So they'll end up sending  
the item to a particular faculty member to review, but we'll also  
capture which group was involved. That will be needed for producing  
reports for a specific program.

Review will use a feedback form based on a rubric.

Has anyone else tried something like this?

sakai-dev mailing list
sakai-dev at collab.sakaiproject.org

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

More information about the portfolio mailing list