Autopropagation of business intelligence metadata

• US 20090083306A1
• Filed: 09/26/2007
• Published: 03/26/2009
• Est. Priority Date: 09/26/2007
• Status: Active Grant

• Current Assignee: Pentaho Incorporated (Hitachi, Ltd.)
• Original Assignee: LucidEra, Inc.
• Inventors: Sichi, John V., Kadam, Chetan R., Rudin, Ken M., Tran, Quoc T., Agashe, Vishwas S., Chow, Benny T.
• Granted Patent: US 7,941,398 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A method of processing data is disclosed. A data field change is detected in a received data entry received by a business intelligence application. A shared metadata entry shared by two or more business intelligence application stack elements is processed to derive for each of at least a subset of said two or more business intelligence application stack elements a corresponding set of element specific metadata needed by that element to use a data value associated with the data field change.

Claims

1. A method of processing data, comprising:

detecting a data field change in a received data entry received by a business intelligence application; and

processing a shared metadata entry shared by two or more business intelligence application stack elements to derive for each of at least a subset of said two or more business intelligence application stack elements a corresponding set of element specific metadata needed by that element to use a data value associated with the data field change.

2. A method as recited in claim 1, wherein the business intelligence application stack elements include one or more of the following:

one or more source data agents, an ETL element, a Data Warehouse element, an OLAP element, a data mining element, and a UI element.

3. A method as recited in claim 2, wherein source data agents connect to accounting is sources, CRM sources, SFA sources or ERP sources.

4. A method as recited in claim 1, wherein detecting a data field change comprises detecting a dynamic data field.

5. A method as recited in claim 4, further comprising receiving a binding data associated with the dynamic data field, wherein the binding data indicates a manner in which data associated with the dynamic data field is to be used.

6. A method as recited in claim 1, wherein the corresponding set of element specific metadata is represented by defining views and insert/update statements for data movement in an ETL element.

7. A method as recited in claim 1, wherein the corresponding set of element specific metadata is represented by creating columns and tables in a Data Warehouse element.

8. A method as recited in claim 1, wherein the corresponding set of element specific metadata is represented by categorizing, summarizing and aggregating data in an OLAP element.

9. A method as recited in claim 1, wherein the corresponding set of element specific metadata is represented by building reports from a zero footprint web interface in a UI element.

10. A method as recited in claim 1, further comprising adding, modifying or deleting a business intelligence application stack element from the said two or more business intelligence application stack elements.

11. A method as recited in claim 1, wherein at least one corresponding set of element specific metadata comprises a set of element specific runtime object creation commands.

12. A method as recited in claim 11, where the set of element specific runtime object creation commands include one or more of the following:

database commands, table schema commands, XML commands, or OLAP metadata commands.

13. A system of processing data, including:

a processor; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to;

detect a data field change in a received data entry by a business intelligence application; and

process a shared metadata entry shared by two or more business intelligence application stack elements to derive for each of at least a subset of said two or more business intelligence application stack elements a corresponding set of element specific metadata needed by that element to use a data value associated with the data field change.

14. A system as recited in claim 13, wherein the business intelligence application stack elements include one or more of the following:

one or more source data agents, an ETL element, a Data Warehouse element, an OLAP element, and a UI element.

15. A system as recited in claim 14, wherein source data agents connect to accounting sources, CRM sources, SFA sources or ERP sources.

16. A system as recited in claim 13, wherein detecting a data field change comprises detecting a dynamic data field.

17. A system as recited in claim 16, wherein the processor is further configured to receive a binding data associated with the dynamic data field, wherein the binding data indicates a manner in which data associated with the dynamic data field is to be used.

18. A computer program product for processing data, the computer program product being embodied in a computer readable medium and comprising computer instructions for:

detecting a data field change in a received data entry by a business intelligence application; and

processing a shared metadata entry shared by two or more business intelligence application stack elements to derive for each of at least a subset of said two or more business intelligence application stack elements a corresponding set of element specific metadata needed by that element to use a data value associated with the data field change.

19. A computer program product as recited in claim 18, wherein the business intelligence application stack elements include one or more of the following:

one or more source data agents, an ETL element, a Data Warehouse element, an OLAP element, and a UI element.

20. A computer program product as recited in claim 19, wherein source data agents connect to accounting sources, CRM sources, SFA sources or ERP sources.

21. A computer program product as recited in claim 18, wherein detecting a data field change comprises detecting a dynamic data field.

22. A computer program product as recited in claim 21, the computer program product further comprising computer instructions for receiving a binding data associated with the dynamic data field, wherein the binding data indicates a manner in which data associated with the dynamic data field is to be used.