Method, system, and program for managing information for an application program using a file management system

• US 6,934,721 B2
• Filed: 10/09/2001
• Issued: 08/23/2005
• Est. Priority Date: 10/09/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Schein, Phillip Mark
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US09/973,889
• Publication Number:
  US 20030069901A1
• Time in Patent Office: 1,414 Days
• Field of Search: 707/201, 707/8, 707/102, 707/200, 707/100, 707/103.R, 707/103.Y, 707/103.Z, 707/103
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Provided is a method, system, and program for managing information for an application program. The information includes an information class having a plurality of attributes values. The application program maintains multiple information class instances and wherein each instance includes at least one of the plurality of attribute values. User input is received indicating a plurality of information class instances and for each information class instance at least one attribute value. A main directory is generated for the application program. For each information class instance received from the user, a subdirectory is generated from the main directory for the information class instance and, for each received attribute value for the information class instance, one attribute file is generated providing the at least one attribute value. Each generated attribute file is stored in the subdirectory of the information class instance for which the attribute value is provided.

Claims

1. A method for managing information for an application program, wherein the information includes an information class having a plurality of attributes values, wherein the application program maintains multiple information class instances and wherein each instance includes at least one of the plurality of attribute values, comprising:

receiving user input indicating a plurality of information class instances and for each information class instance at least one attribute value;

generating a main directory for the application program;

for each information class instance received from the user, performing;

(i) generating a subdirectory from the main directory for the information class instance;

(ii) for each received attribute value for the information class instance, generating one attribute file providing the at least one attribute value; and

(iii) storing each generated attribute file in the subdirectory of the information class instance for which the attribute value is provided.

2. The method of claim 1, further comprising:

receiving a request for information on at least one requested attribute value for the information class instances; and

in response to the request for information, performing for each information class instance;

(i) accessing the subdirectory for the information class instance;

(ii) determining whether the accessed subdirectory includes each requested attribute value in one attribute file in the subdirectory; and

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

3. The method of claim 2, wherein the request for information further includes a criteria to apply to at least one of the requested attribute values, further comprising:

determining whether the requested attribute value in the attribute file to which the criteria applies satisfies the criteria, wherein the attribute values for one information class instance are not returned if the criteria for one attribute value of the information class instance is not satisfied.

4. The method of claim 2, wherein the subdirectory does not include one attribute value if there is no attribute file for the attribute value.

5. The method of claim 2, wherein returning the attribute value further comprises:

generating the requested attribute values into a form, wherein the form includes information on attribute values in attribute files in multiple subdirectories for information class instances, and wherein the form is returned.

6. The method of claim 5, wherein the form is implemented in a standard document format capable of being rendered by a viewer program used to render documents retrieved from over a network.

7. The method of claim 6, wherein the form is implemented as one of a HyperText Markup Language file or Extensible Markup Language (XML) file and the viewer program comprises an Internet browser program.

8. The method of claim 1, wherein at least one attribute file provides the attribute value by embedding the attribute value in a file name of the attribute file.

9. The method of claim 1, wherein at least one attribute file provides the attribute value by inserting the attribute value within the attribute file.

10. The method of claim 1, wherein at least one attribute value is comprised of multiple component values.

11. The method of claim 10, wherein each of the multiple component values is capable of being comprised of a plurality of multiple sub-component values.

12. The method of claim 1, wherein the information class comprises a first information class and wherein a second information class is a subclass of the first information class and has at least one attribute value, wherein there is one instance of the second information class for each instance of the first information class, further performing for each instance of the first information class:

generating a subdirectory for the second information class in the subdirectory generated for the first information class.

13. The method of claim 12, further comprising:

receiving user input for one attribute value for the second information class; and

generating one attribute file for the received user input in the subdirectory for the second information class, wherein the attribute file provides the received attribute value.

14. The method of claim 12, wherein the attribute value for the second information class for which the attribute file was generated includes at least one attribute value from the first information class.

15. The method of claim 1, further comprising:

receiving a request for statistical information on requested attribute values;

for each information class instance, performing;

(i) reading the attribute files for the requested attribute values to generate information summarizing the attribute values;

(ii) and returning the information summarizing the attribute values.

16. A method for managing information on a plurality of projects, wherein each project is capable of having a plurality of attribute values, comprising:

receiving user input on a plurality of projects and for each project at least one attribute value;

generating a main directory;

for each project for which user input is received, performing;

(i) generating a subdirectory from the main directory for the project; and

(ii) for each received attribute value, generating one attribute file providing the at least one attribute value;

receiving user input for at least one task for one project;

for each task for which user input is received, generating a task subdirectory in the subdirectory for the project including the task; and

for each received attribute value providing information on the task, generating at least one attribute file indicating each received attribute value.

17. The method of claim 16, wherein the attribute values for each project are capable of comprising one or more of the following project attribute values:

project comments, a project manager, projected completion date, project purpose, project start date, project actual completion date, project status, project holidays, and project interrupts.

18. The method of claim 17, wherein the project interrupts attribute value in the project interrupt file is comprised of multiple interrupt components, wherein each interrupt component includes subcomponents indicating a type of interrupt, date of interrupt, duration of interrupt, and interrupt comments.

19. The method of claim 16, further comprising:

receiving a request for information on at least one requested attribute value for the project; and

in response to the request for information, performing for each project subdirectory;

(i) accessing the project subdirectory;

(ii) determining whether the accessed project subdirectory includes each requested attribute value in one attribute file in the subdirectory;

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

20. The method of claim 19, wherein the request for information further includes a criteria to apply to the requested attribute values, wherein the criteria specifies a status of the project, further comprising:

determining whether the requested attribute value in the attribute file to which the criteria applies satisfies the criteria, wherein the attribute values for one project subdirectory are not returned if the criteria for one attribute value is not satisfied.

21. The method of claim 16, further comprising:

generating a calendar subdirectory for each project subdirectory, wherein the calendar subdirectory includes one calendar file for each day for which calendar information is provided for the project.

22. The method of claim 21, wherein the calendar information for one day and one project is entered by a user.

23. method of claim 21, wherein the calendar information entered into one calendar file for one project comprises one attribute value received from the user for the project that is also entered into one attribute file in the project subdirectory.

24. The method of claim 16, further comprising:

receiving user input for one task indicating a number of subtasks;

receiving user input indicating a percent completion for each subtask of the task; and

for each received percent completion for one subtask, generating at least one attribute file indicating the percent completion of the subtask.

25. A system for managing information for an application program, wherein the information includes an information class having a plurality of attributes values, wherein the application program maintains multiple information class instances and wherein each instance includes at least one of the plurality of attribute values, comprising:

means for receiving user input indicating a plurality of information class instances and for each information class instance at least one attribute value;

means for generating a main directory for the application program;

means for performing, for each information class instance received from the user;

(i) generating a subdirectory from the main directory for the information class instance;

(ii) for each received attribute value for the information class instance, generating one attribute file providing the at least one attribute value; and

(iii) storing each generated attribute file in the subdirectory of the information class instance for which the attribute value is provided.

26. The system of claim 25, further comprising:

means for receiving a request for information on at least one requested attribute value for the information class instances; and

means for performing, in response to the request for information, for each information class instance;

(i) accessing the subdirectory for the information class instance;

(ii) determining whether the accessed subdirectory includes each requested attribute value in one attribute file in the subdirectory; and

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

27. The system of claim 26, wherein the request for information further includes a criteria to apply to at least one of the requested attribute values, further comprising:

means for determining whether the requested attribute value in the attribute file to which the criteria applies satisfies the criteria, wherein the attribute values for one information class instance are not returned if the criteria for one attribute value of the information class instance is not satisfied.

28. The system of claim 26, wherein the means for returning the attribute value further performs:

generating the requested attribute values into a form, wherein the form includes information on attribute values in attribute files in multiple subdirectories for information class instances, and wherein the form is returned.

29. The system of claim 25, wherein the information class comprises a first information class and wherein a second information class is a subclass of the first information class and has at least one attribute value, wherein there is one instance of the second information class for each instance of the first information class, wherein the means for performing for each instance of the first information class further performs:

generating a subdirectory for the second information class in the subdirectory generated for the first information class.

30. A system for managing information on a plurality of projects, wherein each project is capable of having a plurality of attribute values, comprising:

means for receiving user input on a plurality of projects and for each project at least one attribute value;

means for generating a main directory;

means for performing for each project for which user input is received;

(i) generating a subdirectory from the main directory for the project; and

(ii) for each received attribute value, generating one attribute file providing the at least one attribute value;

means for receiving user input for at least one task for one project;

means for generating, for each task for which user input is received, a task subdirectory in the subdirectory for the project including the task; and

means for generating, for each received attribute value providing information on the task, at least one attribute file indicating each received attribute value.

31. The system of claim 30, wherein the attribute values for each project are capable of comprising one or more of the following project attribute values:

project comments, a project manager, projected completion date, project purpose, project start date, project actual completion date, project status, project holidays, and project interrupts.

32. The system of claim 31, wherein the project interrupts attribute value in the project interrupt file is comprised of multiple interrupt components, wherein each interrupt component includes subcomponents indicating a type of interrupt, date of interrupt, duration of interrupt, and interrupt comments.

33. The system of claim 30, further comprising:

means for receiving a request for information on at least one requested attribute value for the project; and

means for performing, for each project subdirectory, in response to the request for information;

(i) accessing the project subdirectory;

(ii) determining whether the accessed project subdirectory includes each requested attribute value in one attribute file in the subdirectory;

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

34. The system of claim 30, further comprising:

means for generating a calendar subdirectory for each project subdirectory, wherein the calendar subdirectory includes one calendar file for each day for which calendar information is provided for the project.

35. The system of claim 30, further comprising:

means for receiving user input for one task indicating a number of subtasks;

means for receiving user input indicating a percent completion for each subtask of the task; and

means for generating, for each received percent completion for one subtask, at least one attribute file indicating the percent completion of the subtask.

36. An article of manufacture including code for managing information for an application program, wherein the information includes an information class having a plurality of attributes values, wherein the application program maintains multiple information class instances and wherein each instance includes at least one of the plurality of attribute values, wherein the code causes operations to be performed comprising:

receiving user input indicating a plurality of information class instances and for each information class instance at least one attribute value;

generating a main directory for the application program;

for each information class instance received from the user, performing;

(i) generating a subdirectory from the main directory for the information class instance;

(ii) for each received attribute value for the information class instance, generating one attribute file providing the at least one attribute value; and

(iii) storing each generated attribute file in the subdirectory of the information class instance for which the attribute value is provided.

37. The article of manufacture of claim 36, further comprising:

receiving a request for information on at least one requested attribute value for the information class instances; and

in response to the request for information, performing for each information class instance;

(i) accessing the subdirectory for the information class instance;

(ii) determining whether the accessed subdirectory includes each requested attribute value in one attribute file in the subdirectory; and

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

38. The article of manufacture of claim 37, wherein the request for information further includes a criteria to apply to at least one of the requested attribute values, further comprising:

determining whether the requested attribute value in the attribute file to which the criteria applies satisfies the criteria, wherein the attribute values for one information class instance are not returned if the criteria for one attribute value of the information class instance is not satisfied.

39. The article of manufacture of claim 37, wherein the subdirectory does not include one attribute value if there is no attribute file for the attribute value.

40. The article of manufacture of claim 37, wherein returning the attribute value further comprises:

generating the requested attribute values into a form, wherein the form includes information on attribute values in attribute files in multiple subdirectories for information class instances, and wherein the form is returned.

41. The article of manufacture of claim 40, wherein the form is implemented in a standard document format capable of being rendered by a viewer program used to render documents retrieved from over a network.

42. The article of manufacture of claim 41, wherein the form is implemented as one of a HyperText Markup Language file or Extensible Markup Language (XML) file and the viewer program comprises an Internet browser program.

43. The article of manufacture of claim 36, wherein at least one attribute file provides the attribute value by embedding the attribute value in a file name of the attribute file.

44. The article of manufacture of claim 36, wherein at least one attribute file provides the attribute value by inserting the attribute value within the attribute file.

45. The article of manufacture of claim 36, wherein at least one attribute value is comprised of multiple component values.

46. The article of manufacture of claim 36, wherein each of the multiple component values is capable of being comprised of a plurality of multiple sub-component values.

47. The article of manufacture of claim 36, wherein the information class comprises a first information class and wherein a second information class is a subclass of the first information class and has at least one attribute value, wherein there is one instance of the second information class for each instance of the first information class, further performing for each instance of the first information class:

generating a subdirectory for the second information class in the subdirectory generated for the first information class.

48. The article of manufacture of claim 47, further comprising:

receiving user input for one attribute value for the second information class; and

generating one attribute file for the received user input in the subdirectory for the second information class, wherein the attribute file provides the received attribute value.

49. The article of manufacture of claim 47, wherein the attribute value for the second information class for which the attribute file was generated includes at least one attribute value from the first information class.

50. The article of manufacture of claim 36, further comprising:

receiving a request for statistical information on requested attribute values;

for each information class instance, performing;

(i) reading the attribute files for the requested attribute values to generate information summarizing the attribute values;

