Synchronizing recurring events

• US 20030061433A1
• Filed: 09/07/2001
• Published: 03/27/2003
• Est. Priority Date: 09/07/2001
• Status: Active Grant

• Current Assignee: Extended Systems Inc. (SAP SE)
• Original Assignee: Extended Systems Inc. (SAP SE)
• Inventors: Jeide, Scott A., Annadurai, Raja, Hall, Lyman
• Granted Patent: US 8,346,718 B2
• Time in Patent Office: Days
• US Class Current: 711/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

A system and method for synchronizing records stored in differing formats in a shared data environment. One aspect of the invention involves distinguishing a record without regard to its format. Once a record is introduced into the environment, it is detected. A record file is generated and associated with the event. A record file typically includes a record tag uniquely identifying a given record in the shared data environment and a record type indicating information such as whether or not the record represents a recurring event as well as the format of the record. A record file also contains data indicating the status of the particular event, that is, whether it is new, unchanged, modified, or deleted. When synchronizing, only those records with equivalent record tags are compared. The record type and status are then used to guide the synchronization of equivalent records.

Claims

1. A method for distinguishing data representing an record in a shared data environment, comprising:

discovering an event new to the shared data environment;

generating a record file for the discovered event; and

associating the generated record file with the data representing the discovered event.

2. The method of claim 1, wherein the act of generating comprises creating a record tag, and noting the record type of the discovered event.

3. The method of claim 2, wherein:

the record type indicates that the discovered event is a recurring event and the data representing the recurring event includes a series of discrete records;

the act of generating comprises generating a single record file for all of the discrete records; and

the act of associating comprises associating the single record file with all of the discrete records.

4. The method of claim 2, wherein:

the record type indicates that the discovered event is a recurring event and the data representing the recurring event includes a complex record;

the act of generating comprises generating a record file for the complex record; and

the act of associating comprises associating the generated record file with the complex record.

5. The method of claim 2, wherein the act of creating comprises:

identifying all other record tags in the shared data environment; and

repeatedly generating a new record tag until the generated record tag is different from each of the other identified record tags.

6. The method of claim 2, wherein the data representing the discovered event is associated with one or more local identifiers and is contained in a data store and the act of creating comprises:

acquiring at least one local identifier for the data representing the discovered event;

acquiring a data store tag associated with the data store; and

generating a record tag for the discovered event by combining the acquired local identifier with the acquired data store tag.

7. A computer program product for distinguishing data representing an event in a shared data environment, the product comprising a computer useable medium having computer readable instructions thereon for:

discovering an event new to the shared data environment;

generating a record file for the discovered event; and

associating the generated record file with the data representing the discovered event.

8. The product of claim 7, wherein the instructions for generating comprise instructions for creating a record tag and noting the record type of the discovered event.

9. The product of claim 8, wherein the record type indicates that the discovered event is a recurring event and the data representing the recurring event includes a series of discrete records;

the instruction for generating comprise instructions for generating a single record file for all of the discrete records; and

the instructions for associating comprise instructions for associating the single generated record file with all of the discrete records.

10. The product of claim 8, wherein the record type indicates that the discovered event is a recurring event and the data representing the recurring event includes a complex record;

the instructions for generating comprise instructions for generating a record file for the complex record; and

the instructions for associating comprises instructions for associating the generated record file with the complex record.

11. The product of claim 8, wherein the instructions for creating comprise instructions for:

identifying all other record tags in the shared data environment; and

repeatedly generating a new record tag until the generated record tag is different from each of the other identified record tags.

12. The product of claim 8, wherein the data representing the discovered event is associated with one or more local identifiers and is contained in a data store and the instructions for creating comprise instructions for:

acquiring at least one local identifier for the data representing the discovered event;

acquiring a data store tag associated with the data store; and

generating a record tag for the discovered event by combining the acquired local identifier with the acquired data store tag.

13. A method for synchronizing data representing recurring events in a shared data environment, comprising:

acquiring a first record tag, a first record type, and a first record status each associated with data representing a first recurring event;

acquiring a second record tag, a second record type, and a second record status each associated with a second recurring event;

comparing the first and second record tags;

synchronizing the data representing the first and second recurring events according to the first and second record types and record statuses only if the first and second record tags are equivalent.

14. The method of claim 13, wherein the act of synchronizing comprises expanding the data representing the second event and replacing the data representing the first event with the expanded data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a series of discrete records;

the record status for the second event indicates that the second event has been modified; and

the record type for the second event indicates that the data representing the first event includes a complex record.

