Integration and migration methods and systems for cross-domain databases

Abstract

The present invention discloses a cross-domain database integration and migration method and system. The integration method includes: establishing a first database corresponding to the first domain for each item from a database in a first domain, containing multiple types of metadata. The multiple types of metadata include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata. Each metadata has a corresponding basic attribute table. The first database includes the basic attribute table for the multiple types of metadata and an extended attribute table for at least one type of metadata corresponding to each item in the first domain; establishing a second database corresponding to the second domain for each item from a database in a second domain; and integrating the first and second databases to generate a unified database. For items in both the first and second domains, databases corresponding to the five types of metadata are first established before integration is performed. This improves the integration effect and facilitates subsequent processing.

Description

Technical Field

[0001] The present invention belongs to the field of database technology, and in particular relates to a method and system for integrating and migrating cross-domain databases. Background Art

[0002] In the prior art, a relational database is a database that uses a relational model to organize data. It stores data in rows and columns for easy understanding. These rows and columns are called tables, and a set of tables constitutes a database. Users retrieve data from the database through queries, which are executable code that limits access to certain areas of the database. The relational model can be simply understood as a two-dimensional table model, and a relational database is a data organization consisting of two-dimensional tables and the relationships between them.

[0003] 1. Storage method: Traditional relational databases use tables for storage, where data is stored in rows and columns, making it very convenient to read and query.

[0004] 2. Storage structure: Relational databases store data in a structured manner. Each data table must have all fields defined (that is, the table structure must be defined first), and then data is stored according to the table structure. The advantage of this is that the form and content of the data are defined before the data is stored, so the reliability and stability of the entire data table are relatively high. However, the problem is that once the data is stored, it will be very difficult to modify the structure of the data table.

[0005] 3. Storage Standards: To avoid duplication, normalize data, and fully utilize storage space, relational databases store data in the form of minimal relational tables. This allows for clear and easy-to-understand data management. This is primarily the case with a single table. The situation is different with multiple tables. Because data spans multiple tables and the relationships between them are complex, data management becomes increasingly complex as the number of tables increases.

[0006] 4. Expansion method: Since relational databases store data in data tables, the bottleneck of data operations occurs in the operation of multiple data tables, and the more data tables there are, the more serious this problem is. If you want to alleviate this problem, you can only improve the processing power, that is, choose a faster and higher-performance computer. Although this method can provide a certain amount of expansion space, such expansion space must be very limited, that is, relational databases only have the ability to expand vertically.

[0007] 5. Query method: Relational databases use structured query language (SQL) to query the database. SQL has long been supported by various database manufacturers and has become the standard in the database industry. It can support database CRUD (add, query, update, delete) operations and has very powerful functions. SQL can use index-like methods to speed up query operations.

[0008] 6. Normalization: During the database design and development process, developers often face the need to operate on one or more data entities (including arrays, lists, and nested data) at the same time. In a relational database, a data entity must first be divided into multiple parts, and then the divided parts must be normalized. After normalization, they are stored in multiple relational data tables. This is a complex process. The good news is that with the development of software technology, many software development platforms provide some simple solutions. For example, the ORM layer (that is, object-relational mapping) can be used to map the object model in the database to a SQL-based relational database and to convert data between different types of systems.

[0009] 7. Transactional: Relational databases emphasize the ACID principles (Atomicity, Consistency, Isolation, and Durability), meeting the requirements for high transactional performance or complex data queries. They also fully meet the requirements for high performance and operational stability. Furthermore, relational databases place great emphasis on strong data consistency and provide excellent support for transactional operations. Relational databases can control transaction atomicity at a fine-grained level and can immediately roll back transactions in the event of an error or if necessary.

[0010] 8. Read and write performance: Relational databases place great emphasis on data consistency, and this comes at a huge cost in reduced read and write performance. Although relational databases are very reliable in storing and processing data, their efficiency becomes very poor when faced with massive amounts of data, especially when encountering high-concurrency read and write operations, where performance will degrade significantly.

[0011] 9. Authorization method: Common relational databases include Oracle, SQL Server, DB2, and MySQL. Except for MySQL, most relational databases require high fees to use. Even the free MySQL performance is subject to many limitations.

[0012] The process of relational database design can be roughly divided into four periods and seven stages.

[0013] (1) The user needs analysis period is mainly about understanding and analyzing the user's functional and application needs for data. It is the basis of the entire design process and is related to the success or failure of the entire database application system design.

[0014] (2) During the database design period, the user requirements are mainly synthesized, summarized and abstracted to form a data model independent of the specific DBMS, which can be represented by an entity-relationship model. It is then converted into a set of relational models supported by the selected relational database management system (RDBMS) and a physical structure suitable for the application environment is selected, including storage structure and access methods.

[0015] (3) The database implementation period, including the database structure creation stage and the application behavior design and implementation stage, is to create the database, create tables, create indexes, create clusters, etc. based on the physical model of the database.

[0016] (4) Database operation and maintenance stage. The last stage is when the database application system can be put into formal operation after trial operation.

[0017] When designing a relational database, the following principles should be followed to improve the database's storage efficiency, data integrity, and scalability.

[0018] 1. Naming standardization

[0019] In conceptual model design, the structures of entities, attributes, and related tables must be unified. For example, in database design, the term "student" specifically refers to undergraduate students, and the associated attributes include student ID, name, gender, date of birth, etc. The type, length, and value range of each attribute must be determined. This ensures that naming avoids homonyms, synonyms, attribute characteristics, and structural conflicts.

[0020] 2. Data consistency and integrity

[0021] In relational databases, constraints such as domain integrity, entity integrity, and referential integrity can be used to meet the consistency and integrity of data, which can be achieved using check, default, null, primary key, and foreign key constraints.

[0022] 3. Data redundancy

[0023] Database data should be designed to minimize redundancy, meaning duplicate data should be minimized. For example, if the phone numbers of employees in a department are stored in different tables, then when the employee's phone number changes, the redundant data will require updates to multiple tables. If one table is omitted, data inconsistencies will result. Therefore, database design must minimize redundancy.

[0024] 4. Paradigm Theory

[0025] When designing a relational database, a good database model is generally obtained by designing it to meet a certain paradigm. It is generally believed that 3NF achieves the best balance in terms of performance, scalability, and data integrity. Therefore, general database design requires achieving 3NF, eliminating unreasonable parts of data dependencies, and ultimately achieving the goal of making a relationship describe only one entity or a connection between entities.

