# Patent

## Title
Method and apparatus for updating rules and transmitting change notifications

## Abstract

A method and apparatus for generating court dates. A Date Calculation Engine (DCE) is coupled to a court date server and a court rule database for generation of court dates. The court rule database includes formulas written in a Date Calculation Scripting Language (DCSL) for calculating the court dates. The court rules further include instructions for generating a Jurisdiction Selection Expert (JSE) and an Event Selection Expert (ESE) that enable a user to quickly select a jurisdiction and an event using hierarchal data structures. The DCE is combined with other software components to build a complete court date server system. The court rule database is maintained up-to-date with the latest changes to the rules. Deadlines affected by any rule changes are automatically identified and recalculated, and customers for whom the deadlines were calculated automatically notified to inform them of the changed deadlines.

## Background
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application is a continuation of U.S. application Ser. No. 11/321,442 filed on Dec. 28, 2005 (now U.S. Pat. No. 7,302,433), which in turn is a continuation-in-part of U.S. application Ser. No. 10/201,563 (now U.S. Pat. No. 7,171,416) and U.S. application Ser. No. 10/201,598 (Patent pending), both filed on Jul. 22, 2002, both claiming the benefit of U.S. Provisional Application No. 60/306,677 filed on Jul. 20, 2001, the contents of all of which are incorporated herein by reference.


BACKGROUND OF THE INVENTION
This invention relates generally to the field of docket scheduling for the legal profession and more specifically to calculating court dates such as court deadlines.
The timing between a sequence of events of most legal matters, such as a lawsuit, are defined by court rules originating from statues, by local court rules originating in a local jurisdiction, and by individual court rules created by individual judges. These court rules may vary by the type of legal matter, by mutual consent of the parties involved in the matter, and by decree of a judge overseeing a matter. Failing to meet a deadline for an event defined by a court rule my result in a procedural error that is fatal to a party's position in the legal matter. Therefore, members of the legal professions place great emphasis and importance in meeting deadlines defined by the court rules.
The complexity and multiple sources of court rules creates a management problem for a legal practitioner. If a legal practitioner intends to successfully meet each and every deadline date in a matter, the legal practitioner must be aware of each court rule in each court, and the legal practitioner must be able to accurately calculate a court date using a set of court rules. In addition, the court rules may change in time, necessitating a recalculation of a matter's dates. While an automated court calendar generation system may be used to encapsulate the court rules and relieve the legal practitioner from understanding the complexity of the court rules, some legal practitioners may not have the resources to create such an automated system. Also, even if a legal practitioner does have the necessary resources to create a court calendar generation system, the legal practitioner may not want to maintain such a complex system.
SUMMARY OF THE INVENTION
According to one embodiment, the present invention is directed to a method for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding. The method includes maintaining in a database rules for calculating event dates for a plurality of different legal events, receiving an initial trigger date for an initial trigger legal event, selecting at least one of the rules from the database based on the initial trigger legal event, retrieving from the database date calculation instructions for the selected rule, calculating an event date of an associated legal event based on the retrieved date calculation instructions and the initial trigger date, transmitting the calculated event date to a user client, monitoring the database for a change in the rules, automatically identifying at least one of the plurality of different legal events affected by the change in the rules, automatically recalculating an event date for the identified at least one of the plurality of different legal events based on the change in the rules, and transmitting the recalculated event date to the user client.
According to one embodiment of the invention, the change in the rules is a change to date calculation instructions for the identified at least one of the plurality of different legal events.
According to one embodiment of the invention, the method for generating and transmitting the calendar further includes maintaining a relationship table storing relationship information for a plurality of the rules, the relationship table indicating whether a particular rule is related to another rule, and updating relationship information in the relationship table based on the change in the rules.
According to one embodiment of the invention, a customer affected by the recalculated event date is identified and notified for the recalculated event date.
According to one embodiment of the invention, a fee is calculated for recalculating the event date, and a user account is charged based on the calculated fee.
According to one embodiment, the present invention is directed to a method for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, where method includes maintaining a database storing rules associated with a plurality of different legal events, receiving rule update information, updating rules in the rules database based on the rule update information, determining whether a particular rule update is an update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events, responsive to the determination, recalculating the existing deadline based on the particular rule update, identifying a customer affected by the recalculated deadline; and notifying the customer of the recalculated deadline.
According to one embodiment of the invention, the particular rule update is an update to date calculation instructions used to calculate at least one deadline.
According to one embodiment of the invention, the rule update information identifies a rule set affected by the update. The rule update information further identifies the update as an event maintenance update or a non-event maintenance update. An event maintenance update is an update potentially affecting at least one existing deadline calculated for at least one of the plurality of different legal events.
According to one embodiment of the invention, the rule update information identifies one or more changed or new formulas for the rule set. In updating the rules in the rules database based on the changed or new formulas, a determination is made as to whether a formula identified by the rule update information exists in the rules database. In response to a determination that the identified formula exists in the rules database, changes are made to the formula in the rules database. Otherwise, if the identified formula does not exist in the rules database, the identified formula is added to the rules database. During the database update, a determination is further made as to whether the change or addition of the identified formula is an event maintenance or non-event maintenance update. This determination may be made based on the identification of the associated rule set as an event maintenance update or a non-event update. If the change or addition of the identified formula is an event maintenance update, information on the changed or added formula is stored as event maintenance change information.
According to one embodiment of the invention, calculated deadlines and formulas used for calculating the deadlines are tracked in customer-specific transaction records. In recalculating any such deadlines based on changed formulas, the changed formula is identified from the event maintenance change information. A customer-specific transaction record that includes the changed formula is then identified, and a deadline in the customer-specific transaction record is recalculated based on the changed formula.
In handling new formulas, the new formula is identified from the event maintenance change information. A formula relationship table is then queried for determining a related formula referenced by the new formula, and a customer-specific transaction record including the related formula is identified. A new event date is calculated based on the new formula and added to the identified customer-specific transaction.
According to one embodiment of the invention, the rule update information includes a list of holidays and associated dates for the rule set. In updating the rules in the rules database based on a holiday update, a determination is made as to whether a holiday identified in the list of holidays exists in the rules database. If the identified holiday exists in the rules database, and a date for the holiday in the list of holidays differs from a date for the holiday in the rule update information, the date of the holiday in the rules database is changed. If the identified holiday does not exist in the rules database, the identified holiday is added. The holiday date change or addition information is then stored as event maintenance change information.
In updating existing deadlines based on holiday updates, an earliest holiday date and a latest holiday date are identified from the event maintenance change information. A customer-specific transaction record including a deadline between the identified earliest holiday date and the identified latest holiday date is also identified, and the deadline is verified based on holiday change or addition.
According to one embodiment of the invention, the rule update information includes a list of deleted formulas in the rule set. In updating the rules in the rules database based on deleted formulas, a determination is made as to whether a formula identified in the list of deleted formulas exists in the rules database. If the identified formula exists in the rules database, the formula is deleted, and information on the deleted formula is stored as event maintenance change information.
In updating existing deadlines based on deleted formulas, the deleted formula is identified from the event maintenance change information. A customer-specific transaction record including the identified formula is also identified. The identified formula and a deadline calculated by the identified formula are deleted from the customer-specific transaction.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram of an application service provider embodiment of a court date server in accordance with an exemplary embodiment of the present invention;
FIG. 2 is Web site diagram of a court date server in accordance with an exemplary embodiment of the present invention;
FIG. 3 is a calendar date options page as used by an exemplary embodiment of the present invention;
FIG. 4 is a Matter Management page as used by an exemplary embodiment of the present invention;
FIG. 5 is a Matter List page in accordance with an exemplary embodiment of the present invention;
FIG. 6 is a Matter Information page as used in an exemplary embodiment of the present invention;
FIG. 7 is a Matter Recovery page in accordance with an exemplary embodiment of the present invention;
FIG. 8 is an Event Management page in accordance with an exemplary embodiment of the present invention;
FIG. 9 is an Event List page in accordance with an exemplary embodiment of the present invention;
FIG. 10 is a page used to add an event in accordance with an exemplary embodiment of the present invention;
FIG. 11 is an event edit page in accordance with an exemplary embodiment of the present invention;
FIG. 12 is a screen capture of a Jurisdiction Selection Expert in accordance with an exemplary embodiment of the present invention;
FIG. 13 is a screen capture of an Event Selection Expert in accordance with an exemplary embodiment of the present invention;
FIG. 14 is an Event Generation Charges page in accordance with an exemplary embodiment of the present invention;
FIG. 15 is a group selection process in accordance with an exemplary embodiment of the present invention;
FIG. 16 is a Verify Events page in accordance with an exemplary embodiment of the present invention;
FIG. 17 is an Event Maintenance Log page in accordance with an exemplary embodiment of the present invention;
FIG. 18 is an Event Maintenance Detail page in accordance with an exemplary embodiment of the present invention;
FIG. 19 is a process flow diagram of a “Quick Dates” process in accordance with an exemplary embodiment of the present invention;
FIG. 20 is a diagram of a an embodiment of a computer suitable for use as a host for a court calendar generation server in accordance with an exemplary embodiment of the present invention;
FIG. 21 is a process flow diagram of an add event process in accordance with an exemplary embodiment of the present invention;
FIG. 22 is an event maintenance process in accordance with an exemplary embodiment of the present invention;
FIG. 23 is an event maintenance process as used by an event maintenance module in accordance with an exemplary embodiment of the present invention;
FIG. 24 is a block diagram of a change notification module in accordance with an exemplary embodiment of the present invention;
FIG. 25 is a change notification process in accordance with an exemplary embodiment of the present invention;
FIG. 26 is a reminder notification process in accordance with an exemplary embodiment of the present invention;
FIG. 27 is a process flow diagram of a jurisdiction and event expert generation process in accordance with an exemplary embodiment of the present invention;
FIG. 28 is a block diagram of a court date server configured for rules updating and notification according to one embodiment of the invention;
FIG. 29 is a layout diagram of the rules update file according to one embodiment of the invention;
FIG. 30 is a layout diagram of the EM changes DB containing information of EM changes that call for event maintenance and change notification to affected customers according to one embodiment of the invention;
FIG. 31 is a layout diagram of a notification information DB for notifying customers of changed deadlines according to one embodiment of the invention;
FIG. 32 is a flow diagram of an overall rules updating and notification process according to one embodiment of the invention;
FIG. 33 is a more detailed flow diagram of updating a rules database according to one embodiment of the invention;
FIG. 34 is a more detailed flow diagram of processing formula changes according to one embodiment of the invention;
FIG. 35 is a more detailed flow diagram of processing holiday changes according to one embodiment of the invention;
FIG. 36 is a more detailed flow diagram of for updating existing deadlines based on changes to a rules database according to one embodiment of the invention; and
FIG. 37 is a flow diagram of a process for providing change notification details to a customer according to one embodiment of the invention.



DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 is a diagram of an application service provider embodiment of a court date server in accordance with an exemplary embodiment of the present invention. A court date server 100 includes a Web site 101 having a plurality of Web pages for accessing features of the court date server via a communications link. The court date server includes a date calculation engine 102 for generation of a court calendar using court scheduling rules and a starting event date. The court date server includes a court rules database 104 for storage of court scheduling rules specific to each jurisdiction served by the court date server. The court rule database stores sets of court rules having date formulas used to schedule court deadlines and scheduling dates. All the data needed to schedule court related deadlines is contained in the court rule database.
A “Rule Set” includes the formulas used to calculate court dates for a specific court jurisdiction. A “Formula” includes a date calculation script that calculates a court deadline. A “Trigger” formula causes the scheduling of a set of court dates. The “Trigger” formula is what a user selects when scheduling dates using the court rule database. For example, when scheduling a Trial date the user selects the “Date of Trial” trigger formula and then enters its due date. A “Trigger” formula that bases its date calculation on other “Trigger” formulas is referred to as a “Branching Trigger”.
A “Branching Trigger” can be scheduled like a regular “Trigger” (by selecting it and providing a date) or is scheduled automatically when one of the “Trigger” dates used by its formula calculation are scheduled. A “Trigger” formula cannot base its date calculation on a “Related” formula. Also, a “Trigger” formula does not have to have a date calculation script. The user provides the due date for triggers that do not contain a calculation script (at the time the trigger is scheduled). A “Related” formula is used when one of the trigger dates on which its calculation is based is scheduled. “Related” formulas can also base their calculation on other “Related” formulas. “Related” formulas that base their calculation on other related formulas cannot reference each other within the relationship. This prevents a “circular” relationship from occurring. For example, formula A bases its calculation on formula B which bases its calculation on formula A. In this case a circular relationship is created which would place the calculation engine into an infinite loop since neither formula A or B can successfully calculate their dates.
A “Group” is an interrelated set of dates. All court dates within a group have some relationship to at least one other date in the group. Groups provide the ability to maintain the integrity of interrelated dates. When a formula is added or changed, the formula's script is examined for formula relationships and entries are made in the “Formula Relationship Table” so that the program can quickly retrieve the formulas that are used when a particular trigger date is scheduled. The data in this table is also used when displaying formulas to the user in a hierarchical folder format.
A user database 106 is included in the court date server for tracking the usage of the court date server by a plurality of users. In addition, the court date server stores generated court calendars in the user database for later access by a user. The court date server is hosted by a court date server host 108.
The court date server is accessed via a communications network, such as the Internet 110, by a user using a user client 112. In operation, the user accesses the court date server using Web pages or documents retrieved from the court date server's Web site. The user supplies matter data, trigger event data, and court identification 114 to the court date server via the communications network. The court date server's date calculation engine uses the matter data, trigger event data, and court identification to generate a court calendar 116 for transmission to the user via the communications network. The date calculation engine generates the court calendar by selecting a court's scheduling rules from the rules database using the court identification and the matter data. The date calculation engine then uses the trigger event data to calculate all the remaining related court dates based on the date of the initial trigger event.
FIG. 2 is a Web site diagram of a court date server in accordance with an exemplary embodiment of the present invention. The Web site 101 includes a “Home” page 200 having links to sub-pages of the Web site. Users log in with a valid user id and password before any Web site sub-pages can be accessed. General data is placed on the Home page such as news flashes, product update data and an ad banner. The Home page further includes a link to a “Registration” page 202. From the Registration page, users can select an “Individual” registration page 204 or a “Corporate” registration page 206 for creation of individual or corporate accounts. An individual account allows a user to setup an account for their sole use. All date generation charges are billed to this user's account. A corporate account allows a user to setup an account that can be used for any number of users at a firm. Date generation charges for all users at the firm are billed to the corporate account. The administrator of the account (the user that created the corporate account) controls who at the firm can access the Web site.
The registration process begins when the user selects either the individual or corporate account type from the Registration page. User registration is a multi-page process that is completed before the user submits registration data. No two users can have the same “E-mail Address”. An error message is returned if one user has the same e-mail address as another user.
The user data collected during the registration process includes the user's first and last name, a date of birth for verifying user identity by a password recovery mechanism, and an E-mail address which also serves as the user's login name. The user then selects a password and a password question and response which are used if the user has forgotten their password. The user is then asked for company data including the user's firm's name and address and a contact telephone number.
Usage and billing reports are normally sent to the user using the data provided by the user. If the user would like this data to go to a different location, the user may provide additional billing data if their billing data is different than the previously supplied data. In addition, a user may set up a corporate account with one of several billing types. Possible billing types are “Bill my credit card” and “Monthly statement”. If the user is creating an individual account then a user's credit card is automatically billed.
FIG. 3 is a calendar date options page as used by an exemplary embodiment of the present invention. A calendar date options page 300 includes settings that apply to the calendar dates added by the user. A “Notify me when dates are changed?” setting 302 tells the court date server whether or not the user wishes to be notified when a court date is changed because of a change to the scheduling rules. A “Send me e-mail reminders of upcoming dates?” setting 304 tells the court date server whether or not the user wants to receive e-mail reminder notices of upcoming calendar dates.
Referring again to FIG. 2, a “Welcome/Error” page 208 is generated and transmitted to the user. If an error occurs during the registration process (i.e. required data not provided, duplicate login name or password) then an error page is generated containing data about the error and how to resolve it. Otherwise, a welcoming message is displayed.
The Web site includes a Secure Login page 210 that is displayed after a user selects a “Login” link located on the Home page. The user enters their e-mail address and password in the fields provided and presses the “Login” button to log into the Web site. Selecting a “Cancel” button returns the user to the Home page. Selecting a “Forgot your password?” link displays a “Forgot your password” page 212 which is used to query the user using the previously described password question. A Password Recovery page 214 is displayed after the user enters their e-mail address for the account and their date of birth. This data is verified when a “Submit” button is pressed. If the data is incorrect then an appropriate error page is generated. A Password Recovery page 214 is displayed after the password verification data provided on the “Forgot your password?” page has been validated against account data for the user. This page is used to get the answer to the “password recovery question”. The “password recovery question” is specified by the user when setting up an account. Selecting a “Submit” button sends the answer back to our server for validation. If the answer is incorrect, an appropriate error message is displayed. If the answer is correct, an e-mail is sent to the user containing the user's password. After successfully logging in, the user is allowed to access the features of the court date server.
A court date server main page 218 includes links to the Web site's sub-pages. Calendar generator functions are accessed from this page using links to the following pages. A Refer a Colleague page 220 allows users to refer a colleague to the Web site by sending an e-mail 222 to selected colleagues. The user can enter up to 5 e-mail addresses of colleagues and attach a personal message to each e-mail. A referral manager process (not shown) is responsible for sending the referral e-mails. The referral manager periodically checks a referrals database for new entries and creates and sends an appropriate e-mail to each new prospect. In one embodiment of a court date server, if a referral subsequently registers with the Web site and uses its services, the user that made the referral receives a credit that is applied to date generation charges. Selecting a “Submit” button sends the referral data to the court date server for processing. Selecting a “Cancel” button returns the user to the main page.
An Account Information page 224 allows the user to view and edit their account data. Billing data can also be viewed from here. The Account Information page allows users to view and change their account data and password, view a history of transactions and, if it is a corporate account, view and edit a list of account users. For added security, the users credit card number and expiration date are not displayed on this page. To view or change the account's credit card data the user clicks a “Change” link for a “Payment Information” section.
A Corporate User List page 226 includes a list of users for a corporate account. The list is in order by the user's last name. Selecting a letter from a ComboBox displays all users whose last name begins with the selected letter. New users are added by selecting on an “Add” button. This displays a “Corporate User” entry form used to enter a new corporate user. Selecting an “Edit” link next to a users name allows the data for that user to be edited. Selecting a “Delete” link deletes the user from the list. A “De-activate” link is used to de-activate a user. When clicked, the user is deactivated and the link changes to “Activate”.
A Corporate User Account Information page 228 is displayed when the “Edit” or “Add” links are selected from the “Corporate Account User List” page and allows the user to enter data about a corporate account user. Corporate account users are allowed to change their data once they have been setup by an account administrator. Date calculation charges are billed to the primary corporate account set up by an administrator when a corporate account user generates court dates. Selecting a “Submit” link validates the data and stores it in a UserAccounts table.
A Change Password page 230 allows the user to change their password. The user enters their existing password for verification purposes. An “Enter your new password” and a “Re-enter your new password” fields are compared and an error message displayed if they are not the same. Selecting a “Submit” button sends the password data to the court date server for validation and processing. If the existing password data provided by the user is incorrect an error message is returned. If the existing password data is verified then the user's password is changed.
A Transaction Filter page 232 allows a user to enter search criteria used to locate specific transactions with the court date server. The user enters filter criteria in the fields provided and clicks a “Find” link. If transaction records are found, a “Transaction History” page 234 is displayed containing an entry for each transaction. The fields in the Transaction Filter page include: a transaction ID to allow finding a transaction using its unique ID; a date range for searching for transactions that occurred in a specified date range; an amount range for searching for transactions in a specified billing amount range; a corporate user field for an administrator of a corporate account to search for transactions by a specific corporate user; and a Show ‘n’ Transactions field allowing the user to set how many transactions to display per page on a transaction history list. In a Transaction Filter page in accordance with an exemplary embodiment of the present invention, entering a specific transaction record ID disables the other filter fields on the page.
In another Transaction Filter page in accordance with an exemplary embodiment of the present invention, any of the filter options allowing for a range, such as the amount field, allow “open ended” ranges to be entered. If one end of a range is not provided, it means to include all records from that side of the range. In another Transaction Filter page in accordance with an exemplary embodiment of the present invention, if no filter is provided then all transactions are returned for the user.
The Transaction History page includes transaction history data retrieved from a “Transaction Log” table stored in the user database based on the Transaction Filter options. The filter options are displayed in a descriptive paragraph in the “Filter Used” section of the Transaction History page. Selecting a “Change” link returns the user to the “Transaction Filter” page allowing the user to make changes in the transaction filter. Each line item displayed in a “Transaction” section of the Transaction History page has the date and time of the transaction, the amount billed, the number of dates generated, the user that generated the dates if this is a corporate account, and a transaction ID. The number of transactions displayed on the Transaction History page depends on the Show ‘n’ Transactions field setting. Page links are displayed in a Transaction History page heading and are in the format “<<Prev 1 2 3 . . . Next>>”. The “ . . . ” is used to indicate more pages than will fit in the space provided on the page. Selecting a “<<Prev” or “Next>>” link displays the previous or next page of transactions. The page links are not shown if the Transaction History page has only one page of transactions. Selecting selecting an “Account Info” button returns the user to the main Account Information page.
A Contact Technical Support page 236 allows a user to open an incident report with an administrator of the court date server by sending an error report e-mail message 238. A Synchronize PIM page 240 allows a user to download matter and event data to a personal organizer such as a Personal Digital Assistant (PDA) or other specialized computing device.
A Matter Management page 242 allows a user to enter filter criteria to locate a matter or matters they are interested in. Access to the data about a matter, as well as the events associated with a matter, is accessed from the resultant matter list.
FIG. 4 is a Matter Management page as used by an exemplary embodiment of the present invention. The user has the option of finding matters based on all or part of the matter name (400), using matter type field 402, a date opened field 404, or a date closed field 406. Inactive matters can also be optionally included in the search by selecting an inactive case field 408. A matter name search field 400 allows the user to enter all or part of the matter name they are looking for. Using radio button selections, 410, 412, and 414, beneath the matter name text field, users can search for an exact match, matter names that begin with the specified text, or matter names that contain the specified text.
Any of the filter options that allow for a range allow “open ended” ranges to be entered. If one end of a range is not provided, it means to include all records from that side of the range. If no filter is provided then all matters are returned by the query.
A How Many Matters field 416 allows the user to specify how many matters to display in a matter list. Selecting an “Add a New Matter” link 418 allows the user to add a new matter. Selecting a “Matter Recover” button 420 displays the “Matter Recovery” list which allows users to recover deleted matters and their associated dates.
Referring again to FIG. 2, after a user fills out the Matter Management page and submits it to the court date server, the court date server generates a Matter List page 242 by building a database query from the filter settings in the Matter Management page and querying the user database for matters satisfying the filter criteria.
FIG. 5 is a Matter List page in accordance with an exemplary embodiment of the present invention. A Matter List page 244 includes a display of the filter criteria 500 and a list 502 of matters that match the filter criteria entered on the “Matter Management” page. Each matter listed includes the name of the matter 504, the date the matter was opened 506, an “Edit” selection 508, a “Delete” selection 510, and an “Events” selection 512 button next to it. Inactive matters 514 are displayed in a different color than the active matters. Selecting either an “Add a New Matter” button 516 or an “Add a Matter” link 518 allows the user to add a new matter.
Selecting the Delete button next to a matter deletes the matter and all its associated records (transaction log records, events, etc.) from the court date server's user database When the “Delete” button is pressed a Matter Deletion verification page 246 (FIG. 2) is displayed. Selecting the Edit button allows the user to edit the matter. Pressing the Events button displays the events for the matter.
Selecting a “Back” button 520 returns the user to the “Matter Management” page 242 (FIG. 2). Selecting the “Home” button 522 returns the user to the main page 218 (FIG. 2).
FIG. 6 is a Matter Information page as used in an exemplary embodiment of the present invention. A Matter Information page 600 allows a user to add and edit matter data. A matter name field 602 is used to enter a matter name. Matter names are unique for each user. In other words, a user can not have two matters with the same name.
A matter type field 604 is used to enter a matter type. The user selects an existing matter type from a list or may enter a new one. A docket ID field 606 is used to enter a user defined docket ID for the matter.
A date opened field 608 is for display of the date the matter was opened. For a new matter, this field is set to the current date. A date closed field 610 is for display of a date on which a matter was closed.
A jurisdiction field 612 displays a default jurisdiction for a matter. This field is set by using a “List” link 614 and selecting from a to-be-described Jurisdiction Expert process. The Jurisdiction Expert includes a hierarchical list of valid jurisdictions for a matter.
An inactive field 616 allows a user to set the status of a matter to inactive. The matter will not appear on any lists or reports unless the user requests inactive matters.
A matter ID 618 is shown and an “Events” button 620 is available when editing an existing matter. Selecting the Events button displays an “Event List” page 250 (FIG. 2) for a matter.
Selecting a “Delete” button 622 deletes a matter and all of its associated records (transaction log records, events, etc.) When the “Delete” button is pressed the Matter Deletion verification page 248 (FIG. 2) is displayed.
Selecting a “Submit” button 624 sends the matter data to the court date server for processing and storage in the user database. If an error occurs after submitting the data to the database, an error page is displayed containing data about the error and possible solutions.
Referring again to FIG. 2, a Matter Recovery page 252 is available to the user to recover a matter that the user has inadvertently deleted. This page includes a list of deleted matters.
FIG. 7 is a Matter Recovery page in accordance with an exemplary embodiment of the present invention. A Matter Recovery page 252 includes a list 700 of deleted matters. To recover a deleted matter, the user clicks a “Recover” link 702 next to a matter in the list. After recovering a deleted matter, the matter and all it's associated dates are available for the user to access.
Referring again to FIG. 2, an “Event Management” page 254 includes filter fields that allow a user to search the user database for events. A user may also add a new event from this page.
FIG. 8 is an Event Management page in accordance with an exemplary embodiment of the present invention. An Event Management page 254 allows multiple filter options to be entered by a user in order to find an event. A matter name field 800 allows a user to search for a specific matter name or part of a matter name. A search options pull down menu 802 allows a user to set search options including “Exact” for exactly matching a matter name, “Beginning with” for matching to any matter beginning with an entered matter name, and “Includes” for matching to any matter whose name includes an entered matter name. A matter type field 804 allows a user to find events based on the matter type assigned to each matter for which events have been scheduled.
A due date field 806 allows a user to search for events within a specified due date range. A time field 808 allows a user to search for events based on an event time. An added on field 810 allows a user to search for events based on the date they were added to the system. A last changed field 812 allows a user to search for events based on when they were last changed. Any of the filter options that allow for a range also allow “open ended” ranges to be entered. If one end of a range is not provided, it means to include all records from that side of the range.
A unique ID field 814 allows a user to search for a specific event using an event's specific ID. A formula field 816 allows a user to search for events that use a specific formula for their calculation. This field includes a “Rule set” field and a “Formula ID” field separated by a hyphen.
A formula description field 818 allows a user to search for events based on the contents of a formula description. A pull-down menu 820 allows a user to search for all or part of a formula description. Search options include “Exact”, “Beginning with” and “Includes” as previously described.
A note field 822 allows a user to search for events based on the contents of the mote field. A pull-down menu 824 allows a user to search for all or part of a note. Search options include “Exact”, “Beginning with” and “Includes” as previously described.
An Include Completed Events button 826 allows a user to include completed events in the event search. An Include Deleted Events button 828 allows a user to include deleted events in the event search. A How Many Events field 830 allows a user to set the number of event records to display per page on a resultant event list.
With the exception of the “Include completed events” and “Include deleted events” settings, the user provides data for at least one of the other fields on this page. Selecting a “Find” button 832 submits the search request to the court date server for processing.
Referring again to FIG. 2, the court date server receives the filter settings from the Events Management page 254 and generates the Event List page 250 included a list of events satisfying the filtering criteria.
FIG. 9 is an Event List page in accordance with an exemplary embodiment of the present invention. An Event List page 250 includes an event list 900 showing the events that meet the filter criteria provided from the Events Management page. The event list includes the following data for each listed event. A due field 902 has the event due date and the word “Completed” if the event has been marked completed. If the event is marked completed, a “Complete” link 904 is changed to “Un-complete”. A “Time” field 906 has the start and end time of the event. If the event only has a start time then only that time is displayed. If the event has no time then nothing is displayed in this field. A “Matter/Authority/Description” field 908 includes the matter name, a formula authority (the source of the deadline), first 2 lines of a formula's description and first 2 lines of a user provided note. If the formula description or note data needs to be truncated to fit within the 2 line limit then a “ . . . ” is placed at the end of the text to indicate that more text is present.
The listing for each event includes links allowing the user to edit/view, Delete and Complete/Un-complete an event. Selecting an “Edit/View” link 910 displays an Event Detail page 256 (FIG. 2) having data about an event. Selecting a “Delete” link 912 marks the event as deleted and removes it from the list. Selecting a “Complete” link 904 marks the event as completed and places the word “Complete” under the due date in the due field and changes the “Complete” link text to “Un-complete”. Selecting “Un-complete” removes the word “Complete” from the due field and changes the link text back to “Complete”.
Selecting a “Home” button 916 returns the user to the main page 218 (FIG. 2). Selecting a “Filter” button 918 returns the user to the Event Management page so they can change the filter options. A “Print” button 920 allows the user to print the list of events and an “Export” button 922 allows the user to export the events to a delimited ASCII file. (NOTE: we also produce an iCal file that contains the calendar dates in a format that can be imported directly into Outlook).
Referring again to FIG. 2, a Print Events 258 page is displayed when the “Export” button is selected from the Event List page 250. The Print Events page allows the user to specify a file name and location as well as other delimiter options. Selecting an “Export” button exports a current event list to the specified file. Selecting a “Back” button returns user to the Event List page. An “Example” label included in the Print Events page changes depending on the delimiter options selected.
FIG. 10 is an add event page used to add an event in accordance with an exemplary embodiment of the present invention. An add event page 1000 is displayed when an “Add a New Event” link is selected from one of the previously described pages. The add event page steps the user through a process of scheduling court dates using the scheduling rules database. As each step is completed, subsequent steps are enabled. The user performs each step in sequence.
A matter for which event dates will be generated is entered using a “List” link 1002 to display the previously described Matter Management page allowing the user to locate a specific matter. The user may bypass the Matter Management page by entering search criteria in a matter field 1004 then selecting the “List” link. For example, if the user wants to find all matters beginning with the word “Acme” they would enter “Acme*” into the field and select the “List” link. New matters can be added from either the Matter Management or Matter List pages as previously described.
Once a matter is selected, the user selects a jurisdiction. The jurisdiction is set by using a to-be-described Jurisdiction Selection Expert accessed through link 1006. Once selected, the jurisdiction is displayed in the jurisdiction field 1008.
Once the jurisdiction has been selected, the user can select an appropriate court event from a to-be-described Event Selection Expert accessed using link 1010. Once selected, the event is displayed in an event field 1012.
Once an event has been selected, the user provides a date in a date field 1014. An entry in a time field 1016 is optional. Both these fields are set by selecting data from appropriate selection dialogs reached by links 1018 and 1020.
A reminder field 1022 allows a user to schedule a reminder e-mail to be sent to the user for an event. Setting an “Apply to all scheduled dates?” option 1024 applies the reminder offset entered in the reminder field to all subsequently scheduled dates (for example 1 day before each event).
A note field 1026 allows a user to enter a note that will be attached to an event trigger date. Setting an “Apply to all scheduled dates?” option 1028 applies a note to all subsequently scheduled event dates. The user selects a “Schedule” button 1030 to schedule the dates or selects a “Cancel” button 1032 to return to a previous page.
FIG. 21 is a process flow diagram of an add event process in accordance with an exemplary embodiment of the present invention. An add event process 2100 adds an event date for a user. A caller process 2101 gets (2102) event data from the user and transmits the event data to the court date server. The court date server validates (2104) the event data is valid. If the event data cannot be validated, the court date server generates (2106) an error document and transmits the error document back to the caller process.
If the event data is valid, the court date server gets (2108) a group to which the event belongs in order to determine the new event's trigger date. The court date server calls (2110) the date calculation engine to generate new dates for the event. The court date server uses the new dates to generate a date calculation result document 2112, such as a Web page, including data on the number of dates generated and the calculated amount to be debited from the user's account or charged to a user's credit card account. The calculation result document is transmitted to the user so that the user can accept or reject a debit or charge of the calculated amount. If the user does not accept (2114) the debit or charge, the add event process terminates and no debits or charges are made the user's accounts and no dates are stored our updated in the user database.
If the user does accept the debit or charge, the court date server charges (2116) the user's charge card or debits the user's account. If the debit or charge is not successful, the court date server generates (2118) an error page for transmission back to the user. If the debit or charge is successful, the court date server verifies (2120) the event dates and stores (2122) the dates in the user database. If the store process is not successful, the court date server credits (2124) the user's account or credit card account and generates (2126) an error document for transmission back to the user. If the court date server successfully stores the event date data into the user database, the court date server inserts (2128) a transaction record into a transaction database and generates a date list document (2130) using the event data and the new dates for transmission back to the user. Control then returns to the caller process.
FIG. 11 is an event edit page in accordance with an exemplary embodiment of the present invention. An event edit page 1100 allows the user to view and edit event data. The page is initially displayed in “View” mode. That is, none of the event data can be altered. To change an event, the user selects a “Change” button 1102. Selecting the “Change” button enables the data entry fields and changes the “Change” button text to “Submit”.
Only “Due date” 1104, “Time” 1106, “Reminder” 1108, “Note” 1110, “Complete” 1112, and “Don't change” 1114 fields on the event can be changed. The “Due date” and “Time” fields are set by using the associated selection dialogs accessed by links 1116 and 1118, “Calendar” and “Time” links respectively. The “Reminder” field is set using a reminder spinner button 1120 next to the Reminder field. The user can type anything they want into a “Note” field 1122. In operation, a user modifies the due date for the event and selects the Submit button to update the data stored by the court date server in the user database.
FIG. 12 is a screen capture of a Jurisdiction Selection Expert in accordance with an exemplary embodiment of the present invention. A Jurisdiction Selection Expert (JSE) 1200 allows users to select rule sets used to schedule dates for any jurisdiction from a hierarchal list of jurisdictions. The JSE includes a hierarchical list 1202 of rule sets used by a court date server. The user selects category topics, such as category 1204, to expand the sub-categories beneath, such as subcategory 1206. Selecting on a sub-category either displays more categories or a selectable jurisdiction item 1207.
In one court rule database in accordance with an exemplary embodiment of the present invention, court rules are encoded as formulas including data used to generate a JSE hierarchical folder tree. For example, where “f” means a closed folder, and “fo” means an open folder:













