Synchronization of recurring time-scheduled data objects between incompatible databases

A computer-implemented synchronizer for adapting a recurring time-scheduled data record for an application that does not support a pattern of recurrence of the record, comprising:

• an event analyzer module configured to receive a first recurring time-scheduled data record from a first calendaring application on a server, wherein the event analyzer determines that the received first recurring time-scheduled data record has a recurrence pattern that is unsupported by a second calendaring application operating on a mobile device;
• a pattern selector module configured to, upon a determination by the event analyzer that the received data record has a first recurrence pattern that is unsupported by the second calendaring application, select a recurrence pattern supported by the second calendaring application that is similar to the recurrence pattern of the received data record;
• a conversion module configured to apply exceptions to the selected supported recurrence pattern, and convert the received first recurring time-scheduled data record into a second recurring time-scheduled data record having the selected supported recurrence pattern;
• a synchronizer module configured to transfer the second recurring time-scheduled data record to the second calendaring application;
• and
• storing the first recurrence pattern on the mobile device.

A computer-readable storage device having computer-executable instructions stored thereon that, if executed by a computing device, cause the computing device to perform a method comprising:

• receiving from a first calendaring application on a server, a first recurring time-scheduled data record having a first recurrence pattern;
• determining that the first recurrence pattern is not supported by a second calendaring application operating on a mobile device;
• selecting a closest recurrence pattern supported by the second calendaring application;
• modifying the selected closest recurrence pattern by applying recurrence exceptions, the modifying creating a second recurrence pattern;
• modifying the first recurring time-scheduled data record based on the second recurrence pattern to create a second recurring time-scheduled data record;
• transferring the second recurring time-scheduled data record to the second calendaring application;
• and
• storing the first recurrence pattern on the mobile device.

A computer-implemented method of synchronizing recurring time-scheduled data records, comprising:

• storing at a first calendaring application, a first recurring time-scheduled data record having a first recurrence pattern;
• selecting a closest recurrence pattern supported by a second calendaring application, the second calendaring application operated on a mobile device, wherein the selecting is based on a list mapping recurrence patterns unsupported by the second calendaring application to recurrence patterns supported by the second calendaring application;
• storing the second recurring time-scheduled data record in the second calendaring application using the closest recurrence pattern and recurrence exceptions;
• storing the first recurrence pattern on the mobile device;
• receiving a request to synchronize the first and second recurring time-scheduled data records;
• receiving the stored first recurrence pattern from the mobile device;
• and
• synchronizing the first and second recurring time-scheduled data records using the stored first recurrence pattern.