[0026] The inventors discovered that the above-mentioned data management model has at least the following defects: it is difficult to integrate and share information resources. The data management model of traditional information systems has not made plans for data sharing from the beginning, resulting in great difficulties in the aggregation, integration, governance, application, and sharing of information resources across information systems. Due to the independence of business demand departments, information systems with independent boundaries are established based on determined business needs, which seriously restricts the effective integration of information resources and makes it difficult to build an integrated information service system. Therefore, insufficient data integration and sharing accelerates the fragmentation, compartmentalization, and islanding of information, which in turn leads to repeated collection of information data, repeated construction of information systems, and the lack of a unified data foundation. Summary of the Invention

[0027] The embodiments of the present invention aim to solve at least one of the above technical problems.

[0028] In a first aspect, an embodiment of the present invention provides a cross-domain database integration and migration method, comprising: analyzing a user's functional expansion requirements, determining at least one project corresponding to the functional expansion requirements and each attribute table corresponding to the at least one project, the attribute table comprising a basic attribute table of multiple categories of metadata and an extended attribute table of at least one category of metadata, the multiple categories of metadata comprising: natural person metadata, organization metadata, address metadata, object metadata, and event metadata; when the at least one project is a new project, adding the basic attribute table of the multiple categories of metadata and the extended attribute table of at least one category of metadata corresponding to the new project to the database, wherein the database is composed of each project and the corresponding basic attribute table and the extended attribute table.

[0029] In a second aspect, an embodiment of the present invention provides a cross-domain database integration and migration system, comprising: an analysis program module, configured to analyze a user's functional expansion requirements, determine at least one project corresponding to the functional expansion requirements and each attribute table corresponding to the at least one project, the attribute table including a basic attribute table of multiple categories of metadata and an extended attribute table of at least one category of metadata, the multiple categories of metadata including: natural person metadata, organization metadata, address metadata, object metadata and event metadata; and an update program module, configured to add, when the at least one project is a new project, the basic attribute table of the multiple categories of metadata corresponding to the new project and the extended attribute table of at least one category of metadata in the database, wherein the database is composed of each project and the corresponding basic attribute table and the extended attribute table.

[0030] In a third aspect, an embodiment of the present invention provides an electronic device comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the above-mentioned cross-domain database integration and migration methods of the present invention.

[0031] In a fourth aspect, an embodiment of the present invention provides a storage medium, which stores one or more programs including execution instructions, and the execution instructions can be read and executed by electronic devices (including but not limited to computers, servers, or network devices, etc.) to execute any of the above-mentioned cross-domain database integration and migration methods of the present invention.

[0032] In a fifth aspect, an embodiment of the present invention further provides a computer program product, which includes a computer program stored on a storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes any one of the above-mentioned cross-domain database integration and migration methods.

[0033] This embodiment of the present invention integrates customer expansion requirements into the basic and extended attribute tables of five types of metadata. Because the five-category metadata framework encompasses a wide range of attributes to be expanded, expansion requirements can be modeled and described through flexible metadata combinations. First, the relationship between the customer's expansion requirements and the basic and extended attribute tables of the five types of metadata is analyzed and determined. Then, the corresponding basic and extended attribute tables are added to the database. This makes expansion relatively simple, and the five-category metadata framework can flexibly address various expansion requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0035] Figure 1 is a flow chart of an embodiment of the cross-domain database integration method of the present invention;

[0036] Figure 2 is a flow chart of another embodiment of the cross-domain database integration method of the present invention;

[0037] Figure 3 is a flow chart of another embodiment of the cross-domain database integration method of the present invention;

[0038] Figure 4 A flowchart of an embodiment of the cross-domain database migration method of the present invention;

[0039] Figure 5a 、 Figure 5b 、 Figure 5c 、 Figure 5d 、 Figure 5e and Figure 5f A schematic diagram of metadata of a cross-domain database integration and migration method provided by one embodiment of the present invention;

[0040] Figure 6 is a block diagram of a cross-domain database integration system according to an embodiment of the present invention;

[0041] Figure 7 is a block diagram of a cross-domain database integration system according to another embodiment of the present invention;

[0042] Figure 8 is a block diagram of the cross-domain database migration system of the present invention;

[0043] Figure 9 FIG. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0044] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0045] It should be noted that, unless there is any conflict, the embodiments and features in the embodiments of this application can be combined with each other.

[0046] The present invention may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. The present invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0047] In the present invention, "module", "device", "system" and the like refer to related entities applied to a computer, such as hardware, a combination of hardware and software, software or software in execution, etc. Specifically, for example, an element can be, but is not limited to, a process running on a processor, a processor, an object, an executable element, an execution thread, a program and / or a computer. In addition, an application or script program running on a server, or a server can all be an element. One or more elements can be in an execution process and / or thread, and an element can be localized on a computer and / or distributed between two or more computers, and can be run by various computer-readable media. An element can also communicate through local and / or remote processes based on a signal having one or more data packets, for example, a signal from a data packet interacting with another element in a local system, a distributed system, and / or a signal from a network on the Internet that interacts with other systems via signals.

[0048] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "include" and "comprise" include not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article or device. In the absence of further limitations, the elements defined by the phrase "include..." do not exclude the presence of other identical elements in the process, method, article or device that includes the elements.

[0049] The embodiments of the present invention provide a cross-domain database integration method and migration method for integrating and migrating cross-domain databases. It should be noted that although the limitations of the first field and the second field are used in the subsequent embodiments, those skilled in the art will understand that the first field and the second field generally refer to different application fields, and the first field and the second field are not used to limit only two fields, but to highlight that different fields can be integrated and migrated with each other, and there can be multiple fields for different applications in the social ecological environment. For example, for various existing application systems in different industries, each application system will have a corresponding database, different applications, different departments, different organizations, etc., if data integration or migration is required, the technical solutions of the embodiments of the present application can be used to implement them, and this application will not go into details here.

[0050] Please refer to Figure 1 , which illustrates a cross-domain database integration method provided by an embodiment of the present invention.

[0051] like Figure 1 As shown, in step 101, for each item from a first domain database, a first database corresponding to the first domain is established, which includes multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the first database includes the basic attribute table of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata;

[0052] In step 102, for each item from the second domain database, a second database corresponding to the second domain is established, wherein the second database includes basic attribute tables of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item in the second domain;

[0053] In step 103, the first database and the second database are integrated to generate a unified database.

