US2014208325A1PendingUtilityA1

Systems and methods for managing tasks

61
Assignee: BROADVISION INCPriority: Jan 24, 2013Filed: Jan 23, 2014Published: Jul 24, 2014
Est. expiryJan 24, 2033(~6.5 yrs left)· nominal 20-yr term from priority
G06Q 10/06311G06Q 10/107G06F 9/4881
61
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Systems and methods for creating and sharing tasks over one or more networks are disclosed. In one embodiment, a system comprises a message retrieval module configured to retrieve electronic messages and parse them into a plurality of tasks. The system can also include a task creation module configured to process the message to identify task information and one or more task recipients. The task creation module can also be configured to create a task based on the identified task information. A task notification module can be configured to notify the one or more task recipients about the created task. The system may also include a multi-layer network management module configured to organize the tasks and task participants into multiple networks and clouds and into a federation of clouds. The system can also include a task analytics module programmed to analyze the tasks performed by users of the system.

Claims

exact text as granted — not AI-modified
1 . (canceled) 
     
     
         2 . A computer-implemented method for managing tasks stored on a system of one or more networks, the method comprising:
 providing a graphical user interface that lists a plurality of tasks, wherein each task comprises task information;   associating each task with one or more authorized users;   organizing each task into one or more persistent containers;   updating a status to each task that indicates the status of that task within the system;   displaying the assigned status on the graphical user interface to each of the authorized users associated with the task; and   tracking a history of one or more tasks in each of the one or more persistent containers over time.   
     
     
         3 . The method of  claim 1 , further comprising tracking the status of each task over time. 
     
     
         4 . The method of  claim 1 , further comprising notifying at least one authorized user about at least one of the status of a task, documents associated with the task, comments associated with the task, other users associated with the task, and changes to the task information. 
     
     
         5 . The method of  claim 1 , further comprising tracking actions of the one or more authorized users over time. 
     
     
         6 . The method of  claim 1 , wherein indicating the assigned status comprises presenting the object status to the authorized users on the graphical user interface. 
     
     
         7 . The method of  claim 1 , wherein organizing each task into one or more persistent containers comprises organizing each task based at least in part on a topic associated with the task, a project associated with the task, or a group of authorized users associated with the task. 
     
     
         8 . The method of  claim 1 , wherein the one or more persistent container comprises a folder including multiple tasks. 
     
     
         9 . The method of  claim 1 , further comprising organizing a plurality of computer objects into the one or more persistent containers, each computer object comprising at least one of a task, a message, and a document. 
     
     
         10 . The method of  claim 1 , wherein updating the status comprises sorting the plurality of tasks based at least in part on whether the task is assigned, pending, or completed. 
     
     
         11 . The method of  claim 1 , wherein updating the status comprises sorting the plurality of tasks based at least in part on at least one of due dates associated with the respective tasks, importance of the respective tasks, activity level of the respective tasks, and number of authorized users associated with the respective tasks. 
     
     
         12 . The method of  claim 1 , further comprising identifying a task recipient and a task creator for each task. 
     
     
         13 . A system for managing a plurality of tasks stored on one or more networks, the system comprising:
 an object management module programmed to:
 associate each task with one or more authorized users; 
 organize each task into one or more persistent containers; 
 update a status to each task that indicates the status of that task within the system; and 
 track a history of one or more tasks in each of the one or more persistent containers over time; and 
   an integrated interface module programmed to:
 provide a graphical user interface that lists the plurality of tasks, wherein each task comprises task information; and 
 display the assigned status on the graphical user interface to each of the authorized users associated with the task. 
   
     
     
         14 . The system of  claim 13 , wherein the one or more persistent container comprises a folder including multiple tasks. 
     
     
         15 . The system of  claim 13 , wherein the integrated interface module is programmed to notify at least one authorized user about at least one of the status of a task, documents associated with the task, comments associated with the task, other users associated with the task, and changes to the task information. 
     
     
         16 . The system of  claim 13 , wherein the object management module is programmed to track the status of each task over time. 
     
     
         17 . The system of  claim 13 , wherein the object management module is programmed to track actions of the one or more authorized users over time. 
     
     
         18 . The system of  claim 13 , wherein the object management module is programmed to organize each task into the one or more persistent containers based at least in part on a topic associated with the task, a project associated with the task, or a group of authorized users associated with the task. 
     
     
         19 . The system of  claim 13 , wherein the integrated interface module is programmed to present the status to the authorized users using the graphical user interface. 
     
     
         20 . The system of  claim 13 , wherein the object management module is programmed to receive at least one of a task, a message, and a document. 
     
     
         21 . The system of  claim 13 , wherein the object management module is programmed to sort the plurality of tasks based at least in part on whether the task is assigned, pending, or completed. 
     
     
         22 . The system of  claim 13 , wherein the object management module is programmed to sort the plurality of tasks based at least in part on at least one of due dates associated with the respective tasks, importance of the respective tasks, activity level of the respective tasks, and number of authorized users associated with the respective tasks. 
     
     
         23 . The system of  claim 13 , wherein the object management module is programmed to identify a task recipient and a task creator for each task. 
     
     
         24 . The system of  claim 13 , wherein the object management module is programmed to receive data from the authorized users regarding whether the tasks are assigned, pending, or completed. 
     
     
         25 . A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, perform a method comprising:
 providing a graphical user interface that lists a plurality of tasks, wherein each task comprises task information;   associating each task with one or more authorized users;   organizing each task into one or more persistent containers;   updating a status to each task that indicates the status of that task within the system;   displaying the assigned status on the graphical user interface to each of the authorized users associated with the task; and   tracking a history of one or more tasks in each of the one or more persistent containers over time.   
     
     
         26 . The non-transitory computer-readable medium of  claim 25 , wherein the one or more persistent container comprises a folder including multiple tasks.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.