Metadata management method and device, electronic equipment, storage medium and program

Abstract

The embodiment of the invention discloses a metadata management method and device, electronic equipment, a storage medium and a program, and relates to the field of computer application and financial science and technology. The method comprises the following steps: in response to a change instruction of target metadata, obtaining a target metadata configuration file; generating a change application of target metadata according to the target metadata configuration file, and sending the change application of the target metadata to a metadata management platform; wherein the metadata management platform is used for generating target metadata content of the target metadata in response to the change application of the target metadata. According to the technical scheme, the management process of the metadata can be optimized, and the efficiency of metadata management is improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the fields of computer applications and financial technology, and in particular to a metadata management method, device, electronic device, storage medium, and program. Background Art

[0002] As the core infrastructure for data asset governance, metadata management platforms enable full lifecycle management of metadata. However, in practice, metadata registration and usage are two separate processes. In the field of software development, metadata involved in the application development process is often manually entered into the metadata management platform by relevant personnel. Staff using this metadata then need to locate and apply it during subsequent development or analysis. This fragmented workflow not only increases communication costs but also makes it easy for human factors to cause metadata updates to lag or registration omissions, which in turn affects business efficiency and hinders the full realization of the value of metadata. Summary of the Invention

[0003] Embodiments of the present invention provide a metadata management method, apparatus, electronic device, storage medium, and program, which can optimize the metadata management process and improve the efficiency of metadata management.

[0004] According to one aspect of the present invention, a metadata management method is provided, which is applied to a metadata management plug-in, comprising:

[0005] Responding to a target metadata change instruction, obtaining a target metadata configuration file;

[0006] Generating a target metadata change application according to the target metadata configuration file, and sending the target metadata change application to a metadata management platform;

[0007] The metadata management platform is configured to generate target metadata content of the target metadata in response to a change application for the target metadata.

[0008] According to another aspect of the present invention, there is provided a metadata management device, configured in a metadata management plug-in, comprising:

[0009] A target metadata configuration file acquisition module is used to acquire a target metadata configuration file in response to a target metadata change instruction;

[0010] A change application sending module, configured to generate a change application for target metadata according to the target metadata configuration file, and send the change application for the target metadata to a metadata management platform;

[0011] The metadata management platform is configured to generate target metadata content of the target metadata in response to a change application for the target metadata.

[0012] According to another aspect of the present invention, an electronic device is provided, comprising:

[0013] at least one processor; and

[0014] a memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores a computer program executable by the at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the metadata management method described in any embodiment of the present invention.

[0016] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the metadata management method according to any embodiment of the present invention when executed.

[0017] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the metadata management method according to any embodiment of the present invention.

[0018] In an embodiment of the present invention, a metadata management plug-in responds to a target metadata change instruction to obtain a target metadata configuration file. Furthermore, a target metadata change request is generated based on the target metadata configuration file and sent to a metadata management platform. In response to the target metadata change request, the metadata management platform generates target metadata content for the target metadata. This solution automates the metadata change process through the metadata management plug-in, resolving the low efficiency and error-prone nature of existing manual metadata management methods. It optimizes the metadata management process and improves metadata management efficiency.

[0019] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1This is a flowchart of a metadata management method provided by the first embodiment of the present invention;

[0022] Figure 2 This is a flowchart of a metadata management method provided by the second embodiment of the present invention;

[0023] Figure 3 This is a flowchart of a new error code application provided in the second embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of a target metadata matching process provided by the second embodiment of the present invention;

[0025] Figure 5 is a schematic diagram of a metadata management device provided by Embodiment 3 of the present invention;

[0026] Figure 6 This is a structural diagram of an electronic device provided in Example 4 of the present invention. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "objective", "association", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] Example 1

[0030] Figure 1This is a flowchart of a metadata management method provided by the first embodiment of the present invention. This embodiment is applicable to the case of automatically managing metadata in a metadata management platform based on a metadata management plug-in. The method can be executed by a metadata management device, which can be implemented by software and / or hardware and can generally be integrated into an electronic device. The electronic device can be a terminal device or a server device. As long as it can run the metadata management plug-in to execute the metadata management method, the embodiment of the present invention does not limit the specific device type of the electronic device. Accordingly, if Figure 1 As shown, the method includes the following operations:

