Browse Prior Art Database

Utilizing "agenda time slicing" to better coordinate overlapping calendar events

IP.com Disclosure Number: IPCOM000236280D
Publication Date: 2014-Apr-16
Document File: 1 page(s) / 56K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is an electronic calendaring function that enables Agenda Time Slicing. Agenda Time Slicing allows a user to define or tag specific time segments as required or optional within a calendar event, effectively splitting one accepted meeting into two or more segments showing, in actuality, both unavailable and available time.

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

Page 01 of 1

Utilizing "agenda time slicing" to better coordinate overlapping calendar events

As the global workforce continues to expand, so does the challenge of coordinating and prioritizing multiple meeting entries across and within time zones. While calendaring applications have evolved with technology to address almost every need, calendaring functions offer the ability to intelligently time slice entries such that a user can define/manage the "must attend segments" in order to better manage overlapped calendar entries for the most effective use of their time.

An electronic calendaring function is needed that provides a user with the ability to

use defined meeting agendas in order to prioritize the true "time slices" required of an individual to be in attendance for any given event. In addition, the function must allow the calendar to show segments of free time where time slices of meetings are tagged as optional.

The novel contribution is a method to enhance existing calendaring algorithms to enable Agenda Time Slicing. Agenda Time Slicing allows a user to define or tag

specific time segments or agenda items of a calendar event as required or optional. This enables the user to better manage, via visual interpretation, multiple events.

The method allows the user to accept a calendar event using required and optional time segments. For example, if a calendar event is scheduled for 10AM - 11AM

allow users to accept it based on the following logic:


• Accept All Required...