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
Currently the
is_club_repfunction (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).