f
Los Angeles Superior Court


fo
Orange County Superior Court











f
$DC
Last court day to complete non-expert discovery . . .



fo
$MO
Date set for motion to be heard.









 3 cn Last court day to request continuance hearing . . .



 5 db Last court day to file and serve replay papers . . .



10 db Last court day to file and serve opposition to motion . . .











fo
$TR
Date of trial.









 2 cb Last court day before trial for either party to serve . . .



70 df Last court day to demand the exchange of expert . . .










$TS
10df (sec/rel)








f
San Diego County Superior Court









The relationship data for this tree view is retrieved from a to-be-described formula relationship table.

In one court rule database in accordance with an exemplary embodiment of the present invention, the format for JSE data providing hierarchical text data for a court is as follows:















<tree hierarchy text>||<tree hierarch text>...||[!USAGE! |



!NOTE!]<rule set1>;<rule set 2>



[!MORE!]...










The “<tree hierarchy text>” entries tell the court date server where in the tree hierarchy to place an entry for the rule set. Each tree hierarchy text entry is separated by “∥”. The rule set usage data (that is the actual rule set selection data) is located after a “[!USAGE!]” tag. If this is a note entry then the note text follows a “[!NOTE!]” tag. Each rule set in the usage section is separated by a semi-colon (;). A “[!MORE!]” tag is used when an entry needs to be made in the JSE selection tree in more than one location.

The following example shows JSE data for the CA:LA-FT rule set:
List by State∥California∥State∥Trial Courts∥Southern California Los Angeles County∥Civil Litigation∥Unlimited Jurisdiction Case∥Case assigned to Independent Calendar Judge∥[!USAGE!]CA:LA-FT;CA:DISC
The next example shows how to add a note to a JSE branch. The note entries appear immediately beneath the specified branch:
List by State∥California∥State∥Trial Courts∥[!NOTE!]Local civil litigation rules include relevant provisions of CCP, CRC and California Code. Limited Jurisdiction cases have value of $25,000 or less, see CCP Sec. 85.
The next example shows the JSE data for the CA:APPRULE rule set (shows how to use the “[!MORE!]” tag):
List by State∥California∥State∥Appellate∥Sixth Appellate District—Sixth Appellate has no local rule deadlines. CA:APPRULE will be selected. ∥[!USAGE!]CA:APPRULE[!MORE!] List by State∥California∥State∥Appellate∥Supreme Court∥[!USAGE!]CA:APPRULE
In the above example, the “CA:APPRULE” rule set is located under the “Sixth Appellate District” and “Supreme Court” branches of the JSE selection tree.
In one court date server in accordance with an exemplary embodiment of the present invention, the data displayed by the JSE is contained in a text file. The text file is created and maintained by an administrator of a court date server. If jurisdictions are added, changed, or removed, a new file is created and copied to the court date server Web site. In another court date server in accordance with an exemplary embodiment of the present invention, the court rule database includes jurisdiction hierarchy data linked to a rule set record. The data used to build the JSE is retrieved from each rule set.
In the illustrated example, a “Limited Jurisdiction Case” child 1206 has been expanded to show the actual Jurisdiction (rule set) code 1207 used to schedule dates for that venue. In another court date server in accordance with an exemplary embodiment of the present invention, the JSE does not expose this final child node. When the user selects a jurisdiction, such as the “Limited Jurisdiction Case” child node, the JSE returns the complete hierarchical path. In the example shown, “List by State→California→State→Trial Courts→Southern California→Los Angeles County→Civil Litigation→Limited Jurisdiction Case” is returned as well as an actual jurisdiction code, for example “CA:LAMU-FT”, that is passed to a date calculation engine for event date generation. If more than one jurisdiction code is present for a selected jurisdiction then a comma separated list of jurisdiction codes is returned (for example “CA:LA-FT,CA:DISC”).
FIG. 13 is a screen capture of an Event Selection Expert in accordance with an exemplary embodiment of the present invention. An Event Selection Expert (ESE) 1300 is used by a user to select an event type for an event. In the illustrated example, a “Trial Date” node 1302 has been selected exposing actual event code “$TR” 1304 that is passed into a to-be-described date calculation engine for date generation. In another court date server in accordance with an exemplary embodiment of the present invention, the actual code is not shown. In the illustrated example shown, when the user selects the Trial Date node, the ESE returns the node description “Trial Date” and the actual event code of “$TR” 1304. The data used by the ESE is compiled from the data tables included in the court rule database.
A trigger formula is court rule formula that is used as a formula for a calculating event dates for a trigger event. A trigger event is an event that is linked to other events. When the trigger event date is calculated by the court date server using the trigger events trigger formula, then other dates for other events linked to the trigger event are calculated as well. Table A includes database entries for a trigger formula including data used to generate an ESE by the court date server:














Field
Explanation









Key Code
The key code for the trigger date.



Category
Category code attached to this




formula.



Priority
Priority code attached to the




formula.



Authority
The formulas authority text.



Formula
Contains the formula script.



Description
The event description.



Expert Data
Event Selection Expert data. See




below for a full description.










Each trigger formula includes ESE data used to place the trigger in the ESE selection tree. The format for the ESE data is:

<tree hierarchy text>∥<tree hierarchy text> . . . ∥[!KEYCODE!|!NOTE!]<key code>[!MORE!] . . .

The “<tree hierarch text>” entries include a location of the entry in the ESE selection tree.
Key code data (that is the key code selection data) is located after the “[!KEYCODE!]” tag. The “[!MORE!]” tag is used if ESE data for a trigger formula needs to be in more that one location in the ESE selection tree. Here is an example of an ESE data string for a “Date of Trial” trigger formula:

Trial∥Trial∥Date∥[!KEYCODE!]$TR

A note may appear beneath a branch in the selection list as shown below:
Trial∥Trial Date∥[!NOTE!]This is a note that appears just beneath the “Trial Date” branch.[!MORE!] Trial∥Trial Date∥[!KEYCODE!]$TR
In the above example, a note is added to the “Trial” branch.
FIG. 27 is a process flow diagram of a jurisdiction and event expert generation process in accordance with an exemplary embodiment of the present invention. A jurisdiction and event expert generation process 2700 uses a court rule database 104 including date calculation formulas 2706 having JSE data associated with the formulas as previously described to generate a JSE document 1200. The jurisdiction and event expert generation process transmits the JSE document to the user and receives 2710 a jurisdiction selection from the user selected using the JSE. The jurisdiction and event expert generation process generates an ESE 1300 using the selected jurisdiction and ESE data 2714 associated with the formulas in the court rule database. The ESE document is transmitted to the user and the jurisdiction and event expert generation process receives 2708 an event selection from the user selected using the ESE.
Referring again to FIG. 2, the court date server Web site includes an “Event Generation Charges” page 260. The Event Generation Charges page is used to confirm a user's request to have event dates calculated by the court date server.
FIG. 14 is an event generation charges page in accordance with an exemplary embodiment of the present invention. When new dates are added, the user is prompted to accept event date generation charges using an Event Generation Charges page 260. The Event Generation Charges page displays a number of events added 1400 to the user database along with an amount 1402 that is charged to the user's credit card. The amount billed includes the amount for generating the event dates and may include an event date storage charge. Selecting an “Accept” button 1404 transmits the user's acceptance of the charges to the user's account by the court date server and finalizes scheduling of the event dates. Selecting a “Cancel” button 1406 cancels the date generation process.
Users are charged based on the number of additions and/or changes made to an event group for the billing type assigned to the rule set used to generate event dates. A charges matrix table maintained by an administrator of a court date server determines the amount to charge for date calculations based on the number of addition and/or changes to a group. A rule set type table is used to retrieve the billing type data of a rule set. Once the charge has been calculated, any user discounts and credits are applied. New dates and changes made by an event maintenance process initiated by the administrator of a court date server are not charged to the user.
FIG. 22 is an event maintenance process in accordance with an exemplary embodiment of the present invention. An event maintenance process 2200 is initiated by an administrator to maintain and update the court rule database. As the court rule database is updated, an event date previously calculated for a matter may need to be updated if the court rules for calculating the event date have been changed. To initiate the event maintenance process, the administrator makes (2202) formula changes that are stored in a formula changes table (2206) and in the court rules stored in the court rules database. An event maintenance module 2208 is responsible for processing event groups affected by changes to the court rule formulas. The event maintenance module periodically polls the formula changes table looking for finalized changes or formula changes that have been approved by the administrator. If changes are found, all event groups affected by the changes are examined and event dates (2210) belonging to the affected event groups are altered if needed. The changes in the events are stored in an event maintenance log table (2212) with specific details about the changed events stored in an event maintenance change detail table (2214). A change notification module (2216) periodically polls the event maintenance log table looking for new log entries and uses that data along with the change detail data in the event maintenance change detail log to send notification e-mails 2218 to users regarding the changes made to the users events.
FIG. 23 is an event maintenance process as used by an event maintenance module in accordance with an exemplary embodiment of the present invention. An event maintenance process 2300 is the method used by an event maintenance Module to apply formula changes to events. The event maintenance process begins by getting (2302) event groups 2304 for each user that will be affected by changes made to formulas. The data for each group includes a user ID and a group ID of each group affected. The record set is ordered by user ID and group ID so that the groups for each user can be processed as a unit.
For each user (2306) the event maintenance process examines the events in the groups for additions, changes and deletions. Before processing the groups for a particular user ID, an entry is made (2308) in an event maintenance log table 2212 for the user. The data in this entry is used later by a change notification module to notify the user of date changes. After the log entry is made, the events in each group (2312) are examined and altered according to the formula changes. The event maintenance process gets (2314) the events 2316 for a group from the user database and alters (2318) the event dates based on the formula changes and updates (2320) the event dates in the user database. Each change made to an event in the group is recorded in an event maintenance detail table 2214.
After all groups (2324) for a user have been processed, the event maintenance log entry made earlier is “finalized” (2326) (the AllGroupsProcessed field is set) making it available to the change notification module (see the Change Notification Module topic below for details). After finalizing the previous user's changes, the groups for the next user (2328) are processed.
FIG. 24 is a block diagram of a change notification module in accordance with an exemplary embodiment of the present invention. Periodically, a change notification module 2216 checks an event maintenance log table 2212 for changes made to user events. For each user with a modified event, the change notification module uses the event maintenance change detail table 2214 to generate and send an e-mail 2402 to each user notifying them of the changes made to the user's events. The notification e-mail contains a “response” link 2403 that when selected sends a confirmation message 2404 to the court date server that indicates the user has received the notification e-mail.
A change notification response handler 2405 processes the confirmation message and updates the log record associated with the change notification e-mail sent to the user. The change notification response handler builds a response page 2406 that is returned to the user verifying that the confirmation of receipt was successful. If an error occurs during the update process, an error page is generated and sent to the user instead. An administrator periodically checks the event maintenance log table for log records whose notification e-mails have never been responded to and sends the corresponding users a letter that requests a written verification and/or the users' new e-mail address.
In one embodiment of a change notification module in accordance with an exemplary embodiment of the present invention, only a certain number of notification e-mails are sent for each log record. An administrator of a court date server periodically checks for all log records whose confirmation e-mails have never been responded to and send these users a notice via regular mail requesting written confirmation or the users new e-mail address. Also, each time a user logs into the court date Web site, the user receives a display with data about any e-mail notices that have not been responded to. The user is able to confirm receipt of the change notification at this time.
FIG. 25 is a change notification process in accordance with an exemplary embodiment of the present invention. A change notification process 2500 polls (2502) an event maintenance log table 2212 to see if any event changes need to be processed. An event maintenance log entry 2503 includes “Confirmed”, “NeverConfirmed”, “AllGroupsProcessed”, “NotifiedOn”, and “TimesNotified” fields holding the status of notification of a user. The criteria used to determine if a log record needs to be processed is whether or not the “Confirmed” and “NeverConfirmed” fields are False, the “AllGroupsProcessed” field is True, and the period of time that has elapsed between the date the last notification was sent, as indicated by the “NotifiedOn”, field and the current system date is greater than or equal to a specified notification period or a notification has never been sent for this log record.
If the change notification process determines (2504) that there are event date changes that a user needs to be notified about, then for each log record found (2506), the change notification process generates (2508) a change notification e-mail 2414 (of FIG. 24) for the user using the details of the changes associated with a log record in an event maintenance detail table 2214. The change notification e-mail includes the number of times the user has been notified and the last notification date. If this is the last notification, the change notification e-mail contains an appropriate message warning the user that no further notifications will be sent for this log record. The change notification process updates (2510) log records in the event maintenance log table 2212 upon successfully sending the change notification e-mail. The NotifiedOn field is set to the current system date and the TimesNotified count is incremented. Processing continues (2512) until all log records have been processed. Before completing the process, the change notification process polls the event maintenance log table to ensure that any log records added to the event maintenance log table during the notification process are processed. If the change notification process determines (2516) that no new changes have been made, the change notification process ends 2518. If otherwise, the change notification process processes each (2506) new change.
FIG. 26 is a reminder notification process in accordance with an exemplary embodiment of the present invention. A reminder notification process 2600 gathers (2602) all reminders for events on a specified date. The events returned are in order by user ID and reminder date. While there are reminders to process (2604), for each user (2606) the reminder notification process adds (2608) a reminder to a reminder notification e-mail message 2614. The reminder notification process adds all reminders for a single user (2610) to the reminder notification e-mail message and sends (2612) the reminder notification e-mail to the user. The reminder notification e-mail includes data about each event date that the user asked to be reminded of. If the reminder notification process determines (2616) that the reminder notification e-mail message is generated and e-mailed successfully, the reminder notification processes continues to process reminders while (2622) there are additional reminders for other users. If an error occurs, then an appropriate message is written (2618) to a reminder notification activity log. Processing continues in this fashion until all reminder e-mails have been sent.
Referring again to FIG. 2, a user is allowed to create aggregates of event dates into a group. A group is an interrelated set of event dates. All event dates within a group have some relationship to at least one other event date in the group. Groups allow maintenance of the integrity of interrelated event dates. The court date server Web site includes a Group Select page 262 that allows a user to select a group for inclusion of an event.
FIG. 15 is a group selection process in accordance with an exemplary embodiment of the present invention. A group selection process 1500 receives (1502) a matter ID, a rule set ID, and a key code. The group selection process gets (1504) groups for the matter that use the specified rule sets from the user database. The group selection process determines (1506) if any groups were identified. If not, the group selection process creates (1508) a new group for the matter and groups the event dates specified by the key codes. If groups were identified for the matter, the group selection process finds (1510) groups to which the specified key codes should be added. The group selection process determines (1512) if any groups were found. If not, the group selection process creates a new group as previously described. If only a single groups was found (1514), the group selection process adds (1516) the new event date specified by the key code to the identified group. If more than one group is found, the group selection process builds (1518) a group selection page (1520) for use by the user to select a group to which the event dates specified by the key codes will be assigned. If group selection process determines (1522) the user selected a group, the group selection process adds (1516) the event dates to the selected group. If group selection process determines (1524) the user requested a new group to be created, group selection process creates (1508) a new group for the event dates. If the user has not either selected a group or requested a new group, group selection process exits (1526) without adding the new event dates to a group.
Referring again to FIG. 2, the court date server Web site includes a Verify Events page 262. The Verify Events page displays newly added events for a group as well as changes to related dates after the user changes a “trigger” date.
FIG. 16 is a Verify Events page in accordance with an exemplary embodiment of the present invention. A Verify Events page 262 is similar to the previously described Event List page with the following exceptions. Additions and changes are indicated in an “A/C” field 1600. The user may avoid a change by selecting a “Skip” link 1602. The user may also remove an addition by selecting a “Delete” link 1604. The user may also edit a note associated with the event by selecting a “Note” link 1606.
Selecting an “Accept” button 1608 accepts the additions and changes and returns the user to the page from which the addition or change was initiated. Selecting a “Cancel” button 1610 cancels the changes and selecting a “Print” button 1612 prints the displayed list.
Referring again to FIG. 2, the court date server Web site includes an “Event Maintenance Log” page 266. An event maintenance process makes changes to users event dates when the event dates' controlling formulas are changed. Each item in the list represents one event maintenance process. In other words, an event maintenance process was run because of changes to the rules and one or more of a user's dates where changed.
FIG. 17 is an Event Maintenance Log page in accordance with an exemplary embodiment of the present invention. An Event Maintenance Log page 266 includes a changed event date list 1700 of event dates that were changed by the event maintenance process. The event date list includes the following fields. A Notified On field 1702 includes a date and time of a last change notification sent to the user. A Notifications field 1704 includes the number of times the user has been notified of date changes before responding to a “Change Notification” e-mail. A Log ID field 1706 include a unique record ID of an event maintenance log entry. A Changes field 1708 includes a count of the number of events that were changed by the event maintenance process. A Confirmed? field 1710 includes a “Yes” once the user has responded to a “Change Notification” e-mail and a No otherwise. Each event maintenance log entry has a “Details” button 1712 next to it allowing the user to view changes made to events associated with an event maintenance log entry.
FIG. 18 is an Event Maintenance Detail page in accordance with an exemplary embodiment of the present invention. An Event Maintenance Detail page 268 displays detailed data for an event maintenance log entry. An ID 1800 of the event maintenance log record is displayed in a page description text at the top of the Event Maintenance Detail page. Each event maintenance log entry includes change data 1802 for one event. An event maintenance log entry change field 1804 includes a full description of the change.
FIG. 19 is a process flow diagram of a Quick Dates process in accordance with an exemplary embodiment of the present invention. A Quick Dates process 1900 option allows a user to generate dates that the user does not wish the court date server to store and track. The user enters enough data to generate court dates and receives a date list that the user can export to another application or print. The user also receives an e-mail including the dates. A Quick Date Entry page 1902 (also of FIG. 2) is used to gather data about the initial court date from the user. A user enters a valid jurisdiction by requesting 1904 the previously described Jurisdiction Expert 1906 to select from a list of valid jurisdictions generated (1908) by the court date server. The user requests (1910) an event to be scheduled using the previously described Event Selection Expert 1912 to display a list of valid events for the selected jurisdiction. The court date server generates the list of valid events by checking (1914) the selected jurisdiction and generating (1916) an event selection list. If the jurisdiction is invalid, the court date server generates (1918) an Event Selection Expert error page 1920. After providing jurisdiction and event data, the user enters a date and time of the event using a date and time selection menu. Selecting a “Submit” button transmits the event data to the court date server. If an error occurs, then the web service generates a descriptive error page and returns it to the user. The court date server generates (1920) event dates and calculates (1922) the appropriate charges for the generated dates.
The court date server asks (1924) the user if the user will accept the charges using a previously described event generation charges page. If the user accepts the charges, the court date server generates (1926) a list 1927 of event dates for transmission to the user. The court date server also generates (1928) and transmits to the user an e-mail (1930) including the generated event dates. At the end of the process, the court date server records (1931) the transaction in a transaction table 1934.
Referring again to FIG. 1, a court date server maintains a user database 106 of user data in order to track event dates for users and a schedule rules database 104 for storing scheduling rules of different courts. The databases include grouped tables allowing each database to reside on different servers thus reducing the workload of each server. For example, an Event Maintenance process can be running continually on the server that includes an “Event Maintenance” database without affecting the performance of a server dedicated to generating and storing court dates.
An accounts database includes tables used to store user account data. A master settings file for the entire court date server web site is also located in this database.
Table 1 is a Site Settings Table including settings that apply to the web site and can only be changed by an administrator of the court date server Web site.










