Data processing method based on metadata configuration drive and related equipment

Abstract

The embodiment of the invention belongs to the technical field of computers, and relates to a metadata configuration drive-based data processing method, which comprises the following steps of: acquiring service configuration information corresponding to a service system to be processed; generating a corresponding metadata configuration file according to the service configuration information; analyzing the metadata configuration file, and determining configuration data corresponding to each preset module in the to-be-processed business system according to an analysis result; and configuring each preset module according to the configuration data to obtain a configured target page, and displaying the target page on a preset front-end interface. The invention further provides a data processing device based on metadata configuration driving, computer equipment and a storage medium. Through the data processing mode of metadata configuration driving, the development workload is reduced, subsequent maintenance and function extension are simplified, and the efficiency of realizing automatic data visualization is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology and is applied to the scenario of realizing automatic data visualization when developing 2B system functions. In particular, it relates to a data processing method and related devices based on metadata configuration drive. Background Art

[0002] In the process of developing traditional 2B system functions, on the one hand, there is the implementation of complex algorithmic logics driven by unconventional business rules, and on the other hand, there are inevitably many data visualization functions with relatively simple logics and based on underlying database tables.

[0003] Currently, the traditional solutions for realizing data visualization functions mainly include the development of front-end and back-end codes based on some mainstream open-source or self-developed ORM frameworks, or the page-level configuration based on some low-code products or tools. However, the former consumes high time and labor costs, while the latter is difficult to meet more customized requirements. Therefore, the efficiency of using traditional solutions to realize data visualization functions is low and the effect is not good. Summary of the Invention

[0004] The purpose of the embodiments of this application is to propose a data processing method and related devices based on metadata configuration drive to solve the technical problem of low efficiency in realizing automatic data visualization when developing 2B system functions.

[0005] To solve the above technical problem, the embodiments of this application provide a data processing method based on metadata configuration drive, and adopt the following technical solutions:

[0006] A data processing method based on metadata configuration drive includes the following steps:

[0007] Obtain the business configuration information corresponding to the business system to be processed;

[0008] Generate a corresponding metadata configuration file according to the business configuration information;

[0009] Parse the metadata configuration file, and determine the configuration data corresponding to each preset module in the business system to be processed according to the parsing result;

[0010] Configure each preset module according to the configuration data to obtain a configured target page, and display the target page on a preset front-end interface.

[0011] Further, the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the business system to be processed according to the parsing result specifically includes:

[0012] When the to-be-processed business system is compiled, the metadata configuration file is parsed to obtain metadata configuration information as the parsing result;

[0013] According to a preset code generation tool, the metadata configuration information is converted to obtain the configuration data.

[0014] Further, the step of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface specifically includes:

[0015] According to the configuration data, determine the display information and function buttons corresponding to each of the preset modules;

[0016] Perform page assembly according to the display information and the function buttons to obtain the target page, and display the target page on the front-end interface.

[0017] Further, the step of generating a corresponding metadata configuration file according to the service configuration information specifically includes:

[0018] When the to-be-processed business system is compiled, generate metadata configuration information according to the service configuration information;

[0019] Generate the metadata configuration file according to the metadata configuration information in a preset file format.

[0020] Further, after the step of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface, it further includes:

[0021] Store the metadata configuration file in a preset database;

[0022] When receiving a file update instruction carrying file update information, extract the metadata configuration file from the database, and update the metadata configuration file according to the file update information to obtain an updated metadata configuration file;

[0023] Return to execute the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the to-be-processed business system according to the parsing result.

[0024] Further, after the step of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface, it further includes:

[0025] In response to a data query instruction triggered by the front-end interface, retrieve in the configuration data according to the keyword information corresponding to the data query instruction to obtain associated target information, and display the target information on the front-end interface.

[0026] Further, the step of obtaining the service configuration information corresponding to the service system to be processed specifically includes:

[0027] According to a preset standardization rule, determine the module configuration standards for each of the preset modules, including configuration semantics and parsing logic;

[0028] Obtain the service basic information corresponding to the service system to be processed, and convert the service basic information into the service configuration information according to the configuration semantics and the parsing logic.

[0029] To solve the above technical problems, an embodiment of the present application further provides a data processing device driven by metadata configuration, adopting the following technical solution:

[0030] A data processing device driven by metadata configuration includes:

[0031] An acquisition module, configured to acquire service configuration information corresponding to a service system to be processed;

[0032] A generation module, configured to generate a corresponding metadata configuration file according to the service configuration information;

