...
Different membership requirements can be configured by different populations. Note: any admin can assign requirements
| Requirement | Who can assign |
|---|---|
| Active at Penn | Power users |
| Penn employee | Power users |
| ISC (IT dept) | ISC employees |
| Pennant team members (Banner team) | Pennant team members |
Make sure you are ready for the requirement of group
See what will change if you apply the requirement in the membership screen. Note: ignore groups listed, those will not be removed, only other types of subjects
Click "Advanced"
Make sure you are ready for the requirement of folder via UI
This only works if the number of ineligible memberships is not very large
Look at memberships in a folder.
Find which will be removed. Note: ignore groups listed, those will not be removed, only other types of subjects
Make sure you are ready for the requirement of folder via report
Have the Grouper admin run a SQL report and export as CSV or make a Grouper report
| Code Block |
|---|
select
gmlv.group_name,
gm.subject_id,
gm.description
from
grouper_memberships_lw_v gmlv,
grouper_members gm
where
gmlv.list_name = 'members'
and gmlv.group_name like 'penn:isc:ait:apps:outsystems:groups:%'
and gmlv.member_id = gm.id
and gmlv.subject_source = 'pennperson'
and not exists (
select
1
from
grouper_memberships_lw_v gmlv2
where
gmlv2.list_name = 'members'
and gmlv2.group_name = 'penn:community:activeNonAlumniWithPennname'
and gmlv2.member_id = gmlv.member_id) |
Assign a requirement to group
...