Database expansion method and system

Abstract

The present invention discloses a database expansion method and system, wherein the method comprises: analyzing a user's functional expansion requirements, determining at least one item corresponding to the functional expansion requirements, and attribute tables corresponding to the at least one item. The attribute tables include basic attribute tables for multiple types of metadata and extended attribute tables for at least one of the metadata types. The multiple metadata types include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata. When the at least one item is new, the basic attribute tables for the multiple types of metadata and the extended attribute tables for the at least one metadata type corresponding to the new item are added to the database. By first analyzing and determining the relationships between the basic attribute tables and extended attribute tables for the five types of metadata, and then adding the corresponding basic attribute tables and extended attribute tables to the database, the expansion is relatively simple.

Description

Technical Field

[0001] The present invention belongs to the technical field of databases, and in particular relates to a database expansion method and system. 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 (i.e. SQL) to query the database. SQL has long been supported by various database manufacturers and has become the standard of 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 design and development of a database, 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 data operations with high transactional performance or complex data queries, and fully satisfying 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 when 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 the 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 schema 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 aforementioned data management model suffers from at least the following drawbacks: poor scalability. Traditional information systems reserve space during construction to accommodate changes in established business needs. However, this reserved space is always limited and can never address the ever-changing nature of real-world business needs. Once business needs change, modifying existing information systems can lead to significant confusion and errors, necessitating a complete redesign of the information system from the ground up to accommodate the new business needs. This results in extremely poor scalability of the traditional information system's data management model. 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 database expansion method, comprising: analyzing a user's functional expansion requirements, determining at least one item corresponding to the functional expansion requirements and each attribute table corresponding to the at least one item, 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, organizational metadata, address metadata, object metadata, and event metadata; when the at least one item is a new item, 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 item to the database, wherein the database is composed of each item and the corresponding basic attribute table and the extended attribute table.

[0029] In a second aspect, an embodiment of the present invention provides a database expansion system, comprising: an analysis program module, configured to analyze a user's functional expansion requirements, determine at least one item corresponding to the functional expansion requirements and each attribute table corresponding to the at least one item, 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; and an update program module, configured to, when the at least one item is a new item, add 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 item to the database, wherein the database is composed of each item 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 database expansion 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 database expansion 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 database expansion 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 A flowchart of an embodiment of a database expansion method of the present invention;

[0036] Figure 2 is a flowchart of another embodiment of the database expansion method of the present invention;

[0037] Figure 3a 、 Figure 3b 、 Figure 3c 、 Figure 3d 、 Figure 3e and 3f A schematic diagram of metadata of a database expansion method provided by one embodiment of the present invention;

[0038] Figure 4 A block diagram of a database expansion system of the present invention;

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

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] An embodiment of the present invention provides a database expansion method, which is applied to a database.

[0046] Please refer to Figure 1 , which shows a database expansion method provided by an embodiment of the present invention.

[0047] like Figure 1 As shown, in step 101, the function expansion requirements of the user are analyzed, and at least one item corresponding to the function expansion requirements and attribute tables corresponding to the at least one item are determined. The attribute tables include basic attribute tables of multiple types of metadata and extended attribute tables of at least one type of metadata. The multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata.

[0048] In step 102, 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.

[0049] In this embodiment, step 101 analyzes the customer's functional expansion requirements and maps them to at least one project and attribute tables corresponding to the at least one project, thereby digitizing the customer's functional expansion requirements. The attribute tables include basic attribute tables for multiple types of metadata and extended attribute tables for at least one of the metadata types. The multiple metadata types include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata. For example, if the customer's functional expansion requirement is to add a customer service department, the customer service department must first be broken down into projects corresponding to at least one of the five metadata types. For example, the personnel in the customer service department correspond to natural person metadata, the customer service department's organizational structure corresponds to organizational metadata, the customer service department's office address or other address information corresponds to address metadata, the items the customer service department requires correspond to object metadata, and the events the customer service department needs to handle correspond to event metadata. In this way, the customer's requirements can be broken down into multiple projects, and then the customer service department can be expanded by specifically adding corresponding tables to the five metadata types. Among them, the basic attribute table is usually only used to record basic information. For example, the basic attribute table of natural person metadata may only include name and gender. The extended attribute table is used to record extended attribute information, such as a person's contact information, title, resume, certificate, and relationship with other people. Each item can be recorded in the corresponding extended attribute table, and this application has no restrictions here.