TABLE 1







Field
Description









MaxCngNotifs
Maximum number of date




change notifications that




will be sent to a user.



MaxEvListItems
Maximum number of




events that can appear on




the Event List. NULL = unlimited.



MaxMatters
Maximum number of




matters per user. NULL = unlimited.



MaxEvents
Maximum number of




events per user. NULL = unlimited.



DisableNotify
Disable the Event Change




Notification process?



NotifyTime
Time at which the Event




Change Notification




process checks for event




changes.



NotifyPeriod
Number of workdays that




must elapse before




another Event Change




Notification e-mail is sent




to the user.



ReminderTime
Time at which the




Reminder Notification




process checks for




reminders.



ActivityLogLevel
Determines what data is




written to an Activity




Log table.










Table entry MaxCngNotifsDetermines is a maximum number of change notification e-mails that will be sent to a user for each Event Maintenance Log record. When this value is reached, the sales department is notified and a letter is sent to the user requesting a written confirmation of the users new e-mail address.
Table entry MaxEvListItems is a maximum number of events that can appear on an Event List. Unlimited if set to NULL.
Table entry MaxMatters is a maximum number of matters allowed per user. Unlimited if set to NULL.
Table entry MaxEvents is a maximum number of events allowed per user. Unlimited if set to NULL.
Table entry DisableNotify disables an Event Change Notification process.
Table entry NotifyTime includes a time at which an Event Change Notification process begins sending change notification to users.
Table entry NotifyPeriod includes a number of days that elapse before subsequent Event Change Notification e-mails are sent for any change notifications that the user has not responded to.
Table entry ReminderTime includes the time at which a Reminder Notification process begins sending reminder e-mails.
Table entry “ActivityLogLevel” determines an amount of detail contained in all activity log tables. 0 (the default) writes just basic system data and errors to a log. Increasing this value increases the amount of detail contained in each log.
Table 2 is a Charges Matrix Table as used in an exemplary embodiment of the present invention to calculate charges for date calculations. The Charges Matrix Table includes amounts to charge for each rule set billing type for a number of dates generated and/or changed. When new dates are added, or dates in an existing group of dates are changed because of the addition of a new date, the court date server uses the Charges Matrix Table to determine how much to charge the user based on the number of additions and/or changes and the billing type of rule sets used. For example, if a new Key Date is added that generates 10 new events for a rule set of billing type 1, the user is charged $10. If a Key Date is added to an existing group of dates causing two (2) new dates to be added to the group and two (2) existing dates to be recalculated, the user is charged $5 if the rule set used has a billing type of 1, $2.50 for billing type 2 and $2.50 for billing type 3.










TABLE 2







Field
Description









BillingType
Rule Set billing type.



NumAddsChgs
Upper limit for the




number of




changes/additions this




record applies to. See




below for an example




of the data contained




in this table.



Amount
Amount to charge.










Table 3 is a User Accounts Table in accordance with an exemplary embodiment of the present invention. The User Accounts Table holds primary user account data.










TABLE 3







Field
Description









CustID
Unique record




ID. Primary




key.



FirstName
User's first




name.



LastName
User's last




name.



EMailAddress
User's e-mail




address. Also




serves as the




user login name.




Date change




notices and




other e-mails are




sent to this




account.




Contents are




encrypted.



DOBMonth
Month part of




date of birth.



DOBDay
Day part of date




of birth.



DOBYear
Year part of date




of birth.



Password
Users password.




Contents are




encrypted.



PasswordQ
Password




question. This




question is




asked when the




user has




forgotten their




password and




needs us to e-




mail it to them.




Contents are




encrypted.



PasswordA
Password




answer. In order




for us to e-mail




the users




password the




user must




provide the




correct answer




(this field) the




Password




Question.



NotifyChanges
Notify user




when any of




their dates are




changed because




of changes to




the rules.



RemEmails
Send reminder




e-mails? This




option is “On”




by default.



Inactive
Is this user




record inactive?




Can only be set




by




administrator.



OnMailingList
Has the user




selected to be on




our mailing list.




Will receive




data about




Administrator




products and




special offers.



OtherMailing
Has the user




selected to




receive




occasional third




party product




data?



SubscriptLevel
User




subscription




level.




Determines




which




application




functions can be




accessed. NULL = all




functions.



CorpAccount
Is this a




corporate




account?



CorpAccountID
This field will




have the ID of




the corporate




account record if




this user is part




of a corporate




account.



TrialPeriod
Number of days




in user's trial




period.



Credit
Allows us to




apply a credit to




the users




account.



Discount
Percentage




discount. 0 to




100 percent.



Visits
Number of times




the user has




logged into our




site.



LastVistedOn
Date and time of




last visit (log




on) to our site.



AddedOn
Date and time




record was




added.



ChangedOn
Date and time




record was last




changed.



BillingType
Includes the




billing type.




Can be set to




“Monthly




statement” or




“Bill credit




card”. The




“Monthly




statement”




setting can only




be used on




corporate




accounts.



CRCardType
Credit card type




(American




Express, Master




Card, etc).



CRCardNumber
Credit card




number. This




field is 128-bit




encrypted.



CRExpireMonth
Credit card




expiration




month.



CRExpireYear
Credit card




expiration year.










The Password, PasswordQ, PasswordA EmailAddress and CRCardNumber fields are 128-bit encrypted. The DOBMonth, DOBDay and DOBYear fields are used to authenticate the user before allowing the user to view their password question (PasswordQ). The password question is asked when the user has forgotten their password and is requesting that the password be e-mailed to the user.
Table 4 is a Firm Information table in accordance with an exemplary embodiment of the present invention. The Firm Information table includes firm data associated with a user's account record. This data is used for product update notices, special offers from alliance partners and date change notifications.










TABLE 4







Field
Description









ID
Unique record ID. Primary key.



CustID
User ID. Foreign key.



FirmName
Office name. Indexed.



Address1
Mailing address line.



Address2
Mailing address line.



City
City. Indexed.



StateProv
State or Province. Indexed.



ZipPCode
Zip or Postal Code. Indexed.



Country
Country code. Selected from a




pulldown list.



Phone
Work phone number.










The above table does not contain any primary contact or e-mail address data. This data is retrieved from an associated User Account table when needed. A Billing Information table includes alternate e-mail and contact data if this data is different than what is in the primary User Account/Firm Information tables.
Table 5 is a Billing Information Table includes billing data for a user. If no billing address data is provided then address data in the User Information table is used.










TABLE 5







Field
Description









ID
Unique record ID. Primary




key.



CustID
User ID. Foreign key.



BillingName
Billing name if different




than FirmName in the Firm




Information table. Indexed.



Attention
Attention name.



Address1
Billing address line.



Address2
Billing address line.



City
City. Indexed.



StateProv
State or Province. Indexed.



ZipPCode
Zip or Postal Code.




Indexed.



Country
Country code. Selected from




a pulldown list.



Phone
Billing phone.



EMailAddress
Billing e-mail address.




Encrypted.










Table 6 is a Transaction Log Table used to track data about dates generated by a user each time the user generates dates.










TABLE 6







Field
Description









TransID
Unique record ID.




Primary key.



CustID
User ID. Foreign key.



DateTime
Date and time of the




transaction.




Indexed.



AmountBilled
Amount billed for




this transaction.



NumDatesAdded
Number of dates




generated by the




transaction. If the




user added dates to




an existing group




then this number is




the number of new




dates added to the




group.










The court rule database includes tables used to schedule court deadlines. The court rule database further includes data used by the JSE and ESE. Table 7 is a Rule Sets table including data about each rule set in the court rule database.










TABLE 7







Field
Description









Code
Rule set code.



RSType
Is this a System or




User rule set?



Active
Is this rule set active?



CurrentAsOf
Update date for the




rule set.



AccessCode
Rule set activation




code.



CreatedOn
Date the rule set was




created.



NextFormulaID
Next available formula




ID for this rule set.



ChangeEvData
Change event data?



UseGlobalSettings
Use the global event




maintenance settings?



ProcessCompleted
Process completed




events during event




maintenance?



AddNewEvents
Add new events if




needed during event




maintenance?



AlterIfDateChanged
Alter events if the due




date has been changed




by the user?



CutoffDate
Event Maintenance




cutoff date.



Description
Rule set description




(name)



ExpertData
Jurisdiction Selection




Expert data.










Table 8 is a Formulas table as used in an exemplary embodiment of the present invention. The Formulas table includes formulas for each rule set in the court rule database.










TABLE 8







Field
Description









RuleSet
Rule set containing




this formula.



FormulaID
Unique ID of the




formula within the




rule set.



Ftype
Type of formula:




Trigger or Related.



Category
Category code.



Priority
Priority code.



Authority
Authority text.



UpdatedOn
Last updated on




this date.



Description
Formulas




description. Can be




up to 1024




characters.



ExpertData
Event Selection




Expert data (trigger




formulas only).




Can be up to 1024




characters.



Script
Formula




calculation script.




Can be up to 4096




characters.










When a formula is added or changed, a Formula Relationship table is updated to include appropriate scheduling data. Table 9 is a formula relationship table in accordance with an exemplary embodiment of the present invention. A Formula Relationship table includes relationship data for each formula in the court rule database. The relationship data is used to track which formulas are scheduled when a particular trigger formula is scheduled allowing retrieval of data for scheduling and display purposes.










TABLE 9







Field
Description









RuleSet
Rule set containing the




formula.



FormulaID
Unique ID of formula within




the rule set.



Trigger
If the formula is a “trigger”




formula then its trigger code




is placed here.



Related
The trigger code of the




relationship is placed in this




field.










When a formula is saved, entries are made in the Formula Relationship table and the formula script is evaluated for relationships with other formulas. If relationships are found, an entry is made in the Formula Relationship table for each relationship.
There are a few scenarios that are handled to create an accurate relationship table:










Scenario 1 - Single Trigger Relationship

















RESULT = CALCDATE 30 DAYS BEFORE TRIGGER $TR










In this scenario, a “Related” formula calculates a date that is 30 days before the $TR trigger date. This relationship is a one-to-one relationship. For example, if the ID of the formula is “CA:LA-FT-123”, the table entry would look like this:
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
123
NULL
$TR










The formula is included when scheduling a $TR trigger date is scheduled because “$TR” is in the “Related” Field.
Scenario 2—Multiple Trigger Relationship

D1=CALCDATE 35 DAYS BEFORE TRIGGER $TR

D2=CALCDATE 70 DAYS AFTER TRIGGER $TS

RESULT=LATER D1, D2

In this scenario a Related formula bases the formula's calculation off more than one trigger date. In this case the formula uses the $TR and $TS trigger dates for the formula's calculation. For example, if the ID of the formula is “CA:LA-100”, the table entries would look like this:
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
100
NULL
$TR



CA:LA-FT
100
NULL
$TS










When the $TR trigger date is scheduled, this formula will be included because it references $TR in Related Field for the first entry in the table.










Scenario 3 - Single Related Relationship















RESULT = CALCDATE 10 DAYS BEFORE RELATED CA:LA-FT-123









This calculation is based on a specific related formula (formula CA:LA-FT-123). In this case, the court date server resolves the formula ID into a trigger code before making an entry in the Formula Relationship table. The formula referenced by the calculation above is examined to determine if it can be resolved into a trigger code. If the specified formula cannot be resolved into a trigger code (because it also bases its calculation on a specific related formula) then an attempt is made to retrieve the trigger code from the formula that it references. This continues until the trigger code is found. If no Trigger Code is found then no date is calculated for the formula (this could occur if the CA:LA-FT-123 formula is deleted). For example, the CA:LA-FT-124 formula bases its date calculation off the $TR trigger formula. In this case, the resolution of the Trigger Code would be $TR and the table entry would look like this:
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
40
NULL
$TR










Note that the related formula used by the date calculation script is in the same rule set as the formula being calculated.
As another example, if the related formula used for the calculation bases its calculation off more than one trigger date, such as CA:LA-FT-123, the date calculation is as follows:

D1=CALCDATE 35 DAYS BEFORE TRIGGER $TR

D2=CALCDATE 70 DAYS AFTER TRIGGER $TS

RESULT=LATER D1, D2

In this case the following entry would be made in the relationship table as:
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
100
NULL
$TR



CA:LA-FT
100
NULL
$TS










Scenario 4—Branching Trigger
A Branch Trigger is a trigger whose date can either be provided by the user when the trigger is scheduled or can be scheduled when another trigger date is scheduled. For example, a Discover Cutoff date can be scheduled by itself or as part of a trial. In this case, the calculation for the Discover Cutoff trigger formula looks like this:

RESULT=CALCDATE 30 DAYS BEFORE TRIGGER $TR

The table entry for this formula looks like this (assuming a formula ID of CA:LA-FT-32):
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
32
$DC
$TR










In the case where the Branching Trigger formula bases its calculation on more than one trigger formula the following would be added to the table (TRIGGER $TR and TRIGGER $XX are referenced by the formula):
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
32
$DC
$TR



CA:LA-FT
32
$DC
$XX










Scenario 5—Trigger Formula
In this scenario the trigger formula does not contain a calculation script. The user must provide the date when the trigger is scheduled. In this case the table entry looks like this:
















