Method and system for managing metadata

• US 20040111728A1
• Filed: 12/05/2002
• Published: 06/10/2004
• Est. Priority Date: 12/05/2002
• Status: Abandoned Application

• Current Assignee: Comprehensive Software Systems Incorporated
• Original Assignee: Comprehensive Software Systems Incorporated
• Inventors: Schwalm, Brian E.
• Application Number:
  US10/313,655
• Publication Number:
  US 20040111728A1
• Time in Patent Office: Days
• US Class Current: 719/316
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/328 in the presentation layer [OSI layer 6]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and system for managing metadata for use by client application programs is disclosed. The client application programs are constructed with various software modules responsible for displaying graphical user interface components to users through a display module, e.g., computer monitor. The graphical user interface components are built using program data and metadata. Program data is data that is entered by a user or generated by a client application program. Metadata is data that describes the program data. The present invention manages metadata using a tri-layer system, which includes a presentation layer, a middle-tier layer and a data layer. The presentation layer includes the client application program, and therefore various software modules used to execute the client application program. The presentation layer also includes an ObjectStore component for managing retrieval and manipulation of metadata for the software modules. Software modules send requests for a metadata object to the ObjectStore component. The ObjectStore component works with the middle-tier layer to extract the requested metadata object from the data layer. The presentation layer, the middle-tier layer and the data layer may reside on a single computer or on multiple computers, such as the case in a client-server environment.

Claims

1. A system for managing metadata for use by a client application program, the system comprising:

a presentation layer managing retrieval of a metadata object in response to a request for the metadata object from a software module of the client application program; and

a data layer storing the metadata object and accessible to the presentation layer such that the presentation layer may retrieve the metadata object from the data layer in response to the request from the software module.

2. A system as defined in claim 1, further comprising:

a middle-tier layer connected between the presentation layer and the data layer, retrieving the metadata object from the data layer and providing the metadata object to the presentation layer.

3. A system as defined in claim 2, wherein the presentation layer, the middle-tier layer and the data layer reside on one computing system.

4. A system as defined in claim 2, wherein the presentation layer resides on a first computing system and the middle-tier layer resides on a second computing system, wherein the presentation layer and the middle-tier layer communicate over a network connection.

5. A system as defined in claim 4, wherein the data layer resides on the second computing system.

6. A system as defined in claim 4, wherein the data layer resides on a third computing system, the middle-tier layer accessing the data layer over a communication link.

7. A system as defined in claim 2, wherein the presentation layer comprises:

an Object management component receiving the request from the software module, managing retrieval of the metadata object and providing the metadata object to the software module.

8. A system as defined in claim 7, wherein the Object management component directs the middle-tier layer to retrieve the metadata object in response to the received request from the software module.

9. A system as defined in claim 8, wherein the presentation layer comprises a cache memory storing the metadata object retrieved by the middle-tier layer.

10. A system as defined in claim 9, wherein the Object management component retrieves the metadata object from the cache memory in response to receiving a second request for the metadata object.

11. A system as defined in claim 7, wherein the data layer stores the metadata object as a standard definition table having one or more row objects, wherein each row object comprises a type code and a corresponding metadata description entry.

12. A system as defined in claim 7, wherein the Object management component constructs the metadata object using one or more row objects of one or more non-standard definition tables stored on the data layer responsive to the request by the software module.

13. A system as defined in claim 12, wherein the Object management component recognizes that the software module has requested retrieval of a custom metadata object based on a custom query being specified in the request, and in response, directs the middle-tier layer to execute the custom query to extract the one or more row objects from the one or more non-standard definition tables stored on the data layer.

14. A system as defined in claim 7, wherein the metadata object is a standard definition table having a plurality of row objects and a predetermined set of metadata fields, the Object management component retrieving the standard definition table and filtering the standard definition table by deleting one or more row objects from the standard definition table such that the standard definition table provided to the software module includes a specified set of row objects.

15. A system as defined in claim 7, wherein the Object management component populates a GUI component with metadata contained in the metadata object specified in the request by the software module.

16. A system as defined in claim 15, wherein the request by the software module comprises the GUI component.

17. A method for managing metadata for use by a client application, the method comprising:

receiving a request for a metadata object from a software module of the client application program;

retrieving the metadata object from a database in response to the request from the software module; and

providing the metadata object to the software module.

18. A method as defined in claim 17, wherein the retrieving act comprises:

communicating an identification of the metadata object to a server computer over a network connection, wherein the server computer accesses the database and extracts the metadata object.

19. A method as defined in claim 18, wherein the retrieving act further comprises:

receiving the metadata object from the server computer over the network connection.

20. A method as defined in claim 17, further comprising:

storing the metadata object retrieved from the database to a cache memory.

21. A method as defined in claim 20, wherein the retrieving act further comprises:

referencing the cache memory to determine whether the metadata object is stored therein; and

retrieving the metadata object from the cache memory if the metadata object is stored therein.

22. A method as defined in claim 17, wherein the metadata object is stored in the database as a standard definition table having row objects divided into one or more metadata fields, wherein the one or more metadata fields comprise a type code and a corresponding metadata description entry, the method comprising:

recognizing that the software module has requested retrieval of a standard metadata object based on detection of a definition table identifier being specified in the request.

23. A method as defined in claim 22, wherein the retrieving act comprises:

sending the definition table identifier to a server computer for accessing the standard definition table from the database; and

receiving the standard definition table from the server computer.

24. A method as defined in claim 23, further comprising:

