CN114490568B

CN114490568B - Integration and migration methods and systems for cross-domain databases

Info

Publication number: CN114490568B
Application number: CN202111601276.1A
Authority: CN
Inventors: 娄健
Original assignee: Beijing Huacheng Zhiyun Software Co ltd
Current assignee: Beijing Huacheng Zhiyun Software Co ltd
Priority date: 2021-12-24
Filing date: 2021-12-24
Publication date: 2025-09-30
Anticipated expiration: 2041-12-24
Also published as: CN114490568A

Abstract

The invention discloses a cross-domain database integration and migration method and system, wherein the integration method comprises the steps of establishing a first database corresponding to a first domain and containing multi-class metadata for each item from the first domain, wherein the multi-class metadata comprises natural human metadata, organization metadata, address metadata, object metadata and event metadata, the metadata respectively have corresponding basic attribute tables, the first database comprises basic attribute tables corresponding to each item of the first domain and extended attribute tables of at least one class of metadata, establishing a second database corresponding to a second domain for each item from the second domain, and integrating the first database and the second database to generate a unified database. For the items in the first field and the second field, databases corresponding to five types of metadata are established first, then integration is carried out, so that the integration effect is better, and other processing is more convenient and rapid.

Description

Cross-domain database integration and migration method and system

Technical Field

The invention belongs to the technical field of databases, and particularly relates to a method and a system for integrating and migrating cross-domain databases.

Background

In the prior art, a relational database refers to a database that uses a relational model to organize data, and stores the data in rows and columns for the convenience of user understanding, the series of rows and columns of the relational database is called a table, and a group of tables forms the database. The user retrieves the data in the database by querying, which is an executable code that defines certain areas in the database. A relational model can be understood simply as a two-dimensional tabular model, and a relational database is a data organization consisting of two-dimensional tables and relationships between them.

1. The traditional relational database adopts a table storage mode, and data is stored in a row and column mode, so that the data is very convenient to read and inquire.

2. The storage structure comprises: the relational database stores data according to a structured method, each data table must be defined for each field (i.e., the table structure is defined first), and then the data is stored according to the table structure, this has the advantage that the reliability and stability of the whole data table is high, since the form and content of the data is defined before the data is stored, but it is problematic that it is very difficult to modify the structure of the data table if necessary once the data is stored.

3. The data is stored in the form of a minimum relation table in order to avoid duplication, normalize the data and fully utilize the storage space, so that the data management becomes clear and obvious, and the data management is mainly the case of a data table. If the situation of multiple tables is different, because the data relates to multiple data tables, complex relations exist among the data tables, and as the number of the data tables increases, the data management becomes more and more complex.

4. The expansion mode is that the relational database stores data in the data tables, the bottleneck of data operation appears in the operation of a plurality of data tables, the problem is more serious as the data tables are more, if the problem is to be alleviated, the processing capacity can only be improved, namely, computers with faster speed and higher performance are selected, and although the method can have a certain expansion space, the expansion space is limited, namely, the relational database only has longitudinal expansion capacity.

5. The relational database adopts a structured query language (namely SQL) to query the database, the SQL is already supported by various database manufacturers and becomes a standard of the database industry, the query mode can support CRUD (adding, querying, updating and deleting) operation of the database, the query mode has very powerful functions, and the SQL can accelerate query operation by adopting a similar index method.

6. Normalization, in the design and development process of a database, a developer usually faces to operate on one or more data entities (including an array, a list and nested data) at the same time, so that in a relational database, one data entity is generally divided into a plurality of parts, then the divided parts are normalized, and after normalization, the data entity is stored in a plurality of relational data tables, which is a complex process. Good messaging is a solution that has been developed with the development of software technology, and a number of software development platforms offer some simplicity, for example, the ORM layer (i.e., object relational mapping) can be used to map object models in databases into SQL-based relational databases and to translate data between different types of systems.

7. The relational database emphasizes ACID rule (atomicity (Atomicity), consistency (Consistency) Isolation (Isolation) persistence (Durability)), can meet data operation with higher transactional requirement or complex data query requirement, and can fully meet the requirements of high performance and operation stability of database operation. And the relational database emphasizes the strong consistency of the data, and has good support for the operation of the transaction. The relational database may control transaction atomicity fine granularity and may rollback transactions as soon as an operation is incorrect or needed.

8. The read-write performance is that the relational database emphasizes the consistency of data very much and has great cost for reducing the read-write performance, and the relational database stores data and processes the data very well, but the efficiency becomes poor once the relational database processes massive data, and particularly the performance is very reduced when the relational database encounters high concurrency read-write.

9. The relational databases are commonly known as Oracle, SQLSERVER, DB, mysql, and most relational databases except Mysql need to pay a high price if used, and even free Mysql performance is subject to a number of limitations.

The process of relational database design may be generally divided into seven phases of four phases.

(1) The user demand analysis period is mainly used for knowing and analyzing the functional demands and the application demands of users on data, and is the basis of the whole design process, and the success and failure of the whole database application system design are related.

(2) The database design period is mainly to integrate, generalize and abstract the user demands to form a data model independent of a specific DBMS, and the data model can be represented by an entity-connection model, and then is converted into a group of relation modes supported by a selected relational database management system RDBMS and a physical structure suitable for an application environment is selected for the relation modes, wherein the physical structure comprises a storage structure and an access method.

(3) The database implementation period comprises a database structure creation stage and an application behavior design and implementation stage, and is used for creating a database, creating a table, creating an index, creating a cluster and the like according to a physical model of the database.

(4) And in the database operation and maintenance stage, the last stage is that the database application system can be put into formal operation after trial operation.

In the process of designing a relational database, the following principles are followed, so that the storage efficiency, data integrity and expandability of the database can be improved.