(ii) and returning the information summarizing the attribute values.

51. An article of manufacture including code for managing information on a plurality of projects, wherein each project is capable of having a plurality of attribute values, wherein the code causes operations to be performed comprising:

receiving user input on a plurality of projects and for each project at least one attribute value;

generating a main directory;

for each project for which user input is received, performing;

(i) generating a subdirectory from the main directory for the project; and

(ii) for each received attribute value, generating one attribute file providing the at least one attribute value;

receiving user input for at least one task for one project;

for each task for which user input is received, generating a task subdirectory in the subdirectory for the project including the task; and

for each received attribute value providing information on the task, generating at least one attribute file indicating each received attribute value.

52. The article of manufacture of claim 51, wherein the attribute values for each project are capable of comprising one or more of the following project attribute values:

project comments, a project manager, projected completion date, project purpose, project start date, project actual completion date, project status, project holidays, and project interrupts.

53. The article of manufacture of claim 52, wherein the project interrupts attribute value in the project interrupt file is comprised of multiple interrupt components, wherein each interrupt component includes subcomponents indicating a type of interrupt, date of interrupt, duration of interrupt, and interrupt comments.

54. The article of manufacture of claim 51, further comprising:

receiving a request for information on at least one requested attribute value for the project; and

in response to the request for information, performing for each project subdirectory;

(i) accessing the project subdirectory;

(ii) determining whether the accessed project subdirectory includes each requested attribute value in one attribute file in the subdirectory;

(iii) if the subdirectory includes each requested attribute value in one attribute file, then returning each requested attribute value from the attribute file.

55. The article of manufacture of claim 54, wherein the request for information further includes a criteria to apply to the requested attribute values, wherein the criteria specifies a status of the project, further comprising:

determining whether the requested attribute value in the attribute file to which the criteria applies satisfies the criteria, wherein the attribute values for one project subdirectory are not returned if the criteria for one attribute value is not satisfied.

56. The article of manufacture of claim 51, further comprising:

generating a calendar subdirectory for each project subdirectory, wherein the calendar subdirectory includes one calendar file for each day for which calendar information is provided for the project.

57. The article of manufacture of claim 56, wherein the calendar information for one day and one project is entered by a user.

58. The article of manufacture of claim 56, wherein the calendar information entered into one calendar file for one project comprises one attribute value received from the user for the project that is also entered into one attribute file in the project subdirectory.

59. The article of manufacture of claim 51, further comprising:

receiving user input for one task indicating a number of subtasks;

receiving user input indicating a percent completion for each subtask of the task; and

for each received percent completion for one subtask, generating at least one attribute file indicating the percent completion of the subtask.

60. A computer readable medium including information for an application program, wherein the information includes an information class having a plurality of attributes values, wherein the application program maintains multiple information class instances and wherein each instance includes at least one of the plurality of attribute values, comprising:

a main file directory for the application program;

one subdirectory from the main directory for each information class instance; and

one attribute file for each attribute value for each information class instance, wherein each attribute file provides one attribute value and is in the subdirectory of the information class instance for which the attribute value is provided.

61. The computer readable medium of claim 60, wherein at least one attribute file provides the attribute value by embedding the attribute value in a file name of the attribute file.

62. The computer readable medium of claim 60, wherein at least one attribute file provides the attribute value by inserting the attribute value within the attribute file.

63. The computer readable medium of claim 60, wherein the information class comprises a first information class and wherein a second information class is a subclass of the first information class and has at least one attribute value, wherein there is one instance of the second information class for each instance of the first information class, further comprising:

a subdirectory for the second information class for each first information class in the subdirectory generated for the first information class.

64. A computer readable medium including information on a plurality of projects, wherein each project is capable of having a plurality of attribute values, comprising:

a main directory;

a subdirectory from the main directory for the project;

one attribute file for each attribute value providing the at least one attribute value;

a task subdirectory in the subdirectory for the project including each task for which user input is received; and

one attribute file indicating a received attribute value for each received attribute value providing information on the task.

65. The computer readable medium of claim 64, wherein the attribute values for each project are capable of comprising one or more of the following project attribute values:

project comments, a project manager, projected completion date, project purpose, project start date, project actual completion date, project status, project holidays, and project interrupts.

66. The computer readable medium of claim 64, further comprising:

a calendar subdirectory for each project subdirectory, wherein the calendar subdirectory includes one calendar file for each day for which calendar information is provided for the project.