15. The method of claim 14 wherein the complex record includes a rule and exceptions and wherein the act of expanding comprises generating a series of discrete records according to the rule and exceptions.

16. The method of claim 13, wherein the act of synchronizing comprises retracting the data representing the second event and replacing the data representing the first event with the retracted data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a complex record;

the record status for the second event indicates that the second event has been modified; and

the record type for the second event indicates that the data representing the second event includes a series of discrete records.

17. The method of claim 16, wherein the act of retracting comprises generating a rule and exceptions, if any, by compiling the data in each of the discrete records and forming a complex record from the generated rule and exceptions.

18. The method of claim 13 further comprising:

discovering events new to the environment; and

for each discovered event, generating a record tag, noting a record type and associating that record tag and record type with data representing the discovered event.

19. The method of claim 18, wherein the act of generating comprises:

identifying all other record tags in the shared data environment; and

repeatedly generating a new record tag until the generated record tag is different from each of the other identified record tags.

20. The method of claim 18, wherein the shared data environment includes two or more data stores and data representing each event in the shared data environment is contained within one of the data stores and is associated with one or more local identifiers and wherein the act of generating comprises:

identifying the data store containing the data representing the discovered event;

acquiring at least one local identifier for the data representing the discovered event;

acquiring a data store tag associated with the data store; and

generating a record tag for the discovered event by combining the acquired local identifier with the acquired data store tag.

21. A computer program product for synchronizing data representing recurring events in a shared data environment, the product comprising a computer useable medium having computer readable instructions thereon for:

acquiring a first record tag, a first record type, and a first record status each associated with data representing a first recurring event;

acquiring a second record tag, a second record type, and a second record status each associated with a second recurring event;

comparing the first and second record tags;

synchronizing the data representing the first and second recurring events according to the first and second record types and record statuses only if the first and second record tags are equivalent.

22. The product of claim 21, wherein the instructions for synchronizing comprise instructions for expanding the data representing the second event and replacing the data representing the first event with the expanded data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a series of discrete records;

the record status for the second event indicates that the second event has been modified; and

the record type for the first event indicates that the data representing the first event includes a complex record.

23. The product of claim 22, wherein the complex record includes a rule and exceptions and wherein the instructions for expanding comprise instructions for generating a series of discrete records according to the rule and exceptions.

24. The product of claim 21, wherein the instructions for synchronizing comprise instructions for retracting the data representing the second event and replacing the data representing the first event with the retracted data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a complex record;

the record status for the second event indicates that the second event has been modified; and

the record type for the second event indicates that the data representing the second event includes a series of discrete records.

25. The product of claim 24, wherein the instructions for retracting comprise instructions for generating a rule and exceptions, if any, by compiling the data in each of the discrete records and forming a complex record from the generated rule and exceptions.

26. The product of claim 21, further comprising instructions for:

discovering events new to the environment; and

for each discovered event, generating a record tag, noting a record type and associating that record tag and record type with data representing the discovered event.

27. The product of claim 26, wherein the instructions for generating comprise instructions for:

identifying all other record tags in the shared data environment; and

repeatedly generating a new record tag until the generated record tag is different from each of the other identified record tags.

28. The product of claim 26, wherein the shared data environment includes two or more data stores and data representing each event in the shared data environment is contained within one of the data stores and is associated with one or more local identifiers and wherein the instructions for generating comprise instructions for:

identifying the data store containing the data representing the discovered event;

acquiring at least one local identifier for the data representing the discovered event;

acquiring a data store tag associated with the data store; and

generating a record tag for the discovered event by combining the acquired local identifier with the acquired data store tag.

29. A system for synchronizing data representing recurring events in a shared data environment, comprising:

a first record status, a first record type, and a first record tag each associated with data representing a first event;

a second record status, a second record type, and a second record tag each associated with data representing a second event;

a synch engine operable to compare the first and second record tags and, if the first and second record tags are equivalent, to synchronize the first and second events according to the first and second record types and record statuses.

30. The system of claim 29, wherein the synch engine is operable to retract the data representing the second event and replacing the data representing the first event with the retracted data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a complex record;

the record status for the second event indicates that the second event has been modified; and

the record type for the second event indicates that the data representing the second event includes a series of discrete records.

31. The system of claim 29, wherein the synch engine is operable to expand the data representing the second event and replacing the data representing the first event with the expanded data if:

the record status for the first event indicates that the first event is new or unchanged;

the record type for the first event indicates that the data representing the first event includes a series of discrete records;

the record status for the second event indicates that the second event has been modified; and

the record type for the first event indicates that the data representing the first event includes a complex record.