[0050] Then, for step 102, if at least one of the projects is a new project, the basic attribute tables for the multiple types of metadata and the extended attribute tables for at least one type of metadata corresponding to the new project are added to the database. For example, if the database previously did not have a resume extended attribute table for the natural person metadata, and a new resume extended attribute table is needed for this project, then a resume extended attribute table can be expanded under the natural person metadata to record the resume information of the person in the new project. Similarly, if the database previously did not have a basic attribute table and corresponding extended attribute tables for object metadata, and the new project requires the establishment of a basic attribute table and corresponding extended attribute tables for object metadata, then the corresponding basic attribute table and extended attribute table can be added to the database. This application is not limited to this.

[0051] The method of this embodiment first analyzes and determines the relationship between at least one item corresponding to the customer's expansion requirements and the basic attribute table and extended attribute table of the five types of metadata, and then adds the corresponding basic attribute table and extended attribute table to the database. The expansion is relatively simple. Since the framework of the five types of metadata covers various attributes to be expanded, the expansion requirements can be modeled and described through flexible combinations of metadata, so various expansion requirements can be flexibly responded to.

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

[0053] (1) Natural person metadata

[0054] 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.

[0055] Natural personnel 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.

[0056] Natural person management requires the completion of different forms of personnel input, which must meet the requirements of various relevant attributes of different personnel (such as telephone number, title, job title, etc.) at any time. At the same time, it must also meet the requirements of compound attributes (a certain attribute has multiple corresponding contents, such as telephone number, certificate, etc.) information input, so as to facilitate the systematic and comprehensive collection and management of personnel information.

[0057] (2) Address metadata

[0058] 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.

[0059] (3) Organization metadata

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

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

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

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

[0064] 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.

[0065] (4) Object data

[0066] 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.

[0067] 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.

[0068] (5) Event data

[0069] "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.

[0070] 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.

[0071] 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.

[0072] Please refer to Figure 2 , which shows a flowchart of another database expansion method provided by an embodiment of the present application. Figure 1 The flow chart is further defined by additional steps.

[0073] like Figure 2 As shown, in step 201, when the at least one item is an old item in the database, the basic attribute tables and corresponding extended attribute tables of the at least one item and the old item are compared;

[0074] In step 202, the basic attribute table and / or the extended attribute table in the at least one project that are not included in the old project are added to the database.

[0075] In this embodiment, step 201 compares the basic attribute tables and extended attribute tables of at least one project with those of the old project. Then, in step 202, the basic attribute tables and / or extended attribute tables of at least one project that are not included in the old project are added to the database. For example, for the expansion requirement of the customer service department, the previous project already established basic attribute tables and extended attribute tables corresponding to multiple metadata. The current project simply adds the person-relationship extended attribute table for natural person metadata to the existing one. Therefore, only the person-relationship extended attribute table under the natural person metadata needs to be added.

[0076] The method of this embodiment compares the basic attribute table and extended attribute table of at least one project with the old project when expanding the old project, and then adds the basic attribute table and / or extended attribute table not included in the old project, thereby easily implementing the expansion of the old project.

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

[0078] Basic attribute information of natural persons

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

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

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

[0082] Natural person extended attribute information

[0083] 1. Communication: identification number, associated number (personal basis), communication number (phone, WeChat, QQ, blog, email, website, video account, etc.), number description;

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

[0085] 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;

[0086] 4. Resume: identification number, association number (person basis), association number (organization basis), resume start and end dates, references (affiliated personnel base database), and resume description;

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

[0088] 6. Personal relationships: identification number, association number (person basis), relationship description (father and son, father-in-law, husband and wife, children, uncle and nephew, classmates, poker buddies, cellmates, colleagues... multiple options are allowed), start and end time.

[0089] Basic address attribute information

[0090] 1. Address basis: identification number, association number (primary set), representative name (a duplication of administrative name and appellation), description

[0091] Address extended attribute information

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

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

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

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

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

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

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

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

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

[0101] Basic attributes of the organization

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

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

[0104] Organization Extended Attributes

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

[0106] 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."

[0107] 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.

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

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

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

[0111] 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.

[0112] Basic properties of object collections

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

[0114] Object collection extended attributes

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

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

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

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

[0119] Basic properties of event collection

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

[0121] Event Collection Extended Properties

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

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

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

[0125] 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;

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

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

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

[0129] 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, thereby enabling flexible data combinations to describe objects. This facilitates both real-world business applications and the mining and analysis of evolving big data, providing strong foundational data support for decision-making applications.

[0130] In some optional embodiments, the basic attribute table and the extended attribute table have database timestamps for recording the update time of each data item in the table. By recording the update time of the attribute table, the desired attribute table can be obtained according to the update time.

[0131] In some optional embodiments, after comparing the basic attribute tables and corresponding extended attribute tables of the at least one item with those of the old item, the method further includes: if the at least one item and the old item have different basic attribute tables and / or extended attribute tables, retaining in the database only the basic attribute tables and / or extended attribute tables corresponding to the data with the latest timestamp of the at least one item. If multiple update records of the same data exist in the attribute tables, which have different records, the latest update record is used for comparison with the at least one item, and the latest one is retained.