1. Naming normalization

In the conceptual model design, the structure of the entity, attribute and related table is unified. For example, in the database design, students Sstudent are designated, the students are exclusively designated as the students, and the related attributes include the number, name, sex, birth month and the like, and the type, length, value range and the like of each attribute are determined, so that the problems of homonymy, heteronymy, synonym, attribute characteristics, structural conflict and the like can be avoided in naming.

2. Consistency and integrity of data

Constraints such as domain integrity, entity integrity, reference integrity and the like can be adopted in the relational database to meet the consistency and integrity of data, and the constraint is realized by check, default, null, a primary key and a foreign key.

3. Data redundancy

The data in the database should be reduced as much redundancy as possible, which means that duplicate data should be reduced to a minimum. For example, if the telephones of a staff member of a department are stored in different tables, and if the telephone number of the staff member changes, the existence of redundant data requires updating operation on a plurality of tables, and if a table is ignored unfortunately, the data is inconsistent. There must be as little redundancy in the database design as possible.

4. Van theory

When designing a relational database, a good database mode is generally obtained by designing to meet a certain normal form, and 3NF is generally considered to achieve the best balance in terms of performance, expansibility and data integrity, so that the general database design requirement reaches 3NF, unreasonable parts in data dependence are eliminated, and finally the aim of enabling a relation to describe only one entity or one relation among entities is fulfilled.

The inventor finds that the data management mode has at least the following defects that information resources are difficult to integrate and share. The data management mode of the traditional information system does not plan data sharing from the beginning, so that great difficulties exist in information resource aggregation, integration, management, application and sharing among the information systems. Because of the independence of the business requirement departments, an information system with independent boundaries is established according to the determined business requirements, the effective integration of information resources is severely restricted, and an integrated information service system is difficult to construct. Therefore, the insufficient integration and sharing of the data accelerates the fragmentation, the striping and the islanding of the information, thereby further leading to the repeated collection of the information data and the repeated construction of an information system, and lacking a unified data base.

Disclosure of Invention

Embodiments of the present invention aim to solve at least one of the above technical problems.

In a first aspect, an embodiment of the present invention provides a cross-domain database integration and migration method, including analyzing a function expansion requirement of a user, determining at least one item corresponding to the function expansion requirement and each attribute table corresponding to the at least one item, where the attribute tables include a basic attribute table of multiple types of metadata and an expansion attribute table of at least one type of metadata, the multiple types of metadata include natural personal metadata, organization metadata, address metadata, object metadata and event metadata, and adding, when the at least one item is a new item, the basic attribute table of the multiple types of metadata and the expansion attribute table of at least one type of metadata corresponding to the new item to a database, where the database is formed by each item and the corresponding basic attribute table and expansion attribute table.

In a second aspect, an embodiment of the present invention provides a cross-domain database integration and migration system, including an analysis program module configured to analyze a function expansion requirement of a user, determine at least one item corresponding to the function expansion requirement and each attribute table corresponding to the at least one item, where the attribute table includes a basic attribute table of multiple types of metadata and an expansion attribute table of at least one type of metadata, the multiple types of metadata includes 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 item is a new item, the basic attribute table of the multiple types of metadata and the expansion attribute table of at least one type of metadata corresponding to the new item to a database, where the database is formed by each item and the corresponding basic attribute table and expansion attribute table.

In a third aspect, an embodiment of the present invention provides an electronic device, including at least one processor, and a memory communicatively coupled to the at least one processor, where the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to perform any of the above-described cross-domain database integration and migration methods of the present invention.

In a fourth aspect, embodiments of the present invention provide a storage medium having stored therein one or more programs including execution instructions that are readable and executable by an electronic device (including, but not limited to, a computer, a server, or a network device, etc.) for performing any of the above-described cross-domain database integration and migration methods of the present invention.

In a fifth aspect, embodiments of the present invention also provide a computer program product comprising a computer program stored on a storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform any of the above methods of cross-domain database integration and migration.

According to the embodiment of the invention, the metadata are integrated into the basic attribute table and the extended attribute table of the five types of metadata according to the extended requirements of the clients, and the frames of the five types of metadata comprise various attributes to be extended, so that modeling and description of the extended requirements can be realized through flexible combination among the metadata. The relation between the expansion requirement of the client and the basic attribute table and the expansion attribute table of the five metadata is analyzed and determined, then the corresponding basic attribute table and expansion attribute table are added into the database, the expansion is simple, and the framework of the five metadata can flexibly cope with various expansion requirements.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a cross-domain database integration method according to an embodiment of the present invention;

FIG. 2 is a flow chart of another embodiment of a cross-domain database integration method of the present invention;

FIG. 3 is a flow chart of yet another embodiment of a cross-domain database integration method of the present invention;

FIG. 4 is a flow chart of one embodiment of a cross-domain database migration method of the present invention;

FIG. 5a, FIG. 5b, FIG. 5c, FIG. 5d, FIG. 5e and FIG. 5f are schematic diagrams of metadata of a cross-domain database integration and migration method according to an embodiment of the present invention;

FIG. 6 is a block diagram of a cross-domain database integration system according to one embodiment of the invention;

FIG. 7 is a block diagram of a cross-domain database integration system according to another embodiment of the invention;

FIG. 8 is a block diagram of a cross-domain database migration system of the present invention;

Fig. 9 is a schematic structural diagram of an embodiment of an electronic device of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.

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

