Dynamic rebasing of persisted time information

#Dynamic rebasing of persisted time information is a process for calculating an intended local time. In some situations, static timezone persistence in calendar meeting items may require rebasing of the meeting items whenever there is a DST and/or time zone change. In conventional systems, rebasing requires that either the end user of a calendar client or the administrator of a server where calendar information is stored runs a process that adjusts all meeting items, or each meeting item individually, to correct the static timezone information to reflect the time differences of DST changes. This process has to be regularly repeated with every time zone that is used in a calendar system that goes through regular DST changes. This frequently repeated process often interrupts end user productivity and causes calendar incorrectness by showing meetings at the incorrect times for organizers and attendees, thus making them miss meetings and causing additional costs for maintenance and support of the calendar system.

#Dynamic rebasing of persisted time information may be provided. This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter. Nor is this Summary intended to be used to limit the claimed subject matter's scope.

#Dynamic time rebasing may be provided. After receiving a request to view a calendar item, a base time associated with the calendar item may be retrieved. A local bias associated with the request to view the calendar item may be identified. The base time may be converted to a local time according to the local bias. The calendar item may then be displayed according to the converted local time.

#The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present invention. In the drawings:

#FIG. 1 is a block diagram of an operating environment;

#FIGS. 2A-2B is a block diagram of a calendar application interface;

#The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention. Instead, the proper scope of the invention is defined by the appended claims.

#Dynamic rebasing of persisted time information may be provided. Instead of storing and using statically stored timezone information to display a calendar item to the end user, consistent with embodiments of the present invention, the calendar system may dynamically calculate an intended local time based on the statically stored timezone information. Up-to-date timezone information available on a computer system may be used to apply this intended local time to the timezone information to display the meeting to the end user in the correct time. This calculation may be performed every time an end-user accesses the meeting. The result of this calculation may or may not be persisted in the calendar system. Thus, the user always gets the correct day and time of the meeting without the requirement of the user or administrator having to run any process to adjust meetings on timezone rule changes. Incorrect UTC time on a meeting may also get automatically updated when the user views the item.

#Consistent with embodiments of the invention, persisted time information may be associated with other date and/or time based data items on a computer. For example, an enterprise may comprise installations and/or sites at numerous locations around the world. An administrator may want to run weekly full virus scans on all servers and desktops at 1 am at night, or a billing system may rely on providing statements to customers every Monday at 8 am. By dynamically rebasing the persisted time information, daylight savings time (DST) and/or time zone rule changes may not effect such processing happening at the same time.