Index: openacs-4/packages/acs-core-docs/www/groups-requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/groups-requirements.adp,v diff -u -r1.4 -r1.5 --- openacs-4/packages/acs-core-docs/www/groups-requirements.adp 25 Apr 2018 08:38:27 -0000 1.4 +++ openacs-4/packages/acs-core-docs/www/groups-requirements.adp 3 Sep 2024 15:37:32 -0000 1.5 @@ -1,16 +1,22 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {Groups Requirements} +{/doc/acs-core-docs/ {ACS Core Documentation}} {Groups Requirements} Groups Requirements +

-Groups Requirements

<authorblurb>

By Rafael H. Schloming, Mark -Thomas

</authorblurb>
+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 grouping of users. The OpenACS 4 Parties and Groups @@ -165,7 +171,7 @@ who has registered with an OpenACS site. A user may have additional attributes, such as a screen name.

The data model should enforce these constraints:

40.10 A user must -have a non-empty email address.

+have a nonempty email address.

40.20 Two different users may not have the same email address on a single OpenACS installation; i.e., an email address identifies a single user on