#6 Repeating events

[Jeremy Shaver]

The first iteration/phase of this feature would be
non-linked repeating signups where you can say "repeat
this signup each [week at this time]/[day at this
time]/[month on this day] until [date]" and it will
simply loop over the signup routine adding signups as
necessary.

The next phase will "link" the repeated signups so that
when one is deleted, you are given the option to delete
all future signups related to this repeating signup or
just this ONE signup. Nominally, I think it requires
adding only one field to the user signup files which
indicates that a given signup is linked to other
signups. Maybe a "linking code" number and then any
existing signup with that linking code is related.

The third (and hardest) phase would allow "indefinite"
repeating signups. This will be more tricky and will
require a modification to the yet-incomplete and
unsupported "default.csv" resource files (the automatic
block-out files which can be put into each resource
file). We would have to have signups be automatically
created and associated with a given user. Problem is
doing the consistency tests to make sure the user and
sign-up request still exists.

[Trevor Riedemann]

Logged In: YES
user_id=863786

Jeremy,

This is one feature where you'll want to provide an "on/off switch."

The repeating event feature could be enabled/disabled at the
resource or user level.

We have users that would take every Tuesday 365 days a year -
even if they don't need the resource. I actually had a user ask me
to increase the number of signups and the length of signup rules
because he uses the instrument "so often" it would be easier "if
someone needs it they can come ask me..."

[Jeremy Shaver]

Logged In: YES
user_id=713937

First iteration is done in next release. It is a very
simplistic interface but is functional.