[0033] An analysis module, configured to analyze the metadata configuration file, and determine configuration data corresponding to each preset module in the service system to be processed according to the analysis result;

[0034] A configuration module, configured to configure each preset module according to the configuration data to obtain a configured target page, and display the target page on a preset front-end interface.

[0035] To solve the above technical problems, an embodiment of the present application further provides a computer device, adopting the following technical solution:

[0036] A computer device includes a memory and a processor. A computer-readable instruction is stored in the memory, and when the processor executes the computer-readable instruction, the steps of the data processing method driven by metadata configuration as described above are implemented.

[0037] To solve the above technical problems, an embodiment of the present application further provides a computer-readable storage medium, adopting the following technical solution:

[0038] A computer-readable storage medium stores computer-readable instructions thereon, and when the computer-readable instructions are executed by a processor, the steps of the data processing method based on metadata configuration driving as described above are implemented.

[0039] Compared with the prior art, the embodiments of the present application mainly have the following beneficial effects:

[0040] The data processing method based on metadata configuration driving disclosed in the present application includes: obtaining service configuration information corresponding to a service system to be processed; generating a corresponding metadata configuration file according to the service configuration information; parsing the metadata configuration file, and determining configuration data corresponding to each preset module in the service system to be processed according to the parsing result; configuring each preset module according to the configuration data to obtain a configured target page, and displaying the target page on a preset front-end interface. Through the data processing method driven by metadata configuration, developers no longer need to write long hard-coded codes for each module, but manage and adjust the behavior of the module through a configuration file, which not only reduces the development workload, but also simplifies subsequent maintenance and function expansion, and improves the efficiency of realizing data automatic visualization. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] To more clearly illustrate the solutions in the present application, the following briefly introduces the drawings required for the description of the embodiments of the present application. Obviously, the drawings in the following description are some embodiments of the present application, and those of ordinary skill in the art can obtain other drawings according to these drawings without creative efforts.

[0042] Figure 1 is an exemplary system architecture diagram to which the present application can be applied;

[0043] Figure 2 is a flowchart of an embodiment of the data processing method based on metadata configuration driving according to the present application;

[0044] Figure 3 is a schematic structural diagram of an embodiment of the data processing device based on metadata configuration driving according to the present application;

[0045] Figure 4 is a schematic structural diagram of an embodiment of a computer device according to the present application;

[0046] Figure 5 is a timing diagram of an embodiment of a function button in the data processing method based on metadata configuration driving according to the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0047] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs; the terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above drawings are intended to cover non-exclusive inclusion. The terms "first", "second", etc. in the specification and claims of this application or the above drawings are used to distinguish different objects and not to describe a specific order.

[0048] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of this application. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0049] To enable those skilled in the art to better understand the solution of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0050] As Figure 1 shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0051] Users can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0052] The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 (Moving Picture Experts Group Audio Layer III) players, MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop portable computers, and desktop computers, etc.

[0053] The server 105 may be a server that provides various services, such as a background server that supports the pages displayed on the terminal devices 101, 102, and 103.

[0054] It should be noted that the data processing method based on metadata configuration driving provided by the embodiments of the present application is generally executed by a server. Correspondingly, the data processing device based on metadata configuration driving is generally set in the server.

[0055] It should be understood that Figure 1 the numbers of the terminal devices, networks, and servers in are merely illustrative. According to the implementation requirements, there may be any number of terminal devices, networks, and servers.

[0056] Continuing to refer to Figure 2 , a flowchart of an embodiment of the data processing method based on metadata configuration driving according to the present application is shown. The data processing method based on metadata configuration driving includes the following steps:

[0057] Step S201, obtain the service configuration information corresponding to the service system to be processed.

[0058] In this embodiment, the electronic device (such as the server shown in Figure 1 ) on which the data processing method based on metadata configuration driving runs can send or receive data through a wired connection method or a wireless connection method. It should be noted that the above wireless connection methods may include, but are not limited to, 3G / 4G / 5G connections, WiFi connections, Bluetooth connections, WiMAX connections, Zigbee connections, UWB (ultra wideband) connections, and other currently known or future-developed wireless connection methods.

[0059] In this embodiment, the purpose is to collect all the service configuration information required in the service system to be processed, so as to generate a metadata configuration file according to these configuration information later and finally drive the configuration of the system module. Specifically, the sources of the configuration information usually come from different places, including: the service requirements manually set by the user through the system background; the service data requirements automatically collected by the system; the preset fields and data structures of relevant service systems or databases. The ways to obtain the configuration information may be to obtain it from other service systems or modules through an API interface, such as through database queries or through a configuration management platform (such as Nacos or Zookeeper). It may also be obtained by the user inputting a configuration form, or by reading from an existing system configuration file (such as in JSON or YML format). For example, the service configuration information in an e-commerce service system may include: the product information displayed on each page, the display columns of order management, the rules of data calculation, the styles of page components, and the data sources, etc.

