Eliminating duplicate and invalid calendar items from end user calendars using a unique entry identifier (UEID)

• US 8,041,725 B2
• Filed: 06/25/2008
• Issued: 10/18/2011
• Est. Priority Date: 06/25/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Krissell, Daniel L., Grant, Shayne M.
• Primary Examiner(s): Stevens; Robert
• Application Number:
  US12/145,861
• Publication Number:
  US 20090327919A1
• Time in Patent Office: 1,210 Days
• Field of Search: 707/999.3, 707/754, 707/758, 707/769, 715/751, 709/220
• US Class Current: 707/758
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

Providing a unique entry identifier, which is an identifier specific to a calendar entry. The calendar entry can be an entry associated with a set of different electronic calendars, each associated with a specific user. Data for each user specific calendar can be stored in a structured data store. A set of records for each user specific calendar can be maintained and utilized independent of other sets of records associated with other ones of the users. The unique entry identifier can be an identifier unique for the calendar entry within the associated set of records, and wherein the same unique entry identifier is utilized for the calendar entry within each of the different sets of records as a unique identifier for the calendar entry. For example, when calendar updates are conveyed via email among a set of users, shared meetings can always be associated with a unique entry identifier used by all calendaring systems.

Claims

1. A method for updating structured calendar data comprising:

receiving a message containing data for a shared calendar entry, wherein a shared calendar entry is a content item maintained within records of a plurality of different user specific electronic calendars, wherein each of the plurality of different user specific electronic calendars are functionally independent from any of the other user specific electronic calendars, wherein each of the user specific electronic calendars are maintained and utilized by a plurality of functionally independent calendaring applications, each executing on a one of a plurality of different computing devices, each utilizing a unique record set within which calendar entries are maintained, such that each of the different user specific calendars utilizes its own unique record set, each including a record for the shared calendar entry;

receiving an option to accept the data in the message;

accepting the data by selecting the option;

determining a unique entry identifier for the shared calendar entry;

querying a stored set of structured calendar data wherein said stored set of structured calendar data is one of the unique record sets for a specific one of the different user specific calendars using the unique entry identifier;

when no entry in the stored set is found during the querying that matches the unique entry identifier, initializing at least one programmatic action to create a new calendar entry having the unique entry identifier that is to be stored as part of the structured calendar data of said one of the unique record sets; and

when an entry in the stored set is found during the querying that matches the unique entry identifier, initializing at least one programmatic action to process data of the shared calendar entry in a manner that ensures that only one calendar entry of the stored set of structured calendar data of said one of the unique record sets is associated with the unique entry identifier.

2. The method of claim 1, wherein the received message is received from a messaging application of a client that is one of the different computing devices, which also executes one of the plurality of different functionally independent calendaring applications, wherein said messaging application is independent of the calendaring application.

3. The method of claim 1, further comprising:

presenting a user interface within an messaging application having an option to accept or deny the data relating to the shared calendar entry; and

performing processing actions to update the stored set of structured calendar data within a local data store responsive to a user selection of the option indicating acceptance of the data relating to the shared calendar entry.

4. The method of claim 1, further comprising:

identifying semantic data of the shared calendar entry; and

executing an algorithm driven by the semantic data to automatically generate the unique entry identifier, wherein each execution of the algorithm given the same semantic data produces the same unique entry identifier.

5. The method of claim 1, wherein the message is an email message, and wherein the data comprises the unique entry identifier, which is a value that uniquely identifies as structured record for the shared entry as stored in a calendaring database of a system that sent the message.

6. The method of claim 1, further comprising:

generating a message that contains data relating to the shared calendar entry;

within the message, uniquely identifying the shared calendar entry using the unique entry identifier; and

conveying the message over a network that is directed towards at least one user associated with the shared calendar entry.

7. A computer program product comprising a non-transitory computer useable storage medium having computer usable program embodied therewith, wherein the computer usable program code when executed on a computer causes the computer to:

receive a message containing data for a shared calendar entry, wherein a shared calendar entry is a content item maintained within records of a plurality of different user specific electronic calendars, wherein each of the plurality of different user specific electronic calendars are functionally independent from any of the other user specific electronic calendars, wherein each of the user specific electronic calendars are maintained and utilized by a plurality of functionally independent calendaring applications, each executing on a one of a plurality of different computing devices, each utilizing a unique record set within which calendar entries are maintained, such that each of the different user specific calendars utilizes its own unique record set, each including a record for the shared calendar entry;

receive an option to accept the data in the message;

accept the data by selecting the option;

determine a unique entry identifier for the shared calendar entry;

