Repeating Events

[thedekel]

There should be the option to create a separate event object that acts as a template for repeating event. Every week an event object should be generated. This new event is a standard event and can be edited or removed if need be.

The Repeating event object will be displayed to admins on their org's page and they can create additional events from there (or from the "events list" page).

In order to create an event the following fields need to be specified:

• Title - to be preceded by the date of the event, i.e. "Weekly Meeting" will become "Weekly Meeting 9/16/2012"
• Start/Stop Time - same as normal events
• Description - this will be some static text that is used as the description for these events.
• e-mail for description - this should be a checkbox that, if selected, will cause the org leader(s) to receive an e-mail before the event is generated asking for the exact description for the event. If nothing is specified than the default description is used instead.
• duration/stop date - the date after/on which no more events should be generated.
• org - the org that this is created under
• Place - implement as a field, it'll be used once the Place field on normal events is used

[thelastnode]

This is non-trivial. For example, what if I want to delete a recurring series, or edit the recurring series and then edit a specific event.

Look at Google Calendar or Outlook's implementation of this stuff - when the user edits anything recurring, the option should be presented to edit the series or the instance.

Changes to the series should affect all events, and changes to the instance should only override the specific fields they modify. For example, if I have a recurring series, and I edit the time of one event, then the title of the series, the title change should be reflected everywhere, but that one event should retain the new time.

[thedekel]

that's why the repeating event is a new object and not just a modified event object.

Changes to the "repeating event" object is reflected in future events (since new events aren't generated until the week of the event), but past events are left unchanged. Since the events themselves are separate from the "repeating event" object, we can change them without affecting future events.

Although, we may want to include some sort of link to the parent "repeating event" from a generated event. The use case is that an org admin wants to change a repeating event, but has mistakenly opened a specific event.