[0054] In this embodiment, the first domain can be, for example, the water conservancy domain, and the second domain can be, for example, the agricultural reclamation domain. For each project in the water conservancy database, a water conservancy database containing multiple types of metadata is first established. For example, in the water conservancy domain, there may be an employee information maintenance table containing the employee's name, age, gender, contact information, home address, etc. First, a basic attribute table corresponding to the natural person metadata and an extended attribute table corresponding to each extended attribute of age, contact information, and home address are established. These data can then be transferred to the basic attribute table and each extended attribute table corresponding to the natural person metadata. For example, name and gender data can be transferred to the basic attribute table, and data for other attributes can be transferred to the corresponding extended attribute tables. The establishment of tables and data transfer for the other types of metadata can be similarly accomplished. Furthermore, for some projects that may correspond to multiple types of metadata simultaneously, the metadata can be first split into multiple categories, and then corresponding basic attribute tables and extended attribute tables can be established for data integration. The same process is used for the database in the second domain, such as the agricultural reclamation domain. By establishing the same database structure for databases in different domains and then integrating the data into the same database structure, database integration and unification can be achieved.

[0055] The method of the embodiment of the present application first establishes databases corresponding to the five types of metadata for projects in the first and second fields, and then integrates them, which can achieve better integration results and make subsequent other processing more convenient. Because the five types of metadata encompass all attributes, different projects and applications can be flexibly combined using these five types of metadata. Databases in different fields all establish basic attribute tables and extended attribute tables corresponding to the five types of metadata. Finally, the integration of different databases can be achieved, facilitating subsequent operations such as adding, deleting, modifying, and querying the integrated database.

[0056] In some optional embodiments, the descriptions of various metadata are as follows:

[0057] (1) Natural person metadata

[0058] Individuals are crucial elements in any information system, and they also create a high probability of duplication when data is shared across systems. Application service systems pose challenges to the human element by enabling the sharing of basic human information and ensuring its accuracy, reliability, and timeliness. Furthermore, how to cope with the rapid and flexible changes in organizational and personnel adjustments is crucial.

[0059] Natural person management is divided into basic personnel information and extended information management, which can meet the needs of organizational adjustments and personnel changes by allowing flexible changes to personnel in the system.

[0060] Natural person management requires the completion of different forms of personnel input, to meet the various related attributes of different personnel (such as: telephone, title, title, etc.) input attributes at any time increase or decrease, at the same time, also need to meet the composite attributes (a certain attribute has multiple corresponding contents, such as telephone, certificate, etc.) information input, to facilitate the system's comprehensive collection and management of personnel information.

[0061] (2) Address metadata

[0062] Addresses are essential to every system and are crucial elements. As systems become more widely used, some contain structured data, while others contain semi-structured, non-standardized information. This data struggles to adapt to the system's flexible and adaptable data needs. Therefore, this system design manages both basic and extended address information.

[0063] (3) Organization metadata

[0064] An organization is a social entity composed of several individuals or groups with a common goal and certain boundaries. It has three meanings:

[0065] 1) An organization must be a social entity that is people-centered, rationally coordinates people, finances, and materials, and maintains relative stability.

[0066] 2) The organization must have a common goal that is recognized and strived for by all its members.

[0067] 3) The organization must maintain a clear boundary to distinguish itself from other organizations and the external environment.

[0068] The organizational structure needs to be set up and entered according to commonly used institutions and departments, while also meeting the requirements of flexible additions, subtractions, and changes to the organizational structure due to institutional reforms, as well as the requirements for setting up temporary work units. Therefore, this system is designed to manage basic organizational information and extended information.

[0069] (4) Object data

[0070] Things refer to objective objects incorporated into the basic information management platform. The scope of things is extremely broad, and their applications are extremely complex. In the era of big data and the Internet of Things, things are the mainstay of information management, both the objects of management and the objects being managed. Things are connected, and everything is interconnected, with things being the core and foundation.

[0071] The basic information management platform integrates all things into a collection of objects, identifies them with identification numbers, and describes their essence. Objects are managed using both basic and extended information. Objects can be flexibly used based on user business applications. Objects are immutable, while applications are variable.

[0072] (5) Event metadata

[0073] "Things" refers to the changes in the spatial distribution of mass over time. Since matter is the spatial distribution of mass, "things" can also be defined as the changes in matter over time. "Things" encompasses a wide range of topics, generally referring to events, affairs, phenomena, and situations in society and nature.

[0074] The basic information management platform will carry out a series of actions such as information management, information analysis, and information decision support based on the actual applications and needs of users.

[0075] Events are also entered into a database and managed using basic and extended information, represented by identification numbers and organized in chronological order, allowing for variable information management. Events are an application and extension of the other four elements: people, places, objects, and organizations.

[0076] Please refer to Figure 2 , which shows a flowchart of another cross-domain database integration method provided by an embodiment of the present application. Figure 1 The flowchart is further defined by step 103 of “integrating the first database and the second database to generate a unified database”.

[0077] like Figure 2 As shown, in step 201, when the items of the first database are not completely identical to the items of the second database, one of the databases is used as the base database, and based on the multiple categories of metadata, the basic attribute tables of the other database and the extended attribute tables corresponding to the items in the other database that are identical to those in the base database are merged into the corresponding basic attribute tables and / or extended attribute tables in the base database;

[0078] In step 202, the extended attribute tables corresponding to the items in the other database that are not included in the basic database are added to the basic database to generate a unified database.

[0079] For example, a water conservancy database and an agricultural reclamation database have a lot of overlapping data. After integration through the above method, the overlapping data will only be saved once, greatly reducing the duplication and redundancy of the integrated database. Subsequent data updates will not require updating data in multiple places. It also avoids the situation where data involves multiple data tables and the complex relationships between the data tables will increase, and data management will become increasingly complex as the number of data tables increases.

[0080] The method of this embodiment combines and adds tables based on a single database during integration, resulting in simple processing and effective integration. Because the integration is based on five types of metadata, the integration process only requires adding tables not already in the base database, such as basic attribute tables and extended attribute tables, and then migrating the data. The resulting unified database eliminates duplication of data resources, reducing redundancy and making various database operations like add, delete, modify, and query more convenient than before the integration. After integration, identical attributes appear only in one extended attribute table, making data updates more user-friendly.

