Metadata-based data sharing method and system

Abstract

The invention provides a metadata-based data sharing method and system, and the method comprises the steps that a metadata access request is received by a data retrieval entry corresponding to a virtualization interface layer, and the virtualization interface layer comprises virtual interfaces corresponding to access interfaces of all source systems; the metadata access request comprises database metadata used for representing database information in a source system and interface metadata used for representing interface information of the source system; and in the virtualization interface layer, calling an access interface according to a virtual interface corresponding to the access interface specified by the interface metadata to access a corresponding source system, and searching a database specified by the database metadata in the source system so as to call target data corresponding to the database and return the target data to the data retrieval entry to be displayed. The problems of high storage cost, high system coupling degree, low data management efficiency and the like of traditional data concentration can be solved.

Description

Technical Field

[0001] This application relates to the technical field of data management and sharing, and particularly to a data sharing method and system based on metadata. Background Art

[0002] Traditional data lake systems adopt the "physical into the lake" method, migrating source data to a unified storage center (such as HDFS, cloud storage) for centralized management, but there are many drawbacks. First, a large amount of data migration and storage bring high storage and operation and maintenance costs, especially obvious when the data volume grows rapidly. Second, the migration process takes a long time, resulting in insufficient real-time performance and difficulty in meeting the business requirements of high-frequency updates. In addition, physical into the lake will form a strong coupling relationship between the source system and the data lake, making data updates complex, prone to consistency problems, and increasing maintenance costs.

[0003] Therefore, there is an urgent need to design a data sharing method that can solve problems such as high storage costs, high system coupling degree, and low data management efficiency in traditional data concentration. Summary of the Invention

[0004] In view of this, embodiments of this application provide a data sharing method and system based on metadata to eliminate or improve one or more defects existing in the prior art.

[0005] One aspect of this application provides a data sharing method based on metadata, including:

[0006] Receiving a metadata access request from the data retrieval entry corresponding to the virtualization interface layer, where the virtualization interface layer includes virtual interfaces corresponding to the access interfaces of each source system; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing interface information of the source system;

[0007] In the virtualization interface layer, according to the virtual interface corresponding to the access interface specified by the interface metadata, calling the access interface to access the corresponding source system, and finding the database specified by the database metadata in the source system, so as to call the target data corresponding to the database and return the target data to the data retrieval entry for display.

[0008] In some embodiments of this application, before receiving the metadata access request from the data retrieval entry corresponding to the virtualization interface layer, it further includes:

[0009] Respectively obtaining the metadata corresponding to each source system; where the metadata includes: database metadata for specifying a database in a source system and interface metadata for representing the access interface of a specified source system;

[0010] Generate a unique identifier for each piece of the metadata respectively, store the corresponding relationship between each piece of the metadata and each of the unique identifiers, and construct a resource retrieval view that includes the metadata corresponding to each of the source systems respectively.

[0011] In some embodiments of the present application, before receiving a metadata access request at the data retrieval entry corresponding to the self-virtualization interface layer, it further includes:

[0012] Dock with the access interfaces corresponding to each of the source systems respectively, and configure the access parameters corresponding to each of the docked access interfaces.

[0013] Set a virtualization interface layer that includes the virtual interfaces corresponding to each of the access interfaces according to the access parameters corresponding to each of the access interfaces, and use the resource retrieval view as the unique data retrieval entry corresponding to the virtualization interface layer.

[0014] In some embodiments of the present application, before receiving a metadata access request at the data retrieval entry corresponding to the self-virtualization interface layer, it further includes:

[0015] Set different types of role information and the corresponding permission scope for each piece of role information.

[0016] Correspondingly, the data retrieval entry corresponding to the self-virtualization interface layer receiving a metadata access request includes:

[0017] Obtain the identity information of the user corresponding to the metadata access request sent from the data retrieval entry corresponding to the current self-virtualization interface layer, determine the role information corresponding to the identity information of this user, and judge whether the user has the metadata access permission according to the preset permission scope corresponding to this role information. If so, receive this metadata access request.

[0018] In some embodiments of the present application, the metadata-based data sharing method further includes:

[0019] Determine the availability scores corresponding to each of the access interfaces respectively according to the total number of calls and the number of successful calls of each of the access interfaces within a preset time period.

[0020] Determine the health scores corresponding to each of the access interfaces respectively according to the availability scores corresponding to each of the access interfaces, the pre-obtained average response time of each of the access interfaces within a preset time period, and a preset weight coefficient.

[0021] If there is currently a health score corresponding to the access interface that is less than a first threshold, output a prompt message indicating that there is a call anomaly for this access interface.

[0022] In some embodiments of the present application, the data sharing method based on metadata further includes:

[0023] Recording the identity information, call time, and call parameters of the user corresponding to the currently called access interface into a preset interface call log;

[0024] Periodically outputting the interface call log for auditing.

[0025] In some embodiments of the present application, the resource retrieval view further includes preset approval process template data for the user to set custom approval process data according to the approval process template data;

[0026] Correspondingly, the data sharing method based on metadata further includes:

[0027] Receiving custom approval process data from the data retrieval entry corresponding to the virtualization interface layer and recording the automatic trigger time corresponding to the custom approval process data; and automatically obtaining a plurality of the database metadata and a plurality of interface metadata specified by the custom approval process data when the automatic trigger time is reached;

[0028] In the virtualization interface layer, according to the virtual interfaces corresponding to the access interfaces respectively specified by each of the interface metadata, calling each of the access interfaces to access the corresponding source system, and respectively finding the databases corresponding to each of the database metadata in each of the called source systems, so as to call the target data corresponding to each of the databases and generate corresponding approval result data according to each of the target data, and returning the approval result data to the data retrieval entry for display.

[0029] In some embodiments of the present application, the data sharing method based on metadata further includes:

[0030] According to the update frequency, field integrity score, and preset weight coefficient corresponding to each of the pre-obtained metadata, respectively obtaining the metadata volume quality score corresponding to each of the metadata;

[0031] If there is currently a metadata volume quality score corresponding to the metadata that is less than a second threshold, outputting a prompt message indicating that the metadata has a quality anomaly.

[0032] Another aspect of the present application provides a data sharing system based on metadata, including:

