Customizable metadata merging framework
First Claim
Patent Images
1. A computer implemented method to facilitate merging different versions of a database object, comprising:
- receiving metadata associated with a first version of the database object and a second version of the database object, wherein the metadata provides a data structure that describes the database objects and is distinct from the database objects themselves;
comparing metadata associated with the first version of the database object with metadata associated with the second version of the database object to create a difference report;
creating an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object, wherein creating the action plan from the difference report involves allowing a user to select which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and
using the action plan to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object; and
wherein the first version of the database object and the second version of the database object include other objects that have been captured using Unified Modeling Language (UML) and stored in the database during design time.
1 Assignment
0 Petitions
Accused Products
Abstract
One embodiment of the present invention provides a system that facilitates merging different versions of a database object. During operation, the system receives metadata associated with a first version of a database object and a second version of the database object. The system then compares metadata associated with the first version with metadata associated with the second version to create a difference report. Next, the system uses the different report to create an action plan that specifies how to merge the metadata associated with the first and second versions of the metadata object.
-
Citations
21 Claims
-
1. A computer implemented method to facilitate merging different versions of a database object, comprising:
-
receiving metadata associated with a first version of the database object and a second version of the database object, wherein the metadata provides a data structure that describes the database objects and is distinct from the database objects themselves; comparing metadata associated with the first version of the database object with metadata associated with the second version of the database object to create a difference report; creating an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object, wherein creating the action plan from the difference report involves allowing a user to select which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and using the action plan to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object; and wherein the first version of the database object and the second version of the database object include other objects that have been captured using Unified Modeling Language (UML) and stored in the database during design time. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method to facilitate merging different versions of a database object, the method comprising:
-
receiving metadata associated with a first version of the database object and a second version of the database object, wherein the metadata provides a data structure that describes the database objects and is distinct from the database objects themselves; comparing metadata associated with the first version of the database object with metadata associated with the second version of the database object to create a difference report; creating an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object, wherein creating the action plan from the difference report involves allowing a user to select which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and using the action plan to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object; and wherein the first version of the database object and the second version of the database object include other objects that have been captured using UML and stored in the database during design time. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. An apparatus to facilitate merging different versions of a database object, comprising:
- a processor;
a memory;a receiving mechanism configured to receive metadata associated with a first version of the database object and a second version of the database object, wherein the metadata provides a data structure that describes the database objects and is distinct from the database objects themselves; a comparing mechanism configured to compare metadata associated with the first version of the database object with metadata associated with the second version of the database object to create a difference report; a creating mechanism configured to create an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object, wherein creating the action plan from the difference report involves allowing a user to select which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and a merging mechanism configured to use the action plan to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object; and wherein the first version of the database object and the second version of the database object include other objects that have been captured using UML and stored in the database during design time. - View Dependent Claims (16, 17, 18, 19, 20, 21)
- a processor;
Specification