Support

Current behavior:
Events can not recur automatically, each instance has to be created manually.

Desired behavior:
Ability to setup automatically recurring events, for example monthly board meetings

Notes:
1) We need to figure out what kind of recurrence is required, for example:
- every XX weeks on a certain day
- monthly on certain date
- monthly on a certain weekday (e.g. 2nd Tuesday of each month)
2) probably should be able to set max number of recurrence
3) Initially we will not address the ability to register and pay for several events in the series.

---

Dmitry Buterin, Chief Apricot

A partial solution to this would be to modify the "New Event" work flow,

Add a "Replicate" button  which would work the same as Copy except that we could

1.  click on the date,

2.  select a new date,

3.  select "Publish"

Repeat.

All new events created this way are AUTOMATICALLY VISIBLE.  The problem with the current scheme is the number of steps we have to go through to copy an event (and remember to make it visible) makes the process tedious and slow. 

An improvement to this would be to allow us to give a symbolic name to an event and describe the event only once. Then we could copy the symbolic name in the method described above.  The advantage of this is that if some detail about the event changes, the change only has to be made in one place and is reflected to all other occurrences.

 

If you could duplicate the functions of Microsoft Outlook - Calendar Appointment Recurrence... that would work great

This would be a fantastic feature. I know it's a bit challenging, but we have, for example, recurring events every Friday during the school year (WA is our school's website), and that's a lot of events to replicate manually. 

It seems that you could duplicate the MS Outlook recurrance types with some kind of "master" record .  If an event has a "master" recurring event record associated with it, before editing any particular such recurring event the user would be asked "update series or just this instance"?  If the series is updated, then the master record is what's updated.  If the individual record is what's edited, then it "detaches" from the master record (with suitable warnings) and it becomes it's own event.  I guess you'd have to flag it so that subsequent changes to the master record wouldn't nuke the updated individual event, or duplicate it.  That is, any detached and modified instance of a recurring event would have priority.

For the iCalendar event link you'd want that to be set as "recurring" events for people downloading that "meeting notice" into their Outlook calendar.