In the present invention, "module," "device," "system," and the like refer to a related entity, either hardware, a combination of hardware and software, or software in execution, as applied to a computer. In particular, for example, an element may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. Also, the application or script running on the server, the server may be an element. One or more elements may be in processes and/or threads of execution, and elements may be localized on one computer and/or distributed between two or more computers, and may be run by various computer readable media. The elements may also communicate by way of local and/or remote processes in accordance with a signal having one or more data packets, e.g., a signal from one data packet interacting with another element in a local system, distributed system, and/or across a network of the internet with other systems by way of the signal.

Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," comprising, "or" includes not only those elements but also other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising" does not exclude the presence of additional identical elements in a process, method, article, or apparatus that comprises the element.

The embodiment of the application provides a cross-domain database integration method and a migration method, which are used for integrating and migrating the cross-domain database. It should be noted that, although the definitions of the first domain and the second domain are used in the following embodiments, those skilled in the art will understand that the first domain and the second domain generally refer to different application domains, and the first domain and the second domain are not limited to only two domains, but may be integrated and migrated with each other to highlight different domains, and may also have multiple domains for different applications in the social and ecological environments. For example, for all existing application systems in different industries, each application system has a corresponding database, and if data integration or migration is required, the application systems can be implemented by adopting the technical scheme of the embodiment of the present application, which is not described herein.

Referring to fig. 1, a cross-domain database integration method according to an embodiment of the invention is shown.

As shown in fig. 1, in step 101, for each item from a first domain database, a first database corresponding to a first domain is established, wherein the multi-class metadata includes natural human metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata each has a corresponding basic attribute table, and the first database includes a basic attribute table of the multi-class metadata and an extended attribute table of at least one kind of metadata corresponding to each item of the first domain;

in step 102, for each item from a second domain database, establishing a second database corresponding to a second domain, wherein the second database comprises a base attribute table of the multi-class metadata and an extended attribute table of at least one class metadata corresponding to each item of the second domain;

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

In this embodiment, the first field may be, for example, a water conservancy field, the second field may be, for example, an agricultural reclamation field, for each item of the water conservancy field database, a water conservancy database containing metadata of multiple types is first built, for example, in the water conservancy field, an employee information maintenance table may exist, including name, age, sex, contact, home address, etc. of an employee, then a basic attribute table and an extended attribute table corresponding to the age, contact, home address corresponding to the metadata are first built, then these data may be transferred to the basic attribute table and the extended attribute table corresponding to the metadata, the data of name and sex may be transferred to the basic attribute table, and the data of other attributes may be transferred to the corresponding extended attribute table, so that the building of tables and the transferring of data of other metadata of multiple types are equally available. Further, for some items, the metadata of multiple types may be simultaneously corresponding, then the metadata of multiple types may be split first, and then corresponding basic attribute tables and extended attribute tables are respectively established for data integration. The database in the second field, such as the agricultural reclamation field, is processed as above, and the database can be integrated and unified by establishing the same database structure for the databases in different fields and integrating the data into the same database structure.

According to the method provided by the embodiment of the application, the databases corresponding to the five types of metadata are established for the items in the first field and the second field, and then the metadata are integrated, so that the integration effect is better, and other processing is more convenient and rapid. Because the five types of metadata comprise all attributes, different projects and applications can be flexibly combined by using the five types of metadata, the databases in different fields are established with a basic attribute table and an extended attribute table corresponding to the five types of metadata, and finally, the integration of different databases can be realized, thereby facilitating the subsequent operations such as adding, deleting, modifying and the like to the integrated databases.

Among other things, in some alternative embodiments, various metadata are described as follows:

(1) Natural person metadata

Natural people are important factors in any informatization system, and are also factors with extremely high repetition probability when data of each system is shared. How to realize the basic information data sharing of people and how to realize the accurate, credible and high-timeliness of the data information of people. Meanwhile, how to cope with rapid and flexible changes in organization adjustment and personnel adjustment is a challenge for the application service system to the elements of the person.

The natural person management is divided into person basic information and extended information management, and the change of the adjustment personnel of the mechanism is flexible change of personnel in the system.

The management of natural people needs to complete the recording of different forms of personnel, and the recording attribute of various related attributes (such as telephone, title, job title and the like) of different personnel is required to be increased or decreased at any time, and meanwhile, the recording of information of composite attributes (a certain attribute has a plurality of corresponding contents, such as telephone, certificate and the like) is required, so that the system is convenient for comprehensive collection and management of personnel information.

(2) Address metadata

Addresses are related to various systems, are important system elements, and along with popularization and use of system applications, structured data information and semi-structured non-standardized information exist in the system. The application of these data is difficult to satisfy, adapt to the flexible and variable data application of the system. Therefore, the system design adopts address basic information and extension information for management.

(3) Organizing metadata

An organization is a social entity consisting of several individuals or groups with a common goal and a certain boundary. It comprises three meanings:

1) The organization is a social entity which is formed by reasonably matching people, wealth and things into a whole and keeping relative stability.

2) Organizations must have a common goal that is recognized and struggled with by members of the organization.

3) The organization must maintain a clear boundary to distinguish from other organizations and external environments.

The organization structure is required to be set and recorded according to common institutions and departments, and meanwhile, the requirements of mechanism innovation on flexible increase, decrease and change of the organization structure and temporary working mechanism setting are met. Therefore, the system design adopts organization basic information and extension information for management.

(4) Object metadata

An object refers to an objective object incorporated into a basic information management platform. The range of the materials is extremely wide, and the application is extremely complex. Nowadays, big data and the age of the internet of things are subjects of information management, and are managed objects. The objects are connected, and the objects are the core and the foundation in case of interconnection.

The basic information management platform is used for identifying the all-in-one object by using an identification number and simultaneously carrying out the essential description of the object. The management of the objects adopts a basic information and expansion information mode for management. The use of the object is required to be flexibly applied according to the business application of the user. The substance is constant and the application is variable.

(5) Event metadata