query a stored set of structured calendar data wherein said stored set of structured calendar data is one of the unique record sets for a specific one of the different user specific calendars using the unique entry identifier;

when no entry in the stored set is found during the querying that matches the unique entry identifier, initialize at least one programmatic action to create a new calendar entry having the unique entry identifier that is to be stored as part of the structured calendar data of said one of the unique record sets; and

when an entry in the stored set is found during the querying that matches the unique entry identifier, initialize at least one programmatic action to process data of the shared calendar entry in a manner that ensures that only one calendar entry of the stored set of structured calendar data of said one of the unique record sets is associated with the unique entry identifier.

8. The computer program product of claim 7, wherein the received message is received from a messaging application of a client that is one of the different computing devices, which also executes one of the plurality of different functionally independent calendaring applications, wherein said messaging application is independent of the calendaring application.

9. The computer program product of claim 7, wherein the computer usable program code when executed on a computer causes the computer to:

present a user interface within an messaging application having an option to accept or deny the data relating to the shared calendar entry; and

perform processing actions to update the stored set of structured calendar data within a local data store responsive to a user selection of the option indicating acceptance of the data relating to the shared calendar entry.

10. The computer program product of claim 7, wherein the computer usable program code when executed on a computer causes the computer to:

identify semantic data of the shared calendar entry; and

execute an algorithm driven by the semantic data to automatically generate the unique entry identifier, wherein each execution of the algorithm given the same semantic data produces the same unique entry identifier.

11. The computer program product of claim 7, wherein the message is an email message, and wherein the data comprises the unique entry identifier, which is a value that uniquely identifies as structured record for the shared entry as stored in a calendaring database of a system that sent the message.

12. The computer program product of claim 7, wherein the computer usable program code when executed on a computer causes the computer to:

generate a message that contains data relating to the shared calendar entry;

within the message, uniquely identify the shared calendar entry using the unique entry identifier; and

convey the message over a network that is directed towards at least one user associated with the shared calendar entry.

13. A system comprising hardware and software that is stored in a non-transitory storage medium, wherein when the hardware is operable to execute the software causing the system to:

receive a message containing data for a shared calendar entry, wherein a shared calendar entry is a content item maintained within records of a plurality of different user specific electronic calendars, wherein each of the plurality of different user specific electronic calendars are functionally independent from any of the other user specific electronic calendars, wherein each of the user specific electronic calendars are maintained and utilized by a plurality of functionally independent calendaring applications, each executing on a one of a plurality of different computing devices, each utilizing a unique record set within which calendar entries are maintained, such that each of the different user specific calendars utilizes its own unique record set, each including a record for the shared calendar entry;

receive an option to accept the data in the message;

accept the data by selecting the option;

determine a unique entry identifier for the shared calendar entry;

query a stored set of structured calendar data wherein said stored set of structured calendar data is one of the unique record sets for a specific one of the different user specific calendars using the unique entry identifier;

when no entry in the stored set is found during the querying that matches the unique entry identifier, initialize at least one programmatic action to create a new calendar entry having the unique entry identifier that is to be stored as part of the structured calendar data of said one of the unique record sets; and

when an entry in the stored set is found during the querying that matches the unique entry identifier, initialize at least one programmatic action to process data of the shared calendar entry in a manner that ensures that only one calendar entry of the stored set of structured calendar data of said one of the unique record sets is associated with the unique entry identifier.

14. The system of claim 13, wherein the received message is received from a messaging application of a client that is one of the different computing devices, which also executes one of the plurality of different functionally independent calendaring applications, wherein said messaging application is independent of the calendaring application.

15. The system of claim 13, wherein the hardware is operable to execute the software causing the system to:

present a user interface within an messaging application having an option to accept or deny the data relating to the shared calendar entry; and

perform processing actions to update the stored set of structured calendar data within a local data store responsive to a user selection of the option indicating acceptance of the data relating to the shared calendar entry.

16. The system of claim 13, further comprising:

identifying semantic data of the shared calendar entry; and

executing an algorithm driven by the semantic data to automatically generate the unique entry identifier, wherein each execution of the algorithm given the same semantic data produces the same unique entry identifier.

17. The system of claim 13, wherein the message is an email message, and wherein the data comprises the unique entry identifier, which is a value that uniquely identifies as structured record for the shared entry as stored in a calendaring database of a system that sent the message.

18. The system of claim 13, wherein the hardware is operable to execute the software causing the system to:

generate a message that contains data relating to the shared calendar entry;

within the message, uniquely identify the shared calendar entry using the unique entry identifier; and

convey the message over a network that is directed towards at least one user associated with the shared calendar entry.