Child pages
  • Roster2
Skip to end of metadata
Go to start of metadata

Roster2

About

Roster2 is a replacement for the standard Roster tool that comes with Sakai. Roster2 is a lightweight tool, written using JavaScript and TrimPath.

Roster2 maintains the feature set of the standard Sakai Roster tool, with minimal differences in user interface, while providing increased integration with Profile2, the new default profile tool in Sakai 2.7. Roster2 also provides several requested features and bug fixes that are currently unimplemented in the standard Sakai Roster tool.

Roster2 was developed by the Centre for e-Science, Lancaster University, UK, as part of the JISC-funded Collaborative Research in Business (CRIB) project.

Lancaster University have run Roster2 in production on Sakai 2.7.x since September 2010 and on Sakai 2.8.x since July 2011.

Release

Roster2 version 1.0.0 was released on February 1st, 2012. In addition, there is a 1.0.x maintenance branch available which will receive updates.

Roster2 can be deployed as a Sakai indie project or built from source.

Compatibility

Roster2 is known to work with Sakai 2.7.x, 2.7.1, 2.8.x, 2.9.x, and Sakai trunk.

Roster2 requires Profile2 for full-functionality (Profile2 versions 1.3.x, 1.4.x and 1.5.x recommended and supported).

Preview

Roster2 can be previewed on the Sakai trunk experimental server.

These screen captures show Roster2 in use by the Sakai Administrator user.

Users who have permission to administrate a particular worksite (i.e. those who have the site.upd permission set), are allowed to set roster permissions for all site members within the tool itself. The permissions view is shown above.

Settings

Roster2 maintains support for the standard Roster properties configured in sakai.properties, and includes some new ones of its own. Roster2 is configurable via the following settings in sakai.properties:

Permissions

Roster2 maintains support for the standard Roster permissions set, with the exception of the roster.viewofficialphoto permission (Roster2 displays whichever profile photo is provided by Profile2).

The following table shows the default permissions:

 

 

roster.viewallmembers

roster.viewhidden

roster.viewgroup

roster.viewenrollmentstatus

roster.viewprofile

roster.export

Site

 

 

 

 

 

 

 

 

Instructor

Y

Y

Y

Y

Y

Y

 

TA

N

N

N

N

Y

Y

 

Student

N

N

N

N

Y

N

 

Access

Y

N

N

N

Y

Y

 

Maintain

Y

N

Y

N

Y

Y

Group

 

 

 

 

 

 

 

 

Instructor

N

N

N

x

x

x

 

TA

Y

Y

Y

x

x

x

 

Student

Y

N

Y

x

x

x

 

Access

N

N

Y

x

x

x

 

Maintain

N

N

N

x

x

x

 

 

 

 

 

 

 

 

 

Key

x

The code does not check this permission in this scope

 

 

 

 

 

 

Y

The permission is granted by default

 

 

 

 

 

 

N

The permission is denied by default

 

 

 

 

 

 

 

 

 

 

 

 

Permission Definitions

 

roster.viewallmembers

roster.viewhidden

roster.viewgroup

roster.viewenrollmentstatus

roster.viewprofile

roster.export

 

 

 

 

 

 

 

 

Site-Scoped

 

can view all members of a site.

can view members of a site who are otherwise not visible, having invoked a right to privacy via the Privacy Manager API. Implementation of the API is optional.

can filter on all groups and sections

has access to the Enrollment Status view. The availability of the Enrollment Status view is dependent on the appropriate implementation of the Course Management API.

can click lnks in the Overview page to individual user profiles in the Profile2 tool and view member photos or images uploaded to the Profile2 tool in the Pictures view.

can download the currently displayed data in the Overview and Enrollment Status views

 

 

 

 

 

 

 

 

Group-Scoped

 

limited to viewing only members of the groups and sections in which a user with the permission is also a member.

limited to viewing only members of the groups and sections (in which a user with the permission is also a member) who are otherwise not visible, having invoked a right to privacy via the Privacy Manager API. Implementation of the API is optional.

limited to filtering only on the groups and sections in which a user with the permission is also a member

 

 

 

  • No labels