Rule Set
Formula ID
Trigger
Related









CA:LA-FT
1
$TR
NULL










A “delete” trigger on the Formulas table handles deleting entries in this table when a formula is deleted.
A Rule Set Type table includes billing types for each rule set. A billing type is used to access an additional charge when generating dates using a particular rule set. Table 10 is a Rule Set Type table in accordance with an exemplary embodiment of the present invention.










TABLE 10







Field
Description









RuleSet
Rule set code.



BillingType
This is the rule sets billing




type value. This value is




used to look up any




additional amount to charge




when dates are generated




using a particular type of




rule set.










A Formula Changes Index table includes an entry for each change made to a formula. When an administrator of a court date server adds, changes or deletes a formula, an entry is made in the Formula Changes Index for the change. The previously described Event Maintenance process uses the data in the Formula Changes Index table to process existing events for formula additions, changes or deletions. Table 11 is a Formula Changes Index table in accordance with an exemplary embodiment of the present invention.










TABLE 11







Field
Description









URI
Unique record ID.




Numeric identity field.



ChangeType
Type of change made to




the formula. 0 = Undefined,




1 = Added, 2 = Changed,




3 = Corrected, 4 = Deleted.



Finalized
Setting this field




“finalizes” the change




essentially releasing the




change to the Event




Maintenance Process.



Processed
Has Event Maintenance




finished processing this




change?



AddedOn
The date and time the




index record was added to




the table.



AddedBy
The user that made the




formula change that caused




an entry to be made in this




table.



ProcessedOn
Date and time Event




Maintenance finished




applying this change to




existing events.



RuleSet
Rule set code. This field




and the FormulaID field




below comprise the unique




formula ID.



FormulaID
Unique ID within the rule




set specified by the




RuleSet field.










A formula changes detail table (not shown) includes formula records for each change made to a formula. It's structure is identical to the previously described formulas table structure except that the constraint on duplicate formula ID's is removed.
A docket data database includes user matter and calendar data. A matters table includes matters added by a user. Matters can be added to this table when generating dates or from the user's administration page. Table 12 is a matters table in accordance with an exemplary embodiment of the present invention.










TABLE 12







Field
Description









MatterID
Identity field.



CustID
User ID.



MatterName
Name of the matter.



DocketID
Docket ID.



MatterType
Matter type code.



RuleSets
Comma delimited list of




default rule sets.




Assigned by selecting the




Venue from the




Jurisdiction Selection




Expert.



DateOpened
Date the matter was




opened.



DateClosed
Date the matter was




closed.



Inactive
Matter is no longer




active. Any attempt to




use this matter results in




an error.



DeletedOn
The date the user deleted




this matter. Delete




matters older than a




certain period of time are




periodically removed




from the database.










A Matter Formulas table includes special matter date calculation formulas that are applied to certain types of formula calculations. Table 13 is a Matter Formulas table in accordance with an exemplary embodiment of the present invention.










TABLE 13







Field
Description









MatterID
Identity field.



FormulaTag
Tag string. For example, this




field would contain the tag




“MOTION” if the formula is




applied to motion dates.



Script
Includes the date calculation




script. Can be up to 4096




characters.










An Event Group table includes event groups generated by users. Table 14 is an Event Group table in accordance with an exemplary embodiment of the present invention.










TABLE 14







Field
Description









GroupID
Unique record ID.




Primary key.



MatterID
Matter ID. Foreign




key.



RuleSets
Comma delimited




list of rule sets used.



AddedOn
Date and time the




group was added.




Indexed.



LastChangedOn
Date and time the




group was last




changed. Indexed.










An Events table stores the dates generated by a user. Each record in the Events table is linked to an Event Group record via a GroupID entry. Table 15 is an Events table in accordance with an exemplary embodiment of the present invention.










TABLE 15







Field
Description









ID
Identity field. Primary




key.



GroupID
Event Group ID.




Foreign key linked to the




Event Group Table.



RuleSetUsed
Rule set used to schedule




this date. Indexed.



FormulaID
ID of the formula within




the specified Rule Set.




Indexed.



EventDate
Event date. Indexed.



StartTime
Event start time.



EndTime
Event end time.



Reminder
Send a reminder e-mail




on this date.



RemSentOn
Date a reminder e-mail




was sent to the user.



Complete
Has the event been




completed?



Skipped
Has the event been




skipped by the user?



DontChange
Never change this date




even if the rules change.




The user can set this and




it is also set if the date or




time is changed from its




originally calculated date




or time.



DeletedOn
Date the user deleted this




event. Deleted events




are periodically removed




from the database by




administrator.



Note
Variable length note




field. Up to 1024




characters.










An event maintenance database includes tables used to track event date change data and user notification data. If any user dates are changed during an Event Maintenance process, a master entry is made in an Event Maintenance Log table and the changes associated with the master entry are written to an Event Maintenance Detail table. These tables are later used to notify users of changes to their dates.
Table 16 is an Event Maintenance Log table in accordance with an exemplary embodiment of the present invention.










TABLE 16







Field
Description









LogID
Identity field.




Primary key.



CustID
User ID (link to the




Account table).




Foreign key.



ChangedOn
Date and time the




changes where made




(the date the log




entry was added to




the table).



NotifiedOn
Date user was




notified of any




changes made to any




of their dates.



TimesNotified
How many times the




user has been




notified about this




change.



Confirmed
Has the user




confirmed




notification of




changes?




Confirmation is




performed by




returning the




notification e-mail to




administrator.



AllGroupsProcessed
Have all the event




groups effected by




Event Maintenance




for this user been




processed?



NeverConfirmed
Set to True if the




user never confirms




any of the




notification e-mails.



NumChanges
Number of changed




records.










Table 17 is an Event Maintenance Detail table in accordance with an exemplary embodiment of the present invention.










TABLE 17







Field
Description









LogID
Event Maintenance Log




record ID. Foreign key




used to link to the ID field




of the Event Maintenance




Log table.



EventID
Event ID (link to the Event




table). Foreign key.



Changes
This field includes the




detail of the changes made.




Each change is described in




one sentence. For example




“Date changed from




Feb. 10, 2002 to Feb. 09, 2002”.










Court schedule rules are defined within a court date server using a Date Calculation Scripting Language (DCSL). DCSL includes statements used to calculate court date according to rules defined by the courts. DCSL is designed to be as flexible as possible allowing for all current, and future, date calculation requirements.
DCSL allows the use of Formula Variable arrays by a formula calculation. The Formula Variable arrays are created when a formula is calculated and destroyed when the formula has completed. The scope of the Formula Variables are local to the currently executing formula. In addition, a formula has the following variables it can use during its script execution.











Variables
Description







RESULT
A date variable that includes a result of a formula



calculation. Initialized to 0 (EMPTY) before the script



executes.


D0-DF
16 date variables. Can be used to store any valid date



value.


I0-I9
10 Integer variables.









A Date Calculation Expression is a text string that includes data on how to calculate a date and has the following format:












{amount} {unit} {direction} {event}








Where:



{amount}
Number of units to calculate.


{unit}
Calculation unit. [HOURS|COURTHOURS|DAYS|



COURTDAYS|WEEKS|MONTHS|YEARS].


{direction}
Direction of calculation. [BEFORE|AFTER]


{event}
A target date (event) on which to base the calculation.



[TRIGGER|RELATED] [Key Code|Formula ID].









DCSL includes the following statements:
An “ADD” statement adds two integers. The ADD syntax is:
ADD {integer1}, {integer 2}
An “ADJUST” statement is used to adjust a date a specified number of units in the specified direction. Calculations using COURTHOURS and COURTDAYS units are guaranteed to fall on a court workday. For all other unit settings, use the ADJUSTHOLIDAY statement to ensure that the calculated date falls on a valid court day. The ADJUST syntax is:












 ADJUST {date variable} {direction} {amount} {unit}








Where:



{date variable}
A valid date variable.


{direction}
Direction of adjustment from the calculated



date [FORWARD|BACKWARD]


{amount}
Number of units to calculate.


{unit}
Calculation unit. [HOURS|COURTHOURS|



DAYS|COURTDAYS|WEEKS|MONTHS|



YEARS].









An “ADJUSTDOW” statement adjusts a date to a specified day of the week. Adjustments that use a CONTINUE option are guaranteed to fall on a court workday. The syntax of the ADJUSTDOW statement is:












ADJUSTDOW{date variable} TO {direction} {dow} [WITH {options}]








Where:



{date variable}
A valid date variable or string date.


{direction}
DOW adjustment direction. [PREVIOUS|



NEXT]


{dow}
Day of Week adjustment setting.



[MONDAY|TUESDAY|WEDNESDAY|



THURSDAY|FRIDAY|SATURDAY|



SUNDAY]


{options}
Optional adjustment options. Currently



only CONTINUE is supported. The



CONTINUE option “continues” the DOW



adjustment to the next/previous day of the



week if the adjusted date falls on a court



holiday.









An “ADJUSTHOLIDAY” statement adjusts the specified date to the next or previous court workday. The rule set's holiday list is used to perform this adjustment. The syntax of the ADJUSTHOLIDAY statement is:












   ADJUSTHOLIDAY {date variable} TO {direction} COURTDAY








Where:



  {date variable}
A valid date variable or string date.


  {direction}
Direction of adjustment.  [NEXT |



PREVIOUS].









An “ADJUSTSPECIAL” statement is used to apply adjustments defined at the matter level. For example when a judge assigned to a matter only hears motions on Mondays. A calculation formula can be created for a matter so that when a “Motion” date is calculated the matter formula for “Motion” can be used to adjust the calculated date. A current unique Matter ID is used when retrieving the calculation formula from the appropriate table for the matter. Each date calculation session has a unique Matter ID which allows this statement to retrieve the adjustment formula from matter data. The unique Matter ID is referred to as a “Matter Context”. If no matter context exists, or no special formula is found for the specified “tag”, the date is not changed. The statement simply returns the date that was passed to it in the {date variable} argument. The syntax of the ADJUSTSPECIAL statement is:












   ADJUSTSPECIAL date variable} {“tag”}








Where:



  {date variable}
Any valid date variable or string date.


  {“tag”}
Tag indicating which special formula to use for the



matter when adjusting the date.









An “ADJUSTWMY” statement is used to adjust a date to the beginning or end of the week, month or year the date falls within. The adjusted date is not guaranteed to fall on a court workday. The syntax of the ADJUSTWMY statement is:















 ADJUSTWMY {date variable} TO {direction} OF {unit}










{date variable}
A valid date variable or string date.



{direction}
Adjustment direction. [BEGINNING|END]



{unit}
Unit adjustment setting. [WEEK|MONTH|




YEAR]










An “ASSIGNMENT” statement (=) assigns a variable a value.
A “CALCDATE” statement calculates a date based on another date. If the date on which the calculation is based has not yet been calculated then that date is first calculated and the execution of the CALCDATE statement continues. The CALCDATE statement does not adjust the calculated date for court holidays if the calculation is not based on the COURTHOURS or COURTDAYS units. DCSL does not allow circular formula references. The syntax of the CALCDATE statement is:















  CALCDATE {calculation}



Where:



{calculation}   A valid date calculation expression.










A “COMPLETE” statement is used to complete the dates calculated using specified formulas. Whether or not the event is actually marked “completed” when this statement executes depends on how a user's “Auto complete events” option is set. The syntax of the COMPLETE statement is:















 COMPLETE {note} {formula list}










{note}
A notation assigned to the dates marked




completed by this statement.



{formula list}
List of formula Ids whose dates you wish to




mark completed.










A “DATEDIFF” statement is used to get the difference in days between two dates. The order of the dates doesn't matter. “date1” could be greater than or less than “date2”. The syntax of the DATEDIFF statement is:
DATEDIFF {date1}, {date2}
A “DELETE” statement is used to delete the dates calculated using the specified formulas. The syntax of the DELETE statement is:















 DELETE {note} {formula list}










 Where:




{note}
The notation assigned to the dates marked deleted




by this statement. Can be up to 80 characters.



{formula list}
List of formula Ids whose dates you wish to




delete.










An “EARLIER” statement returns the earlier of the dates in a list of date variables. The syntax of an EARLIER statement is:















 EARLIER {date var list}










 Where:




{date var list}
List of date variables to compare. Can contain




any number of valid date variables.










An “EXIT” statement is used to statement to exit a formula before the formula has completed execution. The syntax of an EXIT statement is:
EXIT
A “GETDATE” statement is used to retrieve the date of an event whose calculation is based on the specified formula. If the date for the specified formula has not been calculated, this statement causes the specified formula to calculate the date. The syntax of a GETDATE statement is:















 GETDATE {date variable} {type} {formula id | key code}










 Where:




{date variable}
A valid date variable.



{type}
Type of date. [TRIGGER|RELATED].



{formula id | key code}
Any valid formula id or key code.




[formula id|key code]










A “GETDATE” statement sets the date variable D1 to the date calculated by the specified related formula. The syntax of a GETDATE statement is:
GETDATE D1 TRIGGER $TR
An “IF THEN” statement is used to perform an action conditionally. The syntax of the IF THEN statement is:















  IF {condition} THEN {action block}










Where:




  {condition}
The condition clause. The values compared




must be the same type. [>|<|!=|=|>=|<=].



  {action block}
Includes an action statement or statements. If




more that one statement you must bracket the




action block with BEGIN...ENDIF.










Another form of the IF THEN statement is:
















  IF [NOT] EXISTS {type} {formula id} THEN {action block}










Where:




  {type}
Type of date.  [TRIGGER |




RELATED].



  {formula id}
Any valid formula id or key code.