[0033] A metadata request receiving module, configured to receive a metadata access request from a data retrieval entry corresponding to a virtualization interface layer, where the virtualization interface layer includes virtual interfaces respectively corresponding to access interfaces of each source system; the metadata access request includes database metadata for indicating database information in a source system and interface metadata for indicating interface information of the source system.

[0034] A virtualization call module, configured to, in the virtualization interface layer, call the access interface according to the virtual interface corresponding to the access interface specified by the interface metadata to access the corresponding source system, find the database specified by the database metadata in the source system, call the target data corresponding to the database, and return the target data to the data retrieval entry for display.

[0035] In some embodiments of the present application, the metadata-based data sharing system further includes:

[0036] A metadata management module, configured to, before receiving a metadata access request from a data retrieval entry corresponding to the virtualization interface layer, respectively obtain metadata corresponding to each source system; where the metadata includes: database metadata for specifying a database in a source system and interface metadata for indicating an access interface of the specified source system; generate a unique identifier for each piece of metadata, store the corresponding relationship between each piece of metadata and each unique identifier, and construct a resource retrieval view including the metadata corresponding to each source system.

[0037] A data sharing interface module, configured to dock with the access interfaces respectively corresponding to each source system, and configure access parameters corresponding to each of the docked access interfaces; set a virtualization interface layer including virtual interfaces respectively corresponding to each of the access interfaces according to the access parameters corresponding to each of the access interfaces, and use the resource retrieval view as the only corresponding data retrieval entry of the virtualization interface layer; the data sharing interface module is further configured to respectively determine availability scores corresponding to each of the access interfaces according to the total number of calls and the number of successful calls of each of the access interfaces within a preset time period; respectively determine health scores corresponding to each of the access interfaces according to the availability scores corresponding to each of the access interfaces, the pre-obtained average response time of each of the access interfaces within a preset time period, and a preset weight coefficient; if there is currently a health score corresponding to an access interface that is less than a first threshold, output a prompt message indicating that there is a call exception for the access interface.

[0038] An approval process module, configured to receive custom approval process data from a data retrieval entry corresponding to the virtualization interface layer and record the automatic trigger time corresponding to the custom approval process data; and when the automatic trigger time is reached, automatically obtain a plurality of the database metadata and a plurality of interface metadata specified by the custom approval process data; the resource retrieval view further includes preset approval process template data for a user to set custom approval process data according to the approval process template data; in the virtualization interface layer, according to the virtual interfaces corresponding to the access interfaces respectively specified by each of the interface metadata, call each of the access interfaces to access the corresponding source system, and in each of the called source systems, respectively find the databases specified by each of the database metadata corresponding thereto, so as to call the target data corresponding to each of the databases and generate corresponding approval result data according to each of the target data, and return the approval result data to the data retrieval entry for display;

[0039] A permission control module, configured to set different types of role information and the permission scope corresponding to each role information before receiving a metadata access request at the data retrieval entry corresponding to the virtualization interface layer; the permission control module is further configured to record the identity information, call time, and call parameters of the user corresponding to the currently called access interface into a preset interface call log; periodically output the interface call log for auditing;

[0040] A data quality monitoring module, configured to respectively obtain the metadata volume quality scores corresponding to each of the metadata according to the update frequency, field integrity score, and preset weight coefficient corresponding to each of the pre-obtained metadata; if there is currently a metadata volume quality score corresponding to the metadata that is less than a second threshold, output a prompt message indicating that the metadata has a quality anomaly.

[0041] Another aspect of the present application provides a metadata-based data sharing system, including:

[0042] An image and model acquisition module, configured to extract target image data including the face of a target person and corresponding target change requirements from video data, and obtain a target eye feature change model corresponding to the target person generated in advance based on a transfer learning method according to the target change requirements;

[0043] An eye feature change module, configured to input the target image data into the target eye feature change model, so that the target eye feature change model performs feature replacement on the eye feature group in the target image data that conforms to the target change requirements, and output eye feature change image data corresponding to the target image data;

[0044] An image data replacement module, configured to replace the target image data with the eye feature change image data in the video data.

[0045] A third aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the data sharing method based on metadata described above is implemented.

[0046] A fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the data sharing method based on metadata described above is implemented.

[0047] A fifth aspect of the present application provides a computer program product, including a computer program. When the computer program is executed by a processor, the data sharing method based on metadata described above is implemented.

[0048] The data sharing method based on metadata provided by the present application receives a metadata access request from the data retrieval entry corresponding to the virtualization interface layer. Among them, the virtualization interface layer includes virtual interfaces corresponding to the access interfaces of each source system; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing the interface information of the source system; in the virtualization interface layer, according to the virtual interface corresponding to the access interface specified by the interface metadata, the access interface is called to access the corresponding source system, and the database specified by the database metadata is found in the source system, so as to call the target data corresponding to the database and return the target data to the data retrieval entry for display. It can flexibly select the storage method according to the usage requirements and storage characteristics of the data, reduce data redundancy and optimize the utilization of storage space, thereby reducing the storage cost. At the same time, by unifying the data access interface, etc., the data collection and sharing process can be effectively simplified, the coupling between different source systems can be reduced, and the flexibility and efficiency of data management can be improved. Finally, the present application can realize the unified retrieval and sharing of data resources, significantly reduce the storage cost and improve the data management efficiency, providing an efficient, flexible and low-cost data management and sharing platform for promoting the maximum utilization of data resources and digital transformation.

[0049] The additional advantages, objectives, and features of the present application will be partially described below, and will become partially apparent to those of ordinary skill in the art after studying the following part, or can be learned from the practice of the present application. The objectives and other advantages of the present application can be achieved and obtained through the structures specifically pointed out in the description and the drawings.

[0050] Those skilled in the art will understand that the objectives and advantages achievable with the present application are not limited to those specifically described above, and the above and other objectives achievable with the present application will be more clearly understood based on the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The drawings described herein are used to provide a further understanding of the present application, form a part of the present application, and do not limit the present application. The components in the drawings are not drawn to scale, but are only for showing the principles of the present application. For the convenience of showing and describing some parts of the present application, the corresponding parts in the drawings may be enlarged, that is, may become larger relative to other components in the exemplary device actually manufactured according to the present application. In the drawings:

[0052] Figure 1 FIG. 9 is a first schematic flowchart of a data sharing method based on metadata in an embodiment of the present application.

[0053] Figure 2 FIG. 13 is a second schematic flowchart of a data sharing method based on metadata in an embodiment of the present application.

[0054] Figure 3 FIG. 17 is a third schematic flowchart of a data sharing method based on metadata in an embodiment of the present application.

[0055] Figure 4 FIG. 21 is a fourth schematic flowchart of a data sharing method based on metadata in an embodiment of the present application.

[0056] Figure 5 FIG. 25 is a first schematic structural diagram of a data sharing system based on metadata in an embodiment of the present application.

[0057] Figure 6 FIG. 29 is a second schematic structural diagram of a data sharing system based on metadata in an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0058] To make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the present application will be further described in detail below in conjunction with the embodiments and the drawings. Herein, the illustrative embodiments and descriptions thereof of the present application are used to explain the present application, but do not limit the present application.

[0059] Herein, it should also be noted that in order to avoid obscuring the present application due to unnecessary details, only the structures and / or processing steps closely related to the solution according to the present application are shown in the drawings, and other details less related to the present application are omitted.

[0060] It should be emphasized that when the term "comprising / including" is used herein, it refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0061] Here, it should also be noted that if not otherwise specified, the term "connection" herein can not only refer to a direct connection, but also represent an indirect connection with an intermediate.

[0062] In the following, embodiments of the present application will be described with reference to the accompanying drawings. In the drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0063] Since the existing data sharing methods have the following problems:

[0064] (1) High storage cost: Migrating a large amount of data to the data lake requires high storage and operation and maintenance costs.

[0065] (2) Insufficient real-time performance: There is a delay in migrating source data, and it is difficult to ensure real-time performance.

[0066] (3) Strong system coupling: After the data enters the lake, the update synchronization between the source system and the data lake is complex, and the system coupling is high.

[0067] Therefore, in order to solve the problems of high storage cost, high system coupling degree and low data management efficiency in traditional data concentration existing in the existing data sharing methods, the embodiments of the present application respectively provide a metadata-based data sharing method, a metadata-based data sharing system for executing the metadata-based data sharing method, an entity device, a computer-readable storage medium, and a computer program product, which not only reduce the management cost, but also improve the data real-time performance and sharing efficiency, help to break data islands, build a flexible and efficient data management system, and provide technical support for the digital transformation and intelligent decision-making of enterprises.

[0068] Specifically, it will be described in detail through the following embodiments.

[0069] Based on this, the embodiments of the present application provide a metadata-based data sharing method that can be implemented by a metadata-based data sharing system. Refer to Figure 1 , the metadata-based data sharing method specifically includes the following content:

[0070] Step 100: Receive a metadata access request from the data retrieval entry corresponding to the virtualization interface layer, where the virtualization interface layer includes virtual interfaces corresponding to the access interfaces of each source system; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing the interface information of the source system.

[0071] In one or more embodiments of the present application, the data sharing method based on metadata can also be referred to as a lightweight data collection and sharing method based on a logical lake-in strategy. The core of the "logical lake-in" strategy is not to physically migrate the source data, but to achieve unified retrieval and sharing through metadata management. Logical lake-in uniformly manages multi-source data through metadata indexing technology, enabling the data to remain in the original system, thus avoiding high migration and storage costs. At the same time, it can directly access the latest data, ensuring data timeliness and meeting real-time analysis requirements. In addition, logical lake-in decouples the source system and the data lake through virtualization technology, simplifies updates and maintenance, and reduces system dependencies. Logical lake-in provides a lightweight solution for big data management. It not only reduces management costs, but also improves data timeliness and sharing efficiency, helps break data silos, constructs a flexible and efficient data management system, and provides technical support for enterprise digital transformation and intelligent decision-making.

[0072] It can be understood that the database information may include at least one of the table name, fields, data types, and indexes of the database. The interface information may include at least one of the interface URL corresponding to the access interface, parameter format, return value definition, and authentication information.

[0073] Step 200: In the virtualization interface layer, according to the virtual interface corresponding to the access interface specified by the interface metadata, call the access interface to access the corresponding source system, and find the database specified by the database metadata in the source system, so as to call the target data corresponding to the database and return the target data to the data retrieval entry for display.

[0074] In step 200, the source system is decoupled from the data sharing service layer through virtualization technology, and the interface of the source system is provided to users through the virtualization interface layer, avoiding direct dependence on the source system. This reduces the coupling between systems and improves the flexibility and scalability of the data sharing platform.

[0075] From the above description, it can be seen that the data sharing method based on metadata provided by the embodiments of the present application can flexibly select the storage method according to the usage requirements and storage characteristics of the data, reduce data redundancy and optimize the utilization of storage space, thereby reducing storage costs. At the same time, through a unified data access interface, etc., it can effectively simplify the data collection and sharing process, reduce the coupling between different source systems, and improve the flexibility and efficiency of data management. Ultimately, the present application can achieve unified retrieval and sharing of data resources, significantly reduce storage costs and improve data management efficiency, providing an efficient, flexible, and low-cost data management and sharing platform for promoting the maximum utilization of data resources and digital transformation.

[0076] To further improve the effectiveness and applicability of metadata management in the data sharing process based on metadata, in a metadata-based data sharing method provided in an embodiment of the present application, refer to Figure 2 Before step 100 in the metadata-based data sharing method, the following specific content is further included:

[0077] Step 010: Obtain the metadata corresponding to each source system respectively; wherein, the metadata includes: database metadata for specifying a database in one of the source systems and interface metadata for representing the access interface of a specified source system.

[0078] Step 020: Generate a unique identifier for each piece of metadata respectively, store the corresponding relationship between each piece of metadata and each unique identifier, and construct a resource retrieval view including the metadata corresponding to each source system respectively.

[0079] Specifically, a unique identifier (such as UUID) is generated for each data resource, and the metadata is uniformly managed through virtualization technology, so that the metadata of different source systems can be flexibly retrieved and accessed on the same management platform. By constructing a full-scale resource retrieval view, a unified data retrieval entry is provided for users, supporting cross-system metadata retrieval.