[0060] Step S202: Generate a corresponding metadata configuration file according to the service configuration information.

[0061] In this embodiment, the service configuration information collected in step S201 is converted into a machine-readable metadata configuration file, which is used to define how to obtain, process, and display data from the underlying data tables. The principle of generating the metadata configuration file is to convert complex business rules into standardized configurations through abstract metadata descriptions, and these configurations will be used to guide the behavior and display of subsequent modules. The metadata configuration file usually contains the names of fields, data types, relationships between fields, data sources (database tables, external APIs, etc.), operation rules (such as calculation formulas), etc. It is stored in formats such as YAML and JSON. These file formats are concise, easy to expand, and have good readability and maintainability. The generation method of the metadata configuration file can be to design corresponding fields, field types, display formats, etc. according to business requirements. For example, if the business requires a "product list" module, the corresponding metadata configuration file should include fields such as product name, price, and inventory quantity. It can also be automatically generated according to a preset template engine or code generation tool. For example, by analyzing the database structure of the system to be processed, metadata related to table fields, sorting rules, filtering conditions, etc. is automatically generated.

[0062] Step S203: Parse the metadata configuration file and determine the configuration data corresponding to each preset module in the service system to be processed according to the parsing result.

[0063] In this embodiment, the previously generated metadata configuration file is parsed to extract the data configurations required for each module. These configurations will guide each module on how to display and process data. The system needs to parse the metadata configuration file, extract the specific fields, logics, and formats contained therein, and perform data extraction and processing according to the requirements of each module. Specifically, the parsing process may involve parsing files in YAML or JSON formats. The system reads these configuration files and converts them into data objects that can be operated on (such as dictionaries, lists, etc.). The parser converts the metadata configuration into a specific data structure for each module to use based on information such as field names, data types, display formats, etc. For example, map the field names and data types to the fields in the database query, or convert the sorting and filtering rules defined by the fields into SQL query statements. For some fields that require calculation or dynamic data generation, the corresponding calculation logics or formulas (such as total price calculation, inventory quantity update, etc.) also need to be extracted from the configuration. After parsing the metadata configuration, the system can prepare data for the "product display" module. For example, after parsing the "product name" field, the system will know that this is a text type field and needs to query the data of this field from the database and display it on the front-end page.

[0064] Step S204: Configure each of the preset modules according to the configuration data to obtain a configured target page, and display the target page on a preset front-end interface.

[0065] In this embodiment, after parsing and obtaining the specific configuration data, the system will configure each module based on this data, finally generate a target page, and display it on the front-end interface. The key to this step is to apply the configuration data obtained in step S203 to the specific preset modules to ensure that each module displays and processes data as required. Specifically, according to the type and requirements of the module, the system will use a front-end framework (such as React, Vue, etc.) to dynamically render the page, displaying the configured fields, data, and interaction methods. For data modules (such as tables, charts), the system will generate a dynamic SQL query according to the metadata configuration, obtain the required data, and display it. For interactive modules (such as search boxes, filters), the system will generate corresponding input components according to the metadata configuration and bind event handling logics. Exemplarily, through a front-end rendering engine, a "product display table" is generated according to the configuration, and the columns in the table will display fields such as "product name", "price", "inventory", etc. The sorting, filtering, and other functions of each column will also be enabled according to the metadata configuration.

[0066] Through the data processing method driven by metadata configuration in this application, developers no longer need to write long and tedious hard-coded code for each module. Instead, they can manage and adjust the behavior of the module through a configuration file, which not only reduces the development workload but also simplifies subsequent maintenance and function expansion, improving the efficiency of realizing automatic data visualization.

[0067] In some optional implementation manners of this embodiment, the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the to-be-processed business system according to the parsing result specifically includes:

[0068] When the to-be-processed business system is compiled, parse the metadata configuration file to obtain metadata configuration information as the parsing result;

[0069] Perform data conversion on the metadata configuration information according to a preset code generation tool to obtain the configuration data.

