Managing project schedule data using separate current and historical task schedule data and revision numbers
First Claim
1. A computer-implemented method for managing project schedule data, the computer-implemented method comprising:
- generating schedule data for a task in the project;
determining whether the schedule data is the first schedule data for the task in the project;
if the schedule data is the first schedule data for the task in the project, thenstoring the schedule data in a current task schedule data structure, andgenerating and storing in association with the schedule data, version data that indicates that the schedule data is a first version of schedule data for the task in the project;
if the schedule data is not the first schedule data for the task in the project, thendetermining whether the schedule data should be considered to be a new version of schedule data for the task in the project,if the schedule data should be considered to be a new version of schedule data for the task in the project, thenmoving existing schedule data from the current task schedule data structure to a historical task schedule data structure that is separate from the current task schedule data structure, andstoring the schedule data in the current task schedule data structure; and
wherein one or more of the steps are performed by one or more processors.
1 Assignment
0 Petitions
Accused Products
Abstract
A project management system manages project schedule data using separate current and historical task schedule data structures. In general, current schedule data is stored separately from historical schedule data, so that the current schedule data may be retrieved separately from the historical task schedule data. The project management system may also maintain unscheduled tasks as “to-do lists.” Tasks may be added to a member'"'"'s schedule without specifying any planned dates and the tasks are added to the database. The tasks have an associated revision number of 0 to indicate that the tasks were added, but not yet scheduled. The tasks are displayed in the member schedule editor and in Web page schedules. The tasks may then be displayed in the member schedule editor and in Web page schedules in a manner that allows a user to readily determine that the tasks are “to-do list” tasks.
-
Citations
24 Claims
-
1. A computer-implemented method for managing project schedule data, the computer-implemented method comprising:
-
generating schedule data for a task in the project; determining whether the schedule data is the first schedule data for the task in the project; if the schedule data is the first schedule data for the task in the project, then storing the schedule data in a current task schedule data structure, and generating and storing in association with the schedule data, version data that indicates that the schedule data is a first version of schedule data for the task in the project; if the schedule data is not the first schedule data for the task in the project, then determining whether the schedule data should be considered to be a new version of schedule data for the task in the project, if the schedule data should be considered to be a new version of schedule data for the task in the project, then moving existing schedule data from the current task schedule data structure to a historical task schedule data structure that is separate from the current task schedule data structure, and storing the schedule data in the current task schedule data structure; and wherein one or more of the steps are performed by one or more processors. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A non-transitory computer-readable medium for managing project schedule data, the computer-readable medium carrying instructions which, when processed by one or more processors, cause:
-
generating schedule data for a task in the project; determining whether the schedule data is the first schedule data for the task in the project; if the schedule data is the first schedule data for the task in the project, then storing the schedule data in a current task schedule data structure, and generating and storing in association with the schedule data, version data that indicates that the schedule data is a first version of schedule data for the task in the project; and if the schedule data is not the first schedule data for the task in the project, then determining whether the schedule data should be considered to be a new version of schedule data for the task in the project, if the schedule data should be considered to be a new version of schedule data for the task in the project, then moving existing schedule data from the current task schedule data structure to a historical task schedule data structure that is separate from the current task schedule data structure, and storing the schedule data in the current task schedule data structure. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
17. An apparatus for managing project schedule data, the apparatus comprising:
-
one or more processors; and a memory storing instructions which, when processed by the one or more processors, cause; generating schedule data for a task in the project; determining whether the schedule data is the first schedule data for the task in the project; if the schedule data is the first schedule data for the task in the project, then storing the schedule data in a current task schedule data structure, and generating and storing in association with the schedule data, version data that indicates that the schedule data is a first version of schedule data for the task in the project; and if the schedule data is not the first schedule data for the task in the project, then determining whether the schedule data should be considered to be a new version of schedule data for the task in the project, if the schedule data should be considered to be a new version of schedule data for the task in the project, then moving existing schedule data from the current task schedule data structure to a historical task schedule data structure that is separate from the current task schedule data structure, and storing the schedule data in the current task schedule data structure. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24)
-
Specification