[0080] That is to say, through virtualization technology, the management module can realize the unified view presentation of the metadata of multiple source systems without directly depending on each source system. The storage and management of metadata decouple the source system from the metadata management platform through virtualization technology, reducing the complexity of data access and system dependence.

[0081] To further improve the effectiveness and applicability of the data sharing interface in the data sharing process based on metadata, in a metadata-based data sharing method provided in an embodiment of the present application, refer to Figure 2 After step 020 and before step 100 in the metadata-based data sharing method, the following specific content is further included:

[0082] Step 030: Dock with the access interfaces corresponding to each source system respectively, and configure the access parameters corresponding to each docked access interface.

[0083] Step 040: Set a virtualization interface layer including virtual interfaces corresponding to each access interface according to the access parameters corresponding to each access interface, and use the resource retrieval view as the only corresponding data retrieval entry for the virtualization interface layer.

[0084] Specifically, implement the interface docking with the source system to ensure that data can be called in real time as needed. Docking with the source system interface, configuring access parameters (such as authentication information, timeout settings), and decoupling the source system from the data sharing service layer through virtualization technology. Develop the data sharing service layer, encapsulate the interface call logic, and provide a unified interface API for users to use, so that the interfaces of different source systems can be presented to the end users through the virtualization layer.

[0085] To further improve the effectiveness and applicability of permission control in the data sharing process based on metadata, in a data sharing method based on metadata provided in an embodiment of the present application, refer to Figure 2 Before step 100 in the data sharing method based on metadata, the following specific content is further included:

[0086] Step 050: Set different types of role information and the corresponding permission scopes for each role information.

[0087] Correspondingly, refer to Figure 3 Step 100 in the data sharing method based on metadata specifically includes the following content:

[0088] Step 110: Obtain the identity information of the user corresponding to the metadata access request issued from the corresponding data retrieval entry of the current virtualization interface layer, determine the role information corresponding to the identity information of the user, and judge whether the user has the metadata access permission according to the preset permission scope corresponding to the role information. If so, receive the metadata access request.

[0089] Among them, if it is determined that the user does not have the metadata access permission, output the corresponding prompt information and stop the execution of subsequent step 200.

[0090] To further improve the effectiveness and applicability of interface status monitoring and health score in the data sharing process based on metadata, in a data sharing method based on metadata provided in an embodiment of the present application, refer to Figure 3 After step 200 in the data sharing method based on metadata, the following specific content is further included:

[0091] Step 310: Determine the availability scores corresponding to each of the access interfaces according to the total number of calls and the number of successful calls of each access interface within a preset time period.

[0092] Among them, the availability of the interface is defined as: Among them, N success is the number of successful calls, and N total is the total number of calls.

[0093] Step 320: Determine the health score corresponding to each of the access interfaces respectively according to the availability score corresponding to each of the access interfaces, the average response time of each of the access interfaces pre-acquired within a preset time period, and a preset weight coefficient.

[0094] Among them, the calculation formula for the health score H is: where t avg is the average response time of the interface, and α and β are weight coefficients, reflecting the influence ratio of availability and response time on the health.

[0095] Step 330: If there is currently a health score corresponding to the access interface that is less than the first threshold, output a prompt message indicating that there is a call exception for the access interface.

[0096] To further improve the effectiveness and applicability of interface call logging and auditing in the data sharing process based on metadata, in a data sharing method based on metadata provided in an embodiment of the present application, refer to Figure 3 , after step 200 in the data sharing method based on metadata, the following specific content is further included:

[0097] Step 410: Record the identity information, call time, and call parameters of the user corresponding to the currently called access interface into a preset interface call log.

[0098] Step 420: Periodically output the interface call log for auditing.

[0099] To further improve the effectiveness and applicability of process automatic execution and tracking in the data sharing process based on metadata, in a data sharing method based on metadata provided in an embodiment of the present application, the resource retrieval view further includes preset approval process template data for the user to set custom approval process data according to the approval process template data;

[0100] Correspondingly, refer to Figure 4 , after step 050 in the data sharing method based on metadata, the following specific content is further included:

[0101] Step 500: Receive custom approval process data from the data retrieval entry corresponding to the virtualization interface layer and record the automatic trigger time corresponding to the custom approval process data; and when the automatic trigger time is reached, automatically obtain a plurality of the database metadata and a plurality of interface metadata specified by the custom approval process data;

[0102] Step 600: In the virtualization interface layer, for each virtual interface corresponding to an access interface specified by each piece of interface metadata, call each access interface to access the corresponding source system, and in each of the called source systems, find the databases specified by each corresponding piece of database metadata respectively, so as to call the target data corresponding to each database and generate corresponding approval result data according to each piece of target data, and return the approval result data to the data retrieval entry for display.

[0103] That is to say, virtualization technology enables the approval process to share and use data across different data source systems, avoiding the limitations of storing data in a single system, thereby improving the efficiency of the approval process.

[0104] To further improve the effectiveness and wide applicability of data quality monitoring in the data sharing process based on metadata, in a data sharing method based on metadata provided in an embodiment of the present application, refer to Figure 3 After step 010 in the data sharing method based on metadata, the following specific content is further included:

[0105] Step 060: According to the update frequency, field integrity score corresponding to each piece of metadata pre-acquired, and a preset weight coefficient, respectively obtain the metadata volume quality score corresponding to each piece of metadata.

[0106] Step 070: If there is currently a metadata volume quality score corresponding to the metadata that is less than a second threshold, output a prompt message indicating that the metadata has a quality anomaly.

[0107] At the software level, the present application also provides a metadata-based data sharing system for executing all or part of the content in the metadata-based data sharing method. Refer to Figure 5 The metadata-based data sharing system specifically includes the following content:

[0108] A metadata request receiving module 10, configured to receive a metadata access request from a data retrieval entry corresponding to the virtualization interface layer, where the virtualization interface layer includes virtual interfaces corresponding to access interfaces of each source system; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing interface information of the source system.

[0109] The virtualization call module 20 is used to, in the virtualization interface layer, call the access interface corresponding to the virtual interface specified by the interface metadata according to the access interface, access the corresponding source system through the access interface, find the database specified by the database metadata in the source system, call the target data corresponding to the database, and return the target data to the data retrieval entry for display.

