Groups

Initial Documentation

Project Lead(s): Project Links:

Oliver Heyer, Project Manager

Groups

What the project aims to accomplish and who should benefit from it - explained in clear, simple language.

In brief, this project aims to deliver a coherent, yet flexible user and group membership management UX across a broad range of organizational possibilities both within and outside the site context:

• institutionally defined and provisioned groups, including course rosters, cohorts etc.
• non-institutionally defined groups via Open Social integration, for example Google groups
• user defined, non-provisioned Sakai groups, for example short term project groups within a course
• combinations of the above

Key Deliverables

• UI for representing, creating, and adding groups
• UI for sub grouping an existing group
• UI for adding, deleting and moving group memberships
• UI for associating groups with sites
• UI for finding groups
• AuthZ to support appropriate levels of access to end user administrative functions
• Any required mechanisms for bringing in external users and groups
• Supporting system configuration options
• Relevant UX Design Patterns for reusable elements of groups UI (i.e. searching (for groups, for people), selecting people...)

Which institutions and individuals are committed to it, for how long, and in what roles.

Project Manager:  Oliver Heyer (UCB)

Developers:  Ray Davis (UCB), UC Davis Development team (Jon Gorrono, Thomas Amsler, Michael Wenk)

Interaction Developers:  Eli Cochran (UCB)

Interaction Designers:  Daphne Ogle (UCB), Keli Amann - 1/3 FTE (Stanford), Joanna Proulx - partial (MIT)

UC Berkeley team members are committed to the project for at least 1 year. The availability of resources from Stanford, UC Davis and MIT is largely contingent on the timing and depth of commitment to other looming 3.0 projects.

What other projects, if any, does this project relate to or depend upon?

K2, 3akai and any other new 3.0 projects that have a groups UX component. At this time, all known dependencies on projects external to Sakai are subsumed by K2.

What does the project know and not know about how it will achieve its aims at this point?

What public communication methods are being used, how may a curious person contribute to or track the project?

Ongoing Documentation