Data interface management methods, devices, electronic equipment and storage media

Abstract

The application discloses a kind of data interface management method, device, electronic equipment and storage medium, the method includes: obtaining each form data corresponding form unit data information and association relationship metadata information;Wherein, form unit data information is used to describe the relevant information of form data itself, and association relationship metadata information is used to describe the association relationship between each form data;Based on form unit data information and association relationship metadata information, construct target data interface;Release target data interface, so that user obtains form data through target data interface.This scheme not only can configure the form unit data information of each form data, but also can configure the association relationship metadata information between multiple forms, increase more dimensional metadata information, and subsequent complex data application query can be supported by the association relationship metadata, realize the flexible configuration of complex data interface, improve the flexibility when managing data interface.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and in particular, to a data interface management method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the improvement of the digital level of various industries and fields in society, the data application as an important basis for digitization has also developed rapidly. At present, providing data interfaces to users as an important means to realize data application, through which data can be shared with users and users can efficiently apply data.

[0003] Traditionally, when managing data interfaces, the form data stored in the database needs to be configured first, and then the data interface is created and published according to the configuration information.

[0004] However, the flexibility of the above-mentioned method for managing data interfaces is poor. SUMMARY

[0005] The present application aims to at least solve the technical problems existing in the prior art, and for this purpose, the first aspect of the present application provides a data interface management method, which comprises:

[0006] Obtaining form unit data information and association relationship metadata information corresponding to each form data; wherein the form unit data information is used to describe the related information of the form data itself, and the association relationship metadata information is used to describe the association relationship between each form data;

[0007] Based on the form unit data information and the association relationship metadata information, a target data interface is constructed;

[0008] Publishing the target data interface to enable users to obtain the form data through the target data interface.

[0009] In one possible implementation, obtaining the form unit data information and the association relationship metadata information corresponding to each form data comprises:

[0010] Obtaining field description information corresponding to each form data in a form unit data entry interface to generate form unit data information;

[0011] Obtaining the connection relationship between each form data in a multi-form visualization interface, and generating association relationship metadata information based on the connection relationship.

[0012] In one possible implementation, the method further comprises:

[0013] Obtaining form name information corresponding to each form data;

[0014] Save the form name information, form unit data information and association relationship metadata information to a preset database.

[0015] In a possible implementation, the target data interface is constructed based on the form unit data information and the association relationship metadata information, including:

[0016] Based on the information of the preset database selected by the user, the form name information, the form unit data information and the association relationship metadata information are obtained from the preset database and displayed on the interface visual configuration interface.

[0017] Based on the target form name information, the target form unit data information and the target association relationship metadata information selected by the user on the interface visual configuration interface, form range index information is created; the target form name information is information corresponding to the target data interface selected from each form name information, the target form unit data information is information corresponding to the target data interface selected from each form unit data information, and the target association relationship metadata information is information corresponding to the target data interface selected from each association relationship metadata information.

[0018] The target data interface is constructed based on the form range index information.

[0019] In a possible implementation, the method further includes:

[0020] For each target form data corresponding to the form range index information, a new association relationship between the target form data is obtained.

[0021] Based on the new association relationship, new association relationship metadata information is generated.

[0022] The new association relationship metadata information is updated to the preset database.

[0023] In a possible implementation, the target data interface is published, including:

[0024] Identity information of the accessible target data interface is obtained on an interface publishing interface.

[0025] Based on the identity information, the target data interface is published.

[0026] In a possible implementation, the method further includes:

[0027] A data interface list is obtained and displayed; the data interface list includes at least one published target data interface.

[0028] At least one retired data interface selected by the user from the data interface list is obtained; the retired data interface is a target data interface in the data interface list that is not accessible.

[0029] In response to a user's decommissioning operation on a decommissioning data interface, decommissioning processing is performed on at least one decommissioning data interface.

[0030] In one possible implementation, the method further includes:

[0031] In response to a user's selection of at least one decommissioned data interface on the interface publishing interface, a new data interface to be published is retrieved from at least one decommissioned data interface.

[0032] In response to a user's publishing operation for a new data interface to be published, the new data interface to be published is published.

[0033] A second aspect of the present invention provides a data interface management device, the device comprising:

[0034] The acquisition module is used to acquire the form metadata information and association metadata information corresponding to each form data; among them, the form metadata information is used to describe the relevant information of the form data itself, and the association metadata information is used to describe the association relationship between each form data;

[0035] The building module is used to construct the target data interface based on form metadata information and relationship metadata information;

[0036] The publishing module is used to publish the target data interface so that users can obtain form data through the target data interface.

[0037] In one possible implementation, the acquisition module described above is specifically used for:

[0038] Obtain the field description information corresponding to each form data in the form metadata entry interface, and generate form metadata information;

[0039] The system obtains the connection relationships between the data in each form through a multi-form visualization interface, and generates metadata information about the relationship based on these connections.

[0040] In one possible implementation, the data interface management device is further configured to:

[0041] Retrieve the form name information corresponding to each form's data;

[0042] Save the form name information, form metadata information, and association metadata information to the preset database.

[0043] In one possible implementation, the above-described building module is specifically used for:

[0044] Based on the information from the preset database selected by the user, the form name information, form metadata information, and relationship metadata information are retrieved from the preset database and displayed on the interface visual configuration interface;

[0045] Based on the target form name information, target form metadata information, and target association metadata information selected by the user in the interface visualization configuration interface, form range index information is created; wherein, the target form name information is the information corresponding to the target data interface selected from each form name information, the target form metadata information is the information corresponding to the target data interface selected from each form metadata information, and the target association metadata information is the information corresponding to the target data interface selected from each association metadata information.

[0046] Based on the form range index information, construct the target data interface.

[0047] In one possible implementation, the data interface management device is further configured to:

[0048] For each target form data corresponding to the form range index information, obtain the new association relationship between each target form data;

[0049] Based on the new relationships, new relationship metadata information is generated;

[0050] Update the new relationship metadata information to the preset database.

[0051] In one possible implementation, the above-mentioned publishing module is specifically used for:

[0052] Obtain the identity information of the target data interface that can be accessed from the interface publishing interface;

[0053] Publish target data interfaces based on identity information.

[0054] In one possible implementation, the data interface management device is further configured to:

[0055] Retrieve and display a list of data interfaces; the list of data interfaces includes at least one published target data interface;

[0056] Obtain at least one decommissioned data interface selected by the user from the data interface list; wherein the decommissioned data interface is a target data interface that is not accessible in the data interface list;

[0057] In response to a user's decommissioning operation on a decommissioning data interface, decommissioning processing is performed on at least one decommissioning data interface.

[0058] In one possible implementation, the data interface management device is further configured to:

[0059] In response to a user's selection of at least one decommissioned data interface on the interface publishing interface, a new data interface to be published is retrieved from at least one decommissioned data interface.

[0060] In response to a user's publishing operation for a new data interface to be published, the new data interface to be published is published.

[0061] A third aspect of the present invention provides an electronic device comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or an instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the data interface management method as described in the first aspect.

[0062] A fourth aspect of the present invention provides a computer-readable storage medium storing at least one instruction, at least one program, a code set, or an instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the data interface management method as described in the first aspect.

[0063] The embodiments of the present invention have the following beneficial effects:

[0064] This invention provides a data interface management method, apparatus, electronic device, and storage medium. The method includes: acquiring form metadata information and relational metadata information corresponding to each form data; wherein the form metadata information describes the relevant information of the form data itself, and the relational metadata information describes the relational relationship between the form data; constructing a target data interface based on the form metadata information and the relational metadata information; and publishing the target data interface so that users can obtain form data through the target data interface. This solution can configure not only the form metadata information of each form data, but also the relational metadata information between multiple forms, adding more dimensions of metadata information; and through this relational metadata, it can support subsequent complex data application queries, realize flexible configuration of complex data interfaces, and improve the flexibility of data interface management. Attached Figure Description