[0110] The embodiments of the data sharing system based on metadata provided in this application can specifically be used to execute the processing procedures of the embodiments of the data sharing method based on metadata in the above embodiments. Its functions will not be elaborated here and can refer to the detailed descriptions of the embodiments of the data sharing method based on metadata above.

[0111] The part of the data sharing system based on metadata for data sharing based on metadata can be executed in the server or completed in the client device. Specifically, it can be selected according to the processing capabilities of the client device and the limitations of the user usage scenario, etc. This application does not make any limitations in this regard. If all operations are completed in the client device, the client device may further include a processor for specific processing of data sharing based on metadata.

[0112] The above client device may have a communication module (i.e., communication unit) and can communicate with a remote server to achieve data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, it may also include a server of an intermediate platform, such as a server of a third-party server platform having a communication link with the task scheduling center server. The server may include a single computer device, or a server cluster composed of multiple servers, or a server structure of a distributed device.

[0113] Any suitable network protocol can be used for communication between the above server and the client device side, including network protocols not yet developed on the filing date of this application. The network protocol may, for example, include TCP / IP protocol, UDP / IP protocol, HTTP protocol, HTTPS protocol, etc. Of course, the network protocol may also include, for example, the RPC protocol (Remote Procedure Call Protocol) and REST protocol (Representational State Transfer) used on top of the above protocols.

[0114] As can be seen from the above description, the data sharing system based on metadata provided by the embodiments of the present application can flexibly select a storage method according to the usage requirements and storage characteristics of data, reduce data redundancy, and optimize the utilization of storage space, thereby reducing storage costs. At the same time, through a unified data access interface, etc., it can effectively simplify the data collection and sharing process, reduce the coupling between different source systems, and improve the flexibility and efficiency of data management. Finally, the present application can achieve unified retrieval and sharing of data resources, significantly reduce storage costs, and improve data management efficiency, providing an efficient, flexible, and low-cost data management and sharing platform for promoting the maximum utilization of data resources and digital transformation.

[0115] To further improve the application reliability of the data sharing system based on metadata, in the embodiments of the data sharing system based on metadata provided by the present application, refer to Figure 6 , the data sharing system based on metadata specifically includes the following content:

[0116] A metadata management module 01, configured to obtain the metadata corresponding to each source system respectively before receiving a metadata access request at the data retrieval entry corresponding to the self-virtualization interface layer; wherein, the metadata includes: database metadata for specifying a database in one of the source systems and interface metadata for representing the access interface of a specified source system; generating a unique identifier for each piece of metadata respectively and storing the correspondence between each piece of metadata and each unique identifier, and constructing a resource retrieval view including the metadata corresponding to each source system respectively;

[0117] A data sharing interface module 02, configured to dock with the access interfaces corresponding to each source system respectively and configure the access parameters corresponding to each docked access interface; setting a virtualization interface layer including virtual interfaces corresponding to each access interface according to the access parameters corresponding to each access interface, and using the resource retrieval view as the only corresponding data retrieval entry of the virtualization interface layer; the data sharing interface module is further configured to determine the availability score corresponding to each access interface respectively according to the total number of calls and the number of successful calls of each access interface within a preset time period; determining the health score corresponding to each access interface respectively according to the availability score corresponding to each access interface, the pre-obtained average response time of each access interface within the preset time period, and a preset weight coefficient; if there is currently a health score corresponding to an access interface that is less than a first threshold, outputting a prompt message indicating that there is a call exception for this access interface;

[0118] The approval process module 03 is used to receive custom approval process data from the data retrieval entry corresponding to the virtualization interface layer and record the automatic trigger time corresponding to the custom approval process data; and when the automatic trigger time is reached, automatically obtain a plurality of the database metadata and a plurality of interface metadata specified by the custom approval process data; the resource retrieval view further includes preset approval process template data for users to set custom approval process data according to the approval process template data; in the virtualization interface layer, according to the virtual interfaces corresponding to the access interfaces respectively specified by each piece of the interface metadata, call each of the access interfaces to access the corresponding source system, and in each of the called source systems, respectively find the databases specified by each of the database metadata corresponding thereto, so as to call the target data corresponding to each of the databases and generate corresponding approval result data according to each of the target data, and return the approval result data to the data retrieval entry for display;

[0119] The permission control module 04 is used to set different types of role information and the permission scope corresponding to each role information before receiving a metadata access request at the data retrieval entry corresponding to the virtualization interface layer; the permission control module is further used to record the identity information, call time, and call parameters of the user corresponding to the currently called access interface into a preset interface call log; periodically output the interface call log for auditing;

[0120] The data quality monitoring module 05 is used to respectively obtain the metadata volume quality scores corresponding to each of the metadata according to the update frequency, field integrity score, and preset weight coefficient corresponding to each of the pre-obtained metadata; if there is currently a metadata volume quality score corresponding to the metadata that is less than a second threshold, output a prompt message indicating that the metadata has a quality anomaly.

[0121] Among them, the metadata management module 01 is respectively communicatively connected to the data sharing interface module 02, the data quality monitoring module 05, the metadata request receiving module 10, and the approval process module 03, and the data sharing interface module 02 is also respectively communicatively connected to the virtualization call module 20 and the approval process module 03; the permission control module 04 is communicatively connected to the metadata request receiving module 10.

[0122] To further illustrate the above embodiments, the present application also provides a specific application example of implementing a metadata-based data sharing method using a metadata-based data sharing system, which is specifically described as follows:

[0123] (1) Metadata management module

[0124] (1) Metadata management module

[0125] Collect and manage the metadata of the source systems: including data location, structure, interface information, etc.

[0126] Build a full - scale resource retrieval view: Provide a unified data retrieval entry for users and support cross - system metadata retrieval.

[0127] Virtualization support: Through virtualization technology, the management module can achieve a unified view presentation of the metadata of multiple source systems without directly depending on each source system. Metadata storage and management decouple the source system from the metadata management platform through virtualization technology, reducing the complexity of data access and system dependencies.

[0128] (2) Data sharing interface module

[0129] Interface docking and sharing: Implement interface docking with the source system to ensure that data can be called in real - time as needed.

