| IP.com Number | IPCOM000177746D |
|
|
|---|---|---|---|
| Dated | Dec 29, 2008 UTC | ||
| Size | 3 page(s) (91.1 KB) | ||
| Disclosed by |
|
||
| Country | |
|---|---|
| Language | English (United States) |
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Intellectual Property Library website before you leave.
Enabling multi TimeZone view for meetings in Lotus Notes
Disclosed is a design for managing timezones issues when scheduling a meeting (throughout a
(PIM) software) involving people working in different timezones (TZ from now) countries.
To be more clear consider the situation of being the chair of a meeting with 5
personal information manage
participants: 4 from Raleigh, 1 from Los Angeles and you from Rome. So there are three
different TZs involved: Rome (the local - GMT +1) , Raleigh (GMT -6), Los Angeles (GMT -8). Obviously, the chair wants to schedule this meeting in a time that would permit everyone to join it.
The Figure 1 shows what a PIM software can do by now:
Figure 1
Let's examinate all the limitations reported in this case:
The first problem is the single TZ choice (in this example Raleigh has been choosen);
The second problem is represented by the scale reported in the scheduler section that only refers to local time.
The third problem is that the availability of each participant is not converted into the related TZ.
All the above problems are solved by a new scheduler view.
To build this new view a time zone converter table, embedded in the PIM software, is required. The TZ info can be extracted in two ways:
1. directly querying a LDAP server;
2. inserting in the PIM software a new function parsing the mail address to determine the
proper TZ.
The final results in both cas...
Copyright © 2004-2010 IP.com. All Rights Reserved.