# US 8,788,931 B1 · Creating mapping rules from meta data for data transformation utilizing visual editing

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,788,931 B1
- Document ID: US8788931B1
- Status: Granted
- Kind: B1
- Application number: 09/722,526
- Filed: 2000-11-28
- Granted: 2014-07-22
- Earliest claimed: 2000-11-28
- Assignees: International Business Machines Corporation
- Applicants: Helen T. Chen; Thomas R. Maguire; John F. Schumacher
- Inventors: Helen T. Chen; Thomas R. Maguire; John F. Schumacher
- Web page: https://patentgrep.com/patent/US8788931B1

## CPC

- G06F 16/258: {Data format conversion from or to a database}
- G06F 17/00: Digital computing or data processing equipment or methods, specially adapted for specific functions (information retrieval, database structures or file system structures therefor G06F16/00)
- G06F 40/151: Transformation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A computer-implemented method for creating a transformation rule usable to transform a source document into a target document, comprising:
receiving, prior to the transformation rule being generated, a source data description of a single data field in the source document;
receiving, prior to the transformation rule being generated, a target data description of a single data field in the target document;
receiving a meta rule configured to create a transformation rule;
creating, by a computer hardware device, the transformation rule using the meta rule with the source data description and the target data description, wherein
each data field is to be populated by data having parameters, and
each respective data description characterizes the parameters of the data.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
selecting the meta rule from a plurality of meta rules using a mapping relation between the source data description and the target data description.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
testing the meta rule using the source data description and the target data description to identify missing parameter information.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
upon the missing parameter information being identified, prompting a user to supply the missing parameter information.

### Claim 5 (depends on 4)

The method of claim 4, wherein
the transformation rule is created using the tested meta rule and the missing parameter information supplied by the user.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving a second source target data description of a second single data field in the source document, wherein
the transformation rule is created using both the source target data description and the second source data description.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
simultaneously visually displaying the source data description and the target data description.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
displaying a source schema in tree form; and
displaying a target schema in tree form.

### Claim 9 (depends on 1)

The method of claim 1, wherein
the transformation rule is written in XSL (Extended Style Language).

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
transforming data in the source document into data formatted for the target document using the transformation rule.