Session management of content driven meeting summaries, action items, meeting context continuity, and segment audio-video (AV) replay for collaboration solutions
A method for the session management of content driven meeting summaries and action items in a commercial environment, which may be tied to multiple back-end cloud services. The method employs an association based data structure directed to improving the organization and persistence of post-meeting generated content or collateral (e.g., meeting summaries, notes, action items, etc.). Further, a method for learned meeting context continuity for past context and future meeting proposals tied to current meeting context. The method may match key topics, conversations, and attendees to deduce relation; and, accordingly, provide suitable next meeting predictions. Moreover, a method for intelligently managing segment audio-visual (AV) replay access, which may be indexed using users, topics, presenters, keywords, etc.
1. A method for asynchronous meeting management, comprising:
performing, by a collaboration platform service and upon meeting a window closure criterion for an asynchronous meeting, a non-iterative process, comprising:
aggregating, for a user and across a set of meeting sessions of the asynchronous meeting associated with the user, a set of session assets to obtain aggregated information;
analyzing the aggregated information to produce meeting collateral; and
submitting, to a target third-party collaboration tool service of a set of third-party collaboration tool services, a collateral-driven request comprising the meeting collateral,
wherein the asynchronous meeting refers to a virtual collaboration meeting between users, using meeting participants, that does not transpire in real-time,
wherein the window closure criterion for the asynchronous meeting is a contribution-based criterion specifying a number of rounds of user contributions received from the meeting participants after which the asynchronous meeting terminates.
2. The method of claim 1 , wherein the set of session assets comprises at least one selected from a group consisting of a set of user contributions contributed by the user throughout the set of meeting sessions, meeting content contributed by the user throughout the set of meeting sessions, and a set of session transcripts associated with and obtained for the user throughout the set of meeting sessions.
3. The method of claim 1 , wherein the meeting collateral comprises at least one action item relevant to the asynchronous meeting and directed to the user.
4. The method of claim 3 , wherein the collateral-driven request results in a creation of at least one selected from a group consisting of a reminder object and a task object by the target third-party collaboration tool service, wherein the at least one selected from the group consisting of the reminder object and the task object associates with the at least one action item.
5. The method of claim 1 , further comprising:
prior to performing the non-iterative process:
performing, by the collaboration platform service and until the window closure criterion for the asynchronous meeting is met, an iterative process, comprising:
receiving a session initiation notice from a meeting participant associated with the user;
submitting, in response to receiving the session initiation notice, an event listener registration to the set of third-party collaboration tool services;
receiving, in response to the submitting the event listener registration, a tool event notice from a source third-party collaboration tool service of the set of third-party collaboration tool services; and
maintaining a meeting management structure based on the tool event notice.
6. The method of claim 5 , further comprising:
performing, by the collaboration platform service, a continuation of the iterative process, comprising:
receiving a session termination notice from the meeting participant associated with the user;
submitting, in response to receiving the session termination notice, a session data request to the source third-party collaboration tool service;
obtaining, in response to submitting the session data request, the set of session assets from the source third-party collaboration tool service; and
maintaining at least another meeting management structure using the set of session assets.
7. A non-transitory computer readable medium (CRM) comprising computer readable program code, which when executed by a computer processor of a collaboration platform service, enables the collaboration platform service to perform a method for asynchronous meeting management, the method comprising:
performing, upon meeting a window closure criterion for an asynchronous meeting, a non-iterative process, comprising:
aggregating, for a user and across a set of meeting sessions of the asynchronous meeting associated with the user, a set of session assets to obtain aggregated information;
analyzing the aggregated information to produce meeting collateral; and
submitting, to a target third-party collaboration tool service of a set of third-party collaboration tool services, a collateral-driven request comprising the meeting collateral,
wherein the asynchronous meeting refers to a virtual collaboration meeting between users, using meeting participants, that does not transpire in real-time,
wherein the window closure criterion for the asynchronous meeting is a contribution-based criterion specifying a number of rounds of user contributions received from the meeting participants after which the asynchronous meeting terminates.
8. The non-transitory CRM of claim 7 , wherein the set of session assets comprises at least one selected from a group consisting of a set of user contributions contributed by the user throughout the set of meeting sessions, meeting content contributed by the user throughout the set of meeting sessions, and a set of session transcripts associated with and obtained for the user throughout the set of meeting sessions.
9. The non-transitory CRM of claim 7 , wherein the meeting collateral comprises at least one action item relevant to the asynchronous meeting and directed to the user.
10. The non-transitory CRM of claim 9 , wherein the collateral-driven request results in a creation of at least one selected from a group consisting of a reminder object and a task object by the target third-party collaboration tool service, wherein the at least one selected from the group consisting of the reminder object and the task object associates with the at least one action item.
11. The non-transitory CRM of claim 7 , the method further comprising:
prior to performing the non-iterative process:
performing, until the window closure criterion for the asynchronous meeting is met, an iterative process, comprising:
receiving a session initiation notice from a meeting participant associated with the user;
submitting, in response to receiving the session initiation notice, an event listener registration to the set of third-party collaboration tool services;
receiving, in response to the submitting the event listener registration, a tool event notice from a source third-party collaboration tool service of the set of third-party collaboration tool services; and
maintaining a meeting management structure based on the tool event notice.
12. The non-transitory CRM of claim 11 , further comprising:
performing a continuation of the iterative process, comprising:
receiving a session termination notice from the meeting participant associated with the user;
submitting, in response to receiving the session termination notice, a session data request to the source third-party collaboration tool service;
obtaining, in response to submitting the session data request, the set of session assets from the source third-party collaboration tool service; and
maintaining at least another meeting management structure using the set of session assets.
13. A system, the system comprising:
a set of third-party collaboration tool services; and
a collaboration platform service operatively connected to the set of third-party collaboration tool services, and comprising a computer processor configured to perform a method for asynchronous meeting management, the method comprising:
performing, upon meeting a window closure criterion for an asynchronous meeting, a non-iterative process, comprising:
aggregating, for a user and across a set of meeting sessions of the asynchronous meeting associated with the user, a set of session assets to obtain aggregated information;
analyzing the aggregated information to produce meeting collateral; and
submitting, to a target third-party collaboration tool service of the set of third-party collaboration tool services, a collateral-driven request comprising the meeting collateral,
wherein the asynchronous meeting refers to a virtual collaboration meeting between users, using meeting participants, that does not transpire in real-time,
wherein the window closure criterion for the asynchronous meeting is a contribution-based criterion specifying a number of rounds of user contributions received from the meeting participants after which the asynchronous meeting terminates.
14. The system of claim 13 , wherein the set of session assets comprises at least one selected from a group consisting of a set of user contributions contributed by the user throughout the set of meeting sessions, meeting content contributed by the user throughout the set of meeting sessions, and a set of session transcripts associated with and obtained for the user throughout the set of meeting sessions.
15. The system of claim 13 , wherein the meeting collateral comprises at least one action item relevant to the asynchronous meeting and directed to the user.
16. The system of claim 15 , wherein the collateral-driven request results in a creation of at least one selected from a group consisting of a reminder object and a task object by the target third-party collaboration tool service, wherein the at least one selected from the group consisting of the reminder object and the task object associates with the at least one action item.
17. The system of claim 13 , the system further comprising:
a mesh network operatively connected to the collaboration platform service, and comprising a plurality of mesh nodes operatively connected to one another,
wherein the user operates a mesh node of the plurality of mesh nodes.