Browse Prior Art Database

Calendar Actions

IP.com Disclosure Number: IPCOM000020615D
Original Publication Date: 2003-Dec-03
Included in the Prior Art Database: 2003-Dec-03
Document File: 2 page(s) / 8K

Publishing Venue

IBM

Abstract

The disclosed software allows a user to add an action entry to his calendar. An action entry is code or a link to start code which is activated through the calendaring system.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Calendar Actions

The disclosed software allows a user to add an action entry to his calendar. An action entry is code or a link to start code which is activated through the calendaring system.

Software calendars contain schedule information and have alarms to remind users of upcoming events. These calendars do not give the user the option to create an action entry that executes code at a particular time and date.

The disclosed software gives the user the ability to add an action entry to a calendar or embed the action itself into an existing calendar entry. For example, the user could specify a script to run when a particular meeting alarm fires. Action code may be stored locally on the user machine, remotely on a general server machine, or remotely on the calendar server. By storing action code on remote machines, the action code may execute even when the local user machine is turned off. Action items may by displayed similarly to other calendar entries, filtered to hide them from view, as icons or indicators next to a calendar entry, or only when viewing a particular calendar entry. Action code may include, but is not limited to, calendar server specific script, bash, perl, and other operating specific binaries. The action code may be stand alone or may require interaction with services and libraries. The code may or may not be interactive.

Example Implementation #1:

1) User has a primary workstation with a software calendar.
2) User leaves primary workstation to go work in the lab at 1PM.
3) User has a 2PM meeting.
4) At 1:50PM, the calendar alarm fires.
5) The alarm notice is displayed on the users primary workstation display.
6) The alarm also executes a script. This script:
a) Determines if the user is logged into an instant messaging service from another machine.
b) If he is, the script sends the meeting notice via instant message to the users ID.
7) User receives the instant message in the lab and then goes to the meeting.

Example Implementation #2:

1) User has a primary workstation with a software calendar.
2) User leaves primary workstation to go work in the lab at 1PM.
3) User has a 2PM meeting.
4) At 1:50PM, the ca...