[0031] S110 : Responding to a target metadata change instruction, obtaining a target metadata configuration file.

[0032] The target metadata may be metadata that requires changes. For example, the target metadata may include, but is not limited to, error codes, service methods, and call relationships involved in the application development process. The embodiments of the present invention do not limit the specific types of target metadata. It is understood that the specific types and content of target metadata may vary depending on the application domain of the metadata. A target metadata change instruction may be an instruction to change the target metadata. For example, target metadata change instructions may include, but are not limited to, instructions to add, modify, and delete target metadata. The embodiments of the present invention do not limit the specific types of target metadata change instructions. A target metadata configuration file may be a file used to store associated descriptive information about the target metadata. The associated descriptive information about the target metadata may include, but is not limited to, descriptive metadata such as name and creation date, structural metadata such as data model and data type, and administrative metadata such as data access permissions and data lifecycle. The embodiments of the present invention do not limit the specific content of the associated descriptive information about the target metadata.

[0033] Metadata is data about data. It describes the data's attributes and characteristics and provides contextual information about the data, thereby facilitating its understanding, management, and use. Metadata may include, but is not limited to, information describing the data's structure, format, content, quality, source, version, location, permissions, and update frequency. The present embodiment does not limit the specific content of metadata. Metadata users can manage metadata using a metadata management plug-in. Specifically, if a metadata user requires a change to a specific metadata, they can use that metadata as the target metadata. Furthermore, metadata users can generate a change instruction for the target metadata by clicking a button in the target business tool or entering a command within the target business tool. In response to the change instruction for the target metadata, the metadata management plug-in can retrieve a target metadata configuration file containing associated descriptive information for the target metadata. It is understood that metadata users can use metadata within the target business tool. A metadata management plug-in can be any plug-in designed for automated metadata management, as long as it has this functionality. The present embodiment does not limit the specific type of metadata management plug-in.

[0034] Optionally, the target business tool has a built-in target metadata profile. Metadata users can add relevant descriptions of the target metadata to the target metadata profile before triggering a change to the target metadata. The type and content of the target metadata profile may vary depending on the metadata application domain.

[0035] In a specific example, assuming the target metadata is a service method during application development, a service method configuration file can be built into the target business tool. If the metadata user requires changes to the service method, associated description information for the service method can be added to the service method configuration file. For example, the associated description information for the service method may include, but is not limited to, the service method name, call path, request method, request parameters, and call relationships. The embodiments of the present invention do not limit the specific content of the associated description information for the service method.

[0036] Assuming the target metadata is a call relationship during application development, a call relationship configuration file can be built into the target business tool. If the metadata user requires changes to the call relationship, they can add associated description information for the call relationship to the call relationship configuration file. For example, the associated description information for the call relationship may include, but is not limited to, caller information, callee information, calling method information, and a description of the call relationship. The embodiments of the present invention do not limit the specific content of the associated description information for the call relationship.

[0037] Assuming that the target metadata is an error code in the application development process, an error code configuration file can be built into the target business tool. If the metadata user has a change requirement for the error code, the associated description information of the error code can be added to the error code configuration file. Exemplarily, the associated description information of the error code may include but is not limited to the error level, error description, and solution, etc. The embodiment of the present invention does not limit the specific content included in the associated description information of the error code. Based on the associated description information of the above-mentioned target metadata, the metadata management plug-in can generate an accurate and compliant change application for the target metadata.

[0038] The above example uses the metadata type in the application development process as an example to illustrate obtaining the target metadata configuration file, but it can be understood that the application field of metadata is not limited to the application development field, and the embodiment of the present invention does not limit the specific application field type of metadata.

[0039] S120. Generate a target metadata change application based on the target metadata configuration file, and send the target metadata change application to a metadata management platform; wherein the metadata management platform is used to generate target metadata content of the target metadata in response to the target metadata change application.

[0040] The target metadata change application may be a request submitted to the metadata management platform when making changes to the target metadata during the metadata management process. The target metadata content may be the specific content information included in the target metadata.