[formula id|key code]



  {action block}
Action or action block.










This condition statement is used to perform an action if a date exists for the specified formula. The optional NOT can be used to test if a date does not exist.
A “LATER” statement returns the later of the dates in a list of date variables. The syntax of the LATER statement is:















 LATER {date var list}



 Where:



{date var list}  List of date variables to compare.










A “NOTAPPLICABLE” statement is used to mark a date as “not applicable”. This means that the addition of some other date has made the dates specified in the statement unnecessary. The syntax of a NOTAPPLICABLE statement is:















   NOTAPPLICABLE {Note} {formula list}










Where:




  {Note}
The notation assigned to the dates marked




“Not Applicable” by this statement.



  {formula list}
List of formula Ids whose dates you wish to




mark as “not applicable”.










A “REM” statement adds a comment to the formula calculation script. The syntax of a REM statement is:















   REM {comment text}



Where:



  {comment text}  Message text string.










A “SUBTRACT” statement is used to subtract two integers. Integer2 is subtracted from Integer1. The syntax of a SUBTRACT statement is:
SUBTRACT {integer1}, {integer 2}
Referring again to FIG. 1, a DCE 102 performs court date calculations based on court rules stored in a court rule database 104. The DCE includes a date calculation script interpreter 103 that processes DCSL.
FIG. 20 is a hardware architecture diagram of a data process system such as a general purpose computer suitable for use as a court date server host. A processor 2000 is coupled via a system bus 2002 to a main memory 2004 and an I/O control unit 2006. The I/O control unit is coupled via an I/O local bus 2008 to a storage controller 2010, and a network controller 2016.
The storage controller is coupled to a storage device 2012. Computer program instructions 2014 implementing a court date server are stored on the storage device until the processor retrieves the computer program instructions and stores them in the main memory. The processor then executes the computer program instructions stored in the main memory to implement the features of a court date server.
The network controller is operatively coupled to communications device 2018. The communications device is adapted to allow a court date server hosted by the general purpose computer to communicate via a computer network such as the Internet with other software objects on the computer network such as a user client.
FIG. 28 is a block diagram of the court date server 100 configured for rules updating and notification according to one embodiment of the invention. According to this embodiment, the court date server 100 is configured with a rules database update module 3000 for automatically updating the rules database 104 with changes to the rules as indicated in a rules update file 3018. The rules update file is provided by a court rules maintenance application 3014 which may be run on a computer 3016 coupled to the court date server 100. The court rules maintenance application 3014 may be a software application run by a processor included in the computer 3016 according to computer instructions stored in memory.
The court date server 100 is also configured with a date maintenance module 3002 for modifying calculated deadlines based on the changes to the rules database, and a change notification module 3004 for informing customers of the modified deadlines. The notifications may be sent, for example, as emails to affected customers' computers 3020. One or more of these modules may be incorporated into the event maintenance module 2208 and/or change notification module 2216 discussed above with reference to FIGS. 22-25. Furthermore, one or more of these modules may be hosted on a separate server, such as, for example, a dedicated change notification server 3010 as illustrated in FIG. 28.
For rule changes that might affect deadlines generated for one or more customers, the database update module 3000 flags those changes by placing the change information in an event maintenance (EM) changes database 3005. The date maintenance module 3002 uses the change information in the EM changes database 3005 to make changes to existing deadlines. The date maintenance module 3002 places notification information for the modified deadlines in a notification information database 3007. The notification information is then used by the change notification module 3004 for notifying the customers of the changed deadlines. The EM changes database 3005 and notification information database 3007 may reside in the rules database 104 or in one or more separately dedicated databases hosted by, for example, a dedicated database server 3012.
FIG. 29 is a layout diagram of the rules update file 3018 provided by the court rules maintenance application 3014 according to one embodiment of the invention. The rules update file 3018 includes all the information needed for updating the rules database 104. According to the illustrated embodiment, the rules update file 3018 includes a rule set record 3030 identifying rule sets 3030a affected by the update, as well as a non-event maintenance (NEM) date field 3030b, and an EM date field 3030c. The EM date field 3030c indicates that the update to a particular rule set is a change that may affect existing deadlines, and thus, event maintenance and change notifications may be needed. The date in the EM date field 3030c may be a date that identifies the particular EM update.
A NEM change is a change to a particular rule set that does not affect any existing deadlines so no change notifications are needed. The date in the NEM date field 3030b may be the date that identifies the particular NEM update. Exemplary NEM changes are changes that slightly change verbiage of rule text but do not affect date calculations, or changes that affect date calculations but are not retroactive to previously calculated dates.
The rules update file 3018 further includes a formulas record 3032 for each rule set identified in the rule set record 3030. The formulas record 3032 includes formula identifiers 3032a for formulas in the associated rule set that have been affected by the update, as well formula details 3032b which include the changes to the formula, and a formula update date 3032c that identifies the date of the particular formula update.
The rules update file also includes a holiday record 3034 and a deleted formulas record 3036. The holiday record 3032 includes for each rule set in the rule set record 3030, an up-to-date list of all holiday names 3034a and holiday dates 3034b for the associated rule set. The delete formulas record 3036 includes a list of deleted formulas 3036a in the associated rule set.
FIG. 30 is a layout diagram of the EM changes DB 3005 containing information of EM changes that call for event maintenance and change notification to affected customers according to one embodiment of the invention. The information in the EM changes DB may be in lieu or in addition to any information provided in the Formula Changes Index table illustrated above in Table 11.
The illustrated EM changes DB 3005 includes an EM queue table 3006 and an EM change record 3050. The EM queue table 3006 includes one or more event maintenance jobs placed by the database update module 3000 based on a determination that there are changes to the rules considered to be EM changes that may require recalculation of deadlines, and notification of the recalculated deadlines.
The EM change record 3050 includes information on the type 3050a of EM change that was made. The change type may be date/time change, authority change, and/or rule description change. The type 3050a field may also indicate whether the change is a formula/holiday addition, deletion, or change. The EM change record 3050 further includes a formula ID field 3050b for identifying the changed formula and/or its rule set, and a changed holiday field 3050c for identifying a changed or new holiday name and/or date. The information in the EM changes record 3050 is then used by the date maintenance module 3002 to recalculate any affected dates as necessary.
FIG. 31 is a layout diagram of the notification information DB 3007 for notifying customers of changed deadlines according to one embodiment of the invention. The notification information DB 3007 includes a notification queue table 3008 and a deadline change record 3060. The notification queue table 3008 includes one or more notification jobs placed by the date maintenance module 3002 as a result to modifications made to deadlines calculated for a particular customer.
The deadline change record 3060 identifies via a customer ID field 3060a the customers affected by the changed deadline. The information in the deadline change record 3018 may be in lieu or in addition to any information provided in the Event Maintenance Log table and Event Maintenance Detail table illustrated above in Tables 16 and 17.
The illustrated deadline change record 3060 identifies for each affected customer, the type of change 3060a associated with the updated/added rule (i.e. date/time change, authority change, and/or description change), a previously calculated deadline 3060c, the updated deadline 3060d resulting from the updated/added rule, and an authority and/or description 3060e of the updated/added rule. The information in the deadline change record 3060 is then used by the change notification module 3004 to provide information to customers of changed deadlines.
FIG. 32 is a flow diagram of an overall rules updating and notification process according to one embodiment of the invention. In step 3100, the change notification server 3010 receives the rules update file 3018 posted by the court rules maintenance application 3014.
In step 3102, the database update module 3000 applies the changes to the rules database 104. During the update process, entries may be made to the EM change record 3050 for use by the date maintenance module 3002 during its processing. Furthermore, in step 3104, the database update module 3000 adds a job entry in the event maintenance queue table 3006 if changes have been made to the database that may affect deadlines generated by one or more customers. The database update module 3000 proceeds to send an email to the site administrators that the database update has completed successfully.
Upon finding a job entry in the event maintenance queue table 3006, the date maintenance module 3002, in step 3106, uses the information generated by the database update module 3000 and stored in the EM change record 3050 to check existing deadlines for changes. Changes are made to the existing deadlines in step 3108 and recorded in the deadline change record 3060 for use by the change notification module 3004 to send notifications. When date maintenance if finished, the change notification module adds a job entry to the notification queue table 3008 in step 3110, and sends an email notifying the site administrators that the date maintenance process is complete.
In step 3112, the change notification module 3004 monitors the notification queue table 3008 and finds a new job in the table. The change notification module 3004 uses the change information generated by the date maintenance module 3002 and stored in the deadline change record 3060 to create and send change notifications to affected customers. According to one embodiment of the invention, the change notifications are sent as email notices to the affected customers. When all notifications have been sent, the change notification module 3004 sends a completion email to all site administrators.
FIG. 33 is a more detailed flow diagram of step 3102 of updating the rules database according to one embodiment of the invention. In step 3200, the database update module 3000 monitors for any rules update files 3018 posted to the change notification server 3010. In doing this, the database update module 3000 may monitor a particular area of the change notification server 3010 for new postings of rules update files.
In step 3202, a determination is made as to whether a rules update file has been found. If the answer is YES, the database update module 3200 proceeds to process any formula changes indicated in the rules update file step 3204, and process any holiday changes listed in the update file in step 3206.
FIG. 34 is a more detailed flow diagram of step 3204 of processing formula changes according to one embodiment of the invention. In step 3300, the database update module 3000 reads from the rules update file 3018 information on the changed, deleted, or added formula.
In step 3302, changes or additions to the rules in a particular rule set are made to the rules database 104 based on the formula details 3032b provided in the formulas record 3032 for that rule set. Deletions to the formulas are made based on the formula IDs included in the deleted formulas record 3036 for that rule set.
According to one embodiment of the invention, a determination is made that an existing formula is being modified if the corresponding formula ID appears in both the formulas record 3032 of the rules update file 3018 as well as in the rules database 104. The existing formula in the rules database 104 is retrieved and modified based on the formula details 3032b in the formulas record 3032. If the formula modification modifies its relationship to other formulas, the Formula Relationship Table in table 9 is updated to reflect the changed relationship.
New formula additions are detected if a formula ID appears in the formulas record 3032 of the rules update file 3018 but not in the rules database 104. Any formulas detected to be new are added to the rules database 104. Furthermore, an entry is made in the Formula Relationship Table for the new rule for indicating any formulas to which the new rule refers. Any such formulas referenced by the new rule may be easily identified by simply parsing the script for the new rule.
Formula deletions are detected if a formula ID is included in the deleted formulas record 3036. Upon such a detection, the corresponding formula is either deleted or marked as being deleted in the rules database 104. The Formula Relationship Table is also modified by either deleting an entry for the deleted formula, or marking the entry to indicate that the formula has been deleted.
In step 3304, a determination is made as to whether the update made is an EM change that needs to be recorded for date maintenance purposes. According to one embodiment of the invention, all formula deletions are considered EM changes. For modified or added formulas, a determination as to whether the formula change/addition is an EM change or a NEM change is made by comparing the formula update date 3032c for the formula against the EM and NEM dates 3030b, 3030c set for the corresponding rule set. If the formula update date matches the EM date, then the change/addition is deemed to be an EM change.
EM changes are recorded in the EM change record 3050 in step 3306. For example, information that indicates what part of the formula was added or changed is included in the change type 3050a field, and the identifier for the changed formula is added in the formula ID field 3050b. 
In step 3308, a determination is made as to whether all formula changes/additions in the formulas record 3032 and the deleted formulas record 3036 have been processed. If there are more changes to process, the date maintenance process returns to step 3300.
FIG. 35 is a more detailed flow diagram of step 3206 (FIG. 33) of processing holiday changes by the date maintenance module according to one embodiment of the invention. In step 3400, a holiday is retrieved from the holiday record 3034 in the rules update file 3018, and a determination is made, in step 3402, as to whether there has been update of this particular holiday. In this regard, the holiday name and date in the holiday record 3034 is looked up in the rules database 104. If the holiday name or date exists in the rules database, it is a holiday update. A determination is then made in step 3404 as to whether the holiday update is an update in the holiday date. If the answer is YES, the change is recorded in step 3406 in the EM change record 3050. The rules database is then updated with the changed holiday name or date in step 3412.
If the holiday in the holiday record 3034 is not reflective of an updated holiday, a determination is made in step 3408 as to whether the holiday is a holiday addition. This may be determined, for example, if neither the holiday name nor date is found in the rules database. The new holiday name and date is recorded in the EM change record 3050, and the rules database 104 is updated in step 3412 with the new holiday.
In step 3414 a determination is made as to whether all the holidays in the holiday record 3034 have been considered. If the answer is NO, the process returns to step 3400 to retrieve the next holiday in the holiday record 3034.
FIG. 36 is a more detailed flow diagram of steps 3106 and 3108 (FIG. 32) executed by the date maintenance module 3002 for updating existing deadlines based on changes to the rules database 104 according to one embodiment of the invention. In step 3500, the date maintenance module 3002 monitors the event maintenance queue 3006 and processes a job in the queue in FIFO order.
In step 3502, the date maintenance module 3002 retrieves the EM change information stored in the EM change record 3050 associated with the current job.
In step 3504, the date maintenance module 3002 identifies the existing transactions affected by the changes indicated in the EM change record 3050. In this regard, the court date server 100 tracks all deadlines generated by customers. According to one embodiment of the invention, this is done by creating a transaction record each time a customer generates deadlines, and associating the deadlines generated for the customer with that transaction. Each transaction record includes the rules set(s) used when generating the deadlines, and each deadline listed in the transaction includes the calculated date and the formula used to calculate the date. The generated transaction records may then be used to determine which deadlines and customers are affected by a rules update. According to one embodiment of the invention, certain transactions and deadlines are safely excluded from processing to reduce the number of transactions that need to be examined during the date maintenance process. For example, any transactions that do not reference any of the rule sets for which there is an EM change are excluded from consideration. Furthermore, any transaction whose associated dates are prior to the date in which the event maintenance is occurring are also excluded from consideration.
In step 3506, a determination is made as to whether there are any more identified transaction records that need to be processed. If the answer is YES, the date maintenance module 3002 processes the next identified transaction record in step 3508. In this regard, the date maintenance module modifies one or more dates in the affected transaction records, and in step 3510, records the deadline change information for each affected customer in the deadline change record 3060. In doing so, the date maintenance module stores in the deadline change record 3060 the customer ID of the affected customer, information on the type of change to the rule, the old deadline, the newly calculated deadline, authority and other description of the changed rule, and the like. This information is then used by the change notification module 3004 for sending notifications to the affected customer.
Referring again to step 3504, deadlines may be affected by formula changes, formula deletions, and formula additions. Deadlines may also be affected by holiday changes and additions. In handling formula changes, the date maintenance module 3002 identifies transaction records containing deadlines whose formula IDs are identified in the EM change record 3050 as being changed formulas. The deadlines in these transactions are then recalculated based on the changed formula.
With respect to formula deletions, the date maintenance module 3002 identifies transaction records containing deadlines whose formula IDs are identified in the EM change record 3050 as being deleted formulas. The identified deadlines associated formulas IDs are then deleted from the transaction records. Furthermore, the date maintenance module queries the Formula Relationship Table for identifying any formulas referencing the deleted formula. Dates in the identified transaction records which make use of such formulas referencing the deleted formula are then recalculated.
With respect to formula additions, new deadlines are calculated based on the newly added formulas. In determining which customers need to be notified of the new deadlines, the date maintenance module queries the Formula Relationship Table for determining what formulas are referenced by the new formula. Those transactions having deadlines whose formulas are referenced by the new formula are then notified of the new deadline.
When locating deadlines for processing based on holiday changes/additions to a rule set, the event maintenance module cannot simply look for any deadlines that have been scheduled for a date that is now a court holiday. This is because in most cases, formula calculations are based on holiday adjustments during the processing of the formulas date calculation script. For example, a formula may use a “COURT DAY” calculation type or use holiday adjustment statements.
According to one embodiment of the invention, the date maintenance module uses the earliest holiday date that was changed or added to a rule set as follows:
1. Find the earliest and latest changed/added holiday dates for the rule set.
2. Find all transaction records that reference the rule set whose holiday list has changed, and that have at least one deadline that is after the date in which the event maintenance processing is occurring (the cutoff date) and at least one deadline that is on or between the earliest and latest holiday date change/addition.
3. Check the deadlines in the identified transaction records for accuracy based on the holiday change/addition. In this regard, the identified deadlines may be recalculated for determining whether the holiday change/addition changes the deadlines.
According to one embodiment of the invention, certain transaction records may be safely excluded from review due to holiday changes. For example, all transactions whose deadlines are before the date in which in the event maintenance processing is occurring are excluded from consideration. All transactions whose deadlines are all either before the earliest holiday date change/addition or after the latest holiday change/addition are also excluded from consideration.
FIG. 37 is a flow diagram of the process for providing change notification details to a customer according to one embodiment of the invention. The change notification module 3004 uses information in the deadline change record 3060 to transmit a change notification email 3500 to the customer identified in the deadline change record 3060. According to one embodiment, the email simply informs the customer that there have been particular types of rule changes that have affected the deadlines they have generated, and tells them how to check the web site provided by the court date server 100 for detailed information about the changes.
The customer selects a link in the notification email in step 3502 to access the web site provided by the court date server 100 and logs-in via a login page 3504. The customer's home page 3506 is displayed upon login.
In step 3508, the customer selects a change notification link on the customer's home page. In response, a historical list 3510 of all change notifications produced as a result of rule updates are displayed on the web page. The most recent notification record appears at the top of the list. Each notification record includes a details link which, when selected by the customer in step 3512, displays a details page 3514 with details of the changes associated with that notification record. According to one embodiment, the details page includes information about each transaction that contains a deadline whose due date, authority, and/or description has changed. For example, the details page may indicate a transaction ID, the number of deadline changes in the transaction, and other descriptions (e.g. matter reference, jurisdiction information, and event selection information).
Each transaction listed on the details page includes a view changes link and a regenerate link. Selection of the view changes link displays a page that contains details on each deadline change for that transaction, such as, for example, the original date/time and the changed new date/time, the original authority and the changed new authority, and/or the original description and the changed new description.
Selection of the regenerate link recalculates the dates in the transaction and sends the resultant date list to the customer.
According to one embodiment of the invention, the customer may view the changes and receive regenerated dates upon making a payment. In this regard, a determination is made, in step 3516, as to whether the view changes link has been selected. A determination is also made, in step 3518, as to whether the regenerate link has been selected. If either link has been selected, a determination is made in step 3520 as to whether the customer has been charged for the viewing and regeneration. If the answer is NO, an amount for the viewing or regeneration is determined, and the customer's account is charged for that amount in step 3522. The change details are displayed and deadlines are recalculated in step 3524 responsive to a determination that the customer has been charged.
In step 3526, a determination is made as to whether the recalculated deadlines are to be emailed to the customer. If the answer is YES, the customer receives an email 3528 indicating that the deadlines have been regenerated. According to one embodiment, the regenerated deadlines are transmitted with the email.
Although this invention has been described in certain specific embodiments, many additional modifications and variations would be apparent to those skilled in the art. It is therefore to be understood that this invention may be practiced otherwise than as specifically described. Thus, the present embodiments of the invention should be considered in all respects as illustrative and not restrictive, the scope of the invention to be determined by any claims supportable by this application and the claims' equivalents.

