CN110807033A - Data management method, device and system - Google Patents
Data management method, device and system Download PDFInfo
- Publication number
- CN110807033A CN110807033A CN201910966362.9A CN201910966362A CN110807033A CN 110807033 A CN110807033 A CN 110807033A CN 201910966362 A CN201910966362 A CN 201910966362A CN 110807033 A CN110807033 A CN 110807033A
- Authority
- CN
- China
- Prior art keywords
- directory
- data
- field
- metadata
- database
- 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
Links
Images
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- 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/24—Querying
- G06F16/242—Query formulation
- G06F16/2428—Query predicate definition using graphical user interfaces, including menus and forms
-
- 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/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present document relates to a data management method, apparatus and system. The data management system and the method relate to the field of data management and solve the problems of poor compatibility and high customization and maintenance cost of the data management system. The method comprises the following steps: storing business directory data of different domains in a plurality of base table directory metadata, wherein the plurality of base table directory metadata have the same structure; configuring data directory metadata according to application requirements; and establishing a mapping relation between each field of the database table directory metadata and each field of the corresponding data directory metadata, and storing the mapping relation in the data directory metadata. The technical scheme provided by the invention is suitable for cross-domain data management, and realizes high-efficiency and low-cost data management.
Description
Technical Field
The present disclosure relates to the field of data management, and in particular, to a method, an apparatus, and a system for data management.
Background
Data management generally manages data in the same field, and metadata management also manages metadata for a database or data warehouse, for example, metadata management of Hive and MySQL.
Metadata management of a database or a big data warehouse generally stores data after abstract description, and metadata information of Hive includes: save VERSIONs of metadata (verify), DATABASE related metadata (DBS, DATABASE _ PARAMS), TABLE and view related metadata (TBLS, TABLE _ PARAMS, TBL _ PRIVS), save related metadata (SDS, SDS _ PARAMS, SERDES, server _ PARAMS), TABLE field related metadata (COLUMNS _ V2), partition related metadata (PARTITIONS), and the like. The metadata of MySQL is kept in a table in the informa _ schema library.
The management of cross-domain data is generally realized by a customized development mode, and a specific data storage and management structure is customized according to a business scene, for example, cross-domain data management for government affairs cannot be performed for the cross-domain data management for the medical industry. Because the fields and attribute information to be managed by the two fields may be completely different, metadata management for different fields needs to be separately developed and customized.
Disclosure of Invention
To overcome the problems in the related art, a data management method, apparatus and system are provided.
According to a first aspect herein, there is provided a data management method comprising:
storing business directory data of different domains in a plurality of base table directory metadata, wherein the plurality of base table directory metadata have the same structure;
configuring data directory metadata according to application requirements;
and establishing a mapping relation between each field of the database table directory metadata and each field of the corresponding data directory metadata, and storing the mapping relation in the data directory metadata.
Preferably, the method further comprises:
constructing resource directory metadata, wherein the resource directory metadata comprises a resource directory basic information table and a directory attribute table,
the resource directory basic information table stores basic information of a resource directory, and the resource directory attribute table stores attribute information of the resource directory.
Preferably, the base table directory metadata includes a database basic information table, a database attribute table, a data table basic information table, a data table attribute table and a data table field table,
the database basic information table stores database basic information, the database attribute table stores database directory attribute information, the database basic information table stores basic information of a database table, the database attribute table stores attribute information of the database table, and the database field table stores field information of the database table.
Preferably, the data directory metadata includes a data directory basic information table, a data directory attribute table, and a data directory field mapping table, where the data directory basic information table stores data directory basic information, the data directory attribute table stores attribute information of a data directory, and the data directory field mapping table stores mapping relationships between fields in the database directory metadata and fields in the corresponding data directory metadata.
Preferably, the data directory basic information table includes a generation rule field, and the content of the generation rule field indicates a rule for filling out the batch generation of the directory field.
Preferably, the data directory field table contains a mapping rule field, and the content of the mapping rule field indicates a rule for obtaining a mapping relationship between the data directory field and the base table directory field.
According to a second aspect herein, there is provided a data management apparatus comprising:
the base table management module is used for storing the business directory data of different domains into a plurality of base table directory metadata, and the base table directory metadata have the same structure;
the data directory management module is used for configuring data directory metadata according to application requirements;
and the mapping relation management module is used for establishing a mapping relation between each field of the base table directory metadata and each field of the corresponding data directory metadata and storing the mapping relation in the data directory metadata.
According to a third aspect herein, there is provided a data management system comprising: the system comprises a resource directory, a data directory and a plurality of base table directories, wherein the base table directories are distributed in a plurality of domains;
and mapping relations between each field of the data directory record base table directory metadata and each field of the corresponding data directory metadata.
According to a fourth aspect herein, there is provided a computer readable storage medium having stored thereon a computer program which, when executed, carries out the steps of the data management method as described above.
According to a fifth aspect of the present document, there is provided a computer device comprising a processor, a memory and a computer program stored on the memory, wherein the processor, when executing the computer program, implements the steps of the data management method as described above.
According to the three-layer metadata architecture of the resource directory, the base table directory and the data directory, the basic information, attributes, fields and other main information of the directory can be configured according to different service scenes, and therefore cross-domain data management is achieved flexibly. When creating and managing data of different domains, storing business data directories of different domains in different base table directory metadata with the same structure, configuring resource directory metadata according to application requirements, then establishing a mapping relation between each field of the base table directory metadata and each field of corresponding data directory metadata, and storing the mapping relation in the data directory metadata. The problems of poor compatibility and high customization and maintenance costs of a data management system are solved, high-efficiency and low-cost data management is realized, and cross-domain data management is more flexible.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification. In the drawings:
FIG. 1 is an architectural block diagram illustrating a data management system in accordance with an exemplary embodiment.
FIG. 2 is a flow chart illustrating a method of data management according to an example embodiment.
FIG. 3 is a block diagram illustrating a data management device according to an example embodiment.
Fig. 4 is a block diagram illustrating a computer apparatus (general structure of a server) according to an exemplary embodiment.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the drawings of the embodiments of the present invention, and it is obvious that the described embodiments are some but not all of the embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection. It should be noted that the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict.
The management of cross-domain data is generally realized by a customized development mode, and a specific data storage and management structure is customized according to a business scene, for example, cross-domain data management for government affairs cannot be performed for the cross-domain data management for the medical industry. Because the fields and attribute information to be managed by the two fields may be completely different, metadata management for different fields needs to be separately developed and customized. The data management system has poor compatibility and high customization and maintenance costs.
In order to solve the above problem, embodiments of the present invention provide a data management method, apparatus and system. By defining a general metadata structure, when in specific application, the metadata can be applied to any scene by configuring key information in the metadata according to an application environment, and efficient and low-cost data management is realized.
An embodiment of the present invention provides a data management system, the architecture of which is shown in fig. 1, and the data management system adopts a three-layer directory structure including a resource directory, a data directory, and a base table directory. The multiple database table directories are distributed in multiple domains, and the data directory records the mapping relationship between each field of the database table directory metadata and each field of the corresponding data directory metadata.
The three-layer directory is constructed by respective metadata, and specifically includes: the resource directory is constructed by resource directory metadata, the data directory is constructed by data directory metadata, and the base table directory is constructed by base table directory metadata.
As shown in fig. 2, a flow of managing data in the data management system includes:
In an embodiment of the present invention, the plurality of base table directory metadata have the same structure. The database table directory metadata comprises a database basic information table, a database attribute table, a database basic information table, a database attribute table and a database field table, wherein the database basic information table stores database basic information, the database attribute table stores database directory attribute information, the database basic information table stores basic information of a database table, the database attribute table stores attribute information of the database table, and the database field table stores field information of the database table.
The data directory metadata comprises a data directory basic information table, a data directory attribute table and a data directory field mapping table, wherein the data directory basic information table stores data directory basic information, the data directory attribute table stores attribute information of a data directory, and the data directory field mapping table stores mapping relations between each field of database table directory metadata and each field of corresponding data directory metadata.
The data directory basic information table comprises a generation rule field, and the content of the generation rule field indicates the batch generation rule of the filling directory field.
The data directory field table contains mapping rule fields, and the content of the mapping rule fields indicates rules for obtaining the mapping relation between each field in the data directory metadata and each field in the base table directory metadata.
And step 204, constructing the resource directory metadata.
In this step, after the data directory metadata is constructed, the resource directory metadata can be generated according to the data directory metadata. The resource directory metadata comprises a resource directory basic information table and a directory attribute table, wherein the resource directory basic information table stores basic information of a resource directory, and the resource directory attribute table stores attribute information of the resource directory.
The resource directory metadata records description information of resources stored in the data directory metadata, and can be used for assisting a user in inquiring data.
The following describes specific contents of each metadata.
The resource directory metadata comprises a database basic information table, a database attribute table, a data table basic information table, a data table attribute table and a data table field table.
1. The RESOURCE directory basic information table (RESOURCE _ CATALOG) stores basic information of the RESOURCE directory, and is specifically shown in table 1.
TABLE 1
Metadata Table fields | Description of the invention | Example data |
RES_ID | Resource directory ID | 1 |
RES_NAME | Directory name of digital resource | Civil administration information |
OWNER | Owner of the system | Civil bureau |
CREATE_TIME | Creation time | 1536317071 |
DESCRIPTION | Description information | This is a description |
LAST_ACCESS_TIME | Last time access time | 1536317071 |
2. The RESOURCE CATALOG attribute table (RESOURCE _ CATALOG _ ATTR) stores attribute information of the RESOURCE CATALOG, such as an organization, a RESOURCE type, a feature description, and the like, and is specifically shown in table 2.
TABLE 2
Metadata Table fields | Description of the invention | Example data |
RES_ID | Resource directory ID | 1 |
PARAM_KEY | Attribute name | Org |
PARAM_VALUE | Attribute value | Civil bureau |
And the data directory metadata comprises a data directory basic information table, a data directory attribute table and a data directory field mapping table.
1. The DATA directory basic information table (DATA _ CATALOG) stores DATA directory basic information, which is specifically shown in table 3.
The generation RULE (GENERATE _ RULE) field is filled with a catalog field batch generation RULE, which may be a Json string, and the generation RULE may be given in SQL and gives a unique association field. The generation rules for different fields of the directory may correspond to different SQL, and the generation rules for different fields may be placed in a list structure.
Generation of "SQL" corresponding to fields SQL, "join _ key" corresponding to associated fields between fields, if there are multiple associated fields, separated by commas. The fields generated in the first batch do not fill in the join _ key since no association is required.
TABLE 3
Metadata Table fields | Description of the invention | Example data |
DATA_ID | Data directory ID | 1 |
RES_ID | Resource directory ID | 1 |
DATA_NAME | Data directory name | Civil administration data catalog |
OWNER | Owner of the system | Civil bureau |
CREATE_TIME | Creation time | 1536317071 |
DESCRIPTION | Description information | This is a description |
LAST_ACCESS_TIME | Last time access time | 1536317071 |
2. The DATA directory attribute table (DATA _ CATALOG _ ATTR) stores attribute information of the resource directory, such as whether it is confidential, open type, DATA providing method, and the like, and is specifically shown in table 4.
TABLE 4
3. The DATA directory FIELD table (DATA _ CATALOG _ FIELD) stores table FIELDs of the DATA directory, as shown in table 5.
TABLE 5
Where the MAPPING RULE (MAPPING _ RULE) field is used to store the RULEs how this field is generated from the library table directory. The generation rule can be described by SQL, and a mapping relation table of the data directory field and the library table directory field is obtained by analyzing SQL. Since MAPPING _ RULE takes a column of data, the ROW UNIQUE key (ROW _ UNIQUE _ KEYS) field is used to uniquely identify a ROW of the data directory, by which data of the same ROW is mapped. The MAPPING _ run field may describe the MAPPING of a single field of the data directory.
4. The DATA directory FIELD MAPPING table (DATA _ CATALOG _ FIELD _ MAPPING) stores the correspondence between the FIELDs of the DATA directory and the FIELDs of the library table. SQL is automatically generated by analyzing the field generation rule of the data directory, and libraries and tables related to the data directory fields in the SQL need to be analyzed, which is specifically shown in Table 6.
TABLE 6
And the table directory metadata comprises a database basic information table, a database attribute table, a data table basic information table, a data table attribute table and a data table field table.
1. The database basic information table (DB _ catalogue) stores database basic information, and is specifically shown in table 7.
TABLE 7
2. The database attribute table (DB _ CATALOG _ ATTR) stores database CATALOG attribute information, which is specifically shown in table 8.
TABLE 8
Metadata Table fields | Description of the invention | Example data |
DB_ID | Database ID | 2 |
PARAM_KEY | Parameter name | size |
PARAM_VALUE | Parameter value | 1024M |
3. The TABLE basic information TABLE (TABLE _ catalogue) stores basic information of the database TABLE, and is specifically shown in TABLE 9.
TABLE 9
4. The TABLE attribute TABLE (TABLE _ CATALOG _ ATTR) stores attribute information of the data TABLE, and is specifically shown in TABLE 10.
Watch 10
Metadata Table fields | Description of the invention | Example data |
TBL_ID | Table directory ID | 1 |
PARAM_KEY | Attribute name | numRows |
PARAM_VALUE | Attribute value | 9701073 |
5. The TABLE FIELD TABLE (TABLE _ catalogue _ FIELD) stores FIELD information of the database TABLE, as shown in TABLE 11.
TABLE 11
An embodiment of the present invention further provides a data management apparatus, whose structure is shown in fig. 3, including:
the base table management module 301 is used for storing the service data of different domains in different base table directory metadata with the same structure;
a data directory management module 302, configured to configure data directory metadata according to application requirements;
the mapping relationship management module 303 is configured to establish a mapping relationship between each field of the library table directory metadata and each field of the corresponding data directory metadata, and store the mapping relationship in the data directory metadata.
Preferably, the data management apparatus further includes:
a resource description module 304 for constructing resource directory metadata, the resource directory metadata including a resource directory basic information table and a directory attribute table,
the resource directory basic information table stores basic information of a resource directory, and the resource directory attribute table stores attribute information of the resource directory.
An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, wherein the computer program is characterized in that when executed, the computer program implements the steps of the data management method provided by the embodiment of the present invention.
An embodiment of the present invention further provides a computer device for cross-domain data management, which is structured as shown in fig. 4, and the computer device 400 may be a server. Referring to fig. 4, the computer apparatus 400 includes a processor 401, and the number of the processors may be set to one or more as necessary. The computer device 400 also includes a memory 402 for storing instructions, such as application programs, that are executable by the processor 401. The number of the memories can be set to one or more according to needs. Which may store one or more application programs. The processor 401 is configured to execute instructions to perform the data management method described above.
The embodiment of the invention provides a data management method, a device and a system. Through a three-layer metadata architecture of a resource directory, a base table directory and a data directory, the basic information, attributes, fields and other main information of the directory can be configured according to different service scenes, and therefore cross-domain data management is achieved flexibly. When creating and managing data of different domains, storing business data directories of different domains in different base table directory metadata with the same structure, configuring resource directory metadata according to application requirements, then establishing a mapping relation between each field of the base table directory metadata and each field of corresponding data directory metadata, and storing the mapping relation in the data directory metadata. The problems of poor compatibility and high customization and maintenance costs of a data management system are solved, high-efficiency and low-cost data management is realized, and cross-domain data management is more flexible.
As will be appreciated by one skilled in the art, the embodiments herein may be provided as a method, apparatus (device), or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied in the medium. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, including, but not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer, and the like. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) and computer program products according to embodiments herein. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that an article or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such article or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of additional like elements in the article or device comprising the element.
While the preferred embodiments herein have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following appended claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of this disclosure.
It will be apparent to those skilled in the art that various changes and modifications may be made herein without departing from the spirit and scope thereof. Thus, it is intended that such changes and modifications be included herein, provided they come within the scope of the appended claims and their equivalents.
Claims (10)
1. A method for managing data, comprising:
storing business directory data of different domains in a plurality of base table directory metadata, wherein the plurality of base table directory metadata have the same structure;
configuring data directory metadata according to application requirements;
and establishing a mapping relation between each field of the database table directory metadata and each field of the corresponding data directory metadata, and storing the mapping relation in the data directory metadata.
2. The data management method of claim 1, further comprising:
constructing resource directory metadata, wherein the resource directory metadata comprises a resource directory basic information table and a directory attribute table,
the resource directory basic information table stores basic information of a resource directory, and the resource directory attribute table stores attribute information of the resource directory.
3. The data management method of claim 1, wherein the library table directory metadata comprises a database basic information table, a database attribute table, a data table basic information table, a data table attribute table, and a data table field table,
the database basic information table stores database basic information, the database attribute table stores database directory attribute information, the database basic information table stores basic information of a database table, the database attribute table stores attribute information of the database table, and the database field table stores field information of the database table.
4. The data management method according to claim 1, wherein the data directory metadata includes a data directory basic information table, a data directory attribute table, and a data directory field mapping table, wherein the data directory basic information table stores data directory basic information, the data directory attribute table stores attribute information of a data directory, and the data directory field mapping table stores mapping relationships between fields in the database directory metadata and fields in the corresponding data directory metadata.
5. The data management method of claim 4, wherein the data directory basic information table comprises a generation rule field, and the content of the generation rule field indicates a rule for filling out the directory field batch generation.
6. The data management method of claim 4, wherein the data directory field table contains a mapping rule field, and the content of the mapping rule field indicates a rule for obtaining a mapping relationship between the data directory field and the base table directory field.
7. A data management apparatus, comprising:
the base table management module is used for storing the business directory data of different domains into a plurality of base table directory metadata, and the base table directory metadata have the same structure;
the data directory management module is used for configuring data directory metadata according to application requirements;
and the mapping relation management module is used for establishing a mapping relation between each field of the base table directory metadata and each field of the corresponding data directory metadata and storing the mapping relation in the data directory metadata.
8. A data management system, comprising: the system comprises a resource directory, a data directory and a plurality of base table directories, wherein the base table directories are distributed in a plurality of domains;
and mapping relations between each field of the data directory record base table directory metadata and each field of the corresponding data directory metadata.
9. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed, implements the steps of the method according to any one of claims 1-6.
10. A computer arrangement comprising a processor, a memory and a computer program stored on the memory, characterized in that the steps of the method according to any of claims 1-6 are implemented when the computer program is executed by the processor.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910966362.9A CN110807033B (en) | 2019-10-12 | 2019-10-12 | Data management method, device and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910966362.9A CN110807033B (en) | 2019-10-12 | 2019-10-12 | Data management method, device and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN110807033A true CN110807033A (en) | 2020-02-18 |
CN110807033B CN110807033B (en) | 2023-01-31 |
Family
ID=69488224
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910966362.9A Active CN110807033B (en) | 2019-10-12 | 2019-10-12 | Data management method, device and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110807033B (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111694611A (en) * | 2020-04-23 | 2020-09-22 | 时时同云科技(成都)有限责任公司 | Data processing method and device and electronic equipment |
CN111708779A (en) * | 2020-06-11 | 2020-09-25 | 中国建设银行股份有限公司 | Data management method, system, management equipment and storage medium |
CN112216347A (en) * | 2020-09-14 | 2021-01-12 | 苏州创腾软件有限公司 | Scientific data genome processing method, device and storage medium |
CN112597175A (en) * | 2020-12-15 | 2021-04-02 | 京东方科技集团股份有限公司 | Data docking method, system, device and storage medium |
CN117171108A (en) * | 2023-11-02 | 2023-12-05 | 北京友友天宇系统技术有限公司 | Virtual model mapping method and system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020184210A1 (en) * | 1999-01-26 | 2002-12-05 | Joseph M. Khan | Universal information warehouse system and method |
US20080294673A1 (en) * | 2007-05-25 | 2008-11-27 | Microsoft Corporation | Data transfer and storage based on meta-data |
CN101859303A (en) * | 2009-04-07 | 2010-10-13 | 中国移动通信集团湖北有限公司 | Metadata management method and management system |
CN102937965A (en) * | 2012-09-29 | 2013-02-20 | 山东浪潮齐鲁软件产业股份有限公司 | Meta-system design method based on data model |
CN104346377A (en) * | 2013-07-31 | 2015-02-11 | 克拉玛依红有软件有限责任公司 | Method for integrating and exchanging data on basis of unique identification |
CN109739893A (en) * | 2018-12-28 | 2019-05-10 | 上海连尚网络科技有限公司 | A kind of metadata management method, equipment and computer-readable medium |
CN109766345A (en) * | 2019-01-10 | 2019-05-17 | 深圳前海微众银行股份有限公司 | Metadata processing method and device, equipment, readable storage medium storing program for executing |
-
2019
- 2019-10-12 CN CN201910966362.9A patent/CN110807033B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020184210A1 (en) * | 1999-01-26 | 2002-12-05 | Joseph M. Khan | Universal information warehouse system and method |
US20080294673A1 (en) * | 2007-05-25 | 2008-11-27 | Microsoft Corporation | Data transfer and storage based on meta-data |
CN101859303A (en) * | 2009-04-07 | 2010-10-13 | 中国移动通信集团湖北有限公司 | Metadata management method and management system |
CN102937965A (en) * | 2012-09-29 | 2013-02-20 | 山东浪潮齐鲁软件产业股份有限公司 | Meta-system design method based on data model |
CN104346377A (en) * | 2013-07-31 | 2015-02-11 | 克拉玛依红有软件有限责任公司 | Method for integrating and exchanging data on basis of unique identification |
CN109739893A (en) * | 2018-12-28 | 2019-05-10 | 上海连尚网络科技有限公司 | A kind of metadata management method, equipment and computer-readable medium |
CN109766345A (en) * | 2019-01-10 | 2019-05-17 | 深圳前海微众银行股份有限公司 | Metadata processing method and device, equipment, readable storage medium storing program for executing |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111694611A (en) * | 2020-04-23 | 2020-09-22 | 时时同云科技(成都)有限责任公司 | Data processing method and device and electronic equipment |
CN111708779A (en) * | 2020-06-11 | 2020-09-25 | 中国建设银行股份有限公司 | Data management method, system, management equipment and storage medium |
CN112216347A (en) * | 2020-09-14 | 2021-01-12 | 苏州创腾软件有限公司 | Scientific data genome processing method, device and storage medium |
CN112597175A (en) * | 2020-12-15 | 2021-04-02 | 京东方科技集团股份有限公司 | Data docking method, system, device and storage medium |
CN112597175B (en) * | 2020-12-15 | 2024-07-23 | 京东方科技集团股份有限公司 | Data docking method, system, device and storage medium |
CN117171108A (en) * | 2023-11-02 | 2023-12-05 | 北京友友天宇系统技术有限公司 | Virtual model mapping method and system |
CN117171108B (en) * | 2023-11-02 | 2024-02-13 | 北京友友天宇系统技术有限公司 | Virtual model mapping method and system |
Also Published As
Publication number | Publication date |
---|---|
CN110807033B (en) | 2023-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110807033B (en) | Data management method, device and system | |
US9785417B2 (en) | Managing reusable artifacts using placeholders | |
KR102449753B1 (en) | System and method for supporting namespaces in a multitenant application server environment | |
CN105488050B (en) | A kind of more indexing means of database, apparatus and system | |
JP7548673B2 (en) | Generating Software Artifacts from Conceptual Data Models | |
US20130339385A1 (en) | Leveraging graph databases in a federated database system | |
US10387401B2 (en) | Version control of records in an electronic database | |
CN109739828B (en) | Data processing method and device and computer readable storage medium | |
KR20170023112A (en) | System and method for portable partitions in a multitenant application server environment | |
CN112182045B (en) | Metadata management method and device, computer equipment and storage medium | |
CN110019111A (en) | Data processing method, device, storage medium and processor | |
CN110825764B (en) | SQL script generation method, system, storage medium and processor | |
US10909487B2 (en) | Workflow customization | |
CN117076473B (en) | Metadata operation method, system, equipment and medium for SaaS multi-tenant | |
CN108595924B (en) | Business authority management method and device, computer equipment and storage medium | |
US11245639B2 (en) | Composition of persistent object instances linking resources across multiple, disparate systems | |
CN107463618B (en) | Index creating method and device | |
CN108241624B (en) | Query script generation method and device | |
CN114547055A (en) | Data processing method and device | |
US11232104B2 (en) | Join and predicate filtering using string lengths for variable character fields | |
CN118733671A (en) | Material synchronization method, equipment and medium | |
CN113642309B (en) | Data comparison method and related device | |
CN117331998A (en) | Metadata management method and device, storage medium and computer equipment | |
CN116541397A (en) | State data query method and device | |
CN112632024A (en) | Method and electronic equipment for managing data of telecommunication network |
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 |