Electronic calendaring system and method determining redundant meeting invitees based on a meeting composition score

• US 10,510,026 B1
• Filed: 04/22/2016
• Issued: 12/17/2019
• Est. Priority Date: 10/03/2015
• Status: Active Grant

• Current Assignee: Teem Technologies LLC
• Original Assignee: WeWork Companies, Inc.
• Inventors: Adamson, Dal, Ross, Ron, Holmquist, Zachary Dean, Reis, Joe, Myers, Ken, Gregersen, Dylan
• Primary Examiner(s): Jarrett, Scott L
• Application Number:
  US15/136,779
• Time in Patent Office: 1,334 Days
• CPC Class Codes: G06F 16/33 Querying
• CPC Class Codes: G06F 9/543 User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 5/01 Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group

Abstract

This disclosure describes, according to some implementations, a method for scoring electronic meeting requests for attendee redundancy. In an example method, the method includes retrieving, using one or more processors, user IDs of meeting attendees; retrieving, using the one or more processors, one or more characteristics associated with the user IDs; retrieving, using the one or more processors, a rule having one or more parameters for scoring meeting composition; comparing, using the one or more processors, the one or more characteristics associated with the user IDs based on the one or more parameters of the rule; and generating, using the one or more processors, a meeting score based on the comparison.

Claims

1. A computer-implemented method for determining redundancy in a meeting, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule the meeting at a particular time and place;

scheduling the meeting based on the meeting request by at least storing a corresponding data entry in a meeting data store;

tracking attendance confirmation transmitted via the computer network from third computing systems associated with attendees of the meeting, the attendance confirmation including user IDs respectively associated with the attendees;

retrieving characteristics associated with the user IDs from a user data store;

determining, using the one or more processors, a meeting purpose;

based on the meeting purpose, retrieving from a rule data store a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the characteristics associated with the user IDs using the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics using the one or more parameters of the rule comprises determining whether a quantity of similar domain categories exceeds the one or more parameters;

generating, using the one or more processors, a meeting composition score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting composition score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces of the third computing systems, an opt-out function to one or more users associated with the redundant user IDs.

2. The method of claim 1, wherein determining the meeting purpose further comprises:

identifying, using the one or more processors, a meeting objective included in the meeting request; and

determining, using the one or more processors, a rule related to the meeting objective.

3. The method of claim 1, further comprising:

comparing, using the one or more processors, the meeting composition score to a previously generated meeting composition score; and

determining, using the one or more processors, an insight based on the comparison.

4. The method of claim 3, wherein the insight is one of a cost, a frequency, and a domain.

5. A computer-implemented method for scoring a composition of a meeting, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule the meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether the domain category satisfies the one or more parameters;

generating, using the one or more processors, a meeting score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces of third computing systems, an opt-out function to one or more users associated with the redundant user IDs.

6. The method of claim 5, wherein generating the meeting score is performed as part of scheduling the meeting and wherein retrieving user IDs of meeting attendees further comprises:

receiving the meeting request including the user IDs.

7. The method of claim 5, wherein retrieving the rule further comprises:

identifying, using the one or more processors, a meeting objective; and

determining, using the one or more processors, the rule based on the meeting objective.

8. The method of claim 5, further comprising:

comparing, using the one or more processors, the meeting score to a previously generated meeting score; and

determining, using the one or more processors, an insight based on the comparison.

9. The method of claim 5, further comprising:

providing the indication of the identified redundant user IDs included in the meeting attendees.

10. The method of claim 9, further comprising:

providing the opt-out function to the one or more users associated with the redundant user IDs.

11. A system comprising:

one or more computer processors; and

one or more memories storing instructions that, when executed by the one or more processors, cause the system to perform operations including;

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule a meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether the domain category satisfies the one or more parameters; and

generating a meeting score based on the comparison;

identifying redundant user IDs included in the meeting using the meeting score; and

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided, in graphical user interfaces, an opt-out function to one or more users associated with the redundant user IDs.

12. The system of claim 11, wherein generating the meeting score is performed as part of scheduling the meeting and wherein retrieving user IDs of meeting attendees further comprises:

receiving the meeting request including the user IDs.

13. The system of claim 11, wherein retrieving the rule further comprises:

identifying a meeting objective; and

determining the rule based on the meeting objective.

14. The system of claim 11, further comprising:

comparing the meeting score to a previously generated meeting score; and

determining an insight based on the comparison.

15. The system of claim 11, further comprising:

providing the indication of the identified redundant user IDs included in the meeting attendees.

16. The system of claim 15, further comprising:

providing the opt-out function to the one or more users associated with the redundant user IDs.

17. One or more instances of computer-readable media collectively having contents configured to cause a input system to perform a method, the method comprising:

exposing, at a first computing system having one or more processors, access via a computer network to a scheduling application program interface (API) for scheduling meetings;

receiving, at the first computing system via the computer network, a meeting request from a second computing system associated with a meeting organizer via the API, the meeting request being a request to schedule a meeting at a particular time and place;

scheduling the meeting based on the meeting request;

retrieving user IDs of meeting attendees;

retrieving one or more characteristics associated with the user IDs;

retrieving a rule having one or more parameters for scoring meeting composition;

comparing, using the one or more processors, the one or more retrieved characteristics associated with the user IDs based on the one or more parameters of the rule, wherein one of the characteristics is a domain category, and wherein comparing the characteristics based on the one or more parameters of the rule comprises determining whether a quantity of similar domain categories exceeds the one or more parameters;

generating, using the one or more processors, a meeting score based on the comparison;

identifying, using the one or more processors, redundant user IDs included in the meeting using the meeting score;

causing to be provided, in a graphical user interface of the second computing system, an indication of the identified redundant user IDs included in the meeting; and

causing to be provided an opt-out function to one or more users associated with the redundant user IDs.