[0041] Accordingly, after obtaining the target metadata configuration file, the metadata management plug-in can parse the target metadata configuration file and generate a target metadata change request based on the parsed target metadata configuration file. After generating the target metadata change request, the metadata management plug-in can send the target metadata change request to the metadata management platform. The metadata management platform can respond to the target metadata change request and generate target metadata content based on the content of the target metadata change request.

[0042] Optionally, before generating the target metadata content in response to the target metadata change request, the metadata management platform may also review the rationality and security of the target metadata change request sent by the metadata management plug-in. For example, the platform may check whether the target metadata change request includes the necessary information for the target metadata change, whether the target metadata change request meets business requirements and objectives, and perform a risk assessment on the target metadata change request.

[0043] In an embodiment of the present invention, a metadata management plug-in responds to a target metadata change instruction to obtain a target metadata configuration file. Furthermore, a target metadata change request is generated based on the target metadata configuration file and sent to a metadata management platform. In response to the target metadata change request, the metadata management platform generates target metadata content for the target metadata. This solution automates the metadata change process through the metadata management plug-in, resolving the low efficiency and error-prone nature of existing manual metadata management methods. It optimizes the metadata management process and improves metadata management efficiency.

[0044] Example 2

[0045] Figure 2 This is a flowchart of a metadata management method provided by the second embodiment of the present invention. This embodiment is specific based on the above embodiment. In this embodiment, a specific optional implementation method for generating a target metadata change application based on the target metadata configuration file is provided. At the same time, optional implementation operations after sending the target metadata change application to the metadata management platform are also provided. Figure 2 As shown, the method of this embodiment may include:

[0046] S210 : Responding to a target metadata change instruction, obtaining a target metadata configuration file.

[0047] S220: Generate a target metadata change application according to the target metadata configuration file, and send the target metadata change application to a metadata management platform.

[0048] In an optional embodiment of the present invention, generating a change application for the target metadata based on the target metadata configuration file further includes: obtaining the target stock assets of the target metadata through the platform interface of the metadata management platform; calculating the text similarity between the associated description information of the target metadata in the target metadata configuration file and the target stock assets of the target metadata; and generating a change application for the target metadata based on the size relationship between the text similarity and a preset similarity threshold and the target metadata configuration file.

[0049] Among them, the platform interface can be an interface provided by the metadata management platform for data transmission and interaction. The target stock asset can be metadata stored in the metadata management platform that is consistent with the target metadata type. The text similarity can be the similarity between the associated description information of the target metadata and the target stock asset of the target metadata. The preset similarity threshold can be a pre-set text similarity threshold. Exemplarily, the preset similarity threshold can be 0.7, and the embodiment of the present invention does not limit the specific value of the preset similarity threshold. The application for adding new target metadata can be a request submitted to the metadata management platform when adding new target metadata during the metadata management process.

[0050] In this embodiment of the present invention, the metadata management platform provides interfaces for data transmission and interaction for different types of metadata. It is understood that different platform interfaces correspond to different types of metadata. Metadata users can click a button on the metadata management plug-in to trigger the plug-in to invoke the metadata management platform's platform interface to obtain target inventory assets with target metadata. The plug-in then stores the target inventory assets in a target metadata configuration file for user access.

[0051] In a specific example, assuming the target metadata is an error code, the metadata management platform's error code registration table provides a download interface for the full set of error codes, including their descriptions. Metadata users can click a button in the target business tool or enter a command within the tool, triggering the metadata management plug-in to invoke the full error code download interface to retrieve the existing error codes. The plug-in then updates the existing error codes to the target business tool's error code usage table or program cache for user access.