[0081] In some optional embodiments, the integration of the first database and the second database includes: when the items of the first database are the same as the items of the second database, merging the basic attribute tables and at least one extended attribute table corresponding to each item to generate a unified database. Therefore, when integrating, for the case where the items are the same, the tables are directly merged, which is simple to handle. The subsequent addition, deletion, modification and query of the unified database are no different from addition, deletion, modification and query in one database, and can greatly reduce the redundancy of the database. The update of a certain attribute will only involve one extended attribute table, and will not need to be updated simultaneously because a certain data exists in multiple data tables. Various extended attribute tables can be associated only with the basic attribute table of the corresponding metadata, which greatly reduces the association between tables and will not cause data overflow as the number of data tables increases.

[0082] Data management will become increasingly complex.

[0083] In some optional embodiments, both the basic attribute table and the extended attribute table have timestamps. When there are two data with different timestamps, the two data are determined to be different data, and only the data that are exactly the same in the table are overwritten during merging. Thus, for two data with only different timestamps but the same other content, they can be retained as different data at the same time, and only the data that are exactly the same can be overwritten. For example, if the contact information of a person in the metadata of a natural person is updated, if there was a phone and WeChat before, and now WeChat needs to be updated, then it is exactly the same data and can be directly overwritten. If what needs to be updated now is the Douyin account, then it is not the same contact information as the previous phone and WeChat, so the Douyin account can be directly updated to the contact information extended attribute table.

[0084] Please refer to Figure 3 , which shows a flowchart of another cross-domain database integration method provided by an embodiment of the present application.

[0085] like Figure 3As shown, in step 301, each item from the first domain database is split into a first database corresponding to the first domain and including multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the first database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata;

[0086] In step 302, each item from the second domain database is split into a second database corresponding to the second domain, wherein the second database includes basic attribute tables of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item in the second domain;

[0087] In step 303, the first database and the second database are integrated to generate a unified database.

[0088] The method of the embodiment of the present application is aimed at projects in the first and second fields. Since the databases of the five types of metadata are more fine-grained databases, each extended attribute table of the basic attribute table only stores one attribute. They can be split into databases corresponding to the five types of metadata first, and then integrated. This can make the integration effect better and make subsequent other processing more convenient. For example, there is a table in the first field that contains attributes such as an employee's name, gender, contact information, home address, resume, and certificate. This table can be mapped to the natural person metadata of the five types of metadata. The employee's name and gender can be split into the basic attribute table of the natural person metadata, and the employee's contact information, home address, resume, and certificate attributes can be split into extended attribute tables such as the communication information table, address information table, resume information table, and certificate information table, thereby completing the splitting and expansion of the basic attribute table and extended attribute table corresponding to the five types of metadata. Since the databases of the first and second fields are both split and data migrated corresponding to the basic attribute table and extended attribute table of the five types of metadata, the databases of the two fields eventually form databases corresponding to the five types of metadata. Then, integrating the two field databases will be more convenient, and the integration process can also minimize data redundancy.

[0089] Since the database containing five types of metadata is more fine-grained than the existing database and provides a more comprehensive description of things, almost all data can be mapped to these five types of metadata. Therefore, it is only necessary to split the projects and then integrate them to form a unified database.

[0090] Furthermore, for the database of existing applications, the database can be expanded first in the database of the original application system to make the data in the original database closer to the attribute requirements of the five types of metadata, and then the database can be integrated and finally migrated according to different new applications.

[0091] In some optional embodiments, the basic attribute table and the extended attribute table of each metadata are specifically introduced as follows:

[0092] Basic attribute information of natural persons

[0093] 1. Natural person basics (hereinafter referred to as "person basics"): identification number, associated number (subject), registered date of birth (lunar calendar, lunar calendar: year, month, day, hour, and minute), place of origin (associated number address), remarks, person entering the information, and time of entry;

[0094] 2. Gender: identification number, association number (person-based), gender (male, female, transgender, intersex), start and end dates;

[0095] Note: The above "identification numbers" are all automatically generated.

[0096] Natural person extended attribute information

[0097] 1. Communication: identification number, associated number (person-based), communication number (phone, WeChat, QQ, blog, email, website, video account, etc.), number description;

[0098] 2. Address: Identification number, association number (person basis), association number (the most basic unit of the address), address description, start and end time (two fields are considered during design);

[0099] 3. Professional title: identification number, association number (personnel basis), professional title (technician, engineer, professor, registered construction engineer, certified public accountant, etc.), professional title description, and professional title start and end dates;