What is meant is the temporal change in the spatial distribution of mass. Since the substance is spatially distributed in mass, this can also be defined as the change of the substance over time. The matters related are relatively wide. Generally refers to social and natural things, matters, phenomena, conditions, etc.

The basic information management platform is a series of actions such as informatization management, informatization analysis, informatization decision support and the like according to the actual application and the requirements of users.

The same is true of entering the database, managing by adopting basic information and extension information, representing by identification numbers, and managing variable information in time sequence. The things are the application and extension of the other four elements of 'people, places, things and organizations'.

Referring to fig. 2, a flowchart of another cross-domain database integration method according to an embodiment of the application is shown. This flowchart is primarily a flowchart further defined for step 103 "integrate the first database and the second database, generating a system database" of fig. 1.

As shown in fig. 2, in step 201, when the items of the first database are not identical to the items of the second database, using one database as a base database, merging each base attribute table of the other database and an extended attribute table corresponding to the same item as the base database in the other database into a corresponding base attribute table and/or extended attribute table in the base database based on the multi-class metadata;

in step 202, an extended attribute table corresponding to an item in the other database, which is not included in the base database, is added to the base database, and a unified database is generated.

For example, the water conservancy database and the agricultural reclamation database have a plurality of data which are overlapped, after the data are integrated in the mode, the overlapped data are stored only once, so that repeated construction and redundancy of the integrated database are greatly reduced, and the situation that a plurality of data are to be updated in the subsequent updating of the data is avoided. The complex relationship exists among the data tables because the data relates to a plurality of data tables, and the data management is more and more complex along with the increase of the number of the data tables.

The method of the embodiment performs the combination and the addition of the table based on one database during the integration, and has simple processing and good integration effect. Because the integration is carried out on the basis of five types of metadata, only tables, such as a basic attribute table and an extended attribute table, which are not in a basic database are needed to be added in the integration process, and then data are migrated, the integrated unified database has no repeated construction of data resources, redundancy is reduced, and various adding, deleting and modifying operations on the database are more convenient than before the integration. The same attribute after integration only appears in one extended attribute table, so that the method is more friendly to data updating.

In some alternative embodiments, the integrating the first database and the second database includes merging the base attribute table and at least one extended attribute table corresponding to each item when the item of the first database is the same as the item of the second database, generating a unified database. Therefore, when integrating, the tables are directly combined under the condition that the items are the same, the processing is simple, the subsequent adding, deleting and changing of the unified database is not different from the adding, deleting and changing of the unified database in one database, the redundancy of the database can be greatly reduced, the updating of a certain attribute only involves one extended attribute table, the condition that the updating is required simultaneously because a certain data exists in a plurality of data tables can not happen, various extended attribute tables can be only associated with the basic attribute table of the corresponding metadata, the association relation among tables is greatly reduced, and the number is not caused along with the increase of the number of the data tables

The situation is managed to be more and more complex.

In some optional embodiments, the base attribute table and the extended attribute table are both provided with timestamps, when two data timestamps are different, the two data are determined to be different data, and when the two data are combined, only the identical data in the table are subjected to overlay processing. Thus, for two pieces of data with only different time stamps and other identical contents, the two pieces of data can be reserved as different data at the same time, and only the identical data is subjected to covering processing. For example, if a phone call and a WeChat exist before and the WeChat needs to be updated, the contact information of a certain person in the metadata of the natural person is directly covered and processed, if the phone call and the WeChat do not belong to the same contact information with the phone call and the WeChat before and the WeChat needs to be updated, the contact information of the tremble number can be directly updated into the contact information expansion attribute table.

Referring to fig. 3, a flowchart of yet another cross-domain database integration method according to an embodiment of the application is shown.

As shown in fig. 3, in step 301, for each item from a first domain database, splitting into a first database corresponding to a first domain, wherein the multi-class metadata includes natural human metadata, organization metadata, address metadata, object metadata, and event metadata, wherein the metadata each has a corresponding base attribute table, and the first database includes a base attribute table of the multi-class metadata and an extended attribute table of at least one class metadata corresponding to each item of the first domain;

Splitting, in step 302, each item from a second domain database into a second database corresponding to a second domain, wherein the second database comprises a base attribute table of the multi-type metadata and an extended attribute table of at least one type of metadata corresponding to each item of the second domain;

in step 303, the first database and the second database are integrated to generate a unified database.

According to the method provided by the embodiment of the application, aiming at the items in the first field and the second field, as the databases of the five types of metadata are finer-granularity databases, each extended attribute table of the basic attribute table only stores one attribute, the extended attribute tables can be split into databases corresponding to the five types of metadata, and then the databases are integrated, so that the integration effect is better, and other processing is more convenient and faster. For example, when a table in the first field contains the name, sex, contact, home address, history, certificate and other attributes of the employee, the table can be corresponding to the natural metadata of the five types of metadata, the name and sex of the employee can be split into the basic attribute table of the natural metadata, the contact, home address, history, certificate and other attributes of the employee can be respectively split into the communication information table, address information table, history information table, certificate information table and other extended attribute tables, so that the splitting and extending of the basic attribute table and the extended attribute table of the table corresponding to the five types of metadata are completed. Because the databases in the first field and the second field are split and data migration is carried out on the basic attribute table and the extended attribute table corresponding to the five types of metadata, finally, the databases in the two fields are formed into the databases corresponding to the five types of metadata, and then, the databases in the two fields are integrated more conveniently, and the data redundancy can be reduced to the greatest extent in the integration process.

Because the database containing five types of metadata is finer granularity than the existing database, the description of things is more comprehensive, and almost all data can be corresponding to the five types of metadata, so that a unified database can be formed by splitting and integrating items.

