OpenACS 4 Groups Requirements

-by Rafael H. Schloming, Mark Thomas
+OpenACS 4 Groups Requirements

Prev	Chapter�10.�Kernel Documentation	Next

OpenACS 4 Groups Requirements

By Rafael H. Schloming, Mark Thomas

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Introduction

Almost all database-backed websites have users, and need to model the +

Introduction

Almost all database-backed websites have users, and need to model the grouping of users. The OpenACS 4 Parties and Groups system is intended to provide the flexibility needed to model complex real-world organizational structures, particularly to support powerful subsite services; that is, where one OpenACS @@ -14,7 +13,7 @@ and their departments) or regions (the Boston office, the LA office); a person who is employed by (is a member of) a specific department is also a member of the division and the corporation, and works at (is a member of, but -in a different sense) a particular office. OpenACS 4's Parties and Groups +in a different sense) a particular office. OpenACS's Parties and Groups system will support such complex relations faithfully.

Historical Motivations

The primary limitation of the OpenACS 3.x user group system is that it restricts the application developer to representing a "flat group" that contains only users: The user_groups table may contain the