isClubRep should be a live attribute #65

New Issue

merenber · 2022-06-30T20:01:30-04:00

merenber commented

2022-06-30 20:01:30 -04:00

Currently the is_club_rep function (in ceod/model/utils.py) uses the maximum of a user's members and non-member terms to determine whether they are a club rep or not. This is incorrect - we should only look at whether the user has a non-member term entry for the current term.

This implies that the isClubRep LDAP attribute should be automatically updated at the beginning of every term. We should create a new API endpoint (e.g. /api/members/updateisclubrep) which will get called on a cron job (like we already do for the shadowExpire attribute).

Currently the `is_club_rep` function (in ceod/model/utils.py) uses the maximum of a user's members and non-member terms to determine whether they are a club rep or not. This is incorrect - we should only look at whether the user has a non-member term entry for the current term. This implies that the isClubRep LDAP attribute should be automatically updated at the beginning of every term. We should create a new API endpoint (e.g. `/api/members/updateisclubrep`) which will get called on a cron job (like we already do for the shadowExpire attribute).

j23leung self-assigned this 2022-11-27 00:03:32 -05:00

j23leung referenced a pull request that will close this issue

2023-05-27 19:02:52 -04:00

WIP: #65 isClubRep fix #93

merenber added the

priority

low

label 2023-10-14 22:19:41 -04:00

Sign in to join this conversation.