Thanks, Olaf, for responding. Still hoping to hear from others describing their 
needs re. levels of authorization for *administering* Matterhorn; I'd hate to 
move forward only taking into account the needs of ETH and Berkeley.
Or should I assume that folks are only concerned with authorization as it 
pertains to *viewing* published media? (Thanks, Pete, for giving us input on 
that side of things.) 

Specific responses inline: 

On Sep 9, 2011, at 5:00 PM, Schulte Olaf A. wrote:

> Changed the "Edit" to "Manage". There is "Make changes" also, is that 
> identical to "Manage" (cannot edit that mock-up)?
Many thanks for making those edits! (Balsamiq can be quite annoying at times!)
"Make changes" was simply the wording I used in an alternative design. I was 
using all three ("Manage", "Make changes", "Edit") to mean essentially the same 
thing and just hadn't settled on one; it's the kind of thing we can change 
easily later on. 

 
>> --Or do you need this to be more fine-grained, e.g. something like
>> <http://opencast.jira.com/wiki/display/MH/Extended+Series+Authorization>?  
>> (This
>> is only a sketch to demonstrate what more fine-grained authorization might
>> entail...don't take it too seriously.)
> 
> Having a quick look at your mock-ups, I'd say that the extended authorization 
> is not necessary for us here at ETH. If I understand your distinction 
> correctly...
Good to know. So far I haven't heard that anybody needs Series permissions to 
be more fine-grained than "Manage". 

>> <http://opencast.jira.com/wiki/display/MH/Roles+page> (again just a sketch 
>> as we
>> begin to play with ideas...these may not be at a useful or realistic level of
>> granularity). We'll also need to limit access to capture agents (no sketches 
>> for this
>> yet).
> 
> ... I would speak in favour of having sophisticated "admin" roles instead in 
> that 
> 
> - we would like students to do the trimming, without being able to do 
> anything else or
> - would like to restrict any deletion action (scheduled recordings, 
> recordings) to the actual admin(s).

If a Roles UI (similar to what I sketched) included  "Trim Recordings" and 
"Authorize publishing" (or something like that) as privileges that could be 
checked, wouldn't that meet your needs? (I realize that the current Review/Trim 
UI doesn't separate out these actions, but it seems like it could.) Or am I 
misunderstanding your needs?

>>  let us know if you'd be
>> willing to be interviewed!
> 
> Sure - makes a change from talking about metadata...

Good! We'll be in touch to set something up. 
(But don't assume you're off the hook for talking about metadata! I need to get 
back to you on that, too!)

thanks,
Judy


Judy Stern
Educational Technology Services, UC Berkeley
[email protected]



_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users

Reply via email to