[0052] Furthermore, assuming that the change instruction of the target metadata is an instruction to add new target metadata, after obtaining the target stock assets of the target metadata, the text similarity between the associated description information of the target metadata in the target metadata configuration file and the target stock assets of the target metadata can be calculated to determine whether it is necessary to submit a change application to the metadata management platform for the target metadata based on the relationship between the text similarity and the preset similarity threshold. In the case where it is determined that the text similarity is less than the preset similarity threshold, it can be determined that there is no metadata in the target stock assets of the target metadata that is highly similar to the associated description information of the target metadata. If the change instruction of the target metadata is an instruction to add new target metadata, then an application for adding new target metadata can be submitted to the metadata management platform for the target metadata; if the change instruction of the target metadata is an instruction to modify the target metadata or an instruction to delete the target metadata, then there is no need to submit an application for modifying the target metadata or an application for deleting the target metadata to the metadata management platform for the target metadata.

[0053] If the text similarity is determined to be greater than or equal to the preset similarity threshold, it can be determined that metadata with a high degree of similarity to the target metadata's associated descriptive information already exists in the target stock asset of the target metadata. If the target metadata change instruction is a target metadata addition instruction, there is no need to submit a target metadata addition application to the metadata management platform for the target metadata. If the target metadata change instruction is a target metadata modification instruction or a target metadata deletion instruction, then a target metadata modification application or a target metadata deletion application can be submitted to the metadata management platform for the target metadata. The above method can effectively avoid unnecessary change operations while ensuring that important changes are not missed, thereby improving metadata management efficiency.

[0054] Figure 3 This is a flow chart of a new error code application provided by the second embodiment of the present invention. In a specific example, Figure 3 As shown, in application development scenarios, error code configuration files can be built into the code engineering process and uniformly named. Before generating instructions for adding target metadata, associated descriptions for the error codes can be defined in the error code configuration file. To prevent newly applied error codes from overwriting existing error codes when written back, temporary error codes can be used as placeholders when defining associated descriptions for error codes, such as those beginning with "777." Developers can trigger the instruction to add an error code using a button or command. The metadata management plug-in can include a metadata management component. In response to the instruction to add an error code, the metadata management component can parse the error code configuration file using an error code configuration file parser and, based on the parsed error code configuration file, request an error code assignment from the metadata management platform. The metadata management platform's error code assigner can assign error codes, and the error code registration table can register the newly applied error code. Metadata change requests based on this metadata management plug-in eliminate the need for developers to manually log in to the metadata management platform, improving development efficiency and ensuring metadata accuracy and consistency.

[0055] S230: Calling the platform interface of the metadata management platform to obtain target metadata content of the target metadata.

[0056] Specifically, after generating a target metadata change request based on the target metadata configuration file and sending the target metadata change request to the metadata management platform, the metadata management platform can generate target metadata content for the target metadata in response to the target metadata change request. Furthermore, the metadata management plug-in can call a platform interface of the metadata management platform to obtain the target metadata content for the target metadata.

[0057] In a specific example, assuming the target metadata change instruction is a target metadata addition instruction, the target metadata change request can be a target metadata addition request. The metadata management platform can register the target metadata based on the target metadata addition request. For example, assuming the target metadata is an error code, the metadata user requests the metadata management platform for an error code corresponding to "Internal Server Error" using the metadata management plug-in. The metadata management platform can then generate an error code "500" based on the associated description information of the error code in the target metadata configuration file. The metadata management plug-in can then call the metadata management platform's platform interface to obtain the error code "500" corresponding to "Internal Server Error."

[0058] Assuming that the target metadata change instruction is a target metadata modification instruction, the target metadata change request can be a target metadata modification request, and the metadata management platform can modify the target metadata based on the target metadata modification request. For example, assuming that the target metadata is a service method, the metadata user, through the metadata management plug-in, submits a request to the metadata management platform to modify the service that service method A depends on to service B. The metadata management platform can then modify the service that service method A depends on to service B based on the associated description information of service method A in the target metadata configuration file. The metadata management plug-in can call the platform interface of the metadata management platform to obtain the services that service method A depends on.

[0059] Assuming the target metadata change instruction is a target metadata deletion instruction, the target metadata change request can be a target metadata deletion request, and the metadata management platform can delete the target metadata based on the target metadata deletion request. For example, assuming the target metadata is a service method, the metadata user requests the metadata management platform to delete service method A using the metadata management plug-in. The metadata management platform can then delete service method A based on the associated description information of service method A in the target metadata configuration file.