[0065] Figure 1 A block diagram of a computer device provided in an embodiment of this application;

[0066] Figure 2 A flowchart illustrating the steps of a data interface management method provided in an embodiment of the present invention;

[0067] Figure 3 A flowchart illustrating the steps for generating metadata is provided in this embodiment of the invention.

[0068] Figure 4 A flowchart illustrating the steps for constructing a target data interface, as provided in an embodiment of the present invention;

[0069] Figure 5 A flowchart illustrating the steps for updating metadata related to an association relationship, as provided in an embodiment of the present invention;

[0070] Figure 6 A flowchart illustrating the steps of publishing target data interface according to an embodiment of the present invention;

[0071] Figure 7 A flowchart illustrating the steps of a decommissioning target data interface provided in an embodiment of the present invention;

[0072] Figure 8 A flowchart illustrating the steps for republishing a decommissioned data interface, as provided in this embodiment of the invention.

[0073] Figure 9 This is an overall framework diagram of a target data publishing interface provided in an embodiment of the present invention;

[0074] Figure 10 This is a structural block diagram of a data interface management device provided in an embodiment of the present invention. Detailed Implementation

[0075] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0076] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this disclosure, unless otherwise stated, "a plurality of" means two or more. Furthermore, the use of "based on" or "according to" implies openness and inclusiveness, because processes, steps, calculations, or other actions "based on" or "according to" one or more of the stated conditions or values ​​may in practice be based on additional conditions or beyond the stated values.

[0077] The data interface management method provided in this application can be applied to computer equipment (electronic devices). The computer equipment can be a server or a terminal. The server can be a single server or a server cluster composed of multiple servers. This application does not specifically limit this. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets and portable wearable devices.

[0078] Taking a computer device as an example, Figure 1 A block diagram of a server is shown, such as Figure 1 As shown, the server may include a processor and memory connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. When the computer program is executed by the processor, it implements a data interface management method.

[0079] Those skilled in the art will understand that Figure 1 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the server to which the present application is applied. Optionally, the server may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0080] It should be noted that the execution subject of the embodiments of this application can be a computer device or a data interface management device. The following method embodiments will be described with computer device as the execution subject.

[0081] Figure 2 This is a flowchart illustrating the steps of a data interface management method provided in an embodiment of the present invention. Figure 2 As shown, the method includes the following steps:

[0082] Step 202: Obtain the form metadata information and related metadata information corresponding to each form data.

[0083] Metadata, also known as intermediary data or relay data, is a type of data that describes data. It mainly describes the attributes of data and is used to support functions such as indicating storage location, historical data, resource lookup, and file records.

[0084] Form metadata information is used to describe relevant information about the form data itself. In other words, form metadata information is data that describes relevant information about the form data itself, and the relevant information about the form data itself can be specific fields in the form data.

[0085] Relationship metadata information is used to describe the relationships between various form data. In other words, relationship metadata information is data that describes the relationships between different form data. These relationships are determined based on actual business operations. For example, if a user completes at least one order, then the form data recording the user's identity can be associated with the form data recording the order information.

[0086] In some optional embodiments, field description information corresponding to each form data can be obtained from the form metadata entry interface to generate form metadata information. The field description information may include field type information, field length information, and other descriptive information corresponding to the form data. Users can configure the corresponding field description information on the form metadata entry interface, thereby enabling the computer device to generate form metadata information based on the user-entered field description information.

[0087] Next, the connection relationships between the data in each form can be obtained through the multi-form visualization interface, and relational metadata information can be generated based on these connections. When multiple forms exist, users can configure the relational metadata information between them within the multi-form visualization interface. Optionally, the connection relationships between the form data can be generated using field connections, thereby generating relational metadata information based on these connections.

