To clarify, we'll likely tie it in to our institutional auth system as we have some rough idea of what roles go with which classes (series). But that would just be to "bootstrap" the roles, we would want to mess a bit with them and customize it later.
Chris > Ouch! That's going to be very painful for an administrator (having to > enter each of those 40 roles); not having a good enough sense of what > roles would be provided by the role provider, I would have hoped that > there was a role for the course instructor, a single role that would > cover all students, and perhaps a single role for all TA's. Sounds > like no such luck (for the admin, that is....hopefully by the time > this actually gets used, this would be automated so admin doesn't > have to do them individually...perhaps a local modification allows > you to take advantage of whatever pattern there may be in the role > strings). So, glad to get this info, and yes, I'll switch to a table > design and figure out other ways to overcome my concerns. > > Judy > > On Apr 29, 2011, at 10:35 AM, Christopher Brooks wrote: > > > 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 > > Judy Stern > Educational Technology Services, UC Berkeley > [email protected] > > > -- 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] _______________________________________________
