Recurring signup modification/deletion
Status: Abandoned
Brought to you by:
jshaver
Menu
▾
▴
#27 Recurring signup modification/deletion
As I understand it, if a user creates a 'real' signup
on the same day where there is a recurring signup, the
recurring signup becomes out of the system's control on
that day. When the signup table is written for that
day, all of the recurring signups are pulled from
default.csv into [date].csv. This makes the recurring
signups loggable, but it also brings an extra step into
removing/modifying the recurring signups.
The signup table for a given day in the future should
be modified if a recurring signup that affects that day
is modified or deleted and at the moment that isn't
happening. Maybe we shouldn't even write a recurring
signup to the 'real' signup table until the day of the
recurring signup?
Logged In: YES
user_id=713937
Just tried this on my local copy and the problem is - how do
you handle when a change to a recurring signup comes into
conflict with an existing signup? A change might cause
someone who is alternate to be "floating" over an open
priority spot (I suppose we could exhaustively go through
all days and checked for promotions?!?) OR a recurring
signup might overlap another user's signup?
Logged In: YES
user_id=829347
I know it may be difficult to implement this, but I think it
should check the future days, promote signups when
appropriate, and not overwrite existing signups. It must
tell the person managing the recurring signup what it did,
though. If they would rather have it blow away an existing
signup, they can do it manually if it's that important. The
system should just tell them which signups conflict.