[0132] In a further optional embodiment, analyzing the user's function expansion request includes: obtaining a textual representation of the user's function expansion request, performing semantic analysis on the textual representation, and determining at least one item to be expanded and attribute tables corresponding to the at least one item based on the result of the semantic analysis. The user's function expansion request is analyzed by automated processing.

[0133] 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.

[0134] 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.

[0135] 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; because the boundaries of objects are defined, when business needs change, the entire information system needs to be redesigned, and the change process of physical objects cannot be recorded and displayed.

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

[0137] 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.

[0138] 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.

[0139] 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.

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] Figure 3a shows a platform function planning topology diagram of an embodiment of the present application, Figure 3b 、 Figure 3c 、 Figure 3d 、 Figure 3e and Figure 3f 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".

[0146] Basic Requirements

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

[0148] The identification of each record is automatically generated by the system (plus one) as the unique identification of the record.

[0149] 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.

[0150] 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; try to use standard formats to assist in inputting manual input items (such as time format) to ensure the standardization of input data; prompt relevant entered information based on the content being entered.

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

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

[0153]

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

[0155] Natural person metadata, see Figure 3b .

[0156] Natural person aggregate information entry

[0157] 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.

[0158] 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.

[0159] 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.

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

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

[0162]

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

[0164]

[0165] Address metadata, see Figure 3c .

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

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

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

[0169]

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

[0171]

[0172] Organization metadata, see Figure 3d .

[0173] 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.

[0174] 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.

[0175] 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.

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

[0177]

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

[0179]

[0180] Object data, see Figure 3e .

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

[0182] 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.

[0183] 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.

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

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

[0186]

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

[0188]

[0189] Event data, see Figure 3f .

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

[0191] 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.

[0192] 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.

[0193] 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.

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

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

[0196]

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

[0198]

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

[0200] 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.

[0201] 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.

[0202] Please refer to Figure 4 , which shows a block diagram of a database expansion system provided by an embodiment of the present invention.

[0203] like Figure 4 As shown, the database expansion system 400 includes an analysis program module 410 and an update program module 420 .

[0204] The analysis program module 410 is configured to analyze the user's function expansion requirements, determine at least one item corresponding to the function expansion requirements, and determine attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables of multiple types of metadata and extended attribute tables of at least one type of metadata, wherein the multiple types of metadata include: natural person metadata, organization metadata, address metadata, object metadata, and event metadata;

[0205] The update program module 420 is configured to add a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to the new project to the database when the at least one project is a new project, wherein the database is composed of each project and the corresponding basic attribute table and extended attribute table.

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

[0207] It is worth noting that the modules described in the embodiments of this disclosure are not intended to limit the solutions of this disclosure. For example, the update program module can also be described as a module that, when at least one item is a new item, adds the basic attribute tables of the multiple types of metadata and the extended attribute table of at least one type of metadata corresponding to the new item to the database. Furthermore, related functional modules can also be implemented using a hardware processor, such as the update program module, which will not be further described here.

[0208] 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, a server, or a network device, etc.) to execute any of the above-mentioned database expansion methods of the present invention.

[0209] 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 database expansion methods.

[0210] 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 execute a database expansion method.

[0211] Figure 5 This is a hardware structure diagram of an electronic device for executing a database expansion method provided by another embodiment of the present application. Figure 5 As shown, the device includes:

[0212] One or more processors 510 and memory 520, Figure 5 A processor 510 is taken as an example.

[0213] The device for executing the database expansion method may further include: an input device 530 and an output device 540 .

[0214] The processor 510, the memory 520, the input device 530 and the output device 540 may be connected via a bus or other means. Figure 5 The bus connection is taken as an example.

[0215] Memory 520, 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 database expansion method in the embodiments of the present application. Processor 510 executes the non-volatile software programs, instructions, and modules stored in memory 520 to execute various server functional applications and data processing, thereby implementing the database expansion method in the above-mentioned method embodiment.

[0216] The memory 520 may include a program storage area and a data storage area. 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 database expansion device. Furthermore, the memory 520 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 520 may optionally include memory remotely located relative to the processor 510. Such remote memory may be connected to the database expansion device via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0217] The input device 530 can receive input digital or character information and generate signals related to user settings and function control of the database expansion device. The output device 540 can include a display device such as a display screen.

[0218] The one or more modules are stored in the memory 520 and, when executed by the one or more processors 510 , perform the database expansion method in any of the above method embodiments.

[0219] 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.