[0100] 4. Resume: identification number, associated number (person basis), associated number (organization basis), resume start and end time, reference person (associated personnel base database, resume description;

[0101] 5. Certificate: identification number, association number (personal basis), association number (file), certificate name, certificate number, certificate description, start and end dates;

[0102] 6. Relationship: Identification number, association number (person-based), relationship description (father and son, father-in-law, husband and wife, children, uncle and nephew, classmates, poker buddies, cellmates, colleagues... multiple selections possible), start and end dates.

[0103] Basic address attribute information

[0104] 1. Address basis: identification number, associated number (main set), representative name (a repeated, descriptive

[0105] Address extended attribute information

[0106] 2. Title: identification number, association number (primary set), title (administrative, common, abbreviation, etc.), title description, and title start and end dates;

[0107] 3. Upper-level relations: identification number, association number (primary set), upper-level association number (address basis), description;

[0108] 4. Province, city, autonomous region, or municipality: identification number, association number (address basis), and title;

[0109] 5. City and county: identification number, association number (address basis), and title;

[0110] 6. Townships and sub-districts: identification number, association number (address basis), and title;

[0111] 7. House number: identification number, association number (address basis), house number;

[0112] 8. Enterprises and institutions: identification number, association number (address basis), name, and name description;

[0113] 9. Relationship table: association number, relationship description (describes the direct relationship between the upper and lower levels of the address).

[0114] Note: The above "identification numbers" are all automatically generated; 4, 5, and 6 can be generated by querying from item 3.

[0115] Basic attributes of the organization

[0116] 1. Organizational basis: identification number, name, description, remarks, entry person, entry time;

[0117] 2. Title: identification number, association number (organizational basis), title, title description, and start and end dates of the title description;

[0118] Organization Extended Attributes

[0119] 1. Address: identification number, association number (the smallest basic unit of the address), and validity period;

[0120] 2. Communication: identification number, association number (organizational basis), communication number, number description; Note: Communication numbers include "telephone, fax, email, website, official account, blog, video account, etc."

[0121] 3. Certificates: Identification number, association number (organizational basis), association number (archival basis), certificate name, certificate description; Note: Institutional approval document, institution code certificate, institution establishment management certificate, award certificates, quality and qualification certificates, etc.

[0122] 4. Upper-level relationship table: identification number, association number (organizational basis), association number (upper-level organizational basis), and relationship description.

[0123] 5. Organization classification: identification number, association number (organization basis), association number (organization classification);

[0124] 6. Organization description: identification number, classification, standard (source, basis), description;

[0125] Note: Classifications are derived from various relevant national administrative guidance documents, local documents, daily agreements, etc., including industry, scale, and region. An organization can have multiple classification options (multiple classification records) for easy retrieval.

[0126] Basic properties of object collections

[0127] 1. Basics: identification number, association number (primary set), name of the object, description of the object;

[0128] Object collection extended attributes

[0129] 1. Specifications and models: identification number, association number (primary set), production date, unit price;

[0130] 2. Purpose: identification number, association number (primary set), unit, quantity, user, and description of purpose;

[0131] 3. Value: identification number, association number (primary set), quantity, price, description;

[0132] 4. Time: identification number, association number (collection of objects), purchase time, and after-sales service time.

[0133] Basic properties of event collection

[0134] 1. Basics: identification number, association number (primary set), item name, item description, and remarks.

[0135] Event Collection Extended Properties

[0136] 1. Item category: identification number, association number (primary set), category name, standards (source, basis, approval documents, etc.);

[0137] 2. Event time: identification number, association number (primary set), event deadline (start and end time), and remarks;

[0138] 3. Funds for the transaction: identification number, association number (primary set), amount of funds, source of funds, description of funds, etc.;

[0139] 4. Stakeholders: Identification number, association number (primary set), legal person (natural person set identification number), stakeholder (natural person set identification number), ID number (ID photo), description of the person, and remarks;

[0140] 5. Matter related address: identification number, association number (primary set), association number (address set identification number), construction location (detailed address), construction scale (area), description, etc.

[0141] 6. Stakeholder organizations: identification number, association number (primary set), stakeholder organization (organization set identification number), stakeholder organization description, stakeholder organization certificates (business license, certification, etc.);

[0142] 7. Matter stakeholders: identification number, association number (primary set), matter stakeholders (object set identification number), matter stakeholder description, stakeholder basis (transfer order, etc.).

[0143] The method of this embodiment utilizes natural object data analysis to abstract the commonalities and natural attributes of metadata, enabling more granular refinement and analysis, thus enabling flexible data combinations to describe different objects. This facilitates both real-world business applications and the mining and analysis of dynamic big data, providing strong foundational data support for decision-making applications.

[0144] Please refer to Figure 4 , which shows a flowchart of a cross-domain database migration method provided by an embodiment of the present application.

[0145] like Figure 4 As shown, in step 401, for each item from the original domain database, an original database corresponding to the original domain and including multiple types of metadata is obtained, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the original database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the original domain and an extended attribute table of at least one type of metadata;

[0146] In step 402, basic attribute tables of various items and corresponding metadata types and extended attribute tables of at least one metadata type required for the domain database to be migrated are prepared in advance;

[0147] In step 403, when there is at least one item required by the database of the domain to be migrated in the original database, the database to be migrated corresponding to the domain to be migrated is prepared by utilizing the items already existing in the original database and the corresponding basic attribute tables of multiple categories of metadata and the extended attribute tables of at least one category of metadata, combined with the items of the pre-prepared migration domain database and the corresponding basic attribute tables of multiple categories of metadata and the extended attribute tables of at least one category of metadata.

[0148] The method of the embodiment of the present application establishes an original database corresponding to five types of metadata for each project in the original field. For the projects to be migrated, a database to be migrated corresponding to the five types of metadata is prepared in advance, and then the migration and integration of the original database is performed. This can make the migration convenient, the migration effect is good, and subsequent other processing is also more convenient.

[0149] The following describes some problems encountered by the inventor in the process of implementing the present invention and a specific embodiment of the solution finally determined, so that those skilled in the art can better understand the solution of the present application.

[0150] In the process of implementing this application, the inventors found that the defects in the existing technology are mainly caused by the following reasons: in the data management model of traditional information systems, the object boundaries are determined in the process of digitizing physical objects based on determined business needs.

[0151] Because the boundaries of objects are defined and the needs of different businesses are different, the data between different information systems are independent of each other and cannot integrate each other's data resources; the boundaries of objects mean that when business needs change, the entire information system needs to be redesigned, and the change process of physical objects cannot be recorded and displayed.

[0152] The problems caused by these defects are long-standing problems in this field.

[0153] The hyper-converged database of the embodiment of the present application adopts a natural object metadata analysis method to reconstruct the data structure. By abstracting the commonalities and natural attributes of metadata, it subdivides the five most basic metadata categories of people, places, things, objects, and organizations, independently and simplifies the original complex structured data, and then recombines the metadata of the five basic data sets according to the application requirements of the "things" to form a new understanding of natural objects. The embodiment of the present application is not to arrogantly use information technology to show the results of human understanding of nature, but to use information technology as a tool to promote the process of human gradual understanding of nature. Ultimately, the purpose of the embodiment of the present application is to achieve a "holographic, full life cycle, and full ecological" understanding of natural objects.

[0154] This is very similar to the evolution of the biological world, which has evolved from simple to complex organisms. Hyperconverged databases follow a similar path, evolving from relational databases to various specialized databases, then to the reconstruction of metadata for natural objects, ultimately evolving into a complex new species: a hyperconverged basic information data management platform.

[0155] As big data becomes increasingly prominent as a strategic resource, people are increasingly aware that the biggest obstacle hindering its development is a renewed understanding of data itself. Natural, borderless metadata governance and a metadata-driven application architecture enable the overall development of basic data information management for big data, providing a new mindset and approach to managing complex big data systems.

[0156] Looking at the development of customized software development applications, although it is gradually adapting to the adaptive application customization development of technologies such as big data, the Internet, and the Internet of Things, it still cannot truly meet actual application needs.

[0157] In order to improve the practicality, adaptability and scalability of the software system, we will adopt the "metadata-driven platform application" architecture to realize the overall construction of the basic information platform.

[0158] Every application can be divided into metadata and metadata-driven applications. Therefore, we will start with metadata, abstracting its commonalities and natural attributes, and then construct metadata resources. This includes the fundamental metadata for the "five elements of a smart city": people, places, events, objects, and organizations.

[0159] Metadata is multi-dimensional, spatial resource data. The actual application of users is a service-oriented data application platform that applies metadata in different dimensions and spaces driven by metadata.

[0160] When the system's data applications are expanded, the organizational structure description of the metadata is edited to implement application component processing of data changes, while adding metadata timestamp history; when the system's functions are expanded, it is implemented in the form of customized metadata-driven function expansion plug-ins, making the platform-customized system highly scalable.

[0161] Figure 5a shows a platform function planning topology diagram of an embodiment of the present application, Figure 5b 、 Figure 5c 、 Figure 5d 、 Figure 5e and Figure 5f The specific functional planning diagrams for natural person metadata, address metadata, organization metadata, object metadata, and event metadata are shown respectively. Among them, all input information includes the attributes of "enter, entry time, and remarks".

[0162] Basic Requirements

[0163] Log: login, browse, query, add, modify.

[0164] The identification of each record is automatically generated by the system as the unique identification of the record.

[0165] Remarks, entry person (the system automatically records the current operator), entry time (the current system time is automatically recorded) are the standard attributes and entry basis (entry data or entity data) required for each record.

[0166] When interactively inputting, try to use drop-down menus or column selection methods. When there are many options, you can use the first letter pinyin index; for manual input items, try to use standard formats to assist input (such as time format) to ensure the standardization of input data; prompt relevant entered information based on the content being entered.

[0167] Entered physical data (process data records, including photos, videos, recordings, etc.).

[0168] The main set structure table is shown in Table 1:

[0169] Table 1: Main collection structure table

[0170]

[0171] Subject: identification number, name, description, basis for entry.

[0172] Natural person metadata, see Figure 5b .

[0173] Natural collection information entry

[0174] 1. Natural person information entry method: In addition to the existing single input and batch import, image recognition and scanning recognition entry methods are added.

[0175] 2. Natural person information attributes: These attributes consist of "basic attributes" and "extended attributes." Basic attributes are fixed and unchanging. "Extended attributes" vary depending on individual circumstances, and some may be filled in while others may not. Additional attributes may be required. Therefore, the entered personal information attributes must be flexible to add and delete.

[0176] 3. Implement drop-down option input whenever possible, make full use of format restrictions to ensure the standardization of input data (such as date), and support copying and pasting from other text.

[0177] 4. Comparison and archiving: After the personnel information is entered, the pictures and tables are required to be uploaded for data comparison and archiving.

[0178] Table 2-1: Basic Information of Natural Persons

[0179]

[0180] Table 2-2: Natural Person Extended Attribute Information Table - Communication Information Table

[0181]

[0182] Address metadata, see Figure 5c .

[0183] The address information structure generally follows the YZT0127-2006 postal address information data structure. The address is location information. When expressing it, priority is given to location information (such as roads, house numbers, etc.), landmarks, and organizations involved.

[0184] Examples: country, province (municipalities, autonomous regions, prefectures, special administrative regions), city (prefectures, districts), counties, towns, villages, and house numbers.

[0185] Table 2-3: Basic address information table

[0186]

[0187] Table 2-4: Address extension information table - title information table

[0188]

[0189] Organization metadata, see Figure 5d .

[0190] 1. Organizational Structure: We recommend using a tree-like directory format to clearly and intuitively represent the organizational hierarchy. Manual entry is recommended for platform organizational structure development, as it reduces workload and allows for easy verification and comparison.

[0191] 2. Organizational Information Entry: Given the limited amount of organizational information, it is recommended to enter information individually or through image recognition or scanning into the corresponding table within the system. After entry, it is also required to upload charts for data comparison and archival retention.

[0192] 3. Organizational attributes: We recommend categorizing them into "basic attributes," which generally remain unchanged, and "extended attributes," which require flexible addition and deletion. Basic attributes should be entered using drop-down options whenever possible; extended attributes should support copying and pasting.

[0193] Table 2-5: Organization basic attribute information table

[0194]

[0195] Table 2-6: Organization Extended Attribute Information - Title Information Table

[0196]

[0197] Object data, see Figure 5e .

[0198] 1. Method for entering object collection information: In addition to the existing single input and batch import, image recognition and scanning recognition are added.

[0199] 2. Object collection information attributes: These attributes consist of "basic attributes" and extended attributes. Basic attributes are fixed and unchanging. "Extended attributes" may require some fields to be filled in, while others may not, depending on the specific object collection. Additional fields may be required. Therefore, the information attributes of the entered objects must be able to be flexibly added and deleted.

[0200] 3. Implement drop-down option input whenever possible, make full use of format restrictions to ensure the standardization of input data, and support copying and pasting from other text.

[0201] 4. Comparison and archiving: After entering the information of the object, the pictures and tables must be uploaded for data comparison and archiving.

[0202] Table 2-7: Basic attribute information table of objects

[0203]

[0204] Table 2-8: Object Extended Attribute Information - Title Information Table

[0205]

[0206] Event data, see Figure 5f .

[0207] 1. The platform inputs transaction information mainly including administrative and public institutions’ affairs information and various engineering project information.

[0208] 2. Method for entering event collection information: In addition to the existing single input and batch import, image recognition and scanning recognition entry methods are added.

[0209] 3. Transaction collection information attributes: These attributes consist of "basic attributes" and "extended attributes." Basic attributes are fixed and unchanging. "Extended attributes" vary depending on the transaction collection, and some may be filled in or not. Additional attributes may be required. Therefore, transaction collection information attributes must be flexible to add and delete.

[0210] 4. Implement drop-down option input whenever possible, make full use of format restrictions to ensure the standardization of input data, and support copying and pasting from other text.

[0211] 5. Comparison and archiving: After entering the information, the collected information requires uploading tables and pictures for data comparison and archiving.

[0212] Table 2-9: Basic attribute information table of event collection

[0213]

[0214] Table 2-10: Event Collection Extended Attribute Information - Fund Information Table

[0215]

[0216] The data interface implementation standard of the embodiment of this application refers to GB / T38672-202 "Basic Requirements for Information Technology Big Data Interfaces".

[0217] Today, smart city informatization is gradually eliminating information silos, promoting open data sharing, and focusing on the connections between data and information. However, informatization construction, driven by application needs, is still inevitable, resulting in widespread boundary-breaking and duplicative construction.

[0218] For example, the "teaching system management platform" manages the people, places, objects, organizations, and events involved in campus teaching. Its construction must be based on teaching requirements and needs, and its application after completion will also serve teaching. The "community comprehensive management information system" is a comprehensive information management system for the people, places, objects, organizations, and events involved in community life. Its construction is based on community management requirements, and its application after completion will serve the community. These two systems have overlapping management objects (people, objects, events, etc.) and some data. Data may overlap; system databases and operating systems may also be duplicated. In most existing systems, each system is built to meet specific application needs, and they are incompatible. This leads to duplication of construction and investment, from systems to data.

[0219] Another example is China Railway 12306 and the systems of major airlines. Although they have applied new technologies such as big data and the Internet, they still operate and provide independent services. This is the case with the duplication of data resources and the duplication of supporting application systems.

[0220] The unified basic data platform aims to address the challenges of data resource systems with boundary-based construction. It aims to be flexible, open, shared, accurate, timely, secure, and reliable, built on metadata that reflects natural attributes. This platform provides the underlying basic data support for increasingly complex and evolving application services.

[0221] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of combined actions, but those skilled in the art should be aware that the present invention is not limited by the order of the actions described, because according to the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention. In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0222] Please refer to Figure 6 , which shows a block diagram of a cross-domain database integration system provided by an embodiment of the present invention.

[0223] like Figure 6 As shown, the cross-domain database integration system 600 includes a first database creation program module 610 , a second database creation program module 620 and an integration program module 630 .

[0224] Among them, the first database establishment program module 610 is configured to establish a first database corresponding to the first field for each item from the first field database, which includes multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata all have corresponding basic attribute tables, and the first database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the first field and the extended attribute tables of at least one type of metadata; the second database establishment program module 620 is configured to establish a second database corresponding to the second field for each item from the second field database, wherein the second database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the second field and the extended attribute tables of at least one type of metadata; and the integration program module 630 is configured to integrate the first database and the second database to generate a unified database.

[0225] In some optional embodiments, the integration program module includes a basic merging program module (not shown in the figure) and an adding program module (not shown in the figure).

[0226] Among them, the basic merging program module is configured to, when the items in the first database are not exactly the same as the items in the second database, use one of the databases as the basic database and, based on the multiple categories of metadata, merge the basic attribute tables of the other database and the extended attribute tables corresponding to the items in the other database that are the same as those in the basic database into the corresponding basic attribute tables and / or extended attribute tables in the basic database; and the adding program module is configured to add the extended attribute tables corresponding to the items in the other database that are not included in the basic database to the basic database to generate a unified database.

[0227] Please refer to Figure 7 , which shows a block diagram of another cross-domain database integration system provided by an embodiment of the present invention.

[0228] like Figure 7 As shown, the cross-domain database integration system 700 includes a first database conversion program module 710 , a second database conversion program module 720 and a unified program module 730 .

[0229] Among them, the first database conversion program module 710 is configured to split each item from the first field database into a first database corresponding to the first field containing multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata all have corresponding basic attribute tables, and the first database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the first field and the extended attribute tables of at least one type of metadata; the second database conversion program module 720 is configured to split each item from the second field database into a second database corresponding to the second field, wherein the second database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the second field and the extended attribute tables of at least one type of metadata; and the unification program module 730 is configured to integrate the first database and the second database to generate a unified database.

[0230] Please refer to Figure 8 , which shows a block diagram of a cross-domain database migration system provided by an embodiment of the present invention.

[0231] like Figure 8 As shown, the cross-domain database migration system 800 includes an original database processing program module 810 , a pre-preparation program module 820 and a migration database forming program module 830 .

[0232] Among them, the original database processing program module 810 is configured to obtain, for each item from the original domain database, an original database containing multiple types of metadata corresponding to the original domain, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata all have corresponding basic attribute tables, and the original database includes the basic attribute tables of the multiple types of metadata corresponding to each item in the original domain and the extended attribute tables of at least one type of metadata; the pre-preparation program module 820 is configured to pre-prepare each item required for the database of the domain to be migrated and the corresponding basic attribute tables of the multiple types of metadata and the extended attribute tables of at least one type of metadata; and the migration database forming program module 830 is configured to, when there is at least one item required for the database of the domain to be migrated in the original database, use the items and the corresponding basic attribute tables of the multiple types of metadata and the extended attribute tables of at least one type of metadata already existing in the original database, combined with each item and the corresponding basic attribute tables of the multiple types of metadata and the extended attribute tables of at least one type of metadata in the pre-prepared migration domain database, to form the database to be migrated corresponding to the domain to be migrated.

[0233] It should be understood that Figure 6 、 Figure 7 and Figure 8 Modules and references documented in Figure 1 、 Figure 2 、 Figure 3 and Figure 4 Therefore, the operations and features described above for the method and the corresponding technical effects also apply to Figure 1 、 Figure 2 、 Figure 3 and Figure 4 The modules in it will not be described in detail here.

[0234] It is worth noting that the modules in the embodiments of this disclosure are not intended to limit the solutions of this disclosure. For example, the first database establishment program module can also be described as a module that establishes a first database corresponding to the first domain and containing multiple types of metadata for each item from the first domain database. Furthermore, related functional modules can also be implemented using a hardware processor. For example, the first database establishment program module can also be implemented using a processor, and this will not be discussed in detail here.

[0235] In some embodiments, an embodiment of the present invention provides a non-volatile computer-readable storage medium, which stores one or more programs including execution instructions, and the execution instructions can be read and executed by an electronic device (including but not limited to a computer, server, or network device, etc.) to execute any of the above-mentioned cross-domain database integration and migration methods of the present invention.

[0236] In some embodiments, an embodiment of the present invention further provides a computer program product, which includes a computer program stored on a non-volatile computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes any one of the above-mentioned cross-domain database integration and migration methods.

[0237] In some embodiments, an embodiment of the present invention also provides an electronic device comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform a cross-domain database integration and migration method.

[0238] Figure 9 FIG. 1 is a schematic diagram of the hardware structure of an electronic device for executing a cross-domain database integration and migration method provided by another embodiment of the present application. Figure 9 As shown, the device includes:

[0239] One or more processors 910 and memory 920, Figure 9 A processor 910 is taken as an example.

[0240] The device for executing the cross-domain database integration and migration method may further include: an input device 930 and an output device 940 .

[0241] The processor 910, the memory 920, the input device 930 and the output device 940 may be connected via a bus or other means. Figure 9 The bus connection is taken as an example.

[0242] Memory 920, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the cross-domain database integration and migration method in the embodiments of the present application. Processor 910 executes the non-volatile software programs, instructions, and modules stored in memory 920 to execute various server functional applications and data processing, thereby implementing the cross-domain database integration and migration method in the above-mentioned method embodiment.

[0243] The memory 920 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the cross-domain database integration and migration device, etc. In addition, the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 920 may optionally include a memory remotely located relative to the processor 910, and these remote memories may be connected to the cross-domain database integration and migration device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0244] The input device 930 can receive input digital or character information and generate signals related to user settings and function control of the cross-domain database integration and migration device. The output device 940 can include a display device such as a display screen.

