PROJECT MANAGEMENT DATABASE AND METHOD OF MANAGING PROJECT RELATED INFORMATION

• US 20110231391A1
• Filed: 05/26/2011
• Published: 09/22/2011
• Est. Priority Date: 12/10/2001
• Status: Abandoned Application

• Current Assignee: Patrick Joseph Coyne
• Original Assignee: Patrick Joseph Coyne
• Inventors: Coyne, Patrick J.
• Application Number:
  US13/116,714
• Publication Number:
  US 20110231391A1
• Time in Patent Office: Days
• US Class Current: 707/722
• CPC Class Codes: G06F 16/2428 Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 50/18 Legal services

Abstract

A database, and method of using the same, are provided for managing professional services projects. Professional services practices typically employ distributed proprietary applications which complicate the ready transfer of data between and among applications. The database of the present invention is preferably built on an ODBC-compliant platform, such as Lotus Notes and operates in conjunction with an SQL database server and supplied to an ODBC-compliant database in Lotus Notes. The data is stored in portable format in the Lotus Notes database, providing an easily accessible data warehouse for the professional services practice.

Claims

1. A method for providing data to a user operating a software application for use in conjunction with a legal services project, the method comprising:

securing data from a first application on an automated basis, without human intervention;

securing legally-related data from a second application on an automated basis, without human intervention;

combining the secured data from the first application and the secured data from the second application into combined data in a substantially portable format of the software application;

generating a view of the combined data, wherein the view is associated with the software application; and

providing the view to the user via a web interface.

2. The method of claim 1, wherein the data from the first application is secured in response to receiving a request to access the data.

3. The method of claim 1, wherein the legally-related data from the second application is secured in response to receiving a request to access the legally-related data.

4. The method of claim 1, wherein the data from the first application is in a proprietary format of the first application.

5. The method of claim 1, wherein the data from the first application is in a format other than a proprietary format.

6. The method of claim 2, wherein the request is received from the user.

7. The method of claim 3, wherein the request is received from the user.

8. The method of claim 1, wherein the legally-related data from the second software application is in a format other than a proprietary format.

9. The method of claim 1, wherein the legally-related data from the second software application is in a proprietary format of the second application.

10. The method of claim 1, wherein the secured data from the first application and the secured data from the second application is combined automatically.

11. A non-transitory computer readable storage medium comprising instructions to cause a processor to perform the method comprising:

securing data from a first application on an automated basis, without human intervention;

securing legally-related data from a second application on an automated basis, without human intervention;

combining the secured data from the first application and the secured data from the second application into combined data in a substantially portable format of a software application, wherein the software application is for use in conjunction with a legal services project;

generating a view of the combined data, wherein the view is associated with the software application; and

providing the view to the user via a web interface.

12. The non-transitory computer readable storage medium of claim 11, wherein the data from the first application is secured in response to receiving a request to access the data.

13. The non-transitory computer readable storage medium of claim 11, wherein the legally-related data from the second application is secured in response to receiving a request to access the legally-related data.

14. The non-transitory computer readable storage medium of claim 11, wherein the data from the first application is in a proprietary format of the first application.

15. The non-transitory computer readable storage medium of claim 11, wherein the data from the first application is in a format other than a proprietary format.

16. The non-transitory computer readable storage medium of claim 12, wherein the request is received from the user.

17. The non-transitory computer readable storage medium of claim 13, wherein the request is received from the user.

18. The non-transitory computer readable storage medium of claim 11, wherein the legally-related data from the second software application is in a format other than a proprietary format.

19. The non-transitory computer readable storage medium of claim 11, wherein the legally-related data from the second software application is in a proprietary format of the second application.

20. The non-transitory computer readable storage medium of claim 11, wherein the secured data from the first application and the secured data from the second application is combined automatically.