[0220] 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.

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

[0222] 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 database expansion method, comprising: Analyzing a user's functional expansion requirements, determining at least one item corresponding to the functional expansion requirements and each attribute table corresponding to the at least one item, wherein the attribute table includes a basic attribute table for multiple types of metadata and an extended attribute table for at least one type of metadata, wherein the multiple types of metadata include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata, wherein each piece of data entered into the basic attribute table and the extended attribute table has corresponding entry information in a main set structure table, wherein the main set structure table includes at least an entry time, an entry identification number, and an entry person, wherein the entry time is the current system time, the entry identification number is automatically generated by the system, and the entry person is the current operator automatically recorded by the system, and relevant already entered information is prompted based on the content being entered to avoid repeated entry of the same information, and the main set structure table is associated with the basic attribute table via the entry identification number in the main set structure table; When the at least one item is a new item, adding a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to the new item to the database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table; When the at least one item is an old item in the database, comparing the basic attribute tables and corresponding extended attribute tables of the at least one item with those of the old item; adding a basic attribute table and / or an extended attribute table of the at least one project that is not included in the old project to the database; Among them, by adopting a natural object metadata analysis method, the data structure is reconstructed, the common characteristics and natural attributes of metadata are abstracted, and the five most basic metadata are subdivided into natural person metadata, organizational metadata, address metadata, object metadata and event metadata. The original complex structured data is simplified independently, and then the five categories of metadata are combined according to the application requirements of event metadata to form a new understanding of natural objects.

2. The method according to claim 1, wherein The basic attribute table and the extended attribute table have database timestamps for recording the update time of each data in the table.

3. The method according to claim 2, wherein: After comparing the basic attribute tables and corresponding extended attribute tables of the at least one item and the old item, the method further includes: If the at least one item and the old item have basic attribute tables and / or extended attribute tables with different recorded data, only the basic attribute tables and / or extended attribute tables corresponding to the data with the latest timestamp of the at least one item are retained in the database.

4. The method according to any one of claims 1 to 3, wherein The function expansion requirements of the analysis user include: A textual expression of a user's function expansion requirement is obtained, a semantic analysis is performed on the textual expression, and at least one item to be expanded and attribute tables corresponding to the at least one item are determined based on a result of the semantic analysis.

5. A database expansion system comprising: an analysis program module configured to analyze a user's functional expansion requirements, determine at least one item corresponding to the functional expansion requirements, and attribute tables corresponding to the at least one item, wherein the attribute tables include basic attribute tables for multiple types of metadata and extended attribute tables for at least one type of metadata, wherein the multiple types of metadata include: natural person metadata, organizational metadata, address metadata, object metadata, and event metadata; wherein each piece of data entered into the basic attribute table and the extended attribute table has corresponding entry information in a main set structure table, wherein the main set structure table includes at least an entry time, an entry identification number, and an entry person, wherein the entry time is the current system time, the entry identification number is automatically generated by the system, and the entry person is the current operator automatically recorded by the system; relevant already entered information is prompted based on the content being entered to avoid repeated entry of the same information; and the main set structure table is associated with the basic attribute table via the entry identification number in the main set structure table; an update program module configured to, when the at least one item is a new item, add a basic attribute table of the multiple types of metadata and an extended attribute table of at least one type of metadata corresponding to the new item to a database, wherein the database is composed of each item and the corresponding basic attribute table and extended attribute table; a comparison program module configured to, when the at least one item is an old item in the database, compare the basic attribute tables and corresponding extended attribute tables of the at least one item with those of the old item; Adding a program module configured to add a basic attribute table and / or an extended attribute table of the at least one project that is not included in the old project to the database; Among them, by adopting a natural object metadata analysis method, the data structure is reconstructed, the common characteristics and natural attributes of metadata are abstracted, and the five most basic metadata are subdivided into natural person metadata, organizational metadata, address metadata, object metadata and event metadata. The original complex structured data is simplified independently, and then the five categories of metadata are combined according to the application requirements of event metadata to form a new understanding of natural objects.

6. The system according to claim 5, wherein: The basic attribute table and the extended attribute table have database timestamps for recording the update time of each data in the table.

7. The system according to claim 6, further comprising: The timestamp processing program module is configured to retain in the database only the basic attribute table and / or extended attribute table corresponding to the latest timestamp data of the at least one project if there are basic attribute tables and / or extended attribute tables with different recorded data in the at least one project and the old project.

8. The system according to any one of claims 5 to 7, wherein: The analysis program module is further configured to: obtain a textual expression of the user's function expansion requirements, perform semantic analysis on the textual expression, and determine at least one item to be expanded and each attribute table corresponding to the at least one item based on the result of the semantic analysis.

Images