[0088] Optionally, users can connect a field in form data A with at least one field in form data B using lines. This establishes a connection between form data A and form data B, and describing this connection yields metadata information about the association between form data A and form data B. For example, if a user completes two orders, field m in form data A (recording user identity) can be connected to fields n and q in form data B (recording order information) using two lines each; that is, field m is connected to field n, and field m is connected to field q.

[0089] Of course, other methods can also be used to establish the connection between form data A and form data B, and this application embodiment does not specifically limit this.

[0090] In this embodiment, a visual interface is used to configure form metadata and relationship metadata, improving the flexibility of configuration and facilitating user operation. Furthermore, configuring the relationship metadata between multiple forms adds more dimensions of metadata, enabling subsequent complex data application queries and flexible configuration of complex data interfaces, thus improving the flexibility of data interface management. Simultaneously, it enhances the readability of form data, making it easier for users to understand and use.

[0091] Step 204: Based on the form metadata information and the association metadata information, construct the target data interface.

[0092] After obtaining the form metadata information and the associated metadata information, this information can be processed before constructing the corresponding target data interface.

[0093] In some alternative embodiments, metadata information can also be saved before constructing the target data interface, such as... Figure 3 As shown, Figure 3 A flowchart of steps for generating metadata, provided in an embodiment of the present invention, includes:

[0094] Step 302: Obtain the form name information corresponding to each form data.

[0095] Step 304: Save the form name information, form metadata information, and association metadata information to the preset database.

[0096] In cases where there are multiple form data, each form data can first be saved to a different preset database. Therefore, you can first configure the corresponding preset database information for each form data, such as the identifier information of the preset database, and then save the form data to the corresponding preset database.

[0097] Next, you can configure the corresponding form name information for each form data, so that after the computer device obtains the form name information, form metadata information and relationship metadata information, it can save all of this information to the corresponding preset database for use when building the target data interface later.

[0098] In some alternative embodiments, when constructing the target data interface, such as Figure 4 As shown, Figure 4 A flowchart illustrating the steps for constructing a target data interface, as provided in this embodiment of the invention, includes:

[0099] Step 402: Based on the information of the preset database selected by the user, retrieve the form name information, form metadata information, and relationship metadata information from the preset database, and display them on the interface visualization configuration interface.

[0100] Step 404: Based on the target form name information, target form metadata information, and target association metadata information selected by the user in the interface visualization configuration interface, create form range index information.

[0101] Step 406: Based on the form range index information, construct the target data interface.

[0102] Among them, the target form name information is the information corresponding to the target data interface selected from the form name information; the target form metadata information is the information corresponding to the target data interface selected from the form metadata information; and the target association metadata information is the information corresponding to the target data interface selected from the association metadata information.

[0103] You can first create a target data interface object in a preset interface creation interface, and then perform subsequent operations in the interface visual configuration interface. Upon entering the interface visual configuration interface, since there are multiple preset databases, you can retrieve form name information, form metadata information, and relationship metadata information from the corresponding preset database based on the information selected by the user, and display this information in the interface visual configuration interface.

[0104] Next, users can select the required target form name information, target form metadata information, and target relationship metadata information from the displayed form name information, form metadata information, and relationship metadata information according to the needs of building the target data interface, and then create form range index information based on the selected information.

[0105] In addition, based on the target form name information, target form metadata information, and target association metadata information in the form range index information, the corresponding database query statement and backend data interface service code can be automatically constructed in the backend, so that the target data interface can be constructed based on the database query statement and backend data interface service code.

[0106] In this embodiment, compared with traditional technologies, which require manual programming for data application interfaces of complex form data, resulting in low efficiency and preventing users familiar with the data from participating in the data application interface development process, this embodiment provides a flexible visual interface that allows users to quickly configure the data required to build the target data interface. Furthermore, the database query statements and backend data interface service code corresponding to the target data interface are automatically constructed, significantly improving the convenience and ease of operation in building the target data interface. This also effectively shortens the development cycle of the target data interface, truly lowering the user threshold and allowing those who understand and use form data to define the target data interface.