## Claims

1. A method for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the method comprising:
maintaining in a database at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;
receiving, under control of a server, an initial trigger date for an initial trigger legal event;
selecting, under control of the server, one or more date calculation instructions from the database based on the initial trigger legal event;
calculating, under control of the server, one or more event dates based on the initial trigger date and the retrieved date calculation instructions;
transmitting, under control of the server, the one or more calculated event dates to a user client;
maintaining, under control of the server, a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;
monitoring, under control of the server, a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions;
automatically determining, under control of the server, whether the one or more date calculation instructions identified in the record are identified in the changes table;
for each one of the one or more date calculation instructions identified in the changes table, recalculating, under control of the server, the associated event date based on the change to the corresponding date calculation instruction; and
transmitting, under control of the server, the recalculated one or more event dates to the user client.

2. The method of claim 1 further comprising:
maintaining a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and
updating, under control of the server, relationship information in the relationship table based on the changed date calculation instructions.

3. The method of claim 1 further comprising:
identifying, under control of the server, a customer affected by the recalculated one or more event dates; and
transmitting, under control of the server, a notification to the customer of the recalculated one or more event dates.

4. The method of claim 1 further comprising:
calculating, under control of the server, a fee for recalculating the one or more event dates; and
charging, under control of the server, a user account based on the calculated fee.

5. The method of claim 1 further comprising:
receiving, under control of the server, update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, and further identifying the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the recalculation of the one or more event dates identified in the changes table.

6. The method of claim 5, wherein the updating includes:
determining, under control of the server, whether a date calculation instruction identified in the changes table exists in the database;
responsive to a determination that the identified date calculation instruction does not exist in the database, adding, under control of the server, the identified date calculation instruction to the database.

7. The method of claim 6 further comprising:
determining, under control of the server, whether the addition of the identified data calculation instruction is an event maintenance or non-event maintenance update; and
responsive to a determination that the addition of the identified date calculation instruction is an event maintenance update, storing, under control of the server, information on the added date calculation instructions as event maintenance change information.

8. The method of claim 5, wherein the update information includes a list of holidays and associated dates for the identified rule set.

9. The method of claim 8, wherein the updating includes:
determining, under control of the server, whether a holiday identified in the list of holidays exists in the database;
responsive to a determination that the identified holiday does not exist in the database, adding, under control of the server, the identified holiday to the database and storing information for the holiday addition as event maintenance change information.

10. The method of claim 9, wherein the recalculating includes:
identifying, under control of the server, an earliest holiday date and a latest holiday date from the event maintenance change information;
determining, under control of the server, whether the one or more calculated event dates fall between the identified earliest holiday date and the identified latest holiday date; and
verifying, under control of the server, the one or more calculated event dates based on the holiday addition.

11. The method of claim 5, wherein the update information includes a list of deleted date calculation instructions in the identified rule set.

12. The method of claim 11, wherein the updating includes:
determining, under control of the server, whether a date calculation instruction identified in the list of deleted date calculation instructions exists in the database;
responsive to a determination that the identified date calculation instruction exists in the database, deleting, under control of the server, the date calculation instruction from the database; and
storing information on the deleted date calculation instruction as event maintenance change information.

13. A system for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the system comprising:
a database storing at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;
a server coupled to the database, the server being configured to:
receive an initial trigger date for an initial trigger legal event;
select one or more date calculation instructions from the database based on the initial trigger legal event;
calculate one or more event dates based on the initial trigger date and the retrieved date calculation instructions;
transmit the one or more calculated event dates to a user client; and
maintain a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;

a database update module coupled to the server, the database update module being configured to monitor a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions; and
a date maintenance module configured to automatically determine whether the one or more date calculation instructions identified in the record are identified in the changes table, and, for each one of the one or more date calculation instructions identified in the changes table, the date maintenance module being further configured to recalculate the associated event date based on the change to the corresponding date calculation instruction, and transmit the recalculated one or more event dates to the user client.

14. The system of claim 13, wherein the server is further configured to:
maintain a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and
update relationship information in the relationship table based on the changed date calculation instructions.

15. The system of claim 13 further comprising:
a change notification module configured to identify a customer affected by the recalculated one or more event dates, and transmit a notification to the customer of the recalculated one or more event dates.

16. The system of claim 13, wherein the server is further configured to:
calculate a fee for recalculating the one or more event dates; and
charge a user account based on the calculated fee.

17. The system of claim 13, wherein the database update module is further configured to receive update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, the database update module being further configured to identify the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the recalculation of the one or more event dates identified in the changes table.

18. The system of claim 17, wherein the database update module, in updating the date calculation instructions, is further configured to:
determine whether a date calculation instruction identified in the changes table exists in the database; and
responsive to a determination that the identified date calculation instruction does not exist in the database, add the identified date calculation instruction to the database.

19. The system of claim 18, wherein the database update module is further configured to:
determine whether the addition of the identified data calculation instruction is an event maintenance or non-event maintenance update; and
responsive to a determination that the addition of the identified date calculation instruction is an event maintenance update, store information on the added date calculation instructions as event maintenance change information.

20. The system of claim 17, wherein the update information includes a list of holidays and associated dates for the identified rule set.

21. The system of claim 20, wherein the database update module, in updating the date calculation instructions, is further configured to:
determine whether a holiday identified in the list of holidays exists in the database; and
responsive to a determination that the identified holiday does not exist in the database, add the identified holiday to the database and store information for the holiday addition as event maintenance change information.

22. The system of claim 21, wherein the date maintenance module, in recalculating the one or more event dates, is further configured to:
identify an earliest holiday date and a latest holiday date from the event maintenance change information;
determine whether the one or more calculated event dates fall between the identified earliest holiday date and the identified latest holiday date; and
verify the one or more calculated event dates based on the holiday addition.

23. The system of claim 17, wherein the update information includes a list of deleted date calculation instructions in the identified rule set.

24. The system of claim 23, wherein the database update module, in updating the date calculation instructions, is further configured to:
determine whether a date calculation instruction identified in the list of deleted date calculation instructions exists in the database;
responsive to a determination that the identified date calculation instruction exists in the database, delete the date calculation instruction from the database; and
store information on the deleted date calculation instruction as event maintenance change information.

25. A system for generating and transmitting a calendar of different legal events capable of occurring in the course of a legal proceeding, the system comprising:
a database maintaining at least one rule set including a plurality of date calculation instructions for calculating a plurality of different legal events;
means for receiving an initial trigger date for an initial trigger legal event; means for selecting one or more date calculation instructions from the database based on the initial trigger legal event;
means for calculating one or more event dates based on the initial trigger date and the retrieved date calculation instructions;
means for transmitting the one or more calculated event dates to a user client;
means for maintaining a transaction record of the one or more date calculation instructions used for generating the one or more event dates for the user client;
means for monitoring a changes table for changes in the plurality of date calculation instructions, the changes table identifying the changed date calculation instructions;
means for automatically determining whether the one or more date calculation instructions identified in the record are identified in the changes table;
for each one of the one or more date calculation instructions identified in the changes table, means for recalculating the associated event date based on the change to the corresponding date calculation instruction; and
means for transmitting the recalculated one or more event dates to the user client.

26. The system of claim 25 further comprising:
means for maintaining a relationship table storing relationship information for a plurality of the date calculation instructions, the relationship table indicating whether a particular date calculation instruction is related to another date calculation instruction; and
means for updating relationship information in the relationship table based on the changed date calculation instructions.

27. The system of claim 25 further comprising: means for identifying a customer affected by the recalculated one or more event dates; and
means for transmitting a notification to the customer of the recalculated one or more event dates.

28. The system of claim 25 further comprising:
means for receiving update information for updating the date calculation instructions identified in the changes table, the update information identifying a rule set affected by the update, and further identifying the update as an event maintenance update or a non-event maintenance update, the event maintenance update triggering the means for recalculating with respect to the one or more event dates identified in the changes table.