Abstract: A system for validating data migrated from a first data store with source data to a second data store for destination data. A comparator is configured to access entity data for a particular entity which has been migrated from a first data store to a second data store. The comparator queries the first data store to a first set of comparison data from the first data store and obtains a second set of comparison data from the second data store. It then compares the first set of data with the second set of data to validate the migration of the data from the first to the second data store.

Abstract: Calendar repair may be provided. Calendar events, such as appointments and meetings, may be created and copied to a plurality of attendee calendars. A first copy of the event may be compared to a second copy of the event, and an event property of the second event may be updated to match a corresponding event property of the first event.

Abstract: Described is a system and method for automatically updating an action item in an electronic communication application using a single input or click from a user. In response to received input, an electronic communication having a mailto link is automatically generated. The mailto link includes the email address of the intended recipient, an identifier associated with the action item, and the update that is to be performed on the action item. The electronic communication is then automatically provided to the intended recipient and the update is performed on the action item.

Abstract: A synchronization window for synchronizing data for a calendar in a client calendar data store on a calendar data client computer system with data for the calendar in a server calendar data store on a calendar data server computer system can be calculated using a current time. A request for synchronization data for calendar items for the calendar with calendar times that are within the synchronization window can be sent to the calendar data server. One or more responses to the request can be received from the calendar data server. The response(s) can include received records for calendar items that are at least partially within the synchronization window. The received records can include a master record of a recurring calendar item and an instance record of an occurrence of the recurring calendar item. The received records for the calendar items can be incorporated in the client calendar data store.

Abstract: A system for validating data migrated from a first data store with source data to a second data store for destination data. A comparator is configured to access entity data for a particular entity which has been migrated from a first data store to a second data store. The comparator queries the first data store to a first set of comparison data from the first data store and obtains a second set of comparison data from the second data store. It then compares the first set of data with the second set of data to validate the migration of the data from the first to the second data store.

Abstract: A system for validating data migrated from a first data store with source data to a second data store for destination data. A comparator is configured to access entity data for a particular entity which has been migrated from a first data store to a second data store. The comparator queries the first data store to a first set of comparison data from the first data store and obtains a second set of comparison data from the second data store. It then compares the first set of data with the second set of data to validate the migration of the data from the first to the second data store.

Abstract: Calendar repair may be provided. Calendar events, such as appointments and meetings, may be created and copied to a plurality of attendee calendars. A first copy of the event may be compared to a second copy of the event, and an event property of the second event may be updated to match a corresponding event property of the first event.

Abstract: Calendar repair may be provided. Calendar events, such as appointments and meetings, may be created and copied to a plurality of attendee calendars. A first copy of the event may be compared to a second copy of the event, and an event property of the second event may be updated to match a corresponding event property of the first event.

Abstract: Migrating data from a source data store to a destination data store and validating the migrated data. The method includes migrating data from a first data store to a second data store using a first protocol to create a first set of comparison data. The method further includes migrating the data from the first data store to the second data store using a second protocol to create a second set of comparison data. The method further includes comparing the first set of comparison data to the second set of comparison data. The method further includes validating migration of the data from the first data store to the second data store based on comparing the first set of comparison data and the second set of comparison data.

Abstract: Described is a system and method for automatically updating an action item in an electronic communication application using a single input or click from a user. In response to received input, an electronic communication having a mailto link is automatically generated. The mailto link includes the email address of the intended recipient, an identifier associated with the action item, and the update that is to be performed on the action item. The electronic communication is then automatically provided to the intended recipient and the update is performed on the action item.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.

Abstract: Examples of the present disclosure describe systems and methods relating to an automatic meeting invite processor. When processing a meeting invite, the automatic meeting invite processor may enforce a calendar booking rule, which may be comprised by a predicate and an action. The predicate may specify characteristics relating to the meeting invite, such as a sender, scheduled date/time, scheduled location, etc. The predicate may also relate to context associated with a recipient of the meeting invite (e.g., the recipient's calendar or mailbox content). When a predicate is satisfied, the automatic meeting invite processor may perform one or more actions, wherein an action may relate to the meeting specified by the meeting invite or to the meeting invite object itself. Thus, when the predicate is satisfied, the meeting invite may be automatically processed by the automatic meeting invite processor using the action specified by the calendar booking rule.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.

Abstract: A synchronization window for synchronizing data for a calendar in a client calendar data store on a calendar data client computer system with data for the calendar in a server calendar data store on a calendar data server computer system can be calculated using a current time. A request for synchronization data for calendar items for the calendar with calendar times that are within the synchronization window can be sent to the calendar data server. One or more responses to the request can be received from the calendar data server. The response(s) can include received records for calendar items that are at least partially within the synchronization window. The received records can include a master record of a recurring calendar item and an instance record of an occurrence of the recurring calendar item. The received records for the calendar items can be incorporated in the client calendar data store.

Abstract: A synchronization window for synchronizing data for a calendar in a client calendar data store on a calendar data client computer system with data for the calendar in a server calendar data store on a calendar data server computer system can be calculated using a current time. A request for synchronization data for calendar items for the calendar with calendar times that are within the synchronization window can be sent to the calendar data server. One or more responses to the request can be received from the calendar data server. The response(s) can include received records for calendar items that are at least partially within the synchronization window. The received records can include a master record of a recurring calendar item and an instance record of an occurrence of the recurring calendar item. The received records for the calendar items can be incorporated in the client calendar data store.

Abstract: Migrating data from a source data store to a destination data store and validating the migrated data. The method includes migrating data from a first data store to a second data store using a first protocol to create a first set of comparison data. The method further includes migrating the data from the first data store to the second data store using a second protocol to create a second set of comparison data. The method further includes comparing the first set of comparison data to the second set of comparison data. The method further includes validating migration of the data from the first data store to the second data store based on comparing the first set of comparison data and the second set of comparison data.

Abstract: A system for validating data migrated from a first data store with source data to a second data store for destination data. A comparator is configured to access entity data for a particular entity which has been migrated from a first data store to a second data store. The comparator queries the first data store to a first set of comparison data from the first data store and obtains a second set of comparison data from the second data store. It then compares the first set of data with the second set of data to validate the migration of the data from the first to the second data store.

Abstract: A computing system record security architecture comprises, in one example, a record generation component configured to generate a record in a computing system, the record identifying a set of users associated with the record, and having an owner property that identifies a first user as an owner of the record, a co-owner assignment component configured to receive a co-owner assignment request, from the first user, to assign a second user to the record as a co-owner, and a record security component configured to receive a record modification request, from the second user, that requests a modification to the record, and to propagate the record modification request to the set of users with a unique identifier that identifies the first user.

Abstract: A synchronization window for synchronizing data for a calendar in a client calendar data store on a calendar data client computer system with data for the calendar in a server calendar data store on a calendar data server computer system can be calculated using a current time. A request for synchronization data for calendar items for the calendar with calendar times that are within the synchronization window can be sent to the calendar data server. One or more responses to the request can be received from the calendar data server. The response(s) can include received records for calendar items that are at least partially within the synchronization window. The received records can include a master record of a recurring calendar item and an instance record of an occurrence of the recurring calendar item. The received records for the calendar items can be incorporated in the client calendar data store.

Abstract: Calendar repair may be provided. Calendar events, such as appointments and meetings, may be created and copied to a plurality of attendee calendars. A first copy of the event may be compared to a second copy of the event, and an event property of the second event may be updated to match a corresponding event property of the first event.