[0107] In other alternative embodiments, such as Figure 5 As shown, Figure 5 A flowchart illustrating the steps for updating metadata related to an association relationship, as provided in this embodiment of the invention, includes:

[0108] Step 502: For each target form data corresponding to the form range index information, obtain the new association relationship between each target form data.

[0109] Step 504: Based on the new relationship, generate new relationship metadata information.

[0110] Step 506: Update the new relationship metadata information to the preset database.

[0111] During the construction of the target data interface, new relationships between forms can be obtained based on actual business needs. Specifically, for each target form data corresponding to the form range index information, new relationships between them can be obtained based on actual business requirements. For example, if form data A, corresponding to the form range index information, is only related to form data B, but during the construction of the target data interface, it is discovered that form data A also has a relationship with form data C, then these new relationships can be obtained during the construction process. Next, new relationship metadata information is generated based on these new relationships, and this new relationship metadata information is updated in the preset database. Ultimately, this updates the preset database with the new relationship metadata information corresponding to the relationship between form data A and form data C.

[0112] In this embodiment, by updating the new relational metadata information in real time during the construction of the target data interface, the accuracy and effectiveness of the relational relationships between the data in each form can be guaranteed, thereby improving the accuracy of the subsequent construction of the target data interface.

[0113] Step 206: Publish the target data interface so that users can obtain form data through the target data interface.

[0114] Once the target data interface is built and published, users can access it to obtain the corresponding form data. Optionally, before publishing the target data interface, relevant permission information for accessing it can be set.

[0115] In some alternative embodiments, such as Figure 6 As shown, Figure 6 A flowchart illustrating the steps of publishing a target data interface according to an embodiment of the present invention includes:

[0116] Step 602: Obtain the identity information of the target data interface that can be accessed from the interface publishing interface.

[0117] Step 604: Publish the target data interface based on the identity information.

[0118] Users can confirm and select which roles can access the target data interface on the interface publishing interface, thereby obtaining the identity information of those who can access the target data interface, and then publishing the target data interface based on the identity information. Optionally, the target data interface can be published automatically after obtaining the identity information; alternatively, it can be published in response to the user's publishing action on the target data interface, such as when the user clicks the publish button.

[0119] In this embodiment, since the target data interface can be published based on identity information, it is possible to flexibly select which users can access the target data interface, thereby improving the flexibility and security of accessing the target data interface.

[0120] In other alternative embodiments, the published target data interface can also be decommissioned, thereby making the target data interface inaccessible to users, such as... Figure 7 As shown, Figure 7 A flowchart illustrating the steps of a decommissioning target data interface provided in this embodiment of the invention includes:

[0121] Step 702: Obtain and display the list of data interfaces.

[0122] Step 704: Obtain at least one decommissioned data interface selected by the user from the list of data interfaces.

[0123] Step 706: In response to the user's decommissioning operation for the decommissioned data interface, decommission at least one decommissioned data interface.

[0124] The data interface list includes at least one published target data interface, which can be displayed on the interface publishing interface after the data interface list is obtained. Each target data interface in the data interface list can correspond to a checkbox. Users can use the checkbox to select at least one decommissioned data interface from the list and perform the decommissioning operation on the decommissioned data interface. The decommissioned data interface is the target data interface that is not accessible in the data interface list.

[0125] After a user selects at least one decommissioned data interface, the system can respond to the user's decommissioning operation on that data interface, such as the user clicking the decommissioning button, thereby decommissioning at least one data interface. After decommissioning, the data interface cannot be accessed.

[0126] Optionally, multiple decommissioning data interfaces can be selected simultaneously during a single decommissioning operation, thereby enabling batch decommissioning of multiple decommissioning data interfaces.