[0070] In this embodiment, in the compilation stage, the system will parse the metadata configuration file and convert it into a data structure for subsequent processing. Different from the conventional runtime parsing, the parsing here occurs during compilation, that is, the system parses the metadata configuration file into structured configuration information for subsequent code generation or module configuration. Parsing during compilation can identify structural problems or inconsistencies in the metadata in advance, which helps the system process data more efficiently at runtime. Compilation-time parsing can not only improve the performance of the system but also ensure that the processing of the configuration file by the system at runtime is based on static analysis, thus avoiding the performance overhead brought by dynamic parsing at runtime. In the compilation stage, the system will read the metadata configuration file (such as in YAML, JSON, etc. formats) and use a parser to convert it into the corresponding data structure. This process is static, that is, the parsing is completed during code construction instead of being parsed every time at runtime. The result of the parsing is a structured data object that will contain all the detailed configurations of the metadata, such as the name, type, calculation rules, display formats, sorting rules, etc. of the fields. Exemplarily, assume the metadata configuration file is in the following format:

[0071]

[0072]

[0073] This structure will be used as the input data for subsequent steps.

[0074] The metadata configuration information parsed at compile time will be further transformed into executable configuration data by a code generation tool. The code generation tool is an automated tool that generates corresponding code (or configuration data) based on the input metadata configuration for direct use during system runtime. The purpose of data transformation is to generate actual configuration data based on the parsed metadata configuration information. The generated data will be embedded in the system in a certain form (such as Java objects, database structures, front-end code, etc.) for use by business logic modules or front-end displays. The code generation tool typically works in a templated manner, using some template files to generate different types of code based on the metadata configuration information. For example: back-end code generation, generating SQL statements for querying databases or code for data access objects (DAOs) to ensure that the data processing logic meets the configuration requirements in the metadata; front-end code generation, generating code for components such as dynamic tables, charts, and forms to generate interactive UI components based on the metadata configuration; middle-tier logic generation, generating data processing logic such as data validation, sorting, filtering, and pagination to ensure that these operations meet the configured business requirements. For example, for "field attribute" metadata, the code generation tool can automatically generate a Java class or database table structure. For "table display" metadata, the tool can generate the corresponding HTML table code or JavaScript front-end components. For "computation logic" metadata, the tool can generate relevant business logic code for processing data calculation and formatting.

[0075] This application parses the metadata configuration file at compile time, avoiding dynamic parsing at runtime, thereby improving the performance of the system; through static parsing, errors or inconsistencies can be captured at the compile stage, reducing errors and delays that may occur at runtime.

[0076] In some alternative implementation manners of this embodiment, the step of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface specifically includes:

[0077] Determine the display information and function buttons corresponding to each of the preset modules according to the configuration data;

[0078] Assemble the page according to the display information and the function buttons to obtain the target page, and display the target page on the front-end interface.

[0079] In this embodiment, as Figure 5As shown, based on the generated configuration data, the system analyzes and determines which information should be displayed for each preset module (such as tables, charts, forms, etc.). The displayed information is usually a collection of field data. For example, in a table, it is necessary to determine which columns should be displayed, what the display names of these columns are, as well as their sorting and formatting rules. Functional buttons refer to controls that interact with users, such as "Save", "Delete", "Export" buttons, etc. According to the configuration data, the system determines which functional buttons need to appear on the page and configures their functions. For example, a certain module may require a "Search" button, while another module may require an "Add" button. Based on the field definitions in the configuration data, the system determines which fields need to be displayed on the page. The display of these fields may include the column names, data types of the fields, formatting rules of the fields, etc. The configuration data may contain field attributes such as "Product Name", "Price", "Inventory", etc., and these fields will be mapped to table or form components on the page. The information in the configuration data may specify which buttons need to be displayed. For example, the configuration data of a certain module may specify "Delete" button and "Edit" button, while another module may only require a "Search" button. Each button will have its corresponding function implementation. For example, when the "Delete" button is clicked, the system needs to perform a delete operation; when the "Export" button is clicked, the system may need to generate a data report and download it. Based on the previously determined display information and functional buttons, the system needs to dynamically assemble the entire page. This process involves combining multiple module components (such as tables, charts, input boxes, buttons, etc.) through front-end technologies (such as HTML, CSS, JavaScript) to form a complete web page. After the page assembly is completed, the final page will be displayed on the front-end interface, and users can view the configured content and interact with it.

[0080] This application generates the front-end page in a configuration-driven manner, which can significantly reduce the workload of front-end developers. The configuration file describes the display method and functions of the module, and the front-end system automatically generates the corresponding UI components by parsing the configuration.

[0081] In some optional implementation manners of this embodiment, the step of generating the corresponding metadata configuration file according to the service configuration information specifically includes:

[0082] When the to-be-processed business system is compiled, generate metadata configuration information according to the service configuration information;

[0083] Generate the metadata configuration file according to the metadata configuration information in a preset file format.

[0084] In this embodiment, metadata configuration information is generated during compilation. During the compilation phase, the system generates metadata configuration information based on the business configuration information provided by the business system to be processed. Here, "during compilation" means that during the code construction and system deployment processes, the system automatically generates a detailed metadata configuration information according to the business requirements to ensure that the configuration of the entire system matches the business requirements. The business configuration information usually comes from multiple channels, such as manual settings, databases, external interfaces, or predefined templates. It includes information about the structure of modules, field definitions, calculation logics, etc. For example, the business configuration information of an e-commerce platform may include fields for product information display (such as product name, price, inventory), query rules, data validation rules, etc. Then, a configuration file is generated based on the metadata configuration information. Once the metadata configuration information is generated during compilation, the next step is to output this information in a certain standard file format. Common file formats include YAML, JSON, XML, etc. These formats are concise, easy to parse, and support extensions. The choice of file format depends on the system's requirements and standards. YAML and JSON are currently commonly used formats because they are highly readable, easy to understand, and have extensive support libraries for parsing and generation. The file format is usually set in advance, which standardizes the structure of the metadata configuration file and enables the system to be consistent during generation and parsing.

[0085] By generating a metadata configuration file that conforms to a standardized format, the system can maintain a consistent configuration management method. The configurations of different modules use a unified format and standard, which is convenient for management and maintenance.

[0086] In some alternative implementation manners of this embodiment, after the step of configuring each of the preset modules according to the configuration data to obtain a target page with configuration completed and displaying the target page on a preset front-end interface, the following steps are further included:

[0087] Store the metadata configuration file in a preset database;

[0088] When receiving a file update instruction carrying file update information, extract the metadata configuration file from the database and update the metadata configuration file according to the file update information to obtain an updated metadata configuration file;

[0089] Return to execute the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the business system to be processed according to the parsing result.

[0090] In this embodiment, once the metadata configuration file is generated, the system needs to store the file in a preset database for subsequent access and update. The role of the database is to ensure the persistence of the configuration file, facilitating management and maintenance. When storing the metadata configuration file, a relational database (such as MySQL, PostgreSQL) or a non-relational database (such as MongoDB, Cassandra) is usually selected. Which database to choose depends on the system architecture and business requirements. The storage format can be JSON, YAML, or other structured formats. After the metadata configuration file is stored, it can be conveniently extracted, updated, or deleted through database queries. When the system receives an instruction with file update information, it indicates that certain requirements of the business system have changed. To adapt to these changes, the system needs to update the metadata configuration file. The system extracts the currently stored metadata configuration file from the database, which is usually completed through database query statements, and can obtain the content of the most recently stored configuration file. According to the received file update information, the system makes necessary updates to the metadata configuration file. These updates can include adding new fields, modifying the attributes of existing fields, adjusting display rules, updating sorting rules, etc. The file update information may include incremental updates (such as adding a field), modifying the attributes of a certain field (such as modifying the sorting field), or deleting a certain field, etc. Once the metadata configuration file update is completed, the system needs to re-execute the above-mentioned parsing process because the update of the configuration file may involve changes in fields, sorting, display rules, etc., and these changes need to be promptly reflected in subsequent business modules. The system re-parses the configuration data of each preset module according to the updated metadata configuration file, and the parsing process will generate configurations adapted to different modules based on the new configuration data, thereby ensuring the correctness of page display and module functions. The updated metadata may affect the display or functions of multiple modules. Through re-parsing, the system can ensure that these modules can correctly display the new configured data and functions.

[0091] This application ensures that each updated configuration can be accurately reflected in the system by re-parsing the configuration after file update, avoiding problems of configuration lag and inconsistency.

[0092] In some optional implementation manners of this embodiment, after the step of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface, the method further includes:

[0093] In response to a data query instruction triggered by the front-end interface, retrieve in the configuration data according to the keyword information corresponding to the data query instruction to obtain associated target information, and display the target information on the front-end interface.

