Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can monitor user or team input (and/or user input events) to the third-party meeting tool before, during, or after a meeting. Captured user input is provided to an input classifier which classifies the input as one of a set of input types. Based on the input type, parsing or analysis operations can be triggered and/or one or more API endpoints of a collaboration tool is selected such that an input to the collaboration tool, including the user input, can be provided.

Abstract: Apparatuses, systems, and techniques to track object movements in a video. In at least one embodiment, a rate, at which one or more neural networks is to identify one or more objects within the video, may be adjusted based, at least in part on one or more user-selected portions of a video frame.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can use meeting data obtained from a third-party meeting tool to obtain task information from a task management system for task associated with a current meeting being hosted by the third-party meeting tool. The bridge service can analyze the task information to determine a status of the tasks, and generate graphical summaries of the task associated with the event. The graphical summaries can be displayed to participants of the current meeting.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can monitor user or team input (and/or user input events) to the third-party meeting tool before, during, or after a meeting. Captured user input is provided to an input classifier which classifies the input as one of a set of input types. Based on the input type, parsing or analysis operations can be triggered and/or one or more API endpoints of a collaboration tool is selected such that an input to the collaboration tool, including the user input, can be provided.

Abstract: Described herein is a method that includes obtaining a first set of messages from the online chat and analyzing the first set of messages to identify a decision flag portion based on content extracted from the first set of messages. The method includes determining, based on the decision flag portion, a decision topic and a decision author, and identifying a subset of messages from the first set of messages having content corresponding to the decision topic. The method includes analyzing the subset of messages to determine a sentiment of one or more messages included in the subset of messages. The method includes generating a table content item including the decision topic or the decision author, and at least an indicium related to the sentiment, and importing the table content item into a content page for displaying in response to a request to view the content page.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can monitor user or team input (and/or user input events) to the third-party meeting tool before, during, or after a meeting. Captured user input is provided to an input classifier which classifies the input as one of a set of input types. Based on the input type, parsing or analysis operations can be triggered and/or one or more API endpoints of a collaboration tool is selected such that an input to the collaboration tool, including the user input, can be provided.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can use meeting data obtained from a third-party meeting tool to obtain task information from a task management system for task associated with a current meeting being hosted by the third-party meeting tool. The bridge service can analyze the task information to determine a status of the tasks, and generate graphical summaries of the task associated with the event. The graphical summaries can be displayed to participants of the current meeting.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can monitor user or team input (and/or user input events) to the third-party meeting tool before, during, or after a meeting. Captured user input is provided to an input classifier which classifies the input as one of a set of input types. Based on the input type, parsing or analysis operations can be triggered and/or one or more API endpoints of a collaboration tool is selected such that an input to the collaboration tool, including the user input, can be provided.

Abstract: Systems for capturing and organizing team-generated content produced during a meeting defined/facilitated by a third-party meeting tool or service. In particular, a server system includes a memory allocation and a processor allocation configured to cooperate to instantiate an instance of a bridge service configured to communicably couple to API endpoints of the third-party meeting tool and to one or more collaboration tools. The bridge service can monitor user or team input (and/or user input events) to the third-party meeting tool before, during, or after a meeting. Captured user input is provided to an input classifier which classifies the input as one of a set of input types. Based on the input type, parsing or analysis operations can be triggered and/or one or more API endpoints of a collaboration tool is selected such that an input to the collaboration tool, including the user input, can be provided.