CN112612778B - Enterprise data architecture method - Google Patents
Enterprise data architecture method Download PDFInfo
- Publication number
- CN112612778B CN112612778B CN202011562598.5A CN202011562598A CN112612778B CN 112612778 B CN112612778 B CN 112612778B CN 202011562598 A CN202011562598 A CN 202011562598A CN 112612778 B CN112612778 B CN 112612778B
- Authority
- CN
- China
- Prior art keywords
- data
- business
- model
- metadata
- physical
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000013499 data model Methods 0.000 claims abstract description 57
- 238000013507 mapping Methods 0.000 claims abstract description 30
- 238000004458 analytical method Methods 0.000 claims abstract description 15
- 238000004519 manufacturing process Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 7
- 238000013523 data management Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000007405 data analysis Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000012098 association analyses Methods 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 238000009960 carding Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
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
An enterprise data architecture method comprises the steps of scanning an enterprise data warehouse, collecting metadata of the data warehouse, and obtaining an application data model; obtaining a cross mapping relation of a physical-application data model by using a data blood-edge analysis tool; identifying and defining a business data object according to the cross mapping relation of the physical-application data model; and analyzing the cross mapping relation of the physical-application data model, and establishing the relation between the business data objects to form an enterprise logic data model.
Description
Technical Field
The invention belongs to the field of manufacturing enterprise data management, and particularly relates to an enterprise data architecture method based on meta-model cross mapping.
Background
As manufacturing progresses, businesses become more complex from product design development, production to business activities, and business operations and decisions are increasingly dependent on efficient, high quality data support. In order to meet the requirement, the current practice of enterprises is to collect and sort and aggregate the data of the whole enterprise business database into a data warehouse so as to support cross-department and cross-system data analysis and query services.
However, with the development of civil aircraft manufacturing activities by civil aircraft enterprises, the data analysis requirements are more and more extensive and deep, and the civil aircraft manufacturing business and technology are very complex, so that the method has the characteristics of large data volume, wide distribution and multiple types. If the civil aircraft enterprise data architecture is unclear and a data panoramic view is lacking, the problems of data redundancy, untimely data response, inconsistent data provision and the like are easily caused. If the service efficiency of the civil aircraft enterprise data asset is low, the data sharing service capability is seriously restricted. Based on the above, the civil engineering manufacturing industry is urgent to construct a data architecture with global height of enterprises so as to support enterprise data management and ensure effective exertion of enterprise data value.
Disclosure of Invention
The invention aims to provide a data architecture method based on meta-model cross mapping, which is used for constructing a logic data model of enterprise global height by comparing the mapping relation between a business system physical model and a data warehouse application data model and providing powerful support for the fields of enterprise data management and data service.
One of the embodiments of the present invention, an enterprise data architecture method, comprises the following steps,
Scanning an enterprise data warehouse, and collecting metadata of the data warehouse to obtain an application data model;
obtaining a cross mapping relation of a physical-application data model by using a data blood-edge analysis tool;
identifying and defining a business data object according to the cross mapping relation of the physical-application data model;
And analyzing the cross mapping relation of the physical-application data model, and establishing the relation between the business data objects to form an enterprise logic data model.
Drawings
The above, as well as additional purposes, features, and advantages of exemplary embodiments of the present invention will become readily apparent from the following detailed description when read in conjunction with the accompanying drawings. Several embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
FIG. 1 is a flow chart of a method for enterprise data architecture based on metadata cross-mapping in accordance with one embodiment of the present invention.
Detailed Description
Currently, in the field of enterprise data architecture development, most enterprises are implemented by way of building data models. Conventional implementations typically have both top-down and bottom-up implementations. The top-down mode depends on familiarity to the service, and a great amount of service investigation is needed by a modeler, so that the acquired service information is accurate, but is time-consuming and labor-consuming. The bottom-up method needs to construct the mapping relation between the data and the service from the database, however, the system construction technical architecture of the enterprise is not uniform, and the data condition of the enterprise on the system is not completely mastered, so that the data asset checking result is difficult to attach to the service reality. Therefore, the enterprise needs a data architecture carding method with small difficulty in the hand, low personnel requirement, standardized process, accurate and reliable obtained result and higher touchdown property.
Aiming at the problems, the prior art solution is to collect technical metadata by using a metadata collection tool, collect corresponding service metadata from a system service scene as a source point, perform link analysis on the service metadata, integrate a data architecture and provide a data panoramic view so as to support data problem tracking and data heat analysis. According to the method, from the metadata perspective, the technical means is utilized to track the data link, the data architecture is constructed, the labor cost is effectively reduced, and the developed data architecture has strong data analysis capability. However, the scheme is based on the service system for data architecture design, so that the metadata integration process is complicated, the technology dependence degree is high, and implementation is difficult to advance.
In order to solve the problems, the method for efficiently constructing the enterprise global height data architecture is explored by considering the data of the data warehouse integrated by the service-oriented theme so as to promote enterprise data management, realize manageability and traceability of enterprise data assets and ensure effective sharing and service of data among various service systems.
In accordance with one or more embodiments, an enterprise data architecture method based on meta-model cross-mapping includes scanning a data warehouse, collecting metadata of the data warehouse, and obtaining an application data model; obtaining a cross mapping relation of a physical-application data model by using a data blood-edge analysis tool; identifying and defining a business data object according to the cross mapping relation of the physical-application data model; and analyzing the cross mapping relation of the physical-application data model, and establishing the relation between the business data objects to form a logic data model.
And the data warehouse is scanned, metadata information of the data warehouse is collected, and an application meta-model is obtained. The specific operation is as follows: collecting data warehouse metadata includes: metadata subject, data table name, field name, etc. Further, considering that the data warehouse construction is of an application driven type, a model whose metadata is constructed is referred to as an application data model. Metadata acquisition is divided into a client and a server, the server is adapted to a data warehouse and a business system and acquires metadata, and the client integrates and visually displays the metadata.
The method for obtaining the physical-application data model by using the data blood edge analysis tool comprises the following steps: with the aid of data lineage analysis tools, data sources are traced forward starting from metadata (application data model) of the data warehouse, in order to keep track of where the current data came from and what has been processed. Based on the blood-edge analysis result, source service system metadata (hereinafter, source service system metadata model is simply referred to as physical data model) is collected, and a mapping relation of the physical-application data model is constructed. Wherein collecting source business system metadata comprises: database type, connection mode, schema, data structure, database table name, field, description, etc.
The step of identifying and defining business data objects based on the cross-mapping of the physical-application data model extracts data objects based on the data warehouse application data model. The reason for this is that,
The physical data model of the source system generally strictly follows a third paradigm to support the scalability of the service, requiring further aggregation of the tightly-business-related metadata into one data object. The data warehouse application model emphasizes data integration, and the data warehouse form design is based on the principle of high cohesion and low coupling, so that in the physical implementation, the business relationship is compact, and the source system influence difference is small; the business relation is small, and the source system has great influence and is separated. In contrast, it is more efficient to identify data objects from the application data model. Moreover, the data warehouse application model generally adopts a star model, and consists of fact tables and dimension tables, wherein the fact tables record the total information of a certain business theme. Thus, the data warehouse fact table may be abstracted into a business data object.
In addition, in the implementation of several bins, there are multiple data tables to extract, integrate the same or similar source data, resulting in duplication or similarity of several bins of service metadata. Therefore, metadata directed to the same business data object needs to be merged during the data asset manipulation process to simplify subsequent business data object association analysis. In particular to a method for realizing the method,
And calculating the similarity of the data sources of the two business data objects according to the cross mapping relation of the physical-application data model, and merging the two data objects if the similarity is higher than a certain threshold value.
And analyzing the cross mapping relation of the physical-application data model, and establishing the relation between the business data objects to form a logic data model. The aim is to construct the association relation between the business data objects by analyzing the data association relation of the source system physical data model. The reason for this is that,
The source system physical model typically designs a fact table based on each business action in the business process to track business process detail data, while data objects identified based on data warehouse data typically aggregate the body information of one business process and keep the relationships between the data objects loose. It is therefore necessary to retrieve the association between data objects by means of a physical data model, which is implemented in such a way,
Aiming at the data objects with the homologous data, establishing the association relation between the corresponding data objects according to the calculation result. And inquiring whether any source data table between the two data objects has a main foreign key association relation aiming at the data objects without the homologous data, and if so, carrying out association of the two data objects.
The method is characterized in that a physical-application data model cross mapping relation analysis is adopted, so that a physical model is quickly converted into a business layer logic data model. The method effectively solves the problems that the time period for constructing the logic data model from top to bottom is long, knowledge of database data is not available from bottom to top, and the combing result cannot be attached to service facts.
In accordance with one or more embodiments, as illustrated in FIG. 1, a flow diagram of a data architecture method based on metamodel cross-mapping. The method comprises the following steps:
step 101, scanning a data warehouse, and collecting metadata of the data warehouse to obtain an application data model;
Here, the data warehouse is scanned according to the account number of the data warehouse, and all metadata information of the data warehouse is obtained. Collecting data warehouse metadata includes: metadata subject, fact table, table field information.
The metadata management unit is divided into a client and a server, the server is adapted to the data warehouse and the service system and collects data, and the client integrates and visually displays metadata.
102, Obtaining a cross mapping relation of a physical-application data model by using a data blood-edge analysis tool;
With the aid of data lineage analysis tools, data sources are traced forward starting from metadata (application data model) of the data warehouse, in order to keep track of where the current data came from and what has been processed.
And collecting metadata (physical data model) of the source business system based on the blood-margin analysis result, and constructing a mapping relation of the physical-application data model. Wherein recording source system metadata comprises: database type, connection mode, schema, data structure, database table name, field, description, etc.
Step 103, identifying and defining a business data object according to the cross mapping relation of the physical-application data model;
Here, data objects are extracted based on the data warehouse application data model and the data warehouse fact table is abstracted into one business data object. In particular, for data objects with higher similarity of data sources, merging into one data object is considered, and the following is specific:
Assuming that the two data objects are O 1,O2, according to the physical-application data model cross mapping relationship, if the data object O 1,O2 has homologous data, the similarity of the data sources is calculated. Assuming that the number of source data forms mapped by O 1,O2 is n 1,n2 (except for the main data form) and the number of homologous forms is m (except for the main data form), the data source similarity of O 1,O2 is:
Sim(O1,O2)＝m/min(n1,n2) (1)
a) When Sim (O 1,O2) > = epsilon (epsilon preset threshold), the business data object O 1,O2 is merged into one data object O 1.
B) When Sim (O 1,O2) < ε (ε preset threshold), business data object O 1,O2 does not need to be merged.
And 104, analyzing the cross mapping relation of the physical-application data model, and establishing the relation between the business data objects to form a logic data model.
On the one hand: for the data objects with the homologous data, according to the calculation result in step 103, an association relationship between the corresponding data objects is established.
On the other hand: aiming at the data objects without the homologous data, inquiring whether a data table mapped to a source system physical model by the data objects has a main foreign key association relationship, and if so, carrying out association of the two data objects;
And (3) integrating the data object association relation combing results, importing a setting template, and generating a global logic data model under a service view angle. To clarify the enterprise data range and data service capability, and support data management, data query and analysis.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (3)
1. A method for constructing an enterprise data model is characterized by comprising the following steps,
A1, scanning an enterprise data warehouse, collecting metadata of the data warehouse, and obtaining a model constructed by the metadata, wherein the model is defined as an application data model;
A2, by means of a data blood-edge analysis tool, taking an application data model of a data warehouse as a starting point, tracing forward a data source, collecting metadata of a source service system based on a blood-edge analysis result, defining the source service system metadata as a physical data model, and constructing a cross mapping relation of the physical-application data model;
A3, identifying and defining a service data object based on the data warehouse application data model, wherein the service data object identification calculates the similarity of a service data object data source according to the cross mapping relation of the physical-application data model, and if the similarity is higher than a certain threshold value, merging the service data objects;
A4, analyzing the cross mapping relation of the physical-application data model, establishing the relation between the business data objects to form an enterprise logic data model, and constructing the relation between the business data objects by analyzing the data relation of the physical data model of the source business system, wherein,
Establishing an association relation between corresponding business data objects aiming at the business data objects with homologous data;
for the business data object without the homologous data, inquiring whether any source data table between the two business data objects has a main foreign key association relationship, and if so, carrying out association of the two business data objects, wherein the specific process comprises the following steps:
Assuming that the two business data objects are O 1、O2, according to the physical-application data model cross mapping relation, if the business data object O 1、O2 has homologous data, the similarity of the data sources is calculated,
Assuming that the number of source data forms mapped by O 1、O2 is n 1,n2 excluding the main data form, and the number of homologous forms excluding the main data form is m, the similarity of the data sources of O 1、O2 is,
Sim(O1,O2)＝m/min(n1,n2) (1)
Wherein the number of the components is also one,
A) When Sim (O 1,O2) > = epsilon, epsilon being a preset threshold, the traffic data object O 1、O2 is merged into one data object O 1,
B) When Sim (O 1,O2) < epsilon, the business data object O 1、O2 does not need to be merged.
2. The method according to claim 1, wherein the step of scanning the data warehouse collects metadata of the data warehouse, including a theme, a data table name and a field name of the metadata, and the metadata is adapted to the data warehouse and the service system through the server and collected, and is integrated and visually displayed through the client.
3. The method of claim 1, wherein the business is a civil aircraft manufacturing business.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011562598.5A CN112612778B (en) | 2020-12-25 | 2020-12-25 | Enterprise data architecture method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011562598.5A CN112612778B (en) | 2020-12-25 | 2020-12-25 | Enterprise data architecture method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112612778A CN112612778A (en) | 2021-04-06 |
| CN112612778B true CN112612778B (en) | 2024-05-07 |
Family
ID=75247815
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011562598.5A Active CN112612778B (en) | 2020-12-25 | 2020-12-25 | Enterprise data architecture method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112612778B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2318299A1 (en) * | 2000-09-01 | 2002-03-01 | Cognos Incorporated | Metadata exchange |
| CN101566981A (en) * | 2008-04-24 | 2009-10-28 | 长沙创智天马财务软件有限公司 | Method for establishing dynamic virtual data base in analyzing and processing system |
| CN102023979A (en) * | 2009-09-09 | 2011-04-20 | 中国工商银行股份有限公司 | Meta-data management method and system |
| CN102402522A (en) * | 2010-09-09 | 2012-04-04 | 中国移动通信集团上海有限公司 | Data query system and method |
| CN102662994A (en) * | 2012-03-14 | 2012-09-12 | 北京久其软件股份有限公司 | Method and system for establishing data warehouse utilizing virtual multidimensional data set |
| WO2012169807A2 (en) * | 2011-06-07 | 2012-12-13 | Baek Seung Ho | Method and system for building database using data warehouse |
| CN104252506A (en) * | 2013-06-28 | 2014-12-31 | 易保网络技术(上海)有限公司 | Method and system for synchronously constructing and mapping service model and data warehouse model |
| CN106157132A (en) * | 2016-06-20 | 2016-11-23 | 中国工商银行股份有限公司 | Credit risk monitoring system and method |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
| CN109376469A (en) * | 2018-11-21 | 2019-02-22 | 中国航空无线电电子研究所 | A kind of modeling method of the avionics system component meta-model based on AADL |
| CN109558393A (en) * | 2018-11-28 | 2019-04-02 | 中国海洋石油集团有限公司 | A kind of data model construction method, device, equipment and storage medium |
| CN109582695A (en) * | 2018-12-04 | 2019-04-05 | 用友网络科技股份有限公司 | Data general-purpose querying method and inquiry system under a kind of micro services framework |
| CN111159184A (en) * | 2019-12-25 | 2020-05-15 | 上海中信信息发展股份有限公司 | Metadata tracing method and device and server |
| CN111611458A (en) * | 2020-06-09 | 2020-09-01 | 普元信息技术股份有限公司 | Method for realizing system data architecture combing based on metadata and data analysis technology in big data management |
| CN111625579A (en) * | 2019-02-27 | 2020-09-04 | 阿里巴巴集团控股有限公司 | Information processing method, device and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7475080B2 (en) * | 2004-11-23 | 2009-01-06 | International Business Machines Corporation | Adaptive data warehouse meta model method |
| US10620612B2 (en) * | 2017-06-08 | 2020-04-14 | Rockwell Automation Technologies, Inc. | Predictive maintenance and process supervision using a scalable industrial analytics platform |
-
2020
- 2020-12-25 CN CN202011562598.5A patent/CN112612778B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2318299A1 (en) * | 2000-09-01 | 2002-03-01 | Cognos Incorporated | Metadata exchange |
| CN101566981A (en) * | 2008-04-24 | 2009-10-28 | 长沙创智天马财务软件有限公司 | Method for establishing dynamic virtual data base in analyzing and processing system |
| CN102023979A (en) * | 2009-09-09 | 2011-04-20 | 中国工商银行股份有限公司 | Meta-data management method and system |
| CN102402522A (en) * | 2010-09-09 | 2012-04-04 | 中国移动通信集团上海有限公司 | Data query system and method |
| WO2012169807A2 (en) * | 2011-06-07 | 2012-12-13 | Baek Seung Ho | Method and system for building database using data warehouse |
| CN102662994A (en) * | 2012-03-14 | 2012-09-12 | 北京久其软件股份有限公司 | Method and system for establishing data warehouse utilizing virtual multidimensional data set |
| CN104252506A (en) * | 2013-06-28 | 2014-12-31 | 易保网络技术(上海)有限公司 | Method and system for synchronously constructing and mapping service model and data warehouse model |
| CN106157132A (en) * | 2016-06-20 | 2016-11-23 | 中国工商银行股份有限公司 | Credit risk monitoring system and method |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
| CN109376469A (en) * | 2018-11-21 | 2019-02-22 | 中国航空无线电电子研究所 | A kind of modeling method of the avionics system component meta-model based on AADL |
| CN109558393A (en) * | 2018-11-28 | 2019-04-02 | 中国海洋石油集团有限公司 | A kind of data model construction method, device, equipment and storage medium |
| CN109582695A (en) * | 2018-12-04 | 2019-04-05 | 用友网络科技股份有限公司 | Data general-purpose querying method and inquiry system under a kind of micro services framework |
| CN111625579A (en) * | 2019-02-27 | 2020-09-04 | 阿里巴巴集团控股有限公司 | Information processing method, device and system |
| CN111159184A (en) * | 2019-12-25 | 2020-05-15 | 上海中信信息发展股份有限公司 | Metadata tracing method and device and server |
| CN111611458A (en) * | 2020-06-09 | 2020-09-01 | 普元信息技术股份有限公司 | Method for realizing system data architecture combing based on metadata and data analysis technology in big data management |
Non-Patent Citations (5)
| Title |
|---|
| 企业模型与ERP系统间映射技术;宋利康;崔德刚;周儒荣;;航空学报(第06期);全文 * |
| 基于复杂组织体架构方法的企业数据中心总体设计;刘彬;梁建交;;智能制造(08);全文 * |
| 数据架构模型在企业管理中的应用;史松;冀亚林;蔡娜;王霞;马成龙;;价值工程(第33期);全文 * |
| 数据架构设计方法研究;李春鸣;IT技术论坛;全文 * |
| 航空工业企业架构构建方法研究;张国蕊;程燕;徐保文;;航空制造技术(第19期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112612778A (en) | 2021-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106960006B (en) | System and method for measuring similarity between different tracks | |
| Wang et al. | Data quality requirements analysis and modeling | |
| CN112183036B (en) | Format document generation method, device, equipment and storage medium | |
| CN108492028A (en) | Demand data standardized method and standardized system | |
| CN110109908B (en) | Analysis system and method for mining potential relationship of person based on social basic information | |
| CN110852699A (en) | Electronic intelligent management system and method for files | |
| US20080091742A1 (en) | System and method for detecting and updating geographical information dataset versions | |
| CN104679827A (en) | Big data-based public information association method and mining engine | |
| CN112183916B (en) | Land reserve life cycle management system | |
| CN116384889A (en) | Intelligent analysis method for information big data based on natural language processing technology | |
| CN114880405A (en) | Data lake-based data processing method and system | |
| CN114255010A (en) | Electronic file archival management and knowledge service collaborative implementation method in electronic government platform | |
| CN115391432A (en) | Judicial big data processing method, system, server and storage medium | |
| CN111311463A (en) | Data processing method and system for establishing population image based on data label | |
| CN112699245A (en) | Construction method and device and application method and device of budget management knowledge graph | |
| CN114281795A (en) | Data model construction method based on service data standard table | |
| CN117436729A (en) | Government system based data management and data analysis method | |
| CN112363996A (en) | Method, system, and medium for building a physical model of a power grid knowledge graph | |
| CN105677723A (en) | Method for establishing and searching data labels for industrial signal source | |
| CN116701771A (en) | Digital library retrieval and resource sharing system based on cloud computing | |
| CN112612778B (en) | Enterprise data architecture method | |
| CN110222057A (en) | A kind of construction method of aerosol document formatted data base | |
| Abdallah et al. | A Data Collection Quality Model for Big Data Systems | |
| CN107357923A (en) | The cubical method of the tax is generated based on FreeMarker | |
| CN113742320B (en) | Management method and device of OLAP data warehouse |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |