Abstract: A computer implemented method for scheduling a meeting includes receiving a set of input parameters as meeting constraints. The meeting input parameters include a meeting organizer attendee identifier and multiple additional meeting attendee identifiers, a duration of the meeting, and a time frame within which to schedule the meeting. Calendar data is accessed from one or more servers storing calendar data corresponding to the organizer attendee and the meeting attendees based on the respective identifiers. The accessed calendar data is processed against the received set of input parameters to identify candidate meetings. In response to no candidate meeting matching all the input parameters, at least one parameter is automatically adjusted, and new candidate meetings are identified. Candidate meeting suggestions are communicated to a meeting organizer.

Abstract: A computing device includes a processor and associated memory. The processor is configured to execute a personal information management service stored in memory to send a first calendar entry for display on a calendar interface for a user. The first calendar entry is for a first account of the user of a first domain. The processor sends a second calendar entry for display on the calendar interface. The second calendar entry is for a calendar of a second account of the user of a second domain. The processor receives a request for an availability of the user from a requesting user having a third account of the first domain. In response to the request, the processor sends to the requesting user the first calendar entry including first calendar entry details, and the second calendar entry without second calendar entry details.

Abstract: Techniques of configuring settings for automatic update of calendar items in an electronic calendar systems are disclosed herein. In one embodiment, a server can receive and store update configuration records indicating that a change to a start date, start time, an end date, an end time, or location of a meeting would render a meeting update actionable. Upon receiving an incoming meeting update, the server can determine whether the incoming meeting update contains a change to one of a start date, start time, an end date, an end time or location. If true, the server can automatically modify, without any input from the recipient, a scheduled meeting appointment in the calendar folder of the recipient according to the received incoming meeting update.

Abstract: Techniques of configuring settings for automatic update of calendar items in an electronic calendar systems are disclosed herein. In one embodiment, a server can receive and store update configuration records indicating that a change to a start date, start time, an end date, an end time, or location of a meeting would render a meeting update actionable. Upon receiving an incoming meeting update, the server can determine whether the incoming meeting update contains a change to one of a start date, start time, an end date, an end time or location. If true, the server can automatically modify, without any input from the recipient, a scheduled meeting appointment in the calendar folder of the recipient according to the received incoming meeting update.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.

Abstract: A computing device includes a processor and associated memory. The processor is configured to execute a personal information management service stored in memory to send a first calendar entry for display on a calendar interface for a user. The first calendar entry is for a first account of the user of a first domain. The processor sends a second calendar entry for display on the calendar interface. The second calendar entry is for a calendar of a second account of the user of a second domain. The processor receives a request for an availability of the user from a requesting user having a third account of the first domain. In response to the request, the processor sends to the requesting user the first calendar entry including first calendar entry details, and the second calendar entry without second calendar entry details.

Abstract: Availability data caching in, meeting services is provided. In some examples, a list of users whose data is to be cached locally for a user may be determined based on factors such as their relevance to the user, a likelihood of a meeting being requested with the users, a history of common meetings, and similar factors. What type of user data to cache, for how long, at which granularity level, and similar parameters may be determined as well. User data for users from the list may be retrieved on-demand or on a regular basis from server associated with those users and stored at a server or other computing device for the user for fast access when the user requests to schedule a meeting.

Abstract: Techniques for protecting mailboxes in computer-implemented conferencing systems are disclosed herein. In one embodiment, a method includes caching availability data representing availability information of meeting participants in a mailbox corresponding to a meeting organizer. The method also includes monitoring a mailbox size of the mailbox corresponding to the meeting organizer and determining whether the monitored mailbox size exceeds a preset threshold. The method further includes in response to determining that the monitored mailbox size exceeds the preset threshold, ceasing to cache additional availability data representing new availability information of the meeting participants received at the mailbox in order to prevent performance degradation of accessing the mailbox by the meeting organizer via the computer network.

Abstract: Techniques of configuring settings for automatic update of calendar items in an electronic calendar systems are disclosed herein. In one embodiment, a server can receive and store update configuration records indicating that a change to a start date, start time, an end date, an end time, or location of a meeting would render a meeting update actionable. Upon receiving an incoming meeting update, the server can determine whether the incoming meeting update contains a change to one of a start date, start time, an end date, an end time or location. If true, the server can automatically modify, without any input from the recipient, a scheduled meeting appointment in the calendar folder of the recipient according to the received incoming meeting update.