[0060] S240: Write the target metadata content of the target metadata back to the target metadata configuration file.

[0061] Correspondingly, after calling the platform interface of the metadata management platform to obtain the target metadata content of the target metadata, the metadata management plug-in can write the target metadata content of the target metadata back to the target metadata configuration file to update the target stock assets of the target metadata in the target metadata configuration file, thereby ensuring the accuracy and consistency of the metadata and improving the management efficiency of the metadata.

[0062] like Figure 3As shown, in a specific example, the metadata management component can use the error code allocation writer to write the newly applied error code back to the error code configuration file, and change the temporary error code in the error code configuration file to the newly applied error code in the metadata management platform.

[0063] In an optional embodiment of the present invention, the target metadata is metadata in the application development field. After writing back the target metadata content of the target metadata to the target metadata configuration file, the method further includes: obtaining a coding input keyword of a code editor; matching the coding input keyword with the target configuration file in an artificial intelligence manner to obtain a keyword matching result; and processing the target metadata according to the keyword matching result.

[0064] Metadata in the application development field may be metadata that may be used during the application development process. A code editor may be a tool for writing and editing computer code. Coding input keywords may be specific words entered by a developer in the code editor. Keyword matching results may be matching results between coding input keywords and the contents of a target metadata configuration file.

[0065] Specifically, in the application development scenario, the metadata management plug-in can obtain the coding input keywords entered by the developer based on the code editor, so that the coding input keywords related to the metadata can be dynamically identified during the development process. For example, when the developer enters specific keywords related to metadata such as error codes, service methods, or call relationships, the metadata management plug-in can trigger corresponding operations. After obtaining the coding input keywords of the code editor, the metadata management plug-in can match the coding input keywords with the contents of the target metadata configuration file based on artificial intelligence, so as to obtain keyword matching results. Furthermore, the target metadata can be processed according to the keyword matching results. For example, possible matching results can be displayed or relevant suggestions can be made based on the keyword matching results. Feedback can be provided in real time when the user enters the coding input keywords, thereby enhancing the user experience. At the same time, the timeliness and accuracy of metadata updates are ensured.

[0066] Figure 4 This is a schematic diagram of a target metadata matching process provided by the second embodiment of the present invention. In a specific example, Figure 4As shown, the metadata management plug-in can also include an intelligent R&D component. When developers enter coding input keywords in the code editor, the intelligent R&D component can use a pre-trained machine learning model to search and match the coding input keywords with the content in the target metadata configuration file, obtaining keyword matching results. It should be noted that historical usage of coding input keywords and target metadata can be used as training sample data to train the machine learning model.

[0067] In an optional embodiment of the present invention, the processing of the target metadata according to the keyword matching result may include: when it is determined that the keyword matching result is successful and the target metadata is an error code, displaying the content of the error code in the interface of the code editor; when it is determined that the keyword matching result is a failure, popping up a prompt message of the change application of the target metadata in the code editor.

[0068] The prompt information for applying for a change in the target metadata may be a prompt for the metadata user to apply for a change in the target metadata.

[0069] like Figure 4 As shown, when processing the target metadata based on the keyword matching result, if the keyword matching result is successful and the target metadata is an error code, the error code of the successful match can be displayed in the code editor. It should be noted that the code editor can not only display the error code of the successful match, but also display the associated description information of the error code. This functional design allows metadata users to more intuitively understand the specific meaning of the error code, so as to quickly locate the problem and take appropriate measures. For example, the display content in the code editor can be "404: Not Found". If the keyword matching result is a failure, it means that the target metadata configuration file does not contain target metadata that matches the encoding input keyword. The metadata user needs to use new metadata. In this case, the metadata management plug-in can pop up a prompt message for the target metadata change application in the code editor, guiding the metadata user to submit a new metadata application to the metadata management platform through the metadata management plug-in, thereby ensuring the timeliness and accuracy of metadata updates.