[0245] The one or more modules are stored in the memory 920 , and when executed by the one or more processors 910 , perform the cross-domain database integration and migration method in any of the above method embodiments.

[0246] The above-mentioned product can execute the method provided in the embodiment of this application, and has the functional modules and beneficial effects corresponding to the execution method. For technical details not fully described in this embodiment, please refer to the method provided in the embodiment of this application.

[0247] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0248] Through the description of the above embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a general hardware platform, or of course, hardware. Based on this understanding, the essence of the above technical solution, or the portion that contributes to the relevant technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for causing a computer device (such as a personal computer, server, or network device) to execute the methods described in each embodiment or certain portions of the embodiments.

[0249] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for integrating cross-domain databases, comprising: For each item from a first domain database, a first database corresponding to the first domain is established, comprising multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, the first database comprising the basic attribute tables of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata, wherein the basic attribute table stores core, invariant fields of the metadata, and the extended attribute table stores dynamically variable fields of the metadata; For each item from the second domain database, a second database corresponding to the second domain is established, wherein the second database includes a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item in the second domain, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; integrating the first database and the second database to generate a unified database; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The method also includes implementing functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

2. The method according to claim 1, wherein Integrating the first database and the second database to generate a unified database includes: When the items in the first database are not identical to the items in the second database, Taking one of the databases as the base database, based on the multiple types of metadata, each basic attribute table of the other database and the extended attribute table corresponding to the same item in the other database as that in the base database are merged into the corresponding basic attribute table and / or extended attribute table in the base database; The extended attribute tables corresponding to the items in the other database that are not included in the basic database are added to the basic database to generate a unified database.