Abstract: Techniques of selective update of calendar items in electronic calendar systems are disclosed herein. In one embodiment, a computer server can be configured to receive an electronic update in the email folder of the user, the electronic update containing modification of one or more details to a meeting that the user is invited to attend. Upon receiving the electronic update, the computer server can determine whether the update is actionable by the user according to a set of pre-configured criteria. In response to determining that the electronic update is not actionable according to the set of pre-configured criteria, the computer server can automatically modify a calendar item corresponding to the meeting in the calendar folder of the user according to the received electronic update without input from the user.

Abstract: Techniques for protecting mailboxes in computer-implemented conferencing systems are disclosed herein. In one embodiment, a method includes caching availability data representing availability information of meeting participants in a mailbox corresponding to a meeting organizer. The method also includes monitoring a mailbox size of the mailbox corresponding to the meeting organizer and determining whether the monitored mailbox size exceeds a preset threshold. The method further includes in response to determining that the monitored mailbox size exceeds the preset threshold, ceasing to cache additional availability data representing new availability information of the meeting participants received at the mailbox in order to prevent performance degradation of accessing the mailbox by the meeting organizer via the computer network.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to receive a record generation request that includes a set of attributes and to generate a record in a computing system based on the record generation request, wherein the record includes the set of attributes and an owner property that identifies a first user as an owner of the record. The architecture comprises a record security component configured to receive a record modification request that requests a modification to the record, to analyze an identifier in the record modification request that identifies a second user as a sender of the record modification request, and to process the record modification request based on an analysis of the identifier in the record modification request relative to the owner property of the record.

Abstract: Availability data caching in, meeting services is provided. In some examples, a list of users whose data is to be cached locally for a user may be determined based on factors such as their relevance to the user, a likelihood of a meeting being requested with the users, a history of common meetings, and similar factors. What type of user data to cache, for how long, at which granularity level, and similar parameters may be determined as well. User data for users from the list may be retrieved on-demand or on a regular basis from server associated with those users and stored at a server or other computing device for the user for fast access when the user requests to schedule a meeting.

Abstract: A method includes identifying a series of events formatted for a modern system. The series of events includes a master message usable by modern systems. The master message includes default information for all events in the series. The method further includes identifying a plurality of instance messages. Each of the instance messages includes default information and exception information for a given event in the series of events. The method further includes sending both the master message and the instance messages to other systems without regard to whether the other systems are modern or legacy systems.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to receive a record generation request that includes a set of attributes and to generate a record in a computing system based on the record generation request, wherein the record includes the set of attributes and an owner property that identifies a first user as an owner of the record. The architecture comprises a record security component configured to receive a record modification request that requests a modification to the record, to analyze an identifier in the record modification request that identifies a second user as a sender of the record modification request, and to process the record modification request based on an analysis of the identifier in the record modification request relative to the owner property of the record.

Abstract: A method includes identifying a series of events formatted for a modern system. The series of events includes a master message usable by modern systems. The master message includes default information for all events in the series. The method further includes identifying a plurality of instance messages. Each of the instance messages includes default information and exception information for a given event in the series of events. The method further includes sending both the master message and the instance messages to other systems without regard to whether the other systems are modern or legacy systems.

Abstract: An application provides a “working elsewhere” status for users working at a location other than their regular work location and still available for meetings, communication sessions, etc. The application determines a user location being other than regular work location and the user still being available through user selection, information from user associated application(s), and/or from a presence notification. The application adjusts the user status to a working elsewhere status and makes the new status available to other applications such as calendaring, communication applications, presence service(s), and comparable ones. Meetings may be scheduled, communication sessions facilitated if the working elsewhere status is sufficient/acceptable for other users.

Abstract: An application provides a “working elsewhere” status for users working at a location other than their regular work location and still available for meetings, communication sessions, etc. The application determines a user location being other than regular work location and the user still being available through user selection, information from user associated application(s), and/or from a presence notification. The application adjusts the user status to a working elsewhere status and makes the new status available to other applications such as calendaring, communication applications, presence service(s), and comparable ones. Meetings may be scheduled, communication sessions facilitated if the working elsewhere status is sufficient/acceptable for other users.

Abstract: Systems that provide users with a model for designing, implementing, complying with, and proving compliance with, message life cycle management policies are disclosed. Such a model may be based on the notion of folders upon which policies are defined, new restrictions on such folders, mechanisms to assure that users have such folders, and mechanisms to establish how well users are complying with the policies by determining how they are filing items into the folders. The concept can be extended to other mutually exclusive grouping mechanisms.