[ 
http://opencast.jira.com/browse/MH-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27532#comment-27532
 ] 

Judy Stern commented on MH-7787:
--------------------------------

Here's text I think we can use:

New functionality for Matterhorn 1.2 allows you to assign access privileges to 
Series, in order to limit who can view Recordings that are part of each Series. 
When you create or edit a Series, you will find a Privileges section, in which 
you can assign View privileges to roles existing in the system
[insert screenshot here]
Any Recordings that are part of that Series  can be viewed in the Engage 
environment only by those users that have roles that have been given View 
privileges for that Series. If you want a recording to be viewable by all users 
whether logged in or not, ensure that the View checkbox for "Public (no 
authorization required)" is selected.  (Future versions of Matterhorn will 
extend this functionality to provide editing/management privileges to roles you 
select.)

You (or whoever is configuring Matterhorn) will want to provide your own roles 
and users, but out-of-the-box you will find that Matterhorn has the following:

Roles are SERIES_1_STUDENT, SERIES_1_INSTRUCTOR, SERIES_1_ADMIN thru 
SERIES_10_STUDENT, SERIES_10_INSTRUCTOR, SERIES_10_ADMIN as well as two 
additional roles: ROLE_ADMIN, ROLE_USER, 

Users are student1 through student200; admin1 thru admin10; instructor 1 thru 
instructor10. Passwords for all users are identical to usernames. 
Each user has a series-specific role, i.e. instructor1 and admin1 have roles 
SERIES_1_INSTRUCTOR and SERIES_1_ADMIN. Roles for student users match the last 
digit in their username, e.g. student3,  student43, and student123 all have 
role SERIES_3_STUDENT;  student10, student 70, and student 100 all have role 
SERIES_10_STUDENT.  
All users have role ROLE_USER. 
ROLE_ADMIN is currently only assigned to the Matterhorn administrator, "admin". 
 


Series in the system out-of-the-box are Series #1 thru Series #10. Each of 
these is preset to allow for View privileges for those in student, instructor, 
and admin roles matching the series name. That is, Series #1 has View 
privileges assigned to those with SERIES_1_STUDENT, SERIES_1_INSTRUCTOR, and 
SERIES_1_ADMIN roles.  You can alter these privileges easily: on the Series 
page, click Edit for the Series for which you want to edit privileges. 

When you create a new series (using the Add Series button on the Series tab OR 
by entering it on the Schedule Recording or Upload Recording) it is given 
public view access by default. Note, however, that there is a known bug which, 
in the latter case (that of creating the series when scheduling or uploading) 
causes the Edit Series UI to not properly show that it has Public View access 
(the Public View checkbox will be unchecked). 

To provide your own roles:
[Adam, fill in here]

To edit your own users: 
[Adam, fill in here]



> add to release notes: Roles explanation
> ---------------------------------------
>
>                 Key: MH-7787
>                 URL: http://opencast.jira.com/browse/MH-7787
>             Project: Matterhorn Project
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 1.1 
>            Reporter: Judy Stern
>            Assignee: Judy Stern
>            Priority: Critical
>             Fix For: 1.2
>
>         Attachments: privilegesUI.png
>
>
> We should add something to the release notes that explains how the demo data 
> is formatted, and suggesting that configurer replace the text with something 
> that does describe the institution's roles format as well as explain how to 
> unpackage the jars to make the process easier. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to