[0094] In this embodiment, the front-end interface usually includes some user interaction elements, such as search boxes, buttons, drop-down menus, etc. Users trigger data query instructions through these elements. When users hope to view certain specific information, the system needs to execute a query operation according to the query conditions input or selected by them. According to the query instructions passed from the front end, the back-end system needs to find corresponding matching information in the stored configuration data. The keyword information may be the text input by the user, the selected option, or other query conditions. The system retrieves relevant information from the configuration data based on these conditions and returns it to the front end for display. Once the back-end retrieves the target information that matches the query conditions, the system needs to return this data to the front end and display it on the user interface. This display can be a table, chart, card, or other visual components, and the specific form depends on the business requirements and front-end design. The front end dynamically updates the user interface by obtaining data from the back end and displays the query results. For example, if a product information is queried, the interface may display information such as the name, price, and inventory of the product. After the query results are displayed, users can continue to perform operations (such as sorting, filtering, paging, etc.), thereby improving the user experience and the interactivity of the system.

[0095] By responding to the query instructions from the front end and retrieving the target information from the configuration data, the system of the present application can dynamically respond to the needs of users. Users can input query conditions at the front end, and the system dynamically returns relevant data and displays it according to the configuration, thereby improving the user interaction experience.

[0096] In some alternative implementation manners of this embodiment, the step of obtaining the business configuration information corresponding to the business system to be processed specifically includes:

[0097] Determine the module configuration standards for each of the preset modules according to the preset standardization rules, including configuration semantics and parsing logic;

[0098] Obtain the business basic information corresponding to the business system to be processed, and convert the business basic information into the business configuration information according to the configuration semantics and the parsing logic.

[0099] In this embodiment, to ensure that the system can process the configurations of different modules efficiently and uniformly, it is first necessary to define a set of standardized rules. These rules cover how to describe and parse the configurations of each module, ensuring the consistency and operability of the configuration data. By defining standardized rules, the system can maintain consistency and ensure that the configurations of different modules follow the same design concept, thus avoiding compatibility issues caused by inconsistent configuration standards among different modules. For example, for a product management module, the configuration semantics may include fields such as product name, price, and inventory, while the parsing logic may involve retrieving field data from a database and displaying it in a specific format. Business basic information is usually the raw data stored in the system, which may come from databases, external interfaces, configuration files, or other sources. Business basic information includes all the basic data related to business modules, such as product information, user information, order records, etc. The system combines the business basic information with the preset configuration semantics and parsing logic to generate specific business configuration information. Specifically, the system parses and processes the basic data according to the configuration semantics and converts it into configuration information that meets business requirements. Business configuration information is the specific configuration information generated based on the basic information and configuration standards. It usually includes specific field values, display rules, calculation logics, etc., for subsequent data processing and page display.

[0100] In this application, through standardized rules, business basic information is transformed into business configuration information. The system can quickly respond to changes in business requirements and automatically generate configuration information that meets the requirements. The transformation of business data and configuration information is automatically completed, reducing manual intervention.

[0101] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Among them, Artificial Intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results.

[0102] Artificial intelligence basic technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, and mechatronics. Artificial intelligence software technologies mainly include several major directions such as computer vision technology, robotics, biometric technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0103] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disc, a Read-Only Memory (ROM), or a Random Access Memory (RAM), etc.

[0104] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and their execution order is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0105] Further referring to Figure 3 as an implementation of the method shown above Figure 2 This application provides an embodiment of a data processing device based on metadata configuration drive. This device embodiment corresponds to the method embodiment shown in Figure 2 and this device can be specifically applied to various electronic devices.

[0106] As shown in Figure 3 the data processing device 300 based on metadata configuration drive described in this embodiment includes: an acquisition module 301, a generation module 302, an analysis module 303, and a configuration module 304. Among them:

[0107] The acquisition module 301 is used to acquire the service configuration information corresponding to the service system to be processed;

[0108] The generation module 302 is used to generate a corresponding metadata configuration file according to the service configuration information;

[0109] The analysis module 303 is used to analyze the metadata configuration file and determine the configuration data corresponding to each preset module in the service system to be processed according to the analysis result;

[0110] The configuration module 304 is used to configure each preset module according to the configuration data, obtain the target page with the configuration completed, and display the target page on the preset front-end interface.

[0111] The data processing device based on metadata configuration drive provided by this application, through the data processing method driven by metadata configuration, developers no longer need to write long hard - coded codes for each module, but manage and adjust the behavior of the module through a configuration file. This not only reduces the development workload, but also simplifies subsequent maintenance and function expansion, and improves the efficiency of realizing data automatic visualization.

[0112] In some alternative implementation manners of this embodiment, the parsing module 303 is further configured to:

[0113] When the to - be - processed business system is compiled, parse the metadata configuration file to obtain metadata configuration information as the parsing result;

[0114] According to a preset code generation tool, perform data conversion on the metadata configuration information to obtain the configuration data.