[0070] The metadata management plug-in of the embodiment of the present invention obtains the target metadata configuration file by responding to the change instruction of the target metadata. Furthermore, a change application for the target metadata is generated based on the target metadata configuration file, and the change application for the target metadata is sent to the metadata management platform. The metadata management platform generates the target metadata content of the target metadata in response to the change application for the target metadata. The metadata management plug-in calls the platform interface of the metadata management platform to obtain the target metadata content of the target metadata, and writes the target metadata content back to the target metadata configuration file. Furthermore, the metadata management plug-in obtains the coding input keywords of the code editor, and matches the coding input keywords with the target metadata configuration file based on artificial intelligence to obtain keyword matching results, thereby processing the target metadata according to the keyword matching results. The above scheme automatically integrates the metadata change process through the metadata management plug-in, solves the problems of low metadata management efficiency and error-proneness in the existing method of manually managing metadata, and can optimize the metadata management process and improve the efficiency of metadata management.

[0071] In the technical solution disclosed herein, the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0072] It should be noted that, in the embodiment of the present invention, a corresponding operation entry can be provided for the user to choose to agree or reject the automated decision result; if the user chooses to reject, the expert decision process will be entered.

[0073] It should be noted that any arrangement and combination of the technical features in the above embodiments also falls within the protection scope of the present invention.

[0074] Example 3

[0075] Figure 5 Schematic diagram of a metadata management device provided by the third embodiment of the present invention. Figure 5 As shown, the device is configured in a metadata management plug-in, including: a target metadata configuration file acquisition module 310, and a change application sending module 320, wherein:

[0076] The target metadata configuration file acquisition module 310 is configured to acquire the target metadata configuration file in response to a target metadata change instruction.

[0077] The change application sending module 320 is configured to generate a change application for target metadata according to the target metadata configuration file, and send the change application for target metadata to a metadata management platform.

[0078] The metadata management platform is configured to generate target metadata content of the target metadata in response to a change application for the target metadata.

[0079] In an embodiment of the present invention, a metadata management plug-in responds to a target metadata change instruction to obtain a target metadata configuration file. Furthermore, a target metadata change request is generated based on the target metadata configuration file and sent to a metadata management platform. In response to the target metadata change request, the metadata management platform generates target metadata content for the target metadata. This solution automates the metadata change process through the metadata management plug-in, resolving the low efficiency and error-prone nature of existing manual metadata management methods. It optimizes the metadata management process and improves metadata management efficiency.

[0080] Optionally, the above-mentioned device may further include a target metadata content write-back module, which is used to call the platform interface of the metadata management platform to obtain the target metadata content of the target metadata; and write the target metadata content of the target metadata back to the target metadata configuration file.

[0081] Optionally, the change application sending module 320 is specifically used to: obtain the target stock assets of the target metadata through the platform interface of the metadata management platform; calculate the text similarity between the associated description information of the target metadata in the target metadata configuration file and the target stock assets of the target metadata; generate a change application for the target metadata based on the size relationship between the text similarity and a preset similarity threshold, and the target metadata configuration file.

[0082] Optionally, the target metadata includes an error code, and the associated description information of the error code includes at least one of the error level, error description and solution; the target metadata includes a service method, and the associated description information of the error code includes at least one of the service method name, call path, request method, request parameters and call relationship; and / or the target metadata includes a call relationship, and the associated description information of the error code includes at least one of the caller information, callee information, call method information and call relationship description.

[0083] Optionally, the target metadata is metadata in the application development field, and the above-mentioned device may further include a target metadata processing module for obtaining a coding input keyword of a code editor; matching the coding input keyword with the target metadata configuration file based on artificial intelligence to obtain a keyword matching result; and processing the target metadata according to the keyword matching result.

[0084] Optionally, the target metadata processing module is specifically used to: when it is determined that the keyword matching result is successful and the target metadata is an error code, display the content of the error code in the interface of the code editor; when it is determined that the keyword matching result is a failure, pop up a prompt message of the target metadata change application in the code editor.

[0085] The metadata management device can execute the metadata management method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. For technical details not fully described in this embodiment, please refer to the metadata management method provided by any embodiment of the present invention.