[0130] Interface virtualization technology: Decouple the source system from the data sharing service layer through virtualization technology. The interfaces of the source system are provided to users through the virtualized interface layer, avoiding direct dependence on the source system. This reduces the coupling between systems and improves the flexibility and scalability of the data sharing platform.

[0131] Interface status monitoring and health score: Provide interface status monitoring, showing the availability and call history of the interface. Calculate the health score based on the interface response time and the number of successful calls:

[0132] The availability of the interface is defined as: where N success is the number of successful calls, and N total is the total number of calls.

[0133] The formula for calculating the health score H is: where t avg is the average response time of the interface, and α and β are weight coefficients, reflecting the influence ratio of availability and response time on the health score.

[0134] (3) Approval process module

[0135] Support the approval process for data collection and sharing: Ensure the compliance of data usage.

[0136] Dynamic approval process configuration function: Adapt to different scenario requirements and support flexible configuration of cross - system approvals.

[0137] Virtualization supports cross - system approval processes: Virtualization technology enables approval processes to span different data source systems for data sharing and usage, avoiding the limitations of data storage in a single system and thus improving the efficiency of the approval process.

[0138] (4) Permission Control Module

[0139] Role-based access control (RBAC): Ensures granular management of data access permissions.

[0140] Interface call logging and auditing function: Detailed logs are recorded for each data call, including the caller identity, call time, call parameters, etc. Through virtualization technology, interface call and data access logs can be uniformly managed and audited across systems.

[0141] Virtualized permission management: Using virtualization technology, the system can dynamically adjust the permissions of each role to access different data sources without being restricted by a single system, thereby improving the efficiency of cross-system permission control.

[0142] (5) Data quality monitoring module

[0143] Metadata quality assessment indicators: such as update frequency, field completeness, etc., to ensure data quality.

[0144] Metadata Quality Scoring:

[0145] The calculation formula of metadata quality score Q is: Q = γ·C + δ·U, where C is field completeness (filled fields / total number of fields), U is update frequency (number of updates per unit time), and γ and δ are weight coefficients.

[0146] Cross-system data quality monitoring: Through the decoupling of virtualization technology, metadata quality monitoring can be uniformly evaluated across multiple data sources, ensuring that no matter where the data is stored, it can be effectively monitored and analyzed through unified quality standards.

[0147] 2. Metadata-based data sharing methods

[0148] Step 1: Metadata Collection and Management

[0149] 1. Metadata collection: Use API interfaces or scripting tools to obtain metadata from various source systems, including:

[0150] Database metadata: table name, field, data type, index, etc.

[0151] Interface metadata: interface URL, parameter format, return value definition, authentication information, etc.

[0152] 2. Metadata registration: Generate a unique identifier (such as UUID) for each data resource, and uniformly manage metadata through virtualization technology, so that metadata from different source systems can be flexibly retrieved and accessed on the same management platform.

[0153] Step 2: Open the data sharing interface

[0154] 1. Interface configuration and docking: Docking with the source system interface, configuring access parameters (such as authentication information, timeout settings), and decoupling the source system from the data sharing service layer through virtualization technology.

[0155] 2. Virtualization and interface encapsulation: Develop the data sharing service layer, encapsulate the interface call logic, and provide a unified API for users to use, enabling the interfaces of different source systems to be presented to the end user through the virtualization layer.

[0156] 3. Interface status monitoring and virtualization support: During the interface call process, record key information such as response time and return code. Through virtualization technology, the monitoring page can display the real-time availability of the interface and support cross-system monitoring.

[0157] Step 3: Approval process design and execution

[0158] 1. Process template definition: Preset multiple data collection and sharing approval process templates, and users can customize approval rules (such as approvers, time limits) according to business requirements. The application of virtualization technology enables the approval process to adapt to cross-system requirements.

[0159] 2. Process execution and tracking: The system automatically triggers the approval process and provides real-time feedback on the approval results. Virtualization technology ensures high efficiency in the execution of cross-system approval processes and is not affected by changes in the source system.

[0160] Step 4: Data access and permission control

[0161] 1. Role definition and permission configuration: Define system roles (such as ordinary users, administrators) and their permission scopes (such as data types that can be accessed, interface call frequency limits).

[0162] 2. Interface call log recording and auditing function: Record detailed logs for each data call, including the identity of the caller, call time, call parameters, etc. Through virtualization technology, cross-system interface call logs can be uniformly managed and audited.

[0163] That is to say, the core improvement content of the data sharing system and method based on metadata provided by the application instance of this application is as follows:

[0164] (1) Logical data lake strategy: Propose to replace physical migration with metadata management, avoid high storage and migration costs, and improve data real-time performance and sharing efficiency.

[0165] (2) Metadata indexing technology: Uniformly manage multi-source data through metadata, retain the data in the original system, and simplify the management process.

[0166] (3) Virtualization technology decoupling: Use virtualization technology to decouple the source system from the data lake, reducing maintenance costs and system dependencies.

[0167] (4) Data sharing and digital support: Break data silos, promote data sharing, and support the digital transformation and intelligent decision-making of enterprises.

[0168] The data sharing system and method based on metadata provided by the application example of this application have the following beneficial effects:

[0169] (1) Lightweight: There is no need to migrate source data to centralized storage, reducing storage and operation and maintenance costs.

[0170] (2) Real-time: Real-time data access is realized based on interfaces, solving the latency problem of traditional physical ingestion into the lake.

[0171] (3) Data security guarantee: By cooperating with independent security technology solutions, such as access control, encryption measures, and audit mechanisms, ensure the security and compliance of data during the sharing process.

[0172] (4) Flexibility: Dynamic approval processes and flexible interface configurations meet the needs of various business scenarios.

[0173] That is to say, the application example of this application is specifically designed for the data collection, approval, and sharing processes in the big data platform, providing a lightweight data collection and sharing system based on the logical ingestion strategy. By adopting the logical ingestion strategy, problems such as high storage costs, high system coupling degree, and low data management efficiency in traditional data collection are solved. The system flexibly selects the storage method according to the usage requirements and storage characteristics of data, reduces data redundancy, and optimizes the utilization of storage space, thereby reducing storage costs. At the same time, the system simplifies the data collection and sharing processes through modular design and unified data access interfaces, reduces the coupling between systems, and improves the flexibility and efficiency of data management. Finally, this application realizes the unified retrieval and sharing of data resources, significantly reduces storage costs, improves data management efficiency, provides an efficient, flexible, and low-cost data management and sharing platform, and promotes the maximization utilization of data resources and digital transformation.

