CA2318302A1 - Methods and transformations for transforming metadata model - Google Patents

Methods and transformations for transforming metadata model Download PDF

Info

Publication number
CA2318302A1
CA2318302A1 CA002318302A CA2318302A CA2318302A1 CA 2318302 A1 CA2318302 A1 CA 2318302A1 CA 002318302 A CA002318302 A CA 002318302A CA 2318302 A CA2318302 A CA 2318302A CA 2318302 A1 CA2318302 A1 CA 2318302A1
Authority
CA
Canada
Prior art keywords
model
data access
business
objects
metadata
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CA002318302A
Other languages
French (fr)
Other versions
CA2318302C (en
Inventor
Glenn D. Rasmussen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CA002281331A external-priority patent/CA2281331A1/en
Application filed by Individual filed Critical Individual
Priority to CA002318302A priority Critical patent/CA2318302C/en
Publication of CA2318302A1 publication Critical patent/CA2318302A1/en
Application granted granted Critical
Publication of CA2318302C publication Critical patent/CA2318302C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/289Object oriented databases

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Transformations are provided for transforming a metadata model that contains model objects. The metadata model has a multiple layers including a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model obj ects having a higher abstraction level. The transformations transform the model objects from the lower layer to the higher layer.

Claims (66)

1. A metadata model transformer for transforming a metadata model, the metadata model having a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model objects having a higher abstraction level, the transformer comprising:
a lower-to-higher transformation having:
means for obtaining information of a lower abstraction model object from the lower layer;
means for abstracting the information by adding business intelligence; and means for creating in the higher layer a higher abstraction model object corresponding to the lower abstraction model object.
2. A metadata model transformer as claimed in claim 1 further comprising:
a lower layer transformation having:
means for obtaining information of a lower abstraction model object from the lower layer;
means for modifying the obtained information; and means for transforming the lower abstraction model object based on the modified information.
3. A metadata model transformer as claimed in claim 1 further comprising:
a lower layer transformation having:
means for obtaining information of a lower abstraction model objects from the lower layer;
means for determining a specific feature included in the obtained information; and means for creating a new lower abstraction model object based on the specific feature.
4. A metadata model transformer as claimed in claim 1 further comprising:
a lower layer transformation having:
means for obtaining relationship information between multiple lower abstraction model objects from the lower layer; and means for creating a new lower abstraction model object based on the relationship information.
5. A metadata model transformer as claimed in claim 1 further comprising:
a higher layer transformation having:
means for obtaining information of a higher abstraction model object from the higher layer;
means for modifying the obtained information; and means for transforming the higher abstraction model object based on the modified information.
6. A metadata model transformer as claimed in claim 1 further comprising:
a higher layer transformation having:
means for obtaining information of a higher abstraction model ob jects from the higher layer;
means for determining a specific feature included in the obtained information; and means for creating a new higher abstraction model object based on the specific feature.
7. A metadata model transformer as claimed in claim 1 further comprising:
a higher layer transformation having:
means for obtaining relationship information between multiple higher abstraction model objects from the higher layer; and means for creating a new higher abstraction model object based on the relationship information.
8. A metadata model transformer as claimed in claim 1 further comprising:
a higher layer transformation having:
means for selecting a subset of the higher abstraction model objects from the higher layer; and means for creating a new higher abstraction model object based on the selected subset of the higher abstraction model objects.
9. A metadata model transformer for transforming a metadata model that represent one or more data sources having physical data, the metadata model having a data access layer containing data access model objects, a business layer containing business model objects, and a package layer containing package model objects, the transformation comprising:
one or more data access model transformations for refining description of the physical data in the data source expressed by the data access model objects;
one or more data access to business model transformations for constructing business model objects based on the data access model objects;
one or more business model transformations for refining the business rules expressed by the business model objects; and one or more business to package model transformations for constructing package model objects based on the business model objects.
10. A metadata model transformer as claimed in claim 9, wherein the data access model transformations refines the description by adding new data acces s model objects to data access model objects which are constructed via import from the data sources or one or more metadata sources.
11. A metadata model transformer as claimed in claim 9, wherein the business model transformations refines the business rules by changing the business model objects.
12. A metadata model transformer as claimed in claim 11, wherein the business model objects include business model objects which are constructed via import from one or more metadata sources.
13. A metadata model transformer as claimed in claim 9 further comprising:
one or more package model transformations for constructing a new package layer based on the package model objects in the model.
14. A metadata model transformer as claimed in claim 13, wherein the package model objects include package model objects which are constructed via import from one or more metadata sources.
15. A metadata model transformer as claimed in claim 9 further comprising:
a name mutation transformation for changing names of objects in the model based on user defined rules.
16. A metadata model transformer as claimed in claim 9, wherein the data access model transformations include a transformation which creates a new data access model object based on the data access model objects contained in the data access layer.
17. A metadata model transformer as claimed in claim 16, wherein the data sources contain tables having columns and indexes;
the data access model objects include data access tables, data access columns and data access indexes which respectively describe information about the tables, columns and indexes in the data sources; and the data access model transformations include a data access join constructing transformation for constructing a data access join between data access tables based on the data access indexes.
18. A metadata model transformer as claimed in claim 16, wherein the data sources contain tables having columns and indexes;
the data access model objects include data access tables, data access columns and data access indexes which respectively describe information about the tables, columns and indexes in the data sources; and the data access model transformations include a data access key constructing transformation for creating a data access key for a data access table based on the data access indexes.
19. A metadata model transformer as claimed in claim 16, wherein the data sources contain at least one of tables having columns and indexes, views having columns or files having columns or fields;
the data access model objects include at least one of data access tables, data access views, data access files, data access columns and data access indexes which respectively describe information about the tables, columns of the tables, indexes of the tables, the views, the columns of the views, the files, and the columns or fields of the files in the data sources; and the data access model transformations include a table extract constructing transformation for constructing a table extract based on the data access tables, the data access views and the data access files.
20. A metadata model transformer as claimed in claim 16, wherein the data access model objects include one or more logical cube, each of which defines a multidimensional space represented in a number of physical storage formats;
and the data access model transformations include a data access cube constructing transformation for constructing data access cubes to instantiate the multidimensional space defined by each logical cube.
21. A metadata model transformer as claimed in claim 9, wherein the data access to business model transformations include a basic business model constructing transformation which obtains information about a data access model object in the data access layer, and create a business model object corresponding to the data access model object.
22. A metadata model transformer as claimed in claim 21, wherein the business model objects include entities that exist as an implementation artifact of a many to many relationship, and many to many business joins associated with the entities; and the business model transformations include a many to many join relationship fixing transformation for locating the entities, and replacing the associated many to many business joins with a single business join.
23. A metadata model transformer as claimed in claim 21, wherein the business model objects include entities that are related via a 1:1 join relationship; and the business model transformations include an entity coalescing transformation for locating the entities that are related via a 1:1 join relationship, and coalescing the located entities into a single entity.
24. A metadata model transformer as claimed in claim 21, the business model objects include one or more redundant joins that express the transitivity of two or more other join relationships in the business layer;
and the business model transformations include a redundant join relationship eliminating transformation for locating the redundant joins, and eliminating the redundant joins from the business layer.
25. A metadata model transformer as claimed in claim 21, wherein the business model transformations include a subclass relationship introducing transformation for introducing a new entity with a subclass relationship into the business layer.
26. A metadata model transformer as claimed in claim 21, wherein the business model objects include an entity acting as a lookup table with respect to the other entity, and a business join between the entities, the business join is an associate type; and the business model transformations include an entity referencing transformation for locating the entity acting as a lookup table, and changing the business join which is an association type to a business join which is a reference type.
27. A metadata model transformer as claimed in claim 21, wherein the business model transformations include an attribute usage determining transformation for determines the usage of an attribute based on how it is used by other business model objects.
28. A metadata model transformer as claimed in claim 21, wherein the business model transformations include a date usage identifying transformation for examining attributes to determine where dates are used in the attributes.
29. A metadata model transformer as claimed in claim 9, wherein the business to package model transformations include a basic package model constructing transformation for constructing a package layer by forming a package with package model objects which corresponds to a subset of the business model objects.
30. A metadata model transformer as claimed in claim 13, wherein the package model transformations include a special package construction transformation for constructing a specific package which is usable by a specific client application from a generic package.
31. A metadata model transformer as claimed in claim 9 further comprising one or more multidimensional model transformations for a multidimensional model.
32. A metadata model transformer as claimed in claim 31, wherein the multidimensional model transformations include a measure identifying and measure dimension constructing transformation for analyzing the structure of each data source to identify entities that contain measure candidates and identifying a reasonable set of measures.
33. A metadata model transformer as claimed in claim 31, wherein the multidimensional model transformations include a category dimension and level constructing transformation for analyzing each data source, and constructing dimensions and levels for the source model.
34. A metadata model transformer as claimed in claim 32, wherein the multidimensional model transformations include a logical cube constructing transformation for constructing a set of logical cubes based on the dimensions in a corresponding data source.
35. A method for transforming a metadata model for containing model objects, the metadata model having multiple layers including a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model objects having a higher abstraction level, the method comprising steps of:
obtaining information of a lower abstraction model object from the lower layer;
abstracting the information by adding business intelligence; and creating in the higher layer a higher abstraction model object corresponding to the lower abstraction model object.
36. A method as claimed in claim 35 further comprising steps of:
obtaining information of a model object from one of the multiple layers;
modifying the obtained information;
transforming the model object based on the modified information; and returning the transformed model object into the one of the multiple layers.
37. A method as claimed in claim 35 further comprising steps of:
obtaining information of a model object from one of the multiple layers;
determining a specific feature included in the obtained information;
creating a new model object based on the specific feature; and adding the new model object into the one of the multiple layers.
38. A method as claimed in claim 35 further comprising steps of:
obtaining relationship information between the model objects in one of the multiple layers;

creating a new model object based on the relationship information; and adding the new model object into the one of the multiple layers.
39. A method as claimed in claim 35 further comprising steps of:
selecting a subset of the model objects from the higher layer;
creating a new higher abstraction model object based on the selected subset of the higher abstraction model objects; and adding the new higher abstraction model object into the higher layer.
40. A method for transforming a metadata model that represent one or more data sources having physical data, the metadata model having a data access layer containing data access model objects, a business layer containing business m odel objects, and a package layer containing package model objects, the method comprising steps of:
refining description of physical data in the data sources expressed by the data access objects;
constructing business model objects based on the data access objects;
refining business rules expressed by the business model objects; and constructing package model objects based on the business model objects.
41. A method as claimed in claim 40, wherein the step of refining the description comprises a step of adding new data access model objects to data access model objects which are constructed via import from the data sources or tine or more metadata sources.
42. A method as claimed in claim 40, wherein the step of refining the business rules comprises a step of changing the business model objects.
43. A method as claimed in claim 40, wherein the step of refining the business rules uses the business model objects that include business model objects which are constructed via import from one or more metadata sources.
44. A method as claimed in claim 40, further comprising a step of constructing a new package layer based on the package model objects in the model.
45. A method as claimed in claim 44, wherein the step of constructing a new package layer uses the package model objects that include package model objects which are constructed via import from one or more metadata sources..
46. A method as claimed in claim 40 further comprising a step of changing names of objects in the model based on user defined rules.
47. A method as claimed in claim 40, wherein the step of transforming the data access model objects comprises a step of creating a new data access model object based on the data access model objects contained in the data access layer.
48. A method as claimed in claim 47, wherein the data sources contain tables having columns and indexes, and the data access model objects include data access tables, data access columns and data access indexes which respectively describe information about the tables, columns and indexes in the data sources; and the step of transforming the data access model objects comprises a step of constructing a data access join between data access tables based on the data access indexes.
49. A method as claimed in claim 47, wherein the data sources contain tables having columns and indexes, and the data access model objects include data access tables, data access columns and data access indexes which respectively describe information about the tables, columns and indexes in the data sources; and the step of transforming the data access model objects comprises a step of creating a data access key for a data access table based on the data access indexes.
50. A method as claimed in claim 47, wherein the data sources contain at least one of tables having columns and indexes, views having columns or files having columns or fields, and the data access model objects include at least one of data access tables, data access views, data access files, data access columns and data access indexes which respectively describe information about the tables, columns of the tables, indexes of the tables, the views, the columns of the views, the files, and the columns or fields of the files in the data sources; and the step of transforming the data access model objects comprises a step of constructing a table extract based on the data access tables, the data access views and the data access files.
51. A method as claimed in claim 47, wherein the data access model objects include data access one or more logical cube, each of which defines a multidimensional space represented in a number of physical storage formats; and the step of transforming the data access model objects comprises a step of constructing a set of data access cubes to instantiate the multidimensional space defined by each logical cube.
52. A method as claimed in claim 40, wherein the step of constructing business model objects comprises a step of obtaining information about a data access model object in the data access layer;
and creating a business model object corresponding to the data access model object.
53. A method as claimed in claim 52, wherein the step of transforming business model objects comprises steps of:
locating a business join which connects entities that exist as an implementation artifact of a many to many relationship; and replacing the business join with a single business join.
54. A method as claimed in claim 52, wherein the step of transforming of the business model objects comprises steps of:
locating entities that are related via a 1:1 join relationship; and coalescing the located entities into a single entity.
55. A method as claimed in claim 52, wherein the step of transforming business model objects comprises steps of:
locating redundant joins that express the transitivity of two or more other join relationships in the business layer; and eliminating the redundant joins from the business layer.
56. A method as claimed in claim 52, wherein the step of transforming business model objects comprises a step of introducing a new entity with a subclass relationship into the business layer.
57. A method as claimed in claim 52, wherein the step of transforming business model objects comprises steps of:
locating an entity acting as a lookup table with respect to the other entity, and a business join between the entities, the business join is an associate type;
and changing the business join which is an association type to a business join which is a reference type.
58. A method as claimed in claim 52, wherein the step of transforming business model objects comprises a step of determining the usage of an attribute based on how it is used by other business model objects.
59. A method as claimed in claim 52, wherein the step of transforming business model objects comprises a step of examining attributes to determine where dates are used in the attributes.
60. A method as claimed in claim 40, wherein the step of construct ing package model objects comprises a step of constructing a package layer by forming a package with package model objects which corresponds to a subset of the business model objects.
61. A method as claimed in claim 44, wherein the step of transforming package model objects comprises a step of constructing from a generic package to a specific package which is usable by a specific client application.
62. A method as claimed in claim 40 further comprising steps of:
analyzing the structure of each data source to identify entities that contain measure candidates; and identifying a reasonable set of measures.
63. A method as claimed in claim 40 further comprising steps of:
analyzing each data source; and constructing dimensions and levels for the source model.
64. A method as claimed in claim 40 further comprising a step of constructing a set of logical cubes based on the dimensions in a corresponding data source.
65. A computer readable memory for storing code which identifying instructions for transforming a metadata model for containing model objects, the metadata model having multiple layers including a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model objects having a higher abstraction level, the instructions comprising:
obtaining information of a lower abstraction model object from the lower layer;

abstracting the information by adding business intelligence; and creating in the higher layer a higher abstraction model object corresponding to the lower abstraction model object.
66. A computer data signal representing code which identifying instructions for transforming a metadata model for containing model objects, the metadata model having multiple layers including a lower layer containing one or more lower abstraction model objects having a lower abstraction level and a higher layer containing one or more higher abstraction model objects having a higher abstraction level, the instructions comprising:
obtaining information of a lower abstraction model abject from the lower layer;
abstracting the information by adding business intelligence; and creating in the higher layer a higher abstraction model object corresponding to the lower abstraction model object.
CA002318302A 1999-09-03 2000-09-01 Methods and transformations for transforming metadata model Expired - Fee Related CA2318302C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CA002318302A CA2318302C (en) 1999-09-03 2000-09-01 Methods and transformations for transforming metadata model

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
CA2,281,331 1999-09-03
CA002281331A CA2281331A1 (en) 1999-09-03 1999-09-03 Database management system
US09/654,744 US6609123B1 (en) 1999-09-03 2000-09-01 Query engine and method for querying data using metadata model
US09/653,035 US6662188B1 (en) 1999-09-03 2000-09-01 Metadata model
CA002318302A CA2318302C (en) 1999-09-03 2000-09-01 Methods and transformations for transforming metadata model

Publications (2)

Publication Number Publication Date
CA2318302A1 true CA2318302A1 (en) 2001-03-03
CA2318302C CA2318302C (en) 2009-11-24

Family

ID=32180541

Family Applications (1)

Application Number Title Priority Date Filing Date
CA002318302A Expired - Fee Related CA2318302C (en) 1999-09-03 2000-09-01 Methods and transformations for transforming metadata model

Country Status (1)

Country Link
CA (1) CA2318302C (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112395370A (en) * 2020-11-26 2021-02-23 北京中电普华信息技术有限公司 Data processing method, device, equipment and storage medium
CN112862302A (en) * 2021-02-03 2021-05-28 北京侏罗纪软件股份有限公司 Petroleum data model modeling method and tool

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112395370A (en) * 2020-11-26 2021-02-23 北京中电普华信息技术有限公司 Data processing method, device, equipment and storage medium
CN112395370B (en) * 2020-11-26 2024-03-15 北京中电普华信息技术有限公司 Data processing method, device, equipment and storage medium
CN112862302A (en) * 2021-02-03 2021-05-28 北京侏罗纪软件股份有限公司 Petroleum data model modeling method and tool

Also Published As

Publication number Publication date
CA2318302C (en) 2009-11-24

Similar Documents

Publication Publication Date Title
Jensen et al. Multidimensional databases and data warehousing
CN1749999B (en) Durable storage of .NET data types and instances
Carey et al. Data-Centric Systems and Applications
CN1856783B (en) Data management structure associated with general data item
CN101036141B (en) A database management system with persistent, user- accessible bitmap values
Chowdhury et al. Organizing information: from the shelf to the web
EP1385100A2 (en) Mapping a class hierarchy to a relational database system
US7613715B2 (en) Map and data location provider
CA2417763A1 (en) System and method for comparing heterogeneous data sources
US20070299860A1 (en) System and method for comparative analysis of business intelligence data
WO2008063738A1 (en) Generic infrastructure for migrating data between applications
WO2009147185A1 (en) Method for mapping an x500 data model onto a relational database
Brunel et al. Supporting hierarchical data in SAP HANA
Lee et al. An integrated approach to metadata interoperability
Medina et al. A standard for representing multidimensional properties: The Common Warehouse Metamodel (CWM)
Kriegel et al. SQL bible
Williams The associative model of data
Stanczyk et al. Theory and practice of relational databases
Strate et al. Expert performance indexing for SQL server 2012
Geffner et al. Browsing large digital library collections using classification hierarchies
CA2318302A1 (en) Methods and transformations for transforming metadata model
US6910051B2 (en) Method and system for mechanism for dynamic extension of attributes in a content management system
Belic et al. User‐friendly web application for bibliographic material processing
Herden A design methodology for data warehouses
Dempsey et al. Specification for resource description methods, Part 1. A review of metadata: a survey of current resource description formats

Legal Events

Date Code Title Description
EEER Examination request
MKLA Lapsed
MKLA Lapsed

Effective date: 20110901