[0115] The data processing device based on metadata configuration drive provided by this application, by parsing the metadata configuration file during compilation, avoids dynamic parsing during runtime, thereby improving the performance of the system; through static parsing, errors or inconsistencies can be captured during the compilation stage, reducing errors and delays that may occur during runtime.

[0116] In some alternative implementation manners of this embodiment, the configuration module 304 is further configured to:

[0117] Determine the display information and function buttons corresponding to each of the preset modules according to the configuration data;

[0118] Perform page assembly according to the display information and the function buttons to obtain the target page, and display the target page on the front - end interface.

[0119] The data processing device based on metadata configuration drive provided by this application, by generating the front - end page in a configuration - driven manner, can significantly reduce the workload of front - end developers. The configuration file describes the display mode and functions of the module, and the front - end system automatically generates the corresponding UI components by parsing the configuration.

[0120] In some alternative implementation manners of this embodiment, the generation module 302 is further configured to:

[0121] When the to - be - processed business system is compiled, generate metadata configuration information according to the service configuration information;

[0122] Generate the metadata configuration file according to the metadata configuration information in a preset file format.

[0123] The data processing device based on metadata configuration drive provided by this application can generate a metadata configuration file that conforms to a standardized format, enabling the system to maintain a consistent configuration management method. The configurations of different modules use a unified format and standard, facilitating management and maintenance.

[0124] In some optional implementation manners of this embodiment, the configuration module 304 is further configured to:

[0125] Store the metadata configuration file in a preset database;

[0126] When receiving a file update instruction carrying file update information, extract the metadata configuration file from the database, and update the metadata configuration file according to the file update information to obtain an updated metadata configuration file;

[0127] Return to execute the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the to-be-processed service system according to the parsing result.

[0128] The data processing device based on metadata configuration drive provided by this application can ensure that each updated configuration can be accurately reflected in the system by re-parsing the configuration after file update, avoiding problems of configuration lag and inconsistency.

[0129] In some optional implementation manners of this embodiment, the configuration module 304 is further configured to:

[0130] In response to a data query instruction triggered by the front-end interface, retrieve in the configuration data according to the keyword information corresponding to the data query instruction to obtain associated target information, and display the target information on the front-end interface.

[0131] The data processing device based on metadata configuration drive provided by this application can dynamically respond to user requirements by responding to a query instruction from the front-end and retrieving target information in the configuration data. Users can input query conditions at the front-end, and the system dynamically returns relevant data and displays it according to the configuration, thereby improving the user interaction experience.

[0132] In some optional implementation manners of this embodiment, the acquisition module 301 is further configured to:

[0133] Determine the module configuration standards for each of the preset modules according to preset standardized rules, including configuration semantics and parsing logic;

[0134] Obtain the service basic information corresponding to the to-be-processed service system, and convert the service basic information into the service configuration information according to the configuration semantics and the parsing logic.

[0135] The data processing device based on metadata configuration drive provided by this application converts business basic information into business configuration information through standardized rules. The system can quickly respond to changes in business requirements and automatically generate configuration information that meets the requirements. The conversion between business data and configuration information is automatically completed, reducing manual intervention.

[0136] To solve the above technical problems, the embodiments of this application also provide a computer device. For details, please refer to Figure 4 , Figure 4 which is the basic structural block diagram of the computer device in this embodiment.

[0137] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are communicatively connected to each other through a system bus. It should be noted that only the computer device 4 with components 41-43 is shown in the figure. However, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Among them, those skilled in the art of this technology can understand that a computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.

[0138] The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The computer device can interact with users through a keyboard, a mouse, a remote control, a touchpad or a voice control device and other means.

[0139] The memory 41 includes at least one type of readable storage medium, which includes flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, FlashCard, etc. equipped on the computer device 4. Of course, the memory 41 may also include both the internal storage unit and the external storage device of the computer device 4. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of a data processing method configured and driven based on metadata. In addition, the memory 41 may also be used to temporarily store various types of data that have been output or will be output.

[0140] In some embodiments, the processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run the computer-readable instructions stored in the memory 41 or process data, such as running the computer-readable instructions of the data processing method configured and driven based on metadata.

[0141] The network interface 43 may include a wireless network interface or a wired network interface, and the network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0142] In the computer device provided by this application, through the data processing method configured and driven by metadata, developers no longer need to write long and tedious hard-coded codes for each module, but manage and adjust the behavior of the module through a configuration file, which not only reduces the development workload, but also simplifies subsequent maintenance and function expansion, and improves the efficiency of realizing data automatic visualization.

