Hi Judy, > I actually had written a comment on the jira ticket (MH-5584) that > addresses why I opted not to do a table. (Anticipated a comment just > like yours!) I also figured that "a lot of roles" for a single Series > was an edge case; if you think there's a common scenario where this > isn't the case, describe it to me, and I'll iterate further on the
Not sure what a lot means, but if I look at our current auth system, we have a bunch of roles institutionally that represent the students we might want to view a particular video. Here's a scenario, a first year computer science course with 5 on campus sections and 3 off campus sections. The lead instructor is going to be recorded, and students from all sections can see his videos. For each section we have "subroles"; instructor, students enrolled, students who are auditing, tas, markers. If we want everyone to have access this means (5+3)*5=40 roles. I think this would be both our "worst case" as well as a "not so uncommon" case. Just some thoughts, I'll visit that ticket too... Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