[0086] Since the metadata management device described above is capable of executing the metadata management method according to the embodiments of the present invention, those skilled in the art will be able to understand the specific implementation and various variations of the metadata management device according to the embodiments of the present invention based on the metadata management method described in the embodiments of the present invention. Therefore, the details of how the metadata management device implements the metadata management method according to the embodiments of the present invention will not be described in detail here. Any device implemented by those skilled in the art using the metadata management method according to the embodiments of the present invention falls within the scope of protection of this application.

[0087] Example 4

[0088] Figure 6 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0089] like Figure 6As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11. The memory stores a computer program that can be executed by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the electronic device 10 can also be stored in the RAM 13. The processor 11, ROM 12, and RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0090] Multiple components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0091] The processor 11 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, a digital signal processor (DSP), and any other suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the metadata management method.

[0092] In some embodiments, the metadata management method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the metadata management method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the metadata management method in any other suitable manner (e.g., via firmware).

[0093] Optionally, a metadata management method, applied to a metadata management plug-in, may include: obtaining a target metadata configuration file in response to a change instruction of the target metadata; generating a change application for the target metadata based on the target metadata configuration file, and sending the change application for the target metadata to a metadata management platform; wherein the metadata management platform is used to generate target metadata content for the target metadata in response to the change application for the target metadata.

[0094] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0095] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0096] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0097] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and the input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0098] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0099] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0100] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not a limitation herein.

[0101] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A metadata management method, characterized in that: Applicable to metadata management plug-ins, including: Responding to a target metadata change instruction, obtaining a target metadata configuration file; Generating a target metadata change application according to the target metadata configuration file, and sending the target metadata change application to a metadata management platform; The metadata management platform is configured to generate target metadata content of the target metadata in response to a change application for the target metadata.

2. The method according to claim 1, characterized in that After sending the target metadata change application to the metadata management platform, the method further includes: Calling the platform interface of the metadata management platform to obtain target metadata content of the target metadata; Write the target metadata content of the target metadata back to the target metadata configuration file.

3. The method according to claim 1, characterized in that Generating a target metadata change application according to the target metadata configuration file includes: Acquire the target stock assets of the target metadata through the platform interface of the metadata management platform; Calculating text similarity between the associated description information of the target metadata in the target metadata configuration file and the target stock asset of the target metadata; A target metadata change application is generated according to a magnitude relationship between the text similarity and a preset similarity threshold, and the target metadata configuration file.

4. The method according to claim 3, wherein: The target metadata includes an error code, and the associated description information of the error code includes at least one of an error level, an error description, and a solution; The target metadata includes a service method, and the associated description information of the error code includes at least one of a service method name, a call path, a request method, request parameters, and a call relationship; and / or The target metadata includes a calling relationship, and the associated description information of the error code includes at least one of caller information, callee information, calling method information, and a calling relationship description.

5. The method according to claim 2, characterized in that The target metadata is metadata in the application development field. After writing the target metadata content of the target metadata back to the target metadata configuration file, the method further includes: Get the coding input keyword of the code editor; Matching the encoded input keyword with the target metadata configuration file in an artificial intelligence manner to obtain a keyword matching result; The target metadata is processed according to the keyword matching result.

6. The method according to claim 5, characterized in that The processing of the target metadata according to the keyword matching result includes: If the keyword matching result is determined to be successful and the target metadata is determined to be an error code, displaying the content of the error code in the interface of the code editor; When it is determined that the keyword matching result is a failure, a prompt message of the target metadata change application is popped up in the code editor.

7. A metadata management device, characterized in that: Configuration in metadata management plug-in, including: A target metadata configuration file acquisition module is used to acquire a target metadata configuration file in response to a target metadata change instruction; A change application sending module, configured to generate a change application for target metadata according to the target metadata configuration file, and send the change application for the target metadata to a metadata management platform; The metadata management platform is configured to generate target metadata content of the target metadata in response to a change application for the target metadata.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executed by the at least one processor, and the computer program is executed by the at least one processor so as to enable the at least one processor to execute the metadata management method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the metadata management method according to any one of claims 1 to 6 when executed.

10. A computer program product comprising a computer program / instructions, wherein: When the computer program / instructions are executed by a processor, the metadata management method according to any one of claims 1 to 6 is implemented.

Images