[0127] In this embodiment, since the published target data interface can be decommissioned, the identity information of those who can access the target data interface can be flexibly changed according to the actual situation, thereby improving the adaptability and flexibility of the target data interface.

[0128] In addition, the decommissioning data interface can be republished after decommissioning, such as... Figure 8 As shown, Figure 8 A flowchart illustrating the steps for republishing a decommissioned data interface, as provided in this embodiment of the invention, includes:

[0129] Step 802: In response to the user's selection operation for at least one retired data interface on the interface publishing interface, retrieve a new data interface to be published from at least one retired data interface.

[0130] Step 804: In response to the user's publishing operation for the new data interface to be published, publish the new data interface to be published.

[0131] The decommissioned data interfaces can be republished. During republishing, all data interfaces to be published can be displayed to users on the interface publishing interface, including newly constructed target data interfaces and decommissioned data interfaces. Each data interface to be published can also correspond to a checkbox, allowing users to select at least one decommissioned data interface, thus obtaining at least one new data interface to be published.

[0132] Next, in response to a user's publishing action on the new data interface to be published, such as clicking the publish button, the new data interface to be published is processed. Additionally, when republishing a new data interface to be published, the identity information that allows access to the new data interface can be retrieved again, and the new data interface to be published is processed based on this identity information. For example... Figure 9 As shown, Figure 9 This is an overall framework diagram of a target data publishing interface provided in an embodiment of the present invention.

[0133] The data interface management method provided in this invention includes: obtaining form metadata information and relational metadata information corresponding to each form data; wherein, the form metadata information describes the relevant information of the form data itself, and the relational metadata information describes the relational relationship between each form data; constructing a target data interface based on the form metadata information and the relational metadata information; and publishing the target data interface so that users can obtain form data through the target data interface. This solution can configure not only the form metadata information of each form data, but also the relational metadata information between multiple forms, adding more dimensions of metadata information. This relational metadata can support subsequent complex data application queries, enabling flexible configuration of complex data interfaces and improving the flexibility of data interface management.

[0134] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0135] Figure 10 This is a structural block diagram of a data interface management device provided in an embodiment of the present invention.

[0136] like Figure 10 As shown, the data interface management device 1000 includes:

[0137] The acquisition module 1002 is used to acquire form metadata information and association metadata information corresponding to each form data; wherein, the form metadata information is used to describe the relevant information of the form data itself, and the association metadata information is used to describe the association relationship between the form data.

[0138] The construction module 1004 is used to construct the target data interface based on the form metadata information and the association metadata information.

[0139] The publishing module 1006 is used to publish the target data interface so that users can obtain the form data through the target data interface.

[0140] Regarding the apparatus in the above embodiments, the specific methods by which each module performs its operations have been described in detail in the embodiments related to the method, and will not be elaborated upon here. Each module in the above data interface management apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations of each module.

[0141] In one embodiment of this application, a computer device is provided, the computer device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0142] Obtain the form metadata information and association metadata information corresponding to each form data; where the form metadata information is used to describe the relevant information of the form data itself, and the association metadata information is used to describe the association relationship between each form data;

[0143] Based on form metadata and relational metadata, construct the target data interface;

[0144] Publish the target data interface so that users can obtain form data through the target data interface.

[0145] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0146] Obtain the field description information corresponding to each form data in the form metadata entry interface, and generate form metadata information;

[0147] The system obtains the connection relationships between the data in each form through a multi-form visualization interface, and generates metadata information about the relationship based on these connections.

[0148] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0149] Retrieve the form name information corresponding to each form's data;

[0150] Save the form name information, form metadata information, and association metadata information to the preset database.

[0151] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0152] Based on the information from the preset database selected by the user, the form name information, form metadata information, and relationship metadata information are retrieved from the preset database and displayed on the interface visual configuration interface;

