Patent Grant
11900323
The present disclosure relates to generating units of work within a collaboration environment based on video dictation.
Collaboration environments, sometimes referred to as integrated collaboration environments, may enable users to assign projects, tasks, or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which a virtual team of users does its work. A collaboration environment may enable users to work in a more organized and efficient manner. A collaboration environment may integrate features and/or functionality such as web-based conferencing and collaboration, desktop videoconferencing, and/or instant message into a single easy-to-use, intuitive interface.
One aspect of the present disclosure relates to a system configured to generate units of work within a collaboration environment based on video dictation. Collaboration environments typically require users to manually input to-do items. Video dictation may solve one or more problems with conventional solutions where manual input of the units of work may be otherwise required. Typically, without such manual input, computers generally cannot generate and/or manage units of work for users automatically. This creates more work for users and reduces user efficiency. As such, users and companies waste valuable resources and may be unlikely to use a work management platform long term. One or more implementations of the systems and methods presented herein may facilitate determining one or more units of work in real-time and/or near real-time for one or more users participating in a video dictation session through a graphical video interface and/or based on content from a video dictation session through the graphical video interface.
One aspect of a system configured to generate units of work within a collaboration environment based on video dictation may include one or more of: one or more servers, one or more client computing platforms, and/or other components. The one or more servers may be configured to communicate with one or more client computing platforms according to a client/server architecture and/or other architecture. The one or more servers and/or client computing platforms may include one or more physical processors configured to execute one or more computer program components. The computer program components may include one or more of an environment state component, a collaboration environment component, a dictation component, a work component, a trigger phrase component, and/or other components.
The environment state component may be configured to manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment and/or other interactions. The environment state information may include work units records describing units of work assigned, created, and/or managed within the collaboration environment. The environment state component may be configured to effectuate transmission of the environment state information to client computing platform(s), and/or vice versa. In some implementations, the environment state component may be configured to receive information over a network from the client computing platforms(s). The environment state component may be configured to effectuate storage of the received information as environment state information to one or more of user records, project records, work unit records, and/or other records.
The dictation component may be configured to obtain user input information and/or other information. The user input information may characterize user-initiation of video dictation sessions by individual users of the collaboration environment.
The dictation component may be configured to obtain video information and/or other information. The video information may characterize content of the video dictation sessions. The dictation component may be configured to obtain video information responsive to the user-initiation of the video dictation sessions. The content of the video dictation sessions may comprise one or more of visual content, audio content, and/or other content. The visual content may include visual representations of the individual users during the video dictation sessions and/or other visual content. The audio content may include speech of the individual users during the video dictation sessions and/or other audio content. By way of non-limiting illustration, responsive to the user-initiation of a first video dictation session by a first user, the dictation component may obtain first video information characterizing content of the first video dictation session.
The work component may be configured to generate one or more units of work based on content of the video dictation sessions and/or other information. The work component may be configured to generate one or more units of work by storing information defining the one or more units of work as part of the environment state information. Such generation may be responsive to detection of completion of the video dictation sessions and/or other triggers. The one or more units of work may be generated by creating and/or storing one or more work unit records for the one or more units of work. By way of non-limiting illustration, a first unit of work may be generated based on the content of the first video dictation session by storing information defining the first unit of work in a first work unit record.
The work component may be configured to store the video information as part of the environment state information and/or other information. Such storage may be responsive to detection of completion of the video dictation sessions. The video information may be included in the one or more work unit records generated for the one or more units of work. By way of non-limiting illustration, the first video information may be stored in the first work unit record.
These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
The presentation of the collaboration environment may be based on environment state information and/or other information. The environment state information may include user records 128, project records 130, work unit records 132, and/or other records. The environment state information may be continuously generated and/or updated based on the state of the collaboration environment representing the users' interactions with the collaboration environment. The state of the collaboration environment may include a user state, a project state, a work unit state, and/or other states. The user state may be defined by user records 128. User records 128 may define user information associated with users interacting with and/or viewing the collaboration environment. The project state may be defined by project records 130. Project records 130 may define project information for projects managed within the collaboration environment. Managing may include one or more of obtaining, defining, storing, updating, deleting, and/or other operations. The work unit state may be defined by work unit records 132. Work unit records 132 may define work information for units of work assigned to, created by, and/or managed by individual users within the collaboration environment.
The user information may include values of user parameters and/or other information. The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters associated with the users interacting with and/or viewing the collaboration environment may include information describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment.
The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, user role information, a user department, descriptive user content, a to—email, a from—email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more work unit records), one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), a presence parameter (e.g., indicating presence and/or interaction level at an environment level, unit of work level, project level, task level, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more units of work the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), one or more performance metrics of a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of units of work, the efficiency of the user, bandwidth of the user, activity level of the user, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, schedule information, sets of preferences of a given user, other user parameters for the given user.
User role information may specify individual roles of the individual users in the individual units of work. A role may represent a position of an individual user. The position may be specified based on a description of one or more of job title, level, stage, and/or other descriptions of position. The role may be specified with respect to a company as a whole, a particular unit of work, and/or other considerations. By way of non-limiting illustration, a role may include one or more of chief executive officer (or other officer), owner, manager, supervisor, accountant, associate, employee, entry level, intern, midlevel, senior, administrator, director, foreman, engineer, product developer, human resource officer, artist, art director, and/or other description.
Schedule information for the individual users may include one or more calendar entries associated with the individual users. The individual calendar entries may be associated with individual start dates and individual end dates.
In some implementations, schedule information may be stored locally within electronic storage 126 by virtue of features and/or functionality provided within a collaboration environment. By way of non-limiting illustration, a collaboration environment may have the features and/or functionality of a calendar application configured to facilitate calendaring entries into a schedule. It is noted that schedule information may be determined through features and/or functionality provided by one or more external resources 122. By way of non-limiting illustration, an external resource may include a calendar application which may be external to a collaboration environment. The collaboration environment may have permissions to access the external calendar application to determine and/or obtain schedule information.
The work information may include values of one or more work unit parameters. The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given unit of work may have one or more assignees and/or team members working on the given unit of work. Units of work may be associated with one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. A given unit of work may include one or more of a task, a sub-task, and/or other units of work possibly assigned to and/or associated with one or more users.
The individual sets of preferences of the individual users may include individual sets of automated actions to carry out in response to occurrence of individual trigger events. The automated actions may include one or more of generation of a project, generation of a task, assignment to a particular user, attachment of one or more particular documents, setting one or more values of one or more work unit parameters, and/or other actions that may be automated responsive to trigger events.
In some implementations, individual sets of automated actions and associated individual trigger events may be stored in individual automation records. An automation record may define one or more of individual actions, individual trigger events, and/or other information. Individual actions may be defined by a target component, an action component, and/or other information. The target component of an automation record may include the environment parameter (or parameters) to which an action is to be carried out on. The action component of an automation record may define what change is to be made on the environment parameter (or parameters) defined by the target component.
Individual trigger events may be defined by a source component, an event component, and/or other information. The source component of an automation record may include the environment parameter (or parameters) from which occurrences of a trigger event may be derived. The event component may include the value (or change in the value) for the environment parameter (or parameters) defined by the source component from which occurrences of a trigger event may be derived.
In some implementations, individual automation records may store counts of occurrences of individual trigger events and/or occurrences of carrying out individual automation actions in the sets of automation actions.
It is noted that while some descriptions presented herein may be directed to an individual trigger event causing an individual set of automated actions to be carried out within the collaboration environment, this is for illustrative purposes only and not to be considered limiting. For example, in some implementations, multiple trigger events may be combined together through some logic criteria, that when satisfied, may cause an individual set of automated actions to be carried out within the collaboration environment. Logic may include, for example, Boolean logic. By way of non-limiting illustration, logic operators such as “AND”, “OR”, “NOT”, and/or other operations may be utilized to generate more complex trigger combinations for sets of automated actions. In some implementations, the use of logic operators may allow for fewer discrete trigger events to be defined yet still have more complex behavior available to users. For example, there may not be a need to specify a trigger event of “when task is unassigned”, since through the use of a logic operator “NOT”, a trigger event may be defined by “when task assigned” combined with the operator “NOT”. Further, the Boolean logic may facilitate multistage automation. By way of non-limiting illustration, instead of input “than-if-then” or “if-and-if-then”, logic may include “if-then-then” and/or other operators. In some implementations, a user may specify a set, or pool, of trigger events to trigger one or more automated actions. In some implementations, a user may specify that one or more of the trigger events in the set may individually and/or in combination trigger the one or more automated actions. This way, a user may specify multiple options of trigger events which may trigger one or more automated actions. Further, an individual trigger event may trigger multiple automated actions.
Individual work unit records may include hierarchical information defining a record hierarchy of the individual work unit records. The hierarchical information of a work unit record may include one or more of information identifying other work unit records associated in a record hierarchy the work unit record belongs to, a specification of the position of the work unit record in the hierarchy, restrictions and/or other relationships placed on the work unit record by virtue of its position, and/or other information.
A record hierarchy may convey individual positions of individual work unit records (and their corresponding units of work) in the record hierarchy. By way of non-limiting illustration, a position may specify one or more of a work unit record being superior to another work unit record, a work unit record being subordinate to another work unit record, and/or other information. As a result, individual work unit records in the individual sets of work unit records may be subordinate to other individual work unit records in the individual sets of work unit records. For example, a work unit record may define a unit of work comprising a task, and a subordinate work unit record may define a unit of work comprising a sub-task to the task. A record hierarchy may define a relationship between work unit records. A work unit record may have some restrictions placed on it by virtue of having a subordinate work unit record. By way of non-limiting illustration, a work unit record may be restricted from access by one or more users unless and/or until a subordinate work unit record is completed and/or started.
The one or more work unit parameters may include one or more of a work assignment parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users.
In some implementations, values of one or more work unit parameters of a given unit of work may describe the unit of work based on one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date, an end date, a completion date, and/or dates), one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, and/or other unit of work members and/or member information), a status parameter (e.g., an update, a hardcoded status update, a completed/uncomplete/mark complete, a measured status, a progress indication, quantity of sub-work units remaining for a given unit of work, completed units of work in a given project, and/or other status parameter), one or more user comment parameters (e.g., permission for who may comments such as a creator, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters.), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, given unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more file attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), dependencies between one or more units of work, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.
The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or an other user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.
In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date). In some implementations, for the purposes of measuring workload, values of the work assignment parameter for a unit of work indicating a status of “marked complete” and/or “complete” may be treated as if the unit of work is no longer assigned to the user for the purpose of measuring a current workload of the user.
The project information may define values of project parameters for projects managed within the collaboration environment. The project parameters may characterize one or more projects managed within the collaboration environment and/or via the collaboration work management platform, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records. The project information may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration work management platform. A given project may have one or more owners and/or one or more team members working on the given project. A given project may include one or more units of work assigned to one or more users under a given project heading. A given project may include a plurality of units of work assigned to one or more users under a given project heading.
The project parameters may, by way of non-limiting example, include one or more of: individual units of work within individual ones of the projects (which may include parameters defined by one or more work unit records), one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), one or more project members (e.g., an owner, one or more other project members, member access information, and/or other project members and/or member information), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of units of work remaining in a given project, completed units of work in a given project, and/or other status parameter), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within the given project, state of a workspace for a given task within the given project, other project parameters for the given project, and/or other information
As is illustrated in
The one or more servers 102 may include one or more physical processors 104 (also referred to herein as “one or more processors” and/or “processor(s)”), non-transitory electronic storage 126, and/or other components. Non-transitory electronic storage 126 may include one or more records. The one or more records may store the environment state information that defines the state of the collaboration environment. The state of the collaboration environment may include a user state, a project state, a work unit state, and/or other states. The records may include the user records 128, the project records 130, the work unit records 132, and/or other records. The one or more physical processors 104 may be configured to access one or more of user records 128, project records 130, work unit records 132, and/or other records to effectuate transmission of the environment state information over network 132 to client computing platform(s) 124. Client computing platform(s) 124 may use the environment state information to effectuate presentation of the collaboration environment via client computing platform(s) 124.
The one or more physical processors 104 may be configured to execute machine-readable instructions 106. The machine-readable instructions 106 may include one or more computer program components. The computer program components may include an environment state component 108 and/or other components.
The client computing platform(s) 124 may include one or more physical processors 105, non-transitory electronic storage 120, and/or other components. The one or more physical processors 105 may be configured to execute machine-readable instructions 107. The machine-readable instructions 107 may include one or more computer program components. The computer program components may include one or more of a collaboration environment component 110, a dictation component 112, a work component 114, a trigger component 116, and/or other components.
It is noted that while some computer program components may be shown and/or described as attributed to an individual one of one or more of client computing platform(s) 124 and/or server(s) 102, this is for illustrative purposes only. Instead, it is to be understand that the features and/or functionality of one or more of the computer program components attributed to client computing platform(s) 124 may additionally and/or alternatively be attributed to server(s) 102, and vice versa.
In some implementations, server(s) 102 may be configured to provide remote hosting of the features and/or functions of machine-readable instructions 106 to one or more client computing platform(s) 124 that may be remotely located from server(s) 102. In some implementations, one or more features and/or functions of server(s) 102 may be attributed as local features and/or functions of one or more client computing platform(s) 124. For example, individual ones of the client computing platform(s) 124 may include one or more additional machine-readable instructions comprising the same or similar components as machine-readable instructions 106 of server(s) 102. The client computing platform(s) 124 may be configured to locally execute the one or more components that may be the same or similar to the machine-readable instructions 106. One or more features and/or functions of machine-readable instructions 106 of server(s) 102 may be provided, at least in part, as an application program that may be executed at a given client computing platform 124. One or more features and/or functions of machine-readable instructions 107 may be provided, at least in part, at server(s) 102.
The client computing platform(s) 124 may monitor, and/or collect information for transmission to the one or more server(s) 102 to be stored as environment state information. The client computing platform(s) 124 may obtain and/or collect environment state information from the one or more server(s) 102.
Referring now to server(s) 102, the environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. Managing may include one or more of obtaining, defining, storing, updating, deleting, and/or other operations. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment and/or other interactions. The environment state information may include one or more of the user information, work information, and/or other information used to define, support, and/or otherwise maintain a collaboration environment.
The environment state component 108 of machine-readable instructions 106 may be configured to effectuate transmission of the environment state information to client computing platform(s) 124, and/or vice versa. In some implementations, environment state component 108 may be configured to receive information over network 132 from client computing platforms(s) 124. Environment state component 108 may be configured to effectuate storage of the received information as environment state information to one or more user records 128, project records 130, work unit records 132, and/or other records. Environment state component 108 may be configured to obtain one or more user records 128, project records 130, work unit records 132, and/or other records in response to and/or based on one or more requests from client computing platform(s) 124. Environment state component 108 may be configured to effectuate transmission of values for user parameters, values for project parameters, values for work unit parameters, and/or other state information to client computing platform(s) 124. The values for user parameters, values for project parameters, values for work unit parameters, and/or other state information may be used to effectuate presentation of the relevant units of work and/or projects for a given user of the collaboration environment associated with the given client computing platform to which the values and/or other state information is transmitted.
Collaboration environment component 110 of machine-readable instructions 107 of client computing platform(s) 124 may be configured to effectuate presentation of one or more user interfaces of a collaboration environment. Presentation of the collaboration environment may be based on environment state information and/or other information.
Collaboration environment component 110 may be configured to effectuate presentation of a user interface through which the users initiate individual video dictation sessions. The user interface may include one or more user interface elements. An individual user interface element may be configured to be selected by the users to cause the user-initiation of the video dictation sessions. The user interface elements may be configured to facilitate user interaction with the user interface, user entry, and/or selection. By way of non-limiting illustration, the user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other user interface elements. The user interface may be presented within and/or outside the collaboration environment. In some implementations, a user interface through which the users initiate individual video dictation sessions may be provided an external resource (e.g., an application outside of the system 100 and/or other resources).
The client computing platform(s) 124 may effectuate presentation of one or more user interfaces of the collaboration environment. The collaboration environment may include the environment in which users interact with and/or view the one or more units of work and/or projects managed via the collaboration work management platform. The collaboration environment may exist whether or not a given user is viewing and/or interacting with the collaboration environment. In some implementations, projects managed via the collaboration environment may include one or more units of work. By way of non-limiting example, the one or more units of work may include action items, to-do items, and/or objectives within a given project. The one or more units of work may be assigned to one or more users such that the one or more units of work assigned to a given user may appear on a given user's task list within the collaboration environment.
Dictation component 112 may be configured to obtain user input information and/or other information. The user input information may characterize user-initiation of the video dictation sessions by individual users of the collaboration environment. The user-initiation of the video dictation sessions by individual users may be a selection of one or more of the user interface elements, user entry by way of the one or more of the user interface elements, and/or user entry via one or more input devices (e.g., keyboard, mouse, etc.). The user interface elements may be presented to the individual users within a given project, within a given unit of work, and/or otherwise within and/or outside the collaboration environment. In some implementations, selection and/or interaction with the one or more user interface elements to initiate a video dictation session may automatically associate the video dictation session with a given project, a given unit, and/or provide other automatic association. As a result, generation of one or more values of one or more work unit parameters (e.g., assignees, due dates, start dates, etc.) of a given unit of work (e.g., task) may be generated and/or otherwise facilitate streamline generation of units of work based on the video dictation session because this information may already be known by virtue of the automatic association.
Responsive to the user-initiation of the video dictation sessions, dictation component 112 may be configured to obtain video information and/or other information. An image sensor of a client computing platform may be configured to generate output signals conveying the video information and/or other information. In some implementations, the video information may define one or more of an image, an image sequence, a video, and/or other representations of a real-world space. Individual images (e.g., video frames) may be defined by a set of pixels and/or other information. Individual pixels in the set of pixels may be defined by one or more of a pixel location, a pixel color, and/or other specifications. A pixel location may include a location on an image plane. Pixel color may be defined by chromaticity of colors specified within a color space, such as an RGB color space. An image sensor may include one or more of a charge-coupled device sensor, an active pixel sensor, a complementary metal-oxide semiconductor sensor, an N-type metal-oxide-semiconductor sensor, and/or other devices.
The video information may characterize content of the video dictation sessions. The content of the video dictation sessions may comprise one or more of visual content, audio content, and/or other content. The visual content may include visual representations of the individual users during the video dictation sessions, and/or other visual content. The audio content may include speech (e.g., words, phrases, noises, etc.) of the individual users during the video dictation sessions and/or other audio content. In some implementation, content of the video dictation sessions may be derived from the video information based on one or more video processing techniques through which individual ones of the visual content, audio content, and/or other content may be determined.
By way of non-limiting illustration, the video dictation sessions may include a first video dictation session. The first video dictation session may be responsive to a user-initiation by the first user. First video information characterizing content of the first video dictation session may be obtained. In some implementations, the video dictation sessions may be related to and/or specific to a given project and/or task within the collaboration environment. As such, a user participating in a given video dictation session may be working on and/or discussing a related and/or specific project and/or task. The first video dictation session may be a task-specific video dictation session. For example, the first video dictation session may relate to Task A. Dictation component 112 may be configured to transcribe one or more spoken communications. In some implementations, dictation component 112 may be configured to determine a source and/or intended recipient of individual items within the video dictation session.
In some implementations, dictation component 112 may be configured to implement an instance of a video dictation session through one or more user interfaces. Dictation component 112 may receive an/or transmit the communications (e.g., textual communications, voice communications, video communications, etc.) that make up the video dictation session to and/or from client computing platform(s) 124 and server(s) 102. The graphical video interface may be part of and/or external to the collaboration environment. The video dictation sessions may be hosted by the collaboration platform and/or one or more third party chat applications integrated with the collaboration platform via an application program interface (API). The video-sessions may be provided by one or more third-party video applications via one or more APIs. In some implementations the collaboration platform may host and/or provide one or more of the video dictation sessions. In some implementations, a video dictation session may correspond to a pre-recorded video dictation session, such as a recorded meeting between one or more users. By way of non-limiting illustration, a meeting between one or more users may be video recorded. The recording may comprise one or more of the visual content, audio content, and/or other content utilized to carry out one or more features and/or functionality described herein.
In some implementations, a video interface may include its own interface and/or a portion of one or more collaboration environment user interfaces for displaying one or more units of work and/or projects for a given user. Dictation component 112 may be configured to effectuate presentation of the video interfaces via the client computing platforms within and/or outside the collaboration environment. By way of non-limiting illustration, first video dictation session may be presented to the first user via a first video interface presented on a first client computing platform associated with the first user.
Work component 114 may be configured to generate one or more units of work for the users based on the content of the video dictation sessions by storing information defining the one or more units of work as part of the environment state information. Such generation may be responsive to detection of completion of the video dictation sessions. By way of non-limiting illustration, one or more work unit records of the one or more units of work may be generated. A first unit of work may be generated based on the content of the first video dictation session by storing information defining the first unit of work in a first work unit record.
In some implementations, generating the one or more units of work may be based on the content from the video dictation sessions may include automatically generating one or more values of one or more work unit parameters of the one or more units of work. Generating the units of work based on the content from the video dictation sessions may include automatically initiating the one or more units of work, and/or automatically generating one or more values of one or more work unit parameters describing the units of work. In some implementations, the one or more values of the one or more work unit parameters may include one or more of a title, a description, a due-date, an assignee, a start date, a project and/or unit of work associated with the generated unit of work, a dependency within a hierarchy, indication of complete and/or incomplete, custom fields, and/or other values. In some implementations, generating the one or more units of work may include automatically generating other metadata associated with the one or more units of work.
In some implementations, the units of work may be generated in real-time and/or near real-time during the video dictation session. By way of non-limiting example, as the user starts speaking within the video interface, work component 114 may identify one or more units of work that should be generated. The units of work, in some implementations, may be generated at or near the conclusion of the video dictation sessions. In some implementations, one or more units of work generated based on the content from the video dictation sessions may be presented to one or more of the users as one or more potential units of work. The potential units of work may be presented to the one or more users for confirmation and/or acceptance. One or more of the users may accept and/or confirm one or more of the potential units of work at the conclusion of the given video dictation session to generate the units of work. A video dictation session may conclude when: a threshold amount of time passes without any communication from one or more users, a user exits or closes the video interface, the user minimizes the video interface, the user responds to a request with acceptance language and/or the user otherwise concludes the video dictation session.
In some implementations, visual content from the video dictation sessions that may trigger generation of the one or more units of work for the users may include one or more trigger gestures and/or emotes. The trigger gestures and/or emotes may indicate a user's request, desire, inquiry, and/or need. By way of non-limiting illustration, a trigger gesture to generate a unit of work may include a thumbs-up gesture and/or other gestures conveying a desire to do something they are talking about. By way of non-limiting illustration, a trigger gesture and/or emote to generate a unit of work with low priority may include a shaking of the head and/or other gestures conveying a desire to do something but having little importance. The one or more units of work may be generated for the individual users based on identifying one or more of the trigger gestures and/or emotes from the visual content. Trigger gestures and/or emotes may be detected and/or identified from visual content based on one or more video processing techniques. By way of non-limiting illustration, the first unit of work may be generated based on identifying a first gesture and/or emote from the visual content in the content of the first video dictation session.
In some implementations, audio content from the video dictation sessions that may trigger generation of the units of work for the users may include one or more trigger phrases and/or words. In some implementations, dictation component 112 may be configured to detect and/or identify one or more trigger phrases and/or words based on natural language processing and/or other audio processing techniques. The trigger phrases and/or words may indicate a user's request, desire, inquiry, and/or need. By way of non-limiting illustration, the one or more units of work may be generated based on identifying one or more of the trigger phrases and/or words from the audio content. In some implementations, trigger phrases and/or words may include one or more of “to do”, “need to”, “should do”, “check on”, “I need”, “UserA should”, “Did I,” and/or other words and/or phrases. In some implementations, trigger phrases and/or words may be direct recitations of values of one or more work unit parameters of a unit of work to be generated. By way of non-limiting illustration, a user may directly speak a desire to generate a unit of work, with a specific due date, and/or assigned to a specific assignee. By way of non-limiting illustration, a first unit of work may be generated based on identifying a first trigger phrase and/or word from the audio content in the content of the first video dictation session.
In some implementations, work component 114 may be configured to determine context of the video information. Work component 114 may be configured to generate one or more units of work for the users based on the context of the video information. Context may include user information for a user participating in the video dictation session, user information for one or more users identified in the video dictation session, and/or other context information. By way of non-limiting illustration, image-processing techniques, such as facial recognition, may be used to identify a user of a video dictation session. User information for the user may then be obtained. By way of non-limiting illustration, the first video information may include first context information. The first unit of work may be generated based on the first context information and/or other information.
In some implementations, work component 114 may be configured to identify individual users of the video dictation sessions based on the context of the video dictation sessions and/or other content. The individual users may be identified based on the audio content (e.g., a spoken name) and/or the visual content (e.g., appearing the video dictation session). In some implementations, individual users may be prompted (through a notification) to explicitly identify the user(s) of the video dictation sessions.
Work component 114 may be configured to obtain individual user records for the individual users. As previously described, individual user records may specify individual sets of preferences of the individual users. Work component 114 may be configured to generate the one or more units of work for the users further based on the individual sets of preferences of the individual users.
In some implementations, work component 114 may identify one or more recommended units of work that should and/or could be generated. The work unit component 114 may be configured to effectuate presentation of one or more recommendation including one or more prompts for generating the one or more recommended units of work. By way of non-limiting example, if a user starts speaking “I need to follow-up with X supplier . . . ”, work component 114 may prompt the user with a recommendation for generating a corresponding unit of work. The prompt may be presented within the video interface in real time and/or near real time during the video dictation session. The user may be able to provide entry and/or selection to accept and/or deny recommendations. By way of non-limiting illustration, work component 114 may generate the unit of work for following-up with X supplier based on the responses to these prompts.
In some implementations, individual units of work may be automatically generated and/or accepted by the users. By way of non-limiting example, the work component 114 may be configured to identify acceptance language based on the video information for the video dictation sessions. Responsive to the work component 114 identifying acceptance language in response to communications triggering generation of a unit of work, work component 114 may automatically accept one or more generated units of work on behalf of the user. Acceptance may be provided through selection of a user interface element (e.g., a virtual button).
Work component 114 may be configured to store the video information as part of the environment state information. Such storage may be responsive to detection of completion of the video dictation sessions. As such, the video information may be included in the one or more work unit records generated for the one or more units of work. By way of non-limiting illustration, the first video information may be stored in the first work unit record. Work component 114 may be configured to communicate with collaboration environment component 110 and/or environment state component 108 to effectuate storage of the information defining the units of work generated as part of the environment state information.
In some implementations, work component 114 may be configured to modify one or more units of work based on the content from the video dictation sessions. Modifying one or more units of work may include modifying, changing, adjusting, adding, and/or removing one or more characteristics associated with individual ones of the units of work. By way of non-limiting example, the one or more characteristics of individual ones of the units of work may include one or more of a task description, a user assigned to a task, a due date, a start date, and/or other characteristics of the individual ones of the units of work. A second task may be modified based on the content of the first video information of the first video dictation session. Work component 114 may be configured to store information defining modifications of the units of work as part of the environment state information. As such, information defining a first modification for the second unit of work may be stored in a second work unit record of the second unit of work. In some implementations, modification of units of work may be determined based on one or more trigger phrases and/or words, and/or one or more trigger gestures and/or emotes.
The trigger component 116 may be configured to store trigger information. The trigger information may include trigger gestures and/or emotes, and/or trigger phrases and/or words, and the corresponding values of work unit parameter that may be generated (and/or modified) for one or more units of work. In some implementation, the trigger gestures and/or emotes, and/or trigger phrases and/or words, may be user-specific and/or system-wide. In some implementations, the trigger gestures and/or emotes, and/or trigger phrases and/or words, may be set by users and stored within the user records for the users. In some implementations, the trigger component 116 may be configured to determine trigger gestures and/or emotes, and/or trigger phrases and/or words, through one or more machine learning techniques. By way of non-limiting illustration, a user may go through a training process where a video dictation session and desired units of work are provided as input to train a machine learning model.
Returning to
A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resources 122, and/or provide other functionality attributed herein to client computing platform(s) 124. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.
External resources 122 may include sources of information outside of system 100, external entities participating with system 100, hosts of video recording functionality, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 124 may be provided by resources included in system 100.
Server(s) 102 may include electronic storage 126, one or more processors 104, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in
Processor(s) 104 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 104 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 104 is shown in
It should be appreciated that although component 108 is illustrated in
Processor(s) 105 may be configured to provide information processing capabilities in client computing platform(s) 124. As such, processor(s) 105 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 105 is shown in
The electronic storage 126 may include electronic storage media that electronically stores information. The electronic storage media of electronic storage 126 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with one or more servers 102 and/or removable storage that is removably connected to one or more servers 102. The connection may be facilitated by, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.).
The electronic storage 126 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storage 126 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). The electronic storage 126 may store software algorithms, information determined by processor(s) 104, information received by one or more servers 102, information received by client computing platforms 124, and/or other information that enables one or more servers 102 to function as described herein.
The electronic storage 126 may be configured to store one or more records and/or information. The one or more records may include one or more of user records 128, project records 130, work unit records 132, and/or other records. The one or more records (e.g., user records 128, project records 130, work unit records 132, and/or other records) may specify and or define values for one or more user parameters, project parameters, work unit parameters, and/or other parameters for the collaboration environment. The one or more records may specify correspondences between one or more of the user records 128, project records 130, work unit records 132, and/or other records. The correspondences may be used to determine which user parameters and/or values, project parameters and/or values, and/or work unit parameters and/or values are associated with a given user, project, and/or unit of work within the collaboration environment.
The electronic storage 120 may include electronic storage media that electronically stores information. The electronic storage media of electronic storage 120 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with one or more client computing platforms 124 and/or removable storage that is removably connected to one or more client computing platforms 124. The connection may be facilitated by, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.).
The electronic storage 120 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storage 120 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). The electronic storage 120 may store software algorithms, information determined by processor(s) 105, information received from one or more servers 102, information received by client computing platforms 124, and/or other information that enables one or more client computing platforms 124 to function as described herein.
In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.
An operation 202 may include managing environment state information maintaining a collaboration environment. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.
An operation 204 may include obtaining user input information characterizing user-initiation of video dictation sessions by individual users of the collaboration environment. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to dictation component 112, in accordance with one or more implementations.
An operation 206 may include obtaining video information characterizing content of the video dictation sessions. Such obtaining may be responsive to the user-initiation of the video dictation sessions. Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to dictation component 112, in accordance with one or more implementations.
An operation 208 may include generating one or more units of work for the users based on the content of the video dictation sessions. Generating the one or more units of work may be by storing information defining the one or more units of work as part of the environment state information. Such generating may be responsive to detection of completion of the video dictation sessions. Operation 208 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to work component 114, in accordance with one or more implementations.
An operation 210 may include storing the video information as part of the environment state information. Such storing may be responsive to detection of completion of the video dictation sessions. Operation 210 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to work component 114, in accordance with one or more implementations.
Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5530861 | Diamant | Jun 1996 | A |
| 5608898 | Turpin | Mar 1997 | A |
| 5611076 | Durflinger | Mar 1997 | A |
| 5721770 | Kohler | Feb 1998 | A |
| 6292830 | Taylor | Sep 2001 | B1 |
| 6332147 | Moran | Dec 2001 | B1 |
| 6385639 | Togawa | May 2002 | B1 |
| 6629081 | Cornelius | Sep 2003 | B1 |
| 6769013 | Frees | Jul 2004 | B2 |
| 7020697 | Goodman | Mar 2006 | B1 |
| 7086062 | Faour | Aug 2006 | B1 |
| 7640511 | Keel | Dec 2009 | B1 |
| 7676542 | Moser | Mar 2010 | B2 |
| 7779039 | Weissman | Aug 2010 | B2 |
| RE41848 | Daniell | Oct 2010 | E |
| 7844454 | Coles | Nov 2010 | B2 |
| 7996744 | Ojala | Aug 2011 | B2 |
| 7996774 | Sidenur | Aug 2011 | B1 |
| 8522240 | Merwarth | Aug 2013 | B1 |
| 8527287 | Bhatia | Sep 2013 | B1 |
| 8768751 | Jakowski | Jul 2014 | B2 |
| 9201952 | Chau | Dec 2015 | B1 |
| 9208262 | Bechtel | Dec 2015 | B2 |
| 9251484 | Cantor | Feb 2016 | B2 |
| 9299039 | Wang | Mar 2016 | B1 |
| 9600136 | Yang | Mar 2017 | B1 |
| 9674361 | Ristock | Jun 2017 | B2 |
| 9712576 | Gill | Jul 2017 | B1 |
| 9830398 | Schneider | Nov 2017 | B2 |
| 9949681 | Badenes | Apr 2018 | B2 |
| 9953282 | Shaouy | Apr 2018 | B2 |
| 10001911 | Breedvelt-Schouten | Jun 2018 | B2 |
| 10264067 | Subramani | Apr 2019 | B2 |
| 10308992 | Chauvin | Jun 2019 | B2 |
| 10373084 | Kurjanowicz | Aug 2019 | B2 |
| 10455011 | Kendall | Oct 2019 | B2 |
| 10594788 | Larabie-Belanger | Mar 2020 | B2 |
| 10616151 | Cameron | Apr 2020 | B1 |
| 10623359 | Rosenstein | Apr 2020 | B1 |
| 10657501 | Choi | May 2020 | B2 |
| 10671692 | Koopman | Jun 2020 | B2 |
| 10810222 | Koch | Oct 2020 | B2 |
| 10846105 | Granot | Nov 2020 | B2 |
| 10846297 | Smith | Nov 2020 | B2 |
| 10922104 | Sabo | Feb 2021 | B2 |
| 10956845 | Sabo | Mar 2021 | B1 |
| 10977434 | Pelz | Apr 2021 | B2 |
| 10983685 | Karpe | Apr 2021 | B2 |
| 11062270 | Hilleli | Jul 2021 | B2 |
| 11082281 | Rosenstein | Aug 2021 | B2 |
| 11095468 | Pandey | Aug 2021 | B1 |
| 11140174 | Patel | Oct 2021 | B2 |
| 11170761 | Thomson | Nov 2021 | B2 |
| 11204683 | Sabo | Dec 2021 | B1 |
| 11212242 | Cameron | Dec 2021 | B2 |
| 11263228 | Koch | Mar 2022 | B2 |
| 11287946 | Jackson | Mar 2022 | B2 |
| 11288081 | Sabo | Mar 2022 | B2 |
| 11290296 | Raghavan | Mar 2022 | B2 |
| 11327645 | Karpe | May 2022 | B2 |
| 11341444 | Sabo | May 2022 | B2 |
| 11341445 | Cheng | May 2022 | B1 |
| 11496711 | Cronan | Nov 2022 | B1 |
| 11627006 | Chew | Apr 2023 | B1 |
| 11676107 | Beauchamp | Jun 2023 | B1 |
| 20020143594 | Kroeger | Oct 2002 | A1 |
| 20030028595 | Vogt | Feb 2003 | A1 |
| 20030041317 | Sokolov | Feb 2003 | A1 |
| 20030065722 | Ieperen | Apr 2003 | A1 |
| 20030097406 | Stafford | May 2003 | A1 |
| 20030097410 | Atkins | May 2003 | A1 |
| 20030126001 | Northcutt | Jul 2003 | A1 |
| 20030200223 | Hack | Oct 2003 | A1 |
| 20030225598 | Yu | Dec 2003 | A1 |
| 20040093290 | Doss | May 2004 | A1 |
| 20040098291 | Newburn | May 2004 | A1 |
| 20040162833 | Jones | Aug 2004 | A1 |
| 20040207249 | Baumgartner | Oct 2004 | A1 |
| 20040210470 | Rusk | Oct 2004 | A1 |
| 20040230447 | Schwerin-Wenzel | Nov 2004 | A1 |
| 20040268451 | Robbin | Dec 2004 | A1 |
| 20050210394 | Crandall | Sep 2005 | A1 |
| 20050222971 | Cary | Oct 2005 | A1 |
| 20060030992 | Iwatsuki | Feb 2006 | A1 |
| 20060047454 | Tamaki | Mar 2006 | A1 |
| 20060095859 | Bocking | May 2006 | A1 |
| 20060136441 | Fujisaki | Jun 2006 | A1 |
| 20060143270 | Wodtke | Jun 2006 | A1 |
| 20060190391 | Cullen | Aug 2006 | A1 |
| 20060277487 | Poulsen | Dec 2006 | A1 |
| 20070016465 | Schaad | Jan 2007 | A1 |
| 20070038494 | Kreitzberg | Feb 2007 | A1 |
| 20070143169 | Grant | Jun 2007 | A1 |
| 20070255715 | Li | Nov 2007 | A1 |
| 20080082389 | Gura | Apr 2008 | A1 |
| 20080082956 | Gura | Apr 2008 | A1 |
| 20080091782 | Jakobson | Apr 2008 | A1 |
| 20080155547 | Weber | Jun 2008 | A1 |
| 20080158023 | Chung | Jul 2008 | A1 |
| 20080167937 | Coughlin | Jul 2008 | A1 |
| 20080222566 | Daughtrey | Sep 2008 | A1 |
| 20080244582 | Brown | Oct 2008 | A1 |
| 20080270198 | Graves | Oct 2008 | A1 |
| 20080281665 | Opaluch | Nov 2008 | A1 |
| 20090018835 | Cooper | Jan 2009 | A1 |
| 20090055796 | Springborn | Feb 2009 | A1 |
| 20090089225 | Baier | Apr 2009 | A1 |
| 20090089682 | Baier | Apr 2009 | A1 |
| 20090089701 | Baier | Apr 2009 | A1 |
| 20090100340 | Paek | Apr 2009 | A1 |
| 20090113310 | Appleyard | Apr 2009 | A1 |
| 20090287523 | Lau | Nov 2009 | A1 |
| 20090296908 | Lee | Dec 2009 | A1 |
| 20090299803 | Lakritz | Dec 2009 | A1 |
| 20090307319 | Dholakia | Dec 2009 | A1 |
| 20100088137 | Weiss | Apr 2010 | A1 |
| 20100106627 | O'Sullivan | Apr 2010 | A1 |
| 20100122334 | Stanzione | May 2010 | A1 |
| 20100131860 | Dehaan | May 2010 | A1 |
| 20100145801 | Chekuri | Jun 2010 | A1 |
| 20100169802 | Goldstein | Jul 2010 | A1 |
| 20100312605 | Mitchell | Dec 2010 | A1 |
| 20100332236 | Tan | Dec 2010 | A1 |
| 20110015961 | Chan | Jan 2011 | A1 |
| 20110022662 | Barber-Mingo | Jan 2011 | A1 |
| 20110054968 | Galaviz | Mar 2011 | A1 |
| 20110060720 | Devereux | Mar 2011 | A1 |
| 20110161128 | Barney | Jun 2011 | A1 |
| 20110307100 | Schmidtke | Dec 2011 | A1 |
| 20120035942 | Graupner | Feb 2012 | A1 |
| 20120066030 | Limpert | Mar 2012 | A1 |
| 20120123835 | Chu | May 2012 | A1 |
| 20120158946 | Shafiee | Jun 2012 | A1 |
| 20120192086 | Ghods | Jul 2012 | A1 |
| 20120304187 | Maresh | Nov 2012 | A1 |
| 20120317108 | Okazaki | Dec 2012 | A1 |
| 20130007332 | Teh | Jan 2013 | A1 |
| 20130013560 | Goldberg | Jan 2013 | A1 |
| 20130014023 | Lee | Jan 2013 | A1 |
| 20130066944 | Laredo | Mar 2013 | A1 |
| 20130073328 | Ehrler | Mar 2013 | A1 |
| 20130124638 | Barreto | May 2013 | A1 |
| 20130179799 | Savage | Jul 2013 | A1 |
| 20130246399 | Schneider | Sep 2013 | A1 |
| 20130275229 | Moganti | Oct 2013 | A1 |
| 20130279685 | Kohler | Oct 2013 | A1 |
| 20130318447 | Deluca | Nov 2013 | A1 |
| 20130321467 | Tappen | Dec 2013 | A1 |
| 20130339099 | Aidroos | Dec 2013 | A1 |
| 20140012603 | Scanlon | Jan 2014 | A1 |
| 20140028826 | Lee | Jan 2014 | A1 |
| 20140040780 | Artz | Feb 2014 | A1 |
| 20140040905 | Tadanobu | Feb 2014 | A1 |
| 20140058801 | Deodhar | Feb 2014 | A1 |
| 20140059910 | Norton | Mar 2014 | A1 |
| 20140089719 | Daum | Mar 2014 | A1 |
| 20140172478 | Vadasz | Jun 2014 | A1 |
| 20140189017 | Prakash | Jul 2014 | A1 |
| 20140200944 | Henriksen | Jul 2014 | A1 |
| 20140208325 | Chen | Jul 2014 | A1 |
| 20140218372 | Missig | Aug 2014 | A1 |
| 20140236663 | Smith | Aug 2014 | A1 |
| 20140257894 | Melahn | Sep 2014 | A1 |
| 20140288987 | Liu | Sep 2014 | A1 |
| 20150006448 | Gupta | Jan 2015 | A1 |
| 20150007058 | Wooten | Jan 2015 | A1 |
| 20150113540 | Rabinovici | Apr 2015 | A1 |
| 20150149540 | Barker | May 2015 | A1 |
| 20150153906 | Liao | Jun 2015 | A1 |
| 20150154291 | Shepherd | Jun 2015 | A1 |
| 20150169069 | Lo | Jun 2015 | A1 |
| 20150181020 | Fitzsimmons | Jun 2015 | A1 |
| 20150215256 | Ghafourifar | Jul 2015 | A1 |
| 20150262111 | Yu | Sep 2015 | A1 |
| 20150363092 | Morton | Dec 2015 | A1 |
| 20150379472 | Gilmour | Dec 2015 | A1 |
| 20160048408 | Madhu | Feb 2016 | A1 |
| 20160063192 | Johnson | Mar 2016 | A1 |
| 20160063449 | Duggan | Mar 2016 | A1 |
| 20160110670 | Chatterjee | Apr 2016 | A1 |
| 20160124775 | Ashtiani | May 2016 | A1 |
| 20160162819 | Hakman | Jun 2016 | A1 |
| 20160180277 | Skiba | Jun 2016 | A1 |
| 20160180298 | McClement | Jun 2016 | A1 |
| 20160182311 | Borna | Jun 2016 | A1 |
| 20160188145 | Vida | Jun 2016 | A1 |
| 20160216854 | McClellan | Jul 2016 | A1 |
| 20160224939 | Chen | Aug 2016 | A1 |
| 20160275436 | Kurjanowicz | Sep 2016 | A1 |
| 20160328217 | Hagerty | Nov 2016 | A1 |
| 20170017924 | Kashiwagi | Jan 2017 | A1 |
| 20170039503 | Jones | Feb 2017 | A1 |
| 20170061341 | Haas | Mar 2017 | A1 |
| 20170068933 | Norton | Mar 2017 | A1 |
| 20170093874 | Uthe | Mar 2017 | A1 |
| 20170097929 | Cecchi | Apr 2017 | A1 |
| 20170103369 | Thompson | Apr 2017 | A1 |
| 20170116552 | Deodhar | Apr 2017 | A1 |
| 20170132200 | Noland | May 2017 | A1 |
| 20170154024 | Subramanya | Jun 2017 | A1 |
| 20170161258 | Astigarraga | Jun 2017 | A1 |
| 20170206217 | Deshpande | Jul 2017 | A1 |
| 20170249577 | Nishikawa | Aug 2017 | A1 |
| 20170316367 | Candito | Nov 2017 | A1 |
| 20170317898 | Candito | Nov 2017 | A1 |
| 20170323233 | Bencke | Nov 2017 | A1 |
| 20170323350 | Laderer | Nov 2017 | A1 |
| 20170344754 | Kumar | Nov 2017 | A1 |
| 20170346861 | Pearl | Nov 2017 | A1 |
| 20170351385 | Ertmann | Dec 2017 | A1 |
| 20170364866 | Steplyk | Dec 2017 | A1 |
| 20180052943 | Hui | Feb 2018 | A1 |
| 20180059910 | Wooten | Mar 2018 | A1 |
| 20180060818 | Ishiyama | Mar 2018 | A1 |
| 20180075387 | Kulkarni | Mar 2018 | A1 |
| 20180089625 | Rosati | Mar 2018 | A1 |
| 20180102989 | Borsutsky | Apr 2018 | A1 |
| 20180131649 | Ma | May 2018 | A1 |
| 20180165610 | Dumant | Jun 2018 | A1 |
| 20180173386 | Adika | Jun 2018 | A1 |
| 20180189706 | Newhouse | Jul 2018 | A1 |
| 20180189736 | Guo | Jul 2018 | A1 |
| 20180225618 | Shaouy | Aug 2018 | A1 |
| 20180225795 | Napoli | Aug 2018 | A1 |
| 20180247352 | Rogers | Aug 2018 | A1 |
| 20180247648 | Nadimpalli | Aug 2018 | A1 |
| 20180260081 | Beaudoin | Sep 2018 | A1 |
| 20180316636 | Kamat | Nov 2018 | A1 |
| 20180331842 | Faulkner | Nov 2018 | A1 |
| 20180341903 | Keen | Nov 2018 | A1 |
| 20180367477 | Hariram | Dec 2018 | A1 |
| 20180367483 | Rodriguez | Dec 2018 | A1 |
| 20190014070 | Mertvetsov | Jan 2019 | A1 |
| 20190018552 | Bloy | Jan 2019 | A1 |
| 20190050811 | Kang | Feb 2019 | A1 |
| 20190138583 | Silk | May 2019 | A1 |
| 20190138589 | Udell | May 2019 | A1 |
| 20190139004 | Vukovic | May 2019 | A1 |
| 20190187987 | Fauchère | Jun 2019 | A1 |
| 20190258985 | Daniek | Aug 2019 | A1 |
| 20190265821 | Pearl | Aug 2019 | A1 |
| 20190272902 | Vozila | Sep 2019 | A1 |
| 20190318321 | Lopez Venegas | Oct 2019 | A1 |
| 20190340574 | Ekambaram | Nov 2019 | A1 |
| 20190347126 | Bhandari | Nov 2019 | A1 |
| 20190362252 | Miller | Nov 2019 | A1 |
| 20200019907 | Notani | Jan 2020 | A1 |
| 20200059539 | Wang | Feb 2020 | A1 |
| 20200065736 | Relangi | Feb 2020 | A1 |
| 20200074510 | Corodimas | Mar 2020 | A1 |
| 20200118568 | Kudurshian | Apr 2020 | A1 |
| 20200162315 | Siddiqi | May 2020 | A1 |
| 20200193556 | Jin | Jun 2020 | A1 |
| 20200228474 | Cameron | Jul 2020 | A1 |
| 20200233879 | Papanicolaou | Jul 2020 | A1 |
| 20200244611 | Rosenstein | Jul 2020 | A1 |
| 20200328906 | Raghavan | Oct 2020 | A1 |
| 20200344253 | Kurup | Oct 2020 | A1 |
| 20200349614 | Batcha | Nov 2020 | A1 |
| 20210004380 | Koch | Jan 2021 | A1 |
| 20210004381 | Smith | Jan 2021 | A1 |
| 20210089860 | Heere | Mar 2021 | A1 |
| 20210097466 | Sabo | Apr 2021 | A1 |
| 20210103451 | Sabo | Apr 2021 | A1 |
| 20210110347 | Khalil | Apr 2021 | A1 |
| 20210117479 | Liu | Apr 2021 | A1 |
| 20210134296 | Iturbe Desentis | May 2021 | A1 |
| 20210136012 | Barbitta | May 2021 | A1 |
| 20210182475 | Pelz | Jun 2021 | A1 |
| 20210209561 | Kishore | Jul 2021 | A1 |
| 20210216562 | Smith | Jul 2021 | A1 |
| 20210232282 | Karpe | Jul 2021 | A1 |
| 20210287673 | Kaplan | Sep 2021 | A1 |
| 20210319408 | Jorasch | Oct 2021 | A1 |
| 20210320891 | Rosenstein | Oct 2021 | A1 |
| 20210342786 | Jiang | Nov 2021 | A1 |
| 20210365862 | Doan | Nov 2021 | A1 |
| 20210382734 | Rosenstein | Dec 2021 | A1 |
| 20220019320 | Sabo | Jan 2022 | A1 |
| 20220058548 | Garg | Feb 2022 | A1 |
| 20220060345 | Wiener | Feb 2022 | A1 |
| 20220075792 | Koch | Mar 2022 | A1 |
| 20220078142 | Cameron | Mar 2022 | A1 |
| 20220158859 | Raghavan | May 2022 | A1 |
| 20220207489 | Gupta | Jun 2022 | A1 |
| 20220377279 | Cronan | Nov 2022 | A1 |
| 20230071838 | Hood | Mar 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 101305350 | Nov 2008 | CN |
| 101563671 | Oct 2009 | CN |
| 102378975 | May 2015 | CN |
| 2015036817 | Mar 2015 | WO |
| 2015123751 | Aug 2015 | WO |
| 2020006634 | Jan 2020 | WO |
| Entry |
|---|
| Sarikaya, Ruhi. “The technology behind personal digital assistants: An overview of the system architecture and key components.” IEEE Signal Processing Magazine 34.1 (2017): 67-81. (Year: 2017). |
| Nanos, Antonios G., and Anne E. James. “A virtual meeting system for the new age.” 2013 IEEE 10th International Conference on e-Business Engineering. IEEE, 2013. (Year: 2013). |
| Dawei Li, “Deepcham: Collaborative Edge-Mediated Adaptive Deep Learning for Mobile Object Recognition”, 2016, IEEE/ACM, pp. 64-76. (Year: 2016). |
| Assef, F., Cassius, T. S., & Maria, T. S. (2018). Confrontation between techniques of time measurement. Journal of Manufacturing Technology Management, 29(5), 789-810. (Year: 2018). |
| Macro, computer science, wikipedia, archives org Feb. 11, 2020 http://web.archive.org/web/20200211082902/https://en.wikipedia.org/wiki/Macro_(computer_science) (Year: 2020). |
| Creating Tables with Fields from 2 Different Tables, published: 2009, publisher: StackOverflow, pp. 1-2. (Year: 2009). |
| “Rules of Data Conversion from Document to Relational Databases”, published: 2014, publisher: Future-processing, pp. 1-8 (Year: 2014). |
| Helen Mongan-Rallis & Terrie Shannon, “Synchronous Chat,” Aug. 2016, Dept. of Education, Univ. of MN Duluth, web.archive.org/web/20160825183503/https://www.d.umn.edu/hrallis/professional/presentations/cotfsp06/indiv_tools/sync_chat.htm (Year: 2016) (2 pages). |
| Wix.com, How to Use Wix Code with Marketing Tools to Create Custom Events, Oct. 18, 2018, YouTube, https://www.youtube.com/watch?v=MTBVykOYGvO&feature=emb_title, 2 pages. |
| Critical chain project management, Wikipedia, archives org, Dec. 17, 2016 https://web.archive.Org/web/20161217090326/https://en.wikipedia.org/wiki/Critical_chain_project_management (Year: 2016) 5 pages. |
| Critical Path Method, Wikipedia, archives org, Sep. 19, 2017 https://web.archive.Org/web/20170919223814/https://en.wikipedia.org/wiki/Critical_path_method (Year: 2017) 6 pages. |
| Fruhlinger, Joshua. “The Best To-Do ListApps for Feeling Productive; With the right app, feeling productive can be just as gratifying as actually getting things done” Wall Street Journal (Online); New York, N.Y. [New York, N.Y]Nov. 8, 2013 (Year: 2013) 4 pages. |
| www.asana.com (as retrieved from https://web.archive.Org/web/20160101054536/https://asana.com/press and https:// web.archive.org/web/20160101054527/https://asana.com/product) (Year: 2016) 15 pages. |
| Tiburca, Andrew) Best Team Calendar Applications for 2018-Toggl https://toggl.com/blog/best-team-calendar-applications-for-2018 (Year: 2017). |
| Lauren Labrecque, “Fostering Consumer-Brand Relationships in Social Media Environments: The Role of Parasocial Interaction”, 2014, Journal of Interactive Markeing, 28 (2014), pp. 134-148 (Year: 2014). |
| Hartmann, “TimeProjectscheduling with resource capacities and requests varying with time: a case study,” 2013, Flexible services and manufacturing journal, vol. 25, No. 1, pp. 74-93 (Year: 2013). |
| Paul Minors, How to automate your tasks, youtube excerpts, Oct. 18, 2019 https://www.youtube.com/watch?v=IwF9XyUQrzw (Year: 2019). |
| Mauricio Aizawa, Zapier, How to Automate Asana Tasks creation using Evernote, youtube excerpts, Mar. 16, 2018 https://www.youtube.com/watch?v=BjDQ4Gny4WI (Year: 2018). |
| Cabanillas, Cristina, Manuel Resinas, and Antonio Ruiz-Cortés. “A template-based approach for responsibility management in executable business processes.” Enterprise information systems 12.5 (2018): 550-586. (Year: 2018). |
| Shi, Yang, et al. “Meetingvis: Visual narratives to assist in recalling meeting context and content.” IEEE Transactions on Visualization and Computer Graphics 24.6 (2018): 1918-1929. (Year: 2018). |
| Number | Date | Country | |
|---|---|---|---|
| 62705465 | Jun 2020 | US |