Further, for the database of the existing application, the expansion of the database can be performed in the database of the original application system, so that the data of the original database is closer to the attribute requirements of five types of metadata, then the integration of the database is performed, and finally the migration application is performed according to different new applications.

In some alternative embodiments, the basic attribute table and the extended attribute table of each metadata are specifically described as follows:

nature person basic attribute information

1. A natural person basis (hereinafter referred to as a person basis, namely, an identification number, a correlation number (theme), a registered birth date (lunar calendar: year, month, day, time), a native place (correlation number address), notes, a person input and a time input;

2. Sex is identification number, association number (human basis), sex (male, female, degeneration, amphiprotic), start-stop time;

the identification numbers are automatically generated.

Nature person extended attribute information

1. Communication, namely an identification number, an associated number (person basis), a communication number (telephone, weChat, QQ, blog, mail, website, video number and the like), and a number description;

2. address, identification number, association number (person basis), association number (most basic unit in address), address description, start-stop time (2 fields are considered in design);

3. Title, identification number, association number (person basis), title name (technician, engineer, professor, registered constructor, registered accountant.+ -.), title description, title start-stop time;

4. The histories comprise identification numbers, a related number person basis), a related number (organization basis), a histories start and stop time and a proving person (a related person basis library and a histories description;

5. certificate, namely an identification number, a correlation number (person basis), a correlation number (archive), a certificate name, a certificate number, a certificate description and start-stop time;

6. Personal relationship, identification number, association number (personal basis), relationship description (father, son, father-in-law, couple, child, tertiary, classmates, trade friends, inmate, colleagues.

Address base attribute information

1. Address base of identification number Guan Lianhao (main set), representative name (repeated by one of administrative naming and naming, description

Address extension attribute information

2. Title, identification number, association number (master set), title (administrative, common name, short name, etc.), title description, title start-stop time;

3. Upper layer relation, namely an identification number, an association number (master set), an upper layer association number (address base) and description;

4. Province, municipality, and direct administration city, namely an identification number, an association number (address base) and a title;

5. City and county identification number, association number (address base), title;

6. villages and towns, streets, identification numbers, association numbers (address basis) and names;

7. Number of house number, identification number, association number (address base), number of house number;

8. The enterprise and public institution comprises an identification number, an association number (address base), a name and a name description;

9. relation table, relation number and relation description (the upper and lower level direct relation to which the address belongs).

The identification numbers are all automatically generated, and the 4,5 and 6 can be inquired and generated from the 3 rd item.

Organizing basic attributes

1. The organization basis comprises identification numbers, names, descriptions, remarks, person input and time input;

2. the title comprises an identification number, an association number (organization basis), a title description and a title description start-stop time;

Organization extension attributes

1. Address, identification number, association number (minimum basic unit of the address), effective time;

2. Communication, namely an identification number, an associated number (organization basis), a communication number and a number description, wherein the communication number comprises a telephone, a fax, a mailbox, a website, a public number, a blog, a video number and the like;

3. Certificate including identification number, association number (organization basis), association number (archive basis), certificate name, and certificate description, and note that organization wholesale, organization code certificate, organization compiling management certificate, winning certificate, and quality certificate;

4. And the upper-layer relation table comprises identification numbers, association numbers (organization basis), association numbers (upper-layer organization basis) and relation descriptions.

5. Tissue classification, namely an identification number, guan Lianhao (tissue basis) and an association number (tissue classification);

6. Organization description, identification number, classification, standard (source, basis), description;

The classification is derived from various related guidance files, local files, daily conventions and the like of national administration, and the industry, scale and region can be provided with a plurality of classification choices (a plurality of classification records) for an organization, so that the organization is convenient to search.

Object collection base attributes

1. The basis is an identification number, a correlation number (master set), a name of an object and a description of the object;

object set extension attributes

1. Specification model number, identification number, association number (master set), production date and unit price;

2. the purposes include identification number, association number (master set), unit, quantity, user and purpose description;

3. Value, identification number, association number (master set), quantity, price, description;

4. time, identification number, association number (collection), purchase time, after-market service time.

Event collection base attributes

1. Basis for identification number, association number (master set), item name, item description, remarks.

Event set extension attributes

1. Item category, identification number, association number (master set), category name, standard (source, basis, approval document, etc.);

2. item time, identification number, association number (master set), item deadline (start and end time), remarks;

3. the event funds comprise an identification number, an association number (master set), a funds amount, a funds source, a funds description and the like;

4. the transaction system person comprises an identification number, a correlation number (master collection), a transaction legal person (natural person collection identification number), a transaction system person (natural person collection identification number), an identity card number (identity card photo), a personnel description and remarks;

5. The transaction trunk address includes identification number, association number (master set), association number (address set identification number), construction site (detailed address), construction scale (area), description, etc.

6. Item stem organization, identification number, guan Lianhao (master set), item stem organization (organization set identification number), item stem organization description, stem organization license (business license, certificate, etc.);

7. the identification number, the association number (master batch), the item dry matter (object batch identification number), the item dry matter description and the dry matter basis (call list and the like).

According to the method, the nature-tending object data analysis is adopted, the commonality and nature attribute of metadata are abstracted, the refinement and analysis of finer granularity are achieved, and the flexible combination of data is achieved for describing different objects. The method is convenient for practical business application and mining and analyzing of big data under a change state. Providing a powerful support for basic data for decision making applications.

Referring to fig. 4, a flowchart of a cross-domain database migration method according to an embodiment of the application is shown.

As shown in fig. 4, in step 401, for each item from an original domain database, an original database corresponding to an original domain is obtained, wherein the multi-class metadata includes natural human metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata each has a corresponding basic attribute table, and the original database includes a basic attribute table of the multi-class metadata corresponding to each item of the original domain and an extended attribute table of at least one class of metadata;

In step 402, preparing a basic attribute table of each item and corresponding multi-class metadata required by a to-be-migrated domain database and an extended attribute table of at least one class of metadata in advance;

in step 403, when at least one item required by the to-be-migrated domain database exists in the original database, the to-be-migrated database corresponding to the to-be-migrated domain is manufactured by using the existing item in the original database, the basic attribute table of the corresponding multi-class metadata, and the extended attribute table of the at least one class metadata, and combining the items of the pre-prepared to-be-migrated domain database, the basic attribute table of the corresponding multi-class metadata, and the extended attribute table of the at least one class metadata.

According to the method provided by the embodiment of the application, the original database corresponding to the five types of metadata is established for each item in the original field, the database corresponding to the five types of metadata is prepared in advance for the item to be migrated, and then migration integration of the original database is carried out, so that migration is convenient, the migration effect is good, and other processes are more convenient and faster to follow.

The following description is given to better understand the solution of the present application by describing some problems encountered by the inventor in the process of implementing the present application and describing one specific embodiment of the finally determined solution.

The inventors have found that the drawbacks of the prior art are mainly caused by the fact that in the data management mode of a conventional information system, the object boundaries are determined during the digitizing of the physical object, starting from the determined traffic demand.

The boundary of the object makes the whole information system need to be redesigned when the service requirement is changed, and the change process of the physical object can not be recorded and displayed.

The problem caused by these defects is a long standing problem in this field.

The super-fusion database adopts an object metadata analysis method which tends to be natural, re-reconstructs the data structure, subdivides the metadata based on five types of people, places, things and things by abstracting the commonality, natural attribute and the like of the metadata, independently simplifies the original complex structured data, and then recombines the metadata of the five types of basic data sets according to the application requirement of the things to form the re-knowledge of the natural object. Instead of using informatization means to show the natural result of human beings, informatization is used as a tool to promote the process of gradually recognizing natural by human beings. Finally, the aim of the embodiment of the application is to achieve the cognition of 'holographic, full life cycle and full ecology' of a natural object.

This is very similar to the evolution of the biological world, which is evolving along a direction from simple to complex organisms. The super-fusion database is a thinking from relational databases to various special databases and to metadata reconstruction of natural objects, and finally develops a complex super-fusion basic information data management platform of new species.

With the increasing emphasis of big data as strategic resources, it is becoming more and more strongly appreciated that short boards, which restrict the big data from growing the most, are a readying of the data itself. The system is a natural and borderless architecture system for metadata management and metadata driving application, realizes the overall construction of basic data information management of big data, and provides a new thinking and a new means for managing a complex system of big data.

While development of software custom development application is gradually adapted to the custom development of big data, the Internet of things and other technologies, the development of software custom development application still cannot really meet the actual application requirements.

In order to improve the practicability, adaptability and expandability of the software system, the framework of the metadata driven platform application is adopted to realize the overall construction of the basic information platform.

Each application may be divided into metadata and metadata driven applications. Therefore, from metadata, commonalities, natural attributes and the like of the metadata are abstracted, and construction of metadata resources is carried out. Including people, places, things, and organisations "five elements of a smart city" base metadata.

The metadata is multidimensional and spatial resource data, and the actual application of the user is a service-oriented data application platform which is driven by the metadata and is applied to the metadata by different dimensions and different spaces.

When the data application of the system is expanded, changing application processing of the application component on the data is realized by editing the organization structure description of the metadata description, and the time stamp record of the metadata is increased; when the functions of the system are expanded, the system customized based on the platform has stronger expandability by customizing the function expansion plug-in driven by metadata.

Fig. 5a shows a topology of a platform function plan according to an embodiment of the present application, and fig. 5b, 5c, 5d, 5e and 5f show specific function plans of natural person metadata, address metadata, organization metadata, object metadata and event metadata, respectively. Wherein, all the input information comprises 'input person, input time and remark' attributes.

Basic requirements

Logging, browsing, querying, adding and modifying.

The identity of each record is automatically generated by the system as a unique identity of the record.

Remarks, recording people (the system automatically records the current operator), recording time (the current system time automatically records) as standard attributes and recording basis (recording data materials or entity data) which are necessary for each record.

The method comprises the steps of selecting a form of a drop-down menu or a list item as much as possible during interactive input, indexing by using initial pinyin when options are more, manually inputting the item as much as possible by using standard format auxiliary input (such as a time format), guaranteeing the specification of input data, and prompting relevant recorded information according to the content being recorded.

Entered entity data (process material records including photographs, videos, sound recordings, etc.).

The main set structure table is shown in table 1:

TABLE 1 Master set Structure Table

The theme is identification number, name, description and input basis.

Natural human metadata, see fig. 5b.

Natural set information entry

1. The natural person information input mode is to add a picture identification and scanning identification input mode besides the existing single input and batch input mode.

2. The natural person information attribute consists of a basic attribute and an extended attribute, wherein the basic attribute is fixed and unchanged, the extended attribute is filled in some cases and not filled in other cases according to different personnel conditions, and the filled-in possible attribute needs to be increased. Thus, the entered person information attributes need to be able to be flexibly added and deleted.

3. The drop-down option input is realized as far as possible, format limitation is fully utilized to ensure the specification (such as date) of input data, and copying and pasting by other characters are supported.

4. And (3) comparing and retaining files, namely uploading the graph and the table according to the recorded personnel information, and comparing the data and retaining files.

TABLE 2-1 Natural person basic information Table

TABLE 2-2 Natural person extended attribute information Table-communication information Table

Address metadata, see fig. 5c.

The address information structure generally follows the YZT0127-2006 postal address information data structure, the address is position information, and the position information (such as roads, house numbers and the like) is preferentially selected when expressed, and the landmark and the organization are involved.

Examples are national, province (directly administered city, municipality, state, district), city (ground, district), county and county, villages and towns, and house number cards.

TABLE 2-3 Address base information Table

TABLE 2-4 Address extension information Table-refer information Table

The metadata is organized, see fig. 5d.

1. The organization mechanism adopts a tree directory mode to suggest that the hierarchical relationship of the organization structure is intuitively and clearly represented. The construction suggestion of the platform organization is carried out by adopting a manual input mode, so that the workload is small, and the comparison is checked at any time.

2. And (3) inputting organization information, namely suggesting to input by adopting a single input mode or correspondingly inputting a table in a system by picture identification and scanning identification in view of less organization information. Meanwhile, the chart is required to be uploaded after the chart is input, and data comparison and file retention are carried out.

3. Organization attributes, suggestions are classified into basic attributes, which are not changed much in most cases, and extended attributes, which are required to be added and deleted flexibly. Basic attribute, which can realize drop-down option input as far as possible, and extended attribute, which can support copy and paste.

TABLE 2-5 organization basic Attribute information Table

TABLE 2-6 organization extension attribute information-title information table

The metadata, see fig. 5e.

1. The method for inputting the information of the object collection is that a picture identification and scanning identification input method is added besides the existing single input and batch input.

2. The object set information attribute consists of a basic attribute and an extended attribute, wherein the basic attribute is fixed and unchanged, the extended attribute is filled in some cases and not filled in other cases because of different object set conditions, and the filled possible attribute needs to be increased. Thus, the information properties of the entered items need to be able to be flexibly added and deleted.

3. The drop-down type option input is realized as far as possible, format limitation is fully utilized to ensure the specification of input data, and copying and pasting by other characters are supported.

4. And (3) comparing and retaining files, namely uploading the graph and the table according to the information requirement of the recorded objects, and comparing the data and retaining files.

TABLE 2-7 basic attribute information table of objects

Tables 2-8 extended attribute information-title information table of objects

The event metadata, see FIG. 5f.

1. The platform is used for inputting transaction information of administrative institutions and various engineering project information.

2. The method for inputting the information of the event collection is that a picture identification and scanning identification input method is added besides the existing single input and batch input.

3. The information attribute of the event set consists of a basic attribute and an extended attribute, wherein the basic attribute is fixed and unchanged, the extended attribute is filled in some cases and not filled in other cases according to different event set conditions, and the filled possible attribute needs to be increased. Thus, the entered event collection information attribute needs to be able to achieve flexible addition and deletion.

4. The drop-down type option input is realized as far as possible, format limitation is fully utilized to ensure the specification of input data, and copying and pasting by other characters are supported.

5. And (3) comparing and retaining files, namely uploading the table and the picture according to the recorded information of the event collection, and carrying out data comparison and file retaining.

TABLE 2-9 event set basic attribute information table

TABLE 2-10 event set extension attribute information-fund information table

The data interface execution standard of the embodiment of the application refers to GB/T38672-202 basic requirements of information technology big data interface.

At present, the informatization construction of the smart city gradually eliminates information islands, promotes open sharing of information data, and focuses on the association between the data and the information. However, the information construction which is guided by the application requirement is unavoidable, and the boundary construction generated by the information construction is similar to the repeated construction.

The system comprises a teaching system management platform, a community comprehensive management information system and a community comprehensive management information system, wherein the teaching system management platform is a teaching management platform for people, places, things, organizations and events of campus teaching, the construction needs to be carried out according to teaching requirements and demands, the established application is also service and teaching, the community comprehensive management information system is a comprehensive information management system for people, places, things, organizations and events of community living, the construction is carried out according to community management requirements, and the established application is service and community. The management objects (people, things, etc.) of the two systems and part of the data overlap. The data may overlap, the system database and the operating system may be repeated, and in most of the existing systems, only one set of applications can be built, and the systems cannot be mutually communicated. And repeated construction and repeated investment exist from the system to the data.

For example, the system of each large airline company such as China railway 12306, although the novel technologies such as big data and Internet are applied, the system still operates independently and serves independently, the repeated construction of data resources among the systems is carried out, and the repeated construction of the application system is carried.

A large-scale basic data platform aims at solving the problem of a data resource system with boundary construction, and pursues a flexible, variable, open-shared, accurate, high-timeliness, safe and reliable large-scale basic data platform which is constructed by metadata tending to natural attributes. Providing underlying data support for application services that are becoming more and more complex.

It should be noted that, for simplicity of description, the foregoing method embodiments are all illustrated as a series of acts combined, but it should be understood and appreciated by those skilled in the art that the present invention is not limited by the order of acts, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention. In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.

Referring to fig. 6, a block diagram of a cross-domain database integration system according to an embodiment of the invention is shown.

As shown in fig. 6, 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.

Wherein the first database creation program module 610 is configured to create, for each item from the first domain database, a first database corresponding to the first domain comprising a plurality of types of metadata, wherein the plurality of types of metadata comprises natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein the metadata each have a corresponding base attribute table, the first database comprises a base attribute table of the plurality of types of metadata and an extended attribute table of at least one type of metadata corresponding to each item of the first domain, the second database creation program module 620 is configured to create, for each item from the second domain database, a second database corresponding to the second domain, wherein the second database comprises a base attribute table of the plurality of types of metadata and an extended attribute table of at least one type of metadata corresponding to each item of the second domain, and the integration program module 630 is configured to integrate the first database and the second database to generate a unified database.

In some alternative embodiments, the integration program modules include a base merge program module (not shown) and an add program module (not shown).

The system comprises a base merging program module, an adding program module and a unified database, wherein the base merging program module is configured to merge each base attribute table of another database and an extended attribute table corresponding to the same item as the base database in the other database into the corresponding base attribute table and/or the extended attribute table in the base database based on the multi-class metadata by taking one database as the base database when each item of the first database is not completely identical with each item of the second database, and the adding program module is configured to add the extended attribute table corresponding to the item which is not contained in the base database in the other database into the base database so as to generate the unified database.

Referring to fig. 7, a block diagram of another cross-domain database integration system according to an embodiment of the invention is shown.

As shown in fig. 7, 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.

Wherein the first database conversion program module 710 is configured to split each item from the first domain database into a first database containing multiple types of metadata corresponding to the first domain, wherein the multiple types of metadata include natural person metadata, organization metadata, address metadata, object metadata, and event metadata, wherein the metadata each have a corresponding base attribute table, the first database includes a base attribute table of the multiple types of metadata corresponding to each item of the first domain and an extended attribute table of at least one type of metadata, the second database conversion program module 720 is configured to split each item from the second domain database into a second database corresponding to the second domain, wherein the second database includes a base attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to each item of the second domain, and the unifying program module 730 is configured to integrate the first database and the second database to generate unifying data.

Referring to fig. 8, a block diagram of a cross-domain database migration system according to an embodiment of the present invention is shown.

As shown in fig. 8, the cross-domain database migration system 800 includes an original database handler module 810, a pre-preparation module 820, and a migration database formation module 830.

The original database processing program module 810 is configured to acquire an original database containing multi-class metadata corresponding to an original domain for each item from the original domain database, wherein the multi-class metadata comprises natural human metadata, organization metadata, address metadata, object metadata and event metadata, wherein the metadata respectively comprise a corresponding basic attribute table, the original database comprises a basic attribute table of the multi-class metadata corresponding to each item of the original domain and an extended attribute table of at least one type of metadata, the pre-preparation program module 820 is configured to pre-prepare each item required by the domain database to be migrated and a basic attribute table of the corresponding multi-class metadata and an extended attribute table of the at least one type of metadata, and the migration database forming program module 830 is configured to make a class of the basic attribute table of the multi-class metadata and the extended attribute table of the at least one type of metadata by utilizing the item existing in the original database and the corresponding multi-class metadata when the item required by the domain database exists in the original database, and the pre-prepared item and the extended attribute table of the at least one type of the metadata to be migrated is combined with the pre-prepared item and the corresponding multi-class metadata.

It should be understood that the modules depicted in fig. 6, 7 and 8 correspond to the various steps in the methods described with reference to fig. 1,2, 3 and 4. Thus, the operations and features described above for the method and the corresponding technical effects are equally applicable to the modules in fig. 1,2, 3 and 4, and are not described here again.

It should be noted that the modules in the embodiments of the present disclosure are not limited to the solution of the present disclosure, for example, the first database creation program module, and may also be described as a module for creating, for each item from the first domain database, a first database containing metadata of multiple types corresponding to the first domain. In addition, the related functional modules may also be implemented by a hardware processor, for example, the first database creation program module may also be implemented by a processor, which is not described herein.

In some embodiments, embodiments of the present invention provide a non-transitory computer readable storage medium having stored therein one or more programs comprising execution instructions that are readable and executable by an electronic device (including, but not limited to, a computer, a server, or a network device, etc.) for performing any of the above-described cross-domain database integration and migration methods of the present invention.

In some embodiments, embodiments of the present invention also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform any of the above methods of cross-domain database integration and migration.

In some embodiments, the present invention further provides an electronic device comprising at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform cross-domain database integration and migration methods.

Fig. 9 is a schematic hardware structure of an electronic device for performing a cross-domain database integration and migration method according to another embodiment of the present application, where, as shown in fig. 9, the device includes:

one or more processors 910, and a memory 920, one processor 910 being illustrated in fig. 9.

The apparatus for performing the cross-domain database integration and migration method may further include an input device 930 and an output device 940.

The processor 910, memory 920, input device 930, and output device 940 may be connected by a bus or other means, for example in fig. 9.

The memory 920 is used as a non-volatile computer readable storage medium for storing non-volatile software programs, non-volatile computer executable programs, and modules, such as program instructions/modules corresponding to the cross-domain database integration and migration method in the embodiments of the present application. The processor 910 executes various functional applications of the server and data processing by running non-volatile software programs, instructions and modules stored in the memory 920, i.e., implements the cross-domain database integration and migration method of the above-described method embodiments.

The memory 920 may include a storage program area that may store an operating system, applications required for at least one function, and a storage data area that may store data created according to the use of the cross-domain database integration and migration device, etc. In addition, memory 920 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 920 optionally includes memory remotely located with respect to processor 910, which may be connected to cross-domain database integration and migration devices through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Input device 930 may receive input numeric or character information and generate signals related to user settings and function control of the cross-domain database integration and migration apparatus. The output device 940 may include a display device such as a display screen.

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

The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. Technical details not described in detail in this embodiment may be found in the methods provided in the embodiments of the present application.

The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

From the above description of embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus a general purpose hardware platform, or may be implemented by hardware. Based on such understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the related art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the method described in the respective embodiments or some parts of the embodiments.

It should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same, and although the present application has been described in detail with reference to the above-mentioned embodiments, it should be understood by those skilled in the art that the technical solution described in the above-mentioned embodiments may be modified or some technical features may be equivalently replaced, and these modifications or substitutions do not make the essence of the corresponding technical solution deviate from the spirit and scope of the technical solution 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 the step of integrating the first database and the second database to generate a unified database comprises:

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 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;

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;

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;

The system is also used to implement functional extensions through customized metadata, including:

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;

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 is 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;