This consultation on the TIER Grouper Deployment Guide is now closed. This consultation was open from March 17, 2017 through April 14, 2017
Document for review/consultation
Document After Consultation: published April 21, 2017:
- Rename basis groups to something else: raw groups? source groups? Instead, use the word basis for the concept below.
- Define the intermediate concept of a grouping as a composite that has a basis group + include group - exclude group.
- The basis of a grouping reflects the grouping's intent and is usually made up of other groups (e.g. reference group for faculty + reference group for staff).
- A grouping's include and exclude groups only have individual members who are exceptions to the grouping's intent. No groups here.
- A grouping is an intermediate-level concept between low-level Grouper primitives (group, composite, subject, memberships) and high-level TIER concepts (reference groups, bundle groups)
- The grouping model can be applied in all situations and helps to clearly define the intent and exceptions of any group.
- Policy groups should be implemented as groupings to easily allow individual exceptions to the policy.
|Julio Polo|| ||Discussed in TIER API WG. Relaxed requirement for access policy to only contain reference groups and showed how existing model could deal with individual exceptions.|
|2||Hyperlink in PDF behind|
"http://software.internet2.edu/grouper/release/2.3.0/" on page 14 links to Grouper 2.2.x download folder.
|Correct hyperlink or perhaps generalize to refer to "latest"||Scott Cantor|| |
|3|| || || || || |
|4|| || || || || |