[0174] In a specific example, the data sharing system based on metadata is specifically a data sharing system for the financial industry. Its background is that a certain financial institution stores data dispersedly in multiple systems, facing problems such as data synchronization, update latency, and high operation and maintenance costs. After introducing virtualization technology, these problems are solved.

[0175] The implementation plan of the data sharing system for the financial industry includes:

[0176] (1) Virtual decoupling: Through virtualization technology, the data in different systems is presented uniformly, avoiding the costs and complexities of traditional physical data migration.

[0177] (2) Real-time data access and sharing: Using virtualization technology, financial institutions can access the data in the source system in real time without waiting for the migration or synchronization process.

[0178] (3) Achievements: Reduced data migration and storage costs, enabled real-time data access and efficient analysis, and improved business response speed and decision-making quality.

[0179] In another specific example, the metadata-based data sharing system is specifically a supply chain data management system for the manufacturing industry. Its background is as follows: A manufacturing company faces the problem of real-time update of data from multiple factories and suppliers, and the traditional methods of data lakes lead to a large number of system dependencies and operation and maintenance burdens. Through virtualization technology, the data sources of different systems can be effectively decoupled.

[0180] The implementation plan of the supply chain data management system for the manufacturing industry includes:

[0181] (1) Virtualization technology: Through virtualization technology, the production, inventory, and logistics data are decoupled, reducing the latency of data synchronization and improving data real-time performance.

[0182] (2) Flexible data sharing and optimization: Each factory and supplier can share data according to their needs, effectively enhancing the flexibility and transparency of supply chain management.

[0183] (3) Achievements: Reduced the cost of data migration, ensured the efficient operation of the supply chain, and improved cross-departmental collaboration.

[0184] The embodiment of the present application also provides an electronic device, which may include a processor, a memory, a receiver, and a transmitter. The processor is used to execute the metadata-based data sharing method mentioned in the above embodiment. The processor and the memory can be connected through a bus or other means. Taking the connection through the bus as an example. The receiver can be connected to the processor and the memory in a wired or wireless manner.

[0185] The processor may be a Central Processing Unit (CPU). The processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., in the form of chips, or combinations of the above types of chips.

[0186] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the data sharing method based on metadata in the embodiments of the present application. By running the non-transitory software programs, instructions, and modules stored in the memory, the processor executes various functional applications and data processing of the processor, that is, implements the data sharing method based on metadata in the above method embodiments.

[0187] The memory may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created by the processor, etc. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely set relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above networks include but are not limited to the Internet, enterprise intranets, local area networks, mobile communication networks, and combinations thereof.

[0188] The one or more modules are stored in the memory and, when executed by the processor, implement the data sharing method based on metadata in the embodiments.

[0189] In some embodiments of the present application, the user equipment may include a processor, a memory, and a transceiver unit. The transceiver unit may include a receiver and a transmitter. The processor, the memory, the receiver, and the transmitter may be connected through a bus system. The memory is used to store computer instructions, and the processor is used to execute the computer instructions stored in the memory to control the transceiver unit to transmit and receive signals.

[0190] As an implementation method, the functions of the receiver and transmitter in the present application can be considered to be implemented through a transceiver circuit or a dedicated transceiver chip, and the processor can be considered to be implemented through a dedicated processing chip, a processing circuit, or a general-purpose chip.

[0191] As another implementation, the server provided by the embodiments of the present application can be implemented by using a general-purpose computer. That is, the program codes for implementing the functions of the processor, receiver, and transmitter are stored in the memory, and the general-purpose processor implements the functions of the processor, receiver, and transmitter by executing the codes in the memory.

[0192] The embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the foregoing data sharing method based on metadata are implemented. The computer-readable storage medium may be a tangible storage medium, such as a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, floppy disk, hard disk, removable storage disk, CD-ROM, or any other form of storage medium well known in the technical field.

[0193] The embodiments of the present application further provide a computer program product, including a computer program. When the computer program is executed by a processor, the steps of the foregoing data sharing method based on metadata are implemented.

[0194] Those of ordinary skill in the art should understand that the exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Specifically, whether to execute in hardware or software depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application. When implemented in hardware, it may be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in, a functional card, etc. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment may be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave on a transmission medium or a communication link.

[0195] It should be clear that the present application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, the detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order between steps after understanding the spirit of the present application.

[0196] In this application, features described and / or illustrated for one embodiment can be used in the same way or in a similar way in one or more other embodiments, and / or combined with the features of other embodiments or replace the features of other embodiments.

[0197] The above are only the preferred embodiments of this application and are not intended to limit this application. For those skilled in the art, various changes and modifications can be made to the embodiments of this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims

1. A metadata-based data sharing method, characterized in that: include: Receive a metadata access request from a data retrieval entry corresponding to a virtualization interface layer, wherein the virtualization interface layer includes virtual interfaces corresponding to access interfaces of respective source systems; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing interface information of the source system; In the virtualization interface layer, according to the virtual interface corresponding to the access interface specified by the interface metadata, the access interface is called to access the corresponding source system, and the database specified by the database metadata is found in the source system to call the target data corresponding to the database and return the target data to the data retrieval entry for display.

2. The metadata-based data sharing method according to claim 1, characterized in that: Before the data retrieval entry corresponding to the virtualization interface layer receives the metadata access request, the method further includes: Obtain metadata corresponding to each source system respectively; wherein the metadata includes: database metadata for specifying a database in the source system and interface metadata for indicating an access interface of the source system; A unique identifier is generated for each metadata, and a corresponding relationship between each metadata and each unique identifier is stored, and a resource retrieval view including the metadata corresponding to each source system is constructed.