[0153] Based on the target form name information, target form metadata information, and target association metadata information selected by the user in the interface visualization configuration interface, form range index information is created; wherein, the target form name information is the information corresponding to the target data interface selected from each form name information, the target form metadata information is the information corresponding to the target data interface selected from each form metadata information, and the target association metadata information is the information corresponding to the target data interface selected from each association metadata information.

[0154] Based on the form range index information, construct the target data interface.

[0155] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0156] For each target form data corresponding to the form range index information, obtain the new association relationship between each target form data;

[0157] Based on the new relationships, new relationship metadata information is generated;

[0158] Update the new relationship metadata information to the preset database.

[0159] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0160] Obtain the identity information of the target data interface that can be accessed from the interface publishing interface;

[0161] Publish target data interfaces based on identity information.

[0162] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0163] Retrieve and display a list of data interfaces; the list of data interfaces includes at least one published target data interface;

[0164] Obtain at least one decommissioned data interface selected by the user from the data interface list; wherein the decommissioned data interface is a target data interface that is not accessible in the data interface list;

[0165] In response to a user's decommissioning operation on a decommissioning data interface, decommissioning processing is performed on at least one decommissioning data interface.

[0166] In one embodiment of this application, the processor further performs the following steps when executing the computer program:

[0167] In response to a user's selection of at least one decommissioned data interface on the interface publishing interface, a new data interface to be published is retrieved from at least one decommissioned data interface.

[0168] In response to a user's publishing operation for a new data interface to be published, the new data interface to be published is published.

[0169] The computer device provided in the above embodiments has similar implementation principles and technical effects to the above method embodiments, and will not be described again here.

[0170] In one embodiment of this application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, it performs the following steps:

[0171] Obtain the form metadata information and association metadata information corresponding to each form data; where the form metadata information is used to describe the relevant information of the form data itself, and the association metadata information is used to describe the association relationship between each form data;

[0172] Based on form metadata and relational metadata, construct the target data interface;

[0173] Publish the target data interface so that users can obtain form data through the target data interface.

[0174] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0175] Obtain the field description information corresponding to each form data in the form metadata entry interface, and generate form metadata information;

[0176] The system obtains the connection relationships between the data in each form through a multi-form visualization interface, and generates metadata information about the relationship based on these connections.

[0177] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0178] Retrieve the form name information corresponding to each form's data;

[0179] Save the form name information, form metadata information, and association metadata information to the preset database.

[0180] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0181] Based on the information from the preset database selected by the user, the form name information, form metadata information, and relationship metadata information are retrieved from the preset database and displayed on the interface visual configuration interface;

[0182] Based on the target form name information, target form metadata information, and target association metadata information selected by the user in the interface visualization configuration interface, form range index information is created; wherein, the target form name information is the information corresponding to the target data interface selected from each form name information, the target form metadata information is the information corresponding to the target data interface selected from each form metadata information, and the target association metadata information is the information corresponding to the target data interface selected from each association metadata information.

[0183] Based on the form range index information, construct the target data interface.

[0184] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0185] For each target form data corresponding to the form range index information, obtain the new association relationship between each target form data;

[0186] Based on the new relationships, new relationship metadata information is generated;

[0187] Update the new relationship metadata information to the preset database.

[0188] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0189] Obtain the identity information of the target data interface that can be accessed from the interface publishing interface;

[0190] Publish target data interfaces based on identity information.

[0191] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0192] Retrieve and display a list of data interfaces; the list of data interfaces includes at least one published target data interface;

[0193] Obtain at least one decommissioned data interface selected by the user from the data interface list; wherein the decommissioned data interface is a target data interface that is not accessible in the data interface list;

[0194] In response to a user's decommissioning operation on a decommissioning data interface, decommissioning processing is performed on at least one decommissioning data interface.

[0195] In one embodiment of this application, the computer program, when executed by a processor, further performs the following steps:

[0196] In response to a user's selection of at least one decommissioned data interface on the interface publishing interface, a new data interface to be published is retrieved from at least one decommissioned data interface.