[0143] The present application also provides another implementation manner, that is, to provide a computer-readable storage medium storing computer-readable instructions, which can be executed by at least one processor to cause the at least one processor to execute the steps of the data processing method based on metadata configuration driving as described above.

[0144] For the computer-readable storage medium provided by the present application, through the data processing method driven by metadata configuration, developers no longer need to write long and tedious hard-coded codes for each module, but manage and adjust the behavior of the module through a configuration file, which not only reduces the development workload, but also simplifies subsequent maintenance and function expansion, and improves the efficiency of realizing automatic data visualization.

[0145] Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation manner. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions to cause a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of the present application.

[0146] Obviously, the above-described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The drawings show the preferred embodiments of the present application, but do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosed content of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the foregoing embodiments, for those skilled in the art, they can still modify the technical solutions described in the foregoing specific embodiments, or perform equivalent replacements for some of the technical features. Any equivalent structure directly or indirectly using the content of the specification and drawings of the present application in other related technical fields is similarly within the scope of the patent protection of the present application.

Claims

1. A data processing method based on metadata configuration drive, characterized in that: The steps include: Obtain business configuration information corresponding to the business system to be processed; Generate a corresponding metadata configuration file according to the business configuration information; Parsing the metadata configuration file, and determining configuration data corresponding to each preset module in the business system to be processed according to the parsing result; Each of the preset modules is configured according to the configuration data to obtain a configured target page, and the target page is displayed on a preset front-end interface.

2. The data processing method based on metadata configuration drive according to claim 1, characterized in that: The step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the business system to be processed according to the parsing result specifically includes: When the business system to be processed is compiled, the metadata configuration file is parsed to obtain metadata configuration information as the parsing result; The metadata configuration information is converted according to the preset code generation tool to obtain the configuration data.

3. The data processing method based on metadata configuration drive according to claim 1, characterized in that: The step of configuring each of the preset modules according to the configuration data to obtain a configured target page, and displaying the target page on a preset front-end interface specifically includes: Determine, according to the configuration data, display information and function buttons corresponding to each of the preset modules; The page is assembled according to the display information and the function button to obtain the target page, and the target page is displayed on the front-end interface.

4. The data processing method based on metadata configuration drive according to claim 1, characterized in that: The step of generating a corresponding metadata configuration file according to the business configuration information specifically includes: When the service system to be processed is compiled, metadata configuration information is generated according to the service configuration information; The metadata configuration file is generated according to the metadata configuration information and in a preset file format.

5. The data processing method based on metadata configuration drive according to claim 1, characterized in that: After the steps of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface, the method further includes: Storing the metadata configuration file in a preset database; When receiving a file update instruction carrying file update information, extracting the metadata configuration file from the database, and updating the metadata configuration file according to the file update information to obtain an updated metadata configuration file; Return to the step of parsing the metadata configuration file and determining the configuration data corresponding to each preset module in the business system to be processed according to the parsing result.

6. The data processing method based on metadata configuration drive according to claim 1, characterized in that: After the steps of configuring each of the preset modules according to the configuration data to obtain a configured target page and displaying the target page on a preset front-end interface, the method further includes: In response to the data query instruction triggered by the front-end interface, the configuration data is searched according to the keyword information corresponding to the data query instruction to obtain the associated target information, and the target information is displayed on the front-end interface.

7. The data processing method based on metadata configuration drive according to any one of claims 1 to 6, characterized in that: The step of obtaining the business configuration information corresponding to the business system to be processed specifically includes: Determining the module configuration standard of each of the preset modules according to the preset standardization rules, including configuration semantics and parsing logic; The basic business information corresponding to the business system to be processed is obtained, and the basic business information is converted into the business configuration information according to the configuration semantics and the parsing logic.

8. A data processing device based on metadata configuration drive, characterized in that: include: The acquisition module is used to obtain the business configuration information corresponding to the business system to be processed; A generation module, used to generate a corresponding metadata configuration file according to the business configuration information; A parsing module, used to parse the metadata configuration file, and determine the configuration data corresponding to each preset module in the business system to be processed according to the parsing result; The configuration module is used to configure each of the preset modules according to the configuration data, obtain a configured target page, and display the target page on a preset front-end interface.

9. A computer device, characterized in that: It comprises a memory and a processor, wherein the memory stores computer-readable instructions, and when the processor executes the computer-readable instructions, the steps of the metadata configuration-driven data processing method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the metadata configuration-driven data processing method according to any one of claims 1 to 7.

Images