filtering the standard definition table by deleting one or more row objects from the standard definition table such that the standard definition table provided to the software module includes a specified set of row objects.

25. A method as defined in claim 17, wherein the database stores non-standard definition tables having one or more metadata fields comprising a type code and a corresponding metadata description entry, the method further comprising:

recognizing that the software module has requested retrieval of a custom metadata object based on detection of a custom query identifier being specified in the request.

26. A method as defined in claim 25, further comprising:

constructing the custom metadata object using one or more row objects extracted from one or more non-standard definition tables, wherein the providing act comprises providing the custom metadata object to the software module requesting the custom metadata object.

27. A method as defined in claim 26, wherein the retrieving act further comprises:

communicating the custom query identifier to a server computer over a network connection, wherein the server computer extracts a custom query from the database based on the custom query identifier and executes the custom query to extract the one or more row objects from the one or more non-standard definition tables.

28. A method as defined in claim 27, wherein the retrieving act further comprises:

receiving the one or more row objects from the server computer over the network connection.

29. A method as defined in claim 17, further comprising:

populating a graphical user interface component with metadata contained in the retrieved metadata object, wherein the graphical user interface component is included within the request from the software module.

30. A method as defined in claim 29, wherein the providing act comprises:

providing the populated graphical user interface component to the software module.

31. A method for managing metadata for use by a client application program, the method comprising:

receiving a request for metadata over a communication link to an object management component managing retrieval of metadata for a plurality of software modules of the client application program;

executing a query for extracting metadata from a database;

receiving metadata specified in the request from the database; and

providing the received metadata to the object management component over the communication link.

32. A method as defined in claim 31, wherein the request specifies a custom query for extracting one or more metadata row objects from one or more definition tables stored in the database, the method further comprising:

retrieving the custom query from the database, wherein the executing act comprises executing the custom query to extract and receive the one or more metadata row objects from the one or more definition tables, wherein the one or more metadata row objects comprise a type code entry and a metadata description entry.

33. A method as defined in claim 32, wherein the providing act comprises:

associating the type code entries and metadata description entries of the one or more metadata row objects to identifiers recognizable by the object management component such that the type code entries and metadata description entries are manipulable by the object management component to construct a custom definition table formatted for recognition by the software modules of the client application program.

34. A method as defined in claim 31, wherein the request specifies a standard definition table stored in the database and having one or more row objects, the executing act comprising:

executing a standard query to extract and receive the standard definition table.

35. A method as defined in claim 34, wherein the request specifies a filter defining a certain set of row objects requested by the software module, the method further comprising:

discarding row objects of the standard definition table that are not included within the certain set of row objects.

36. A computer program storage medium readable by a computing system and encoding a computer program for managing metadata for use by a client application, the computer process comprising:

receiving a request for a metadata object from a software module of the client application program;

retrieving the metadata object from a database in response to the request from the software module; and

providing the metadata object to the software module.

37. A computer program storage medium as defined in claim 36, wherein the retrieving act comprises:

communicating an identification of the metadata object to a server computer over a network connection, wherein the server computer accesses the database and extracts the metadata object.

38. A computer program storage medium as defined in claim 37, wherein the retrieving act further comprises:

receiving the metadata object from the server computer over the network connection.

39. A computer program storage medium as defined in claim 36, the computer process further comprising:

storing the metadata object retrieved from the database to a cache memory.

40. A computer program storage medium as defined in claim 39, wherein the retrieving act further comprises:

referencing the cache memory to determine whether the metadata object is stored therein; and

retrieving the metadata object from the cache memory if the metadata object is stored therein.

41. A computer program storage medium as defined in claim 36, wherein the metadata object is stored in the database as a standard definition table having row objects divided into one or more metadata fields, wherein the one or more metadata fields comprise a type code and a corresponding metadata description entry, the method comprising:

recognizing that the software module has requested retrieval of a standard metadata object based on detection of a definition table identifier being specified in the request.

42. A computer program storage medium as defined in claim 41, wherein the retrieving act comprises:

sending the definition table identifier to a server computer for accessing the standard definition table from the database; and

receiving the standard definition table from the server computer.

43. A computer program storage medium as defined in claim 42, the computer process further comprising:

filtering the standard definition table by deleting one or more row objects from the standard definition table such that the standard definition table provided to the software module includes a specified set of row objects.

44. A computer program storage medium as defined in claim 36, wherein the database stores non-standard definition tables having one or more metadata fields comprising a type code and a corresponding metadata description entry, the method further comprising:

recognizing that the software module has requested retrieval of a custom metadata object based on detection of a custom query identifier being specified in the request.

45. A computer program storage medium as defined in claim 44, the computer process further comprising:

constructing the custom metadata object using one or more row objects extracted from one or more non-standard definition tables, wherein the providing act comprises providing the custom metadata object to the software module requesting the custom metadata object.

46. A computer program storage medium as defined in claim 45, wherein the retrieving act further comprises:

communicating the custom query identifier to a server computer over a network connection, wherein the server computer extracts a custom query from the database based on the custom query identifier and executes the custom query to extract the one or more row objects from the one or more non-standard definition tables.

47. A computer program storage medium as defined in claim 46, wherein the retrieving act further comprises:

receiving the one or more row objects from the server computer over the network connection.

48. A computer program storage medium as defined in claim 36, the computer process further comprising:

populating a graphical user interface component with metadata contained in the retrieved metadata object, wherein the graphical user interface component is included within the request from the software module.

49. A computer program storage medium as defined in claim 48, wherein the providing act comprises:

providing the populated graphical user interface component to the software module.