3. The method according to claim 1, wherein The integrating the first database and the second database comprises: When the items of the first database are identical to the items of the second database, the basic attribute table and at least one extended attribute table corresponding to each item are merged to generate a unified database.

4. A method for integrating cross-domain databases, comprising: For each item from the first domain database, split it into a first database corresponding to the first domain and including multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the first database includes the basic attribute table of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata, wherein the basic attribute table stores core invariant fields of the metadata, and the extended attribute table stores dynamically variable fields of the metadata; For each item from the second domain database, split it into a second database corresponding to the second domain, wherein the second database includes a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item in the second domain, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; integrating the first database and the second database to generate a unified database; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The method also includes implementing functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

5. A cross-domain database migration method, comprising: For each item from the original domain database, an original database corresponding to the original domain and containing multiple types of metadata is obtained, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the original database includes the basic attribute table of the multiple types of metadata corresponding to each item in the original domain and an extended attribute table of at least one type of metadata, wherein the basic attribute table stores core invariant fields of the metadata, and the extended attribute table stores dynamically variable fields of the metadata; Prepare in advance the items required by the database to be migrated and the corresponding basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the original database contains at least one item required by the database for the domain to be migrated, the database to be migrated corresponding to the domain to be migrated is created by using the items already in the original database and the corresponding basic attribute tables of multiple types of metadata and the extended attribute tables of at least one type of metadata, combined with the items in the pre-prepared database for the migration domain and the corresponding basic attribute tables of multiple types of metadata and the extended attribute tables of at least one type of metadata; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The method also includes implementing functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

