International Business Machines Corporation

Helen T Chen

Thomas R Maguire

John F Schumacher

A visual editor creates the meta rules for transforming mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interface (GUI). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g. XSL and sent to a standard transformation engine, e.g. XSLT which accepts an input data file and using the transformation rules generates a transformed output data file The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file. A locking mechanism in the template is selected to lock the context to the template or portion of the rule definition selected at the time the lock is clicked. The new transformation/rule is saved into the transformation rule file. An editor-mapping engine generates a notification of the creation of a new transformation-mapping rule; updates the meta data rules file; and provide the updated rule file to the transformation engine. Input data to the transformation engine is processed using the updated rule file and the transformed data is provided as an output.

Creating mapping rules from meta data for data transformation utilizing visual editing

A visual editor creates the meta rules for transforming or mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interfaces (GUIs). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g., XSL, and sent to a standard transformation engine, e.g., XSLT, which accepts an input data file and using the transformation rules generates a transformed output data file. The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file. A locking mechanism in the template is selected to lock the context to the template or portion of the rule definition selected at the time the lock is clicked. The new transformation/rule is saved into the transformation rule file. An editor-mapping engine generates a notification of the creation of a new transformation-mapping rule; updates the meta data rules file; and provides the updated rule file to the transformation engine. Input data to the transformation engine is processed using the updated rule file and the transformed data is provided as an output.

Growing community of inventors

Oakland Gardens, NY, United States of America

Helen T Chen