Manage recurring calendar data

I need to create a web application with an event calendar section. As in Outlook, the requirement is that users can configure recurring events and can move individual events as part of a series of events.

  • What methods can be used to store (in a database) various ways of describing a repeating series template?
  • How to record exceptions?
  • What strategies do you use to manage the redefinition of the series and its effects on exceptions?

I have done this several times, otherwise, but I would like to see how others solve this problem.

+4
source share
3 answers

See how iCal uses repeating patterns and repeating exceptions . If you want to post events at some point, you still have to avoid iCal, so you could do it just as well from the start.

+4
source

On the one hand: if you are not already familiar with this, check out RFC 5545 (which replaces RFC 2445 ), which defines the iCalendar specification for this type of template.

+3
source

I usually provided interface logic that allows the user to specify a recurring event, but then actually used separate database records to record events as separate records on an SQL server.

In other words, they can indicate a meeting every Monday evening at 7 pm, but I am recording 52 entries per year so that individual meetings can be changed, deleted, or added additional information to these events.

I provide methods that allow the user to cancel all future events, and then re-enter a new repeating series, if necessary.

I have not come up with the perfect way to handle this, so I will follow this thread to see if any big suggestions are coming up.

0
source

All Articles