6. A cross-domain database integration system, comprising: A first database establishment program module is configured to establish, for each item from a first domain database, a first database corresponding to the first domain and comprising multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, the first database including the basic attribute tables of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; a second database establishment program module configured to establish a second database corresponding to the second domain for each item from the second domain database, wherein the second database includes a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item in the second domain, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; an integration program module configured to integrate the first database and the second database to generate a unified database; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The system is also used to implement functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

7. The system according to claim 6, wherein: The integration program module is further configured to: a basic merging program module configured to, when items in the first database are not identical to items in the second database, use one of the databases as the base database and, based on the multiple categories of metadata, merge basic attribute tables of the other database and extended attribute tables corresponding to items in the other database that are identical to those in the base database into corresponding basic attribute tables and / or extended attribute tables in the base database; An additional program module is configured to add the extended attribute table corresponding to the items in the other database that are not included in the basic database to the basic database to generate a unified database.

8. A cross-domain database integration system, comprising: A first database conversion program module is configured to split each item from a first domain database into a first database corresponding to the first domain and including multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, the first database including the basic attribute tables of the multiple types of metadata corresponding to each item in the first domain and an extended attribute table of at least one type of metadata, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; a second database conversion program module configured to split each item from a second domain database into a second database corresponding to the second domain, wherein the second database includes a basic attribute table of the multiple types of metadata corresponding to each item in the second domain and an extended attribute table of at least one type of metadata, the basic attribute table storing core invariant fields of the metadata, and the extended attribute table storing dynamically variable fields of the metadata; a unified program module configured to integrate the first database and the second database to generate a unified database; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The system is also used to implement functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

9. A cross-domain database migration system, comprising: An original database processing program module is configured to obtain, for each item from the original domain database, an original database corresponding to the original domain containing multiple types of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein each of the metadata has a corresponding basic attribute table, and the original database includes the basic attribute table of the multiple types of metadata corresponding to each item in the original domain and an extended attribute table of at least one type of metadata, wherein the basic attribute table stores core invariant fields of the metadata, and the extended attribute table stores dynamically variable fields of the metadata; A pre-preparation program module configured to pre-prepare various items required by the domain database to be migrated and corresponding basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; The migration database forming program module is configured to, when at least one item required by the database for the domain to be migrated exists in the original database, use the items already existing in the original database and the corresponding basic attribute tables of multiple types of metadata and the extended attribute tables of at least one type of metadata, combined with the items in the pre-prepared migration domain database and the corresponding basic attribute tables of multiple types of metadata and the extended attribute tables of at least one type of metadata, to form a database for the domain to be migrated corresponding to the domain to be migrated; Both the basic attribute table and the extended attribute table have timestamps. When two data items have different timestamps, the two items are identified as different data items. When integrating, the different data items are updated to the extended attribute table, and only the identical data items in the table are overwritten. The timestamp history of the metadata is increased when the data is extended. The system is also used to implement functional extensions through customized metadata, including: Analyzing the user's function expansion requirements, determining at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and an extended attribute table of at least one type of metadata; When the at least one item is a new item, a basic attribute table of the multiple types of metadata corresponding to the new item and an extended attribute table of at least one type of metadata are added to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table.

Images