[0197] In response to a user's publishing operation for a new data interface to be published, the new data interface to be published is published.

[0198] The computer storage medium provided in the above embodiments has similar implementation principles and technical effects to the above method embodiments, and will not be described again here.

[0199] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs).

[0200] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0201] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A data interface management method, characterized by, The method comprises: obtaining form element data information and association relationship metadata information corresponding to each form data; wherein the form element data information is used to describe the relevant information of the form data itself, and the association relationship metadata information is used to describe the association relationship between the form data; based on the form element data information and the association relationship metadata information, constructing a target data interface; obtaining identity information that can access the target data interface in an interface publishing interface; based on the identity information, publishing the target data interface, so that the user obtains the form data through the target data interface; obtaining and displaying a data interface list; wherein the data interface list includes at least one published target data interface; obtaining at least one retired data interface selected by the user from the data interface list; wherein the retired data interface is a target data interface that cannot be accessed in the data interface list; in response to the user's retirement operation on the retired data interface, performing retirement processing on the at least one retired data interface; in response to the user's selection operation on the at least one retired data interface in the interface publishing interface, re-obtaining a new to-be-published data interface from the at least one retired data interface; in response to the user's publishing operation on the new to-be-published data interface, performing publishing processing on the new to-be-published data interface.

2. The method of claim 1, wherein, The method comprises: obtaining field description information corresponding to each form data in a form element data entry interface, and generating the form element data information; obtaining the connection relationship between the form data in a multi-form visualization interface, and generating the association relationship metadata information based on the connection relationship.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: obtaining form name information corresponding to each form data; saving the form name information, the form element data information and the association relationship metadata information into a preset database.

4. The method of claim 3, wherein, The method further comprises: based on the information of the preset database selected by the user, obtaining the form name information, the form element data information and the association relationship metadata information from the preset database, and displaying them in an interface visualization configuration interface; based on the target form name information, the target form element data information and the target association relationship metadata information selected by the user in the interface visualization configuration interface, creating form range index information; wherein the target form name information is information corresponding to the target data interface selected from each form name information, the target form element data information is information corresponding to the target data interface selected from each form element data information, and the target association relationship metadata information is information corresponding to the target data interface selected from each association relationship metadata information; based on the form range index information, constructing the target data interface.

5. The method of claim 4, wherein, The method further comprises: For each target form data corresponding to the form range index information, a new association relationship between the target form data is obtained; Based on the new association relationship, new association relationship metadata information is generated; The new association relationship metadata information is updated to the preset database.

6. A data interface management apparatus, characterized by comprising: The device comprises: An acquisition module is configured to acquire form element data information and association relationship metadata information corresponding to each form data; the form element data information is used to describe relevant information of the form data itself, and the association relationship metadata information is used to describe an association relationship between the form data; A construction module is configured to construct a target data interface based on the form element data information and the association relationship metadata information; A publishing module is configured to acquire identity information that can access the target data interface on an interface publishing interface; publish the target data interface based on the identity information, so that a user acquires the form data through the target data interface; acquire and display a data interface list; the data interface list includes at least one published target data interface; acquire at least one retired data interface selected by the user from the data interface list; the retired data interface is a target data interface that cannot be accessed in the data interface list; in response to a retirement operation of the user on the retired data interface, perform retirement processing on the at least one retired data interface; in response to a selection operation of the user on the at least one retired data interface on the interface publishing interface, reacquire a new to-be-published data interface from the at least one retired data interface; in response to a publishing operation of the user on the new to-be-published data interface, perform publishing processing on the new to-be-published data interface.

7. An electronic device, comprising: The electronic device comprises a processor and a memory, and the memory stores at least one instruction, at least one program, a code set or an instruction set, which are loaded and executed by the processor to implement the steps of the method of any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, at least one program, a code set or an instruction set, which are loaded and executed by the processor to implement the steps of the method of any one of claims 1-5.

Images