3. The metadata-based data sharing method according to claim 2, characterized in that: Before the data retrieval entry corresponding to the virtualization interface layer receives the metadata access request, the method further includes: Connecting to the access interfaces corresponding to the respective source systems respectively, and configuring the access parameters corresponding to the respective access interfaces after connection; A virtualization interface layer including virtual interfaces corresponding to the access interfaces is set according to the access parameters corresponding to the access interfaces, and the resource search view is used as the only corresponding data search entry of the virtualization interface layer.

4. The metadata-based data sharing method according to claim 1, characterized in that: Before the data retrieval entry corresponding to the virtualization interface layer receives the metadata access request, the method further includes: Set different types of role information and the corresponding authority range for each role information; Correspondingly, the data retrieval entry corresponding to the self-virtualization interface layer receives the metadata access request, including: Obtain the identity information of the user corresponding to the metadata access request currently issued from the data retrieval entry corresponding to the virtualization interface layer, determine the role information corresponding to the user's identity information, and judge whether the user has metadata access rights based on the preset authority range corresponding to the role information. If so, receive the metadata access request.

5. The metadata-based data sharing method according to claim 1, characterized in that: Also includes: Determine the availability score corresponding to each of the access interfaces according to the total number of calls and the number of successful calls of each of the access interfaces within a preset time period; Determine the health score corresponding to each of the access interfaces according to the availability score corresponding to each of the access interfaces, the pre-acquired average response time of each of the access interfaces within a preset time period, and a preset weight coefficient; If the health score corresponding to the access interface currently exists and is less than the first threshold, a prompt message is outputted to indicate that a call abnormality exists in the access interface.

6. The metadata-based data sharing method according to claim 1, characterized in that: Also includes: Record the identity information, calling time and calling parameters of the user corresponding to the access interface currently called into a preset interface calling log; The interface call log is output periodically for auditing.

7. The metadata-based data sharing method according to claim 2, characterized in that: The resource search view also includes preset approval process template data so that the user can set custom approval process data according to the approval process template data; Correspondingly, the metadata-based data sharing method further includes: Receive the custom approval process data from the data retrieval entry corresponding to the virtualization interface layer and record the automatic trigger time corresponding to the custom approval process data; and automatically obtain the multiple database metadata and multiple interface metadata specified by the custom approval process data when the automatic trigger time is reached; In the virtualization interface layer, according to the virtual interface corresponding to the access interface respectively specified by the interface metadata, each access interface is called to access the corresponding source system, and the database specified by the corresponding database metadata is found in each called source system respectively, so as to call the corresponding target data of each database and generate corresponding approval result data according to each target data, and return the approval result data to the data retrieval portal for display.

8. The metadata-based data sharing method according to claim 2, characterized in that: Also includes: According to the pre-acquired update frequency, field integrity score and preset weight coefficient corresponding to each of the metadata, respectively obtain the metadata quantity quality score corresponding to each of the metadata; If the metadata quantity quality score corresponding to the currently existing metadata is less than the second threshold, a prompt message indicating that the metadata has quality abnormality is output.

9. A metadata-based data sharing system, characterized in that: include: A metadata request receiving module is used to receive a metadata access request from a data retrieval entry corresponding to a virtualization interface layer, wherein the virtualization interface layer includes virtual interfaces corresponding to access interfaces of various source systems; the metadata access request includes database metadata for representing database information in a source system and interface metadata for representing interface information of the source system; A virtualization calling module is used to call the access interface in the virtualization interface layer to access the corresponding source system according to the virtual interface corresponding to the access interface specified by the interface metadata, and to search for the database specified by the database metadata in the source system to call the target data corresponding to the database and return the target data to the data retrieval entry for display.

10. The metadata-based data sharing system according to claim 9, characterized in that: Also includes: A metadata management module is used to obtain metadata corresponding to each source system before receiving a metadata access request at a data retrieval entry corresponding to the self-virtualization interface layer; wherein the metadata includes: database metadata for specifying a database in the source system and interface metadata for indicating an access interface of the source system; generate a unique identifier for each metadata and store the corresponding relationship between each metadata and each unique identifier, and construct a resource retrieval view containing the metadata corresponding to each source system; A data sharing interface module is used to respectively connect with the access interfaces corresponding to each of the source systems, and configure the access parameters corresponding to each of the access interfaces after the connection; a virtualization interface layer including a virtual interface corresponding to each of the access interfaces is set according to the access parameters corresponding to each of the access interfaces, and the resource retrieval view is used as the unique data retrieval entry corresponding to the virtualization interface layer; the data sharing interface module is also used to respectively determine the availability score corresponding to each of the access interfaces according to the total number of calls and the number of successful calls of each of the access interfaces within a preset time period; and to respectively determine the health score corresponding to each of the access interfaces according to the availability score corresponding to each of the access interfaces, the pre-acquired average response time of each of the access interfaces within a preset time period, and a preset weight coefficient; if the health score corresponding to the access interface currently exists and is less than the first threshold, a prompt message indicating that there is a call abnormality in the access interface is output; An approval process module is used to receive custom approval process data from a data retrieval entry corresponding to the virtualization interface layer and record the automatic trigger time corresponding to the custom approval process data; and when the automatic trigger time is reached, automatically obtain multiple database metadata and multiple interface metadata specified by the custom approval process data; the resource retrieval view also includes preset approval process template data so that the user can set custom approval process data according to the approval process template data; in the virtualization interface layer, according to the virtual interface corresponding to the access interface respectively specified by each interface metadata, call each access interface to access the corresponding source system, and find the databases specified by each corresponding database metadata in each called source system, so as to call the target data corresponding to each database and generate corresponding approval result data according to each target data, and return the approval result data to the data retrieval entry for display; The permission control module is used to set different types of role information and the permission range corresponding to each role information before receiving the metadata access request at the data retrieval entry corresponding to the self-virtualization interface layer; the permission control module is also used to record the identity information, call time and call parameters of the user corresponding to the access interface currently called into a preset interface call log; and periodically output the interface call log for auditing; The data quality monitoring module is used to obtain the metadata quantity quality score corresponding to each of the metadata according to the pre-acquired update frequency, field integrity score and preset weight coefficient corresponding to each of the metadata; if the metadata quantity quality score corresponding to the currently existing metadata is less than the second threshold, a prompt message indicating that the metadata has quality abnormalities is output.

Images