CN117609055A

CN117609055A - Data management method, device, electronic equipment and storage medium

Info

Publication number: CN117609055A
Application number: CN202311629716.3A
Authority: CN
Inventors: 郑磊; 唐守忠
Original assignee: Agricultural Bank of China
Current assignee: Agricultural Bank of China
Priority date: 2023-11-30
Filing date: 2023-11-30
Publication date: 2024-02-27

Abstract

The invention discloses a data management method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: under the condition that the end of production change of the target production system is detected, acquiring production technology metadata corresponding to the target production system, and storing the production technology metadata based on a preset data storage form; invoking pre-stored design state technology metadata of a target design state system corresponding to the target production state system; under the condition that the production state technology metadata and the design state technology metadata are inconsistent, the design state technology metadata are updated based on the production state technology metadata, and the updated design state technology metadata are fed back to the target design state system. According to the technical scheme provided by the embodiment of the invention, the effect of effectively managing the data assets of the application system based on the binary technology metadata is realized, and the effect of managing the corresponding data assets by the cooperative coordination of the binary technology metadata is achieved.

Description

Data management method, device, electronic equipment and storage medium

Technical Field

The present invention relates to the field of data management technologies, and in particular, to a data management method, a data management device, an electronic device, and a storage medium.

Background

The enterprise-level data asset management system collects and stores technical metadata information from each application system, and based on the data, various indexes and labels for service development and high-level decision making are derived. How to ensure the quick, accurate and easy-to-use technology metadata updating of all application systems in an enterprise, assist research and development personnel to discover and solve potential problems possibly existing in a production environment in time, and the key is to make the acquisition and application of the technology metadata.

At present, an acquisition application system generally manages design state technology metadata as data asset technology metadata, and when the design state technology metadata is applied to system development, data analysis and decision-making, the problem that the design state technology metadata is inconsistent with an actual production environment and influence is possibly caused, and even, a system safety fault is possibly caused.

Disclosure of Invention

The invention provides a data management method, a device, electronic equipment and a storage medium, which are used for realizing the effect of effectively managing data assets of an application system based on binary technology metadata and achieving the effect of managing corresponding data assets by cooperative coordination of the binary technology metadata.

According to an aspect of the present invention, there is provided a data management method, the method comprising:

under the condition that the end of production change of a target production state system is detected, acquiring production state technology metadata corresponding to the target production state system, and storing the production state technology metadata based on a preset data storage form, wherein the target production state system is an application system positioned in a production environment;

invoking pre-stored design state technology metadata of a target design state system corresponding to the target production state system, wherein the target design state system is an application system positioned in a test environment;

and under the condition that the production state technology metadata and the design state technology metadata are inconsistent, updating the design state technology metadata based on the production state technology metadata, and feeding the updated design state technology metadata back to the target design state system.

According to another aspect of the present invention, there is provided a data management apparatus comprising:

the technical metadata acquisition module is used for acquiring production state technical metadata corresponding to a target production state system under the condition that the end of production change of the target production state system is detected, and storing the production state technical metadata based on a preset data storage form, wherein the target production state system is an application system positioned in a production environment;

The technical metadata calling module is used for calling pre-stored design state technical metadata of a target design state system corresponding to the target production state system, wherein the target design state system is an application system positioned in a test environment;

and the technical metadata updating module is used for updating the design state technical metadata based on the production state technical metadata under the condition that the production state technical metadata and the design state technical metadata are inconsistent, and feeding the updated design state technical metadata back to the target design state system.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the data management method according to any one of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute a data management method according to any one of the embodiments of the present invention.

According to the technical scheme, under the condition that the production state system production change is detected to be finished, the production state technical metadata corresponding to the target production state system are collected and stored based on the preset data storage form, further, the pre-stored design state technical metadata of the target design state system corresponding to the target production state system are retrieved, finally, under the condition that the production state technical metadata and the design state technical metadata are inconsistent, the design state technical metadata are updated based on the production state technical metadata, the updated design state technical metadata are fed back to the target design state system, the problem that influences are generated due to the fact that the design state technical metadata are inconsistent with an actual production environment in the related technology is solved, even the problem that system safety faults are possibly caused is solved, the effect that the data assets of an application system can be effectively managed based on the binary technical metadata is achieved, the effect that the binary technical metadata are cooperatively matched to manage the corresponding data assets is achieved, and further, the management efficiency and the management accuracy of the application system data assets are improved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a data management method according to a first embodiment of the present invention;

fig. 2 is a schematic structural diagram of a data management device according to a second embodiment of the present invention;

fig. 3 is a schematic structural diagram of a data management device according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device implementing a data management method according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

Fig. 1 is a flowchart of a data management method according to a first embodiment of the present invention, where the method may be implemented by a data management device, and the data management device may be implemented in hardware and/or software, and the data management device may be configured in a terminal and/or a server. As shown in fig. 1, the method includes:

S110, when the end of production change of the target production system is detected, the production technology metadata corresponding to the target production system is collected, and the production technology metadata is stored based on a preset data storage form.

Wherein the target production system is an application system located in a production environment.

In this embodiment, the target production system may be understood as an application system that completes the production change, and the application system is located in the production environment. The production environment may be understood as the actual application environment of the application system, or may be understood as the actual production environment of the application system. The production change can be understood as the change of repairing, optimizing, upgrading functions and the like of the produced system. The production state technology metadata can be understood as data table structure information in the production environment after production. The metadata refers to data describing data, mainly information describing data attributes, and is used for supporting functions such as indicating storage locations, historical data, resource searching, file recording and the like. The data storage form may be understood as a form in which metadata is stored in the current system. The current system may be a data asset management system for managing technical metadata corresponding to each application system in various environments. The data storage form may be any form, and alternatively, may be a nested key-value data storage form. In practical application, when storing, the state (production state or design state) of the technical metadata and the table name can be combined together, and the Value is used as a first layer Key Key of a Key-Value storage structure to store a new Key-Value object in a nested manner. The Key of the nested Key-Value object is a field name, and the Value is a list structure, which is a field position, a field type and a field length respectively.

In practical application, a plurality of production state systems to be collected may be preset, and a production change time window corresponding to each production state system to be collected may be obtained. And if any production state system to be collected in the plurality of production state systems to be collected is detected to finish production change within the corresponding production change time window, determining the production state system to be collected as a target production state system. Furthermore, the production state technology metadata corresponding to the target production state system can be collected, the collected production state technology metadata is analyzed to determine the data structure of the production state technology metadata, and the collected production state technology metadata can be stored according to a preset data storage form.

It should be noted that the number of the target production systems may be one or more. Whether one or a plurality of the technical metadata acquisition and the technical metadata processing can be carried out by adopting the technical scheme provided by the embodiment.

S120, the pre-stored design state technology metadata of the target design state system corresponding to the target production state system is called.

Wherein the target design system is an application system located in a test environment.

In this embodiment, the target design system is an application system corresponding to the target production system and located in the test environment. It should be noted that the target production system and the target design system corresponding thereto are the same application system located in two different environments (production environment and test environment). Illustratively, it is assumed that application A, application B, and application C are included in the production environment, and application A, application B, and application C are also included in the test environment. If the target production system is the application system A located in the production environment, the target design system corresponding to the target production system is the application system A located in the test environment. The test environment is understood to be an environment for testing whether programs and codes in the software development process can normally run in the software development period. A test environment can be understood as a simulation scenario of a software development process that simulates various conditions and operations in a real environment. Design state technical metadata may be understood as data table structure information designed by a technician during the development design phase.

It should be noted that, in this embodiment, in order to manage technical metadata of each application system more accurately, a test environment and a production environment may be set at the same time, where the test environment and the production environment include the same application system, that is, after the application system is put into production to be actually applied, the system setting of the application system in the test environment is still kept, and the application system is continuously detected.

In practical application, before the design state technology metadata corresponding to the target design state system is called, the design state technology metadata corresponding to each design state system to be collected in the test environment can be collected and stored. In this embodiment, the manner of collecting the metadata of the design state technology may include at least two, and optionally, automatic collection or manual entry. These two ways can be described separately below:

the first way is: and acquiring at least one design state technical metadata corresponding to the design state system to be acquired according to a preset period, and storing the design state technical metadata according to a preset data storage form.

In this embodiment, the preset period may be any period, and optionally, may be 30 minutes 1 time, 1 hour 1 time, or 6 hours 1 time, which is not limited in this embodiment. A design to collect system is understood to be an application to collect metadata, and the application is located in a test environment.

In practical application, for each design state system to be collected in the test environment, the design state technical metadata corresponding to each design state system to be collected can be collected according to a preset period. Furthermore, the collected technical metadata of each design state can be analyzed to determine the corresponding data structure of the technical metadata of each design state. Furthermore, the metadata of each design state technology can be stored according to a preset data storage form.

It should be noted that, when storing each design state technology metadata, the system identifier corresponding to the corresponding design state system to be collected may be stored correspondingly, so that the design state technology metadata corresponding to the required target design state system may be located in the stored design state technology metadata.

The second way is: displaying a data entry page; and responding to the input triggering operation aiming at the design state metadata input items in the data input page, acquiring the input design state technology metadata, and storing the input design state technology metadata based on a preset data storage form.

In this embodiment, a data entry page may be understood as a visualization page for entry of design metadata. In practical application, a page display trigger operation for displaying the data entry page may be preset, so that when the page display trigger operation is detected, the page display trigger operation may be responded, so that the data entry page is displayed on the display interface. Optionally, the page display triggering operation may include at least one of: triggering a page display control; receiving a page display trigger instruction; the audio information includes wake-up words corresponding to the page display trigger operation, and the like. It should be noted that the benefits of displaying the data entry page are: an interaction portal for data entry is provided for the user so that the user can perform data entry of design state technology metadata based on the data entry page.

The design state metadata entry term can be understood as an entry edit box for entering design state technical metadata.

In practical application, when the triggering operation of page display is detected, the triggering operation can be responded, and the data entry page is displayed. Further, the entry triggering operation can be input for the design metadata entry presented in the data entry page. And when the input trigger operation aiming at the design state metadata input item is detected, responding to the input trigger operation, and acquiring the input design state technical metadata. The entered design state technology metadata may then be stored based on a preset data storage format.

It should be noted that, the metadata may be collected in the first mode or in the second mode, so as to change the stored design technical metadata.

Based on the above, the above technical means further includes: in response to an edit triggering operation for the design state technology metadata, the stored corresponding design state technology metadata is updated based on the edited design state technology metadata.

In this embodiment, the edit triggering operation may be understood as an interactive operation of re-editing the stored design technology metadata. Optionally, the editing trigger operation includes at least one of a data deletion trigger operation, a data addition trigger operation, and a data modification trigger operation. The data deletion triggering operation may be understood as a triggering operation for deleting at least part of data in the stored design technology metadata. The data newly-added triggering operation can be understood as a triggering operation of newly-added data in the stored design state technology metadata. The data change trigger operation may be understood as a trigger operation for modifying stored design technology metadata.

In practical applications, stored design technology metadata may be displayed in a visual editing area so that a user may verify the stored design technology metadata. Further, the user may input an edit trigger operation to the stored design technical metadata through an input device (e.g., a mouse or a keyboard, etc.), and in the case where an edit trigger operation for the design technical metadata is detected, may respond to the detected edit trigger operation. Furthermore, the edited design state technology metadata can be obtained, and the stored corresponding design state technology metadata can be updated based on the edited design state technology metadata.

Further, after the target production state system is determined, a target design state system corresponding to the target production state system may be determined. Furthermore, design state technology metadata corresponding to the target design state system may be retrieved from the stored design state technology metadata.

Optionally, retrieving pre-stored design state technology metadata of a target design state system corresponding to the target production state system includes: acquiring a production state system identifier corresponding to a target production state system; determining a design state system to be acquired corresponding to the target production state system based on prestored system corresponding information and the production state system identification, taking the system to be acquired as a target design state system, and acquiring a design state system identification corresponding to the target design state system; retrieving design state technology metadata corresponding to the target design state system from pre-stored design state technology metadata based on the design state system identification.

The system correspondence information is used for indicating the correspondence between the design state system identification of the design state system to be collected and the production state system identification of the production state system to be collected.

In this embodiment, the production system identification may be identification information for identifying the production system. The production system identifier may be any form of identification information, and may alternatively be a character string composed of at least one character. The system correspondence information may be information characterizing a mapping relationship between a design state system identifier of the design state system to be collected and a production state system identifier of the production state system to be collected. In practical application, a plurality of design systems to be collected may be preset, and design system identifiers corresponding to the design systems to be collected may be determined. Furthermore, the production state systems to be collected corresponding to the design state systems to be collected are determined, and a plurality of production state systems to be collected can be obtained. And then, determining the production state system identification corresponding to each production state system to be acquired. Further, the design state system identifier of each design state system to be collected and the production state system identifier of the corresponding production state system to be collected may be associated, so as to establish a corresponding relationship between the design state system identifier of the design state system to be collected and the production state system identifier of the production state system to be collected. Further, system correspondence information may be generated based on the correspondence relation and stored in the system.

In practical application, after the target production state system is determined, the production state system identifier corresponding to the target production state system can be obtained. Furthermore, the method can be used for inquiring in prestored system corresponding information based on the production state system identification so as to determine a design state system to be acquired corresponding to the target production state system, and the design state system to be acquired is used as the target design state system. Meanwhile, the design state system identification corresponding to the target design state system can be obtained based on the information corresponding to the system. Further, design state technology metadata corresponding to the target design state system may be retrieved from the pre-stored design state technology metadata based on the design state system identification.

And S130, under the condition that the production state technology metadata and the design state technology metadata are inconsistent, updating the design state technology metadata based on the production state technology metadata, and feeding the updated design state technology metadata back to the target design state system.

In this embodiment, after the production state technical metadata corresponding to the target production state system and the design state technical metadata corresponding to the target design state system are obtained, the production state technical metadata and the design state technical metadata may be compared to determine whether the technical metadata in the two states are consistent. Further, in the case where it is determined that the technical metadata of the two states are inconsistent, the design state technical metadata may be processed.

In this embodiment, the manner of determining that the production state technology metadata and the design state technology metadata are inconsistent may include a plurality of ways, and optionally, detecting that the field positions of the production state technology metadata and the design state technology metadata are inconsistent; detecting that field types of the production state technology metadata and the design state technology metadata are inconsistent; the field lengths of the production state technology metadata and the design state technology metadata are detected to be inconsistent.

In practical application, after the production state technical metadata and the design state technical metadata are obtained, field-by-field comparison can be performed on the technical metadata in the two states, and whether the technical metadata in the two states are consistent is determined according to field comparison results of the fields. In the comparison process, if the field positions of the production state technical metadata and the design state technical metadata are detected to be inconsistent, the inconsistency of the production state technical metadata and the design state technical metadata can be determined. If the field types of the production state technology metadata and the design state technology metadata are detected to be inconsistent, the production state technology metadata and the design state technology metadata can be determined to be inconsistent. If the field lengths of the production state technology metadata and the design state technology metadata are detected to be inconsistent, the production state technology metadata and the design state technology metadata can be determined to be inconsistent.

It should be noted that, in addition to the above three manners, other data comparison methods may be used to perform data comparison on the production state technical metadata and the design state technical metadata, and determine whether the technical metadata in the two states are consistent, which is not limited in particular in this embodiment.

Further, in the case that it is determined that the production technology metadata and the design technology metadata are inconsistent, the design technology metadata may be updated based on the production technology metadata, so that the updated design technology metadata is the production technology metadata. The updated design technology metadata may then be fed back to the target design system. The advantages of this arrangement are that: the problems existing in the design system can be corrected in time, and further, the more serious system safety problem is avoided.

In practical application, in order to timely inform related personnel to perform system maintenance when abnormal conditions are detected, under the condition that production state technical metadata and design state technical metadata are inconsistent, tasks to be handled are generated and sent to a target terminal.

In this embodiment, the task to be handled may be understood as a task to be checked and confirmed. The task to be handled may include technical metadata in the production state, technical metadata in the design state, and difference information between the two types of technical metadata (e.g., inconsistent field locations, inconsistent field types, and/or inconsistent field lengths, etc.). The target terminal may be understood as a terminal to which a target user set in advance belongs. The target user may be an operation and maintenance person, for example.

In practical application, under the condition that the production state technology metadata and the design state technology metadata are inconsistent, abnormal information between the production state technology metadata and the design state technology metadata can be acquired. Furthermore, the task to be handled can be generated according to the production state technology metadata, the design state technology metadata and the abnormal information, and the generated task to be handled is sent to the target terminal, so that a target user to which the target terminal belongs can timely check and confirm the production state technology metadata and the design state technology metadata after receiving the task to be handled.

Example two

Fig. 2 is a schematic structural diagram of a data management device according to a second embodiment of the present invention. The embodiment of the invention is an alternative embodiment to the above-described embodiment. The data management method provided by the foregoing embodiments may be performed based on the data management apparatus provided by the embodiments of the present invention. As shown in fig. 2, the system includes: a data asset management system 21, a production environment 22, a stock test environment 23, and a change management system 24. The production environment 22 includes an application system a, an application system B, an application system C, and the like. The stock test environment 23 includes an application system a, an application system B, an application system C, and the like.

Specifically, the design to be collected system and the data storage form are configured in the data asset management system 21. Afterwards, the data asset management system 21 regularly collects design state technical metadata of each design state system to be collected, such as an application system A, an application system B, an application system C and the like, included in the stock test environment 23 every day, and stores the metadata based on a preset data storage form; or, in response to a data entry operation input by a user for the data entry page, acquiring the entered design state technology metadata, and storing the metadata based on a preset data storage form. Thereafter, the to-be-acquired production systems and data storage forms are configured in the data asset management system 21 and associated with the change management system 24 to obtain a commissioning change time window for each to-be-acquired production system based on the change management system 24. Further, when detecting that a target production state system with production change finished exists in each production state system to be collected, including an application system a, an application system B, an application system C and the like, included in the production environment 22, the production state technology metadata of the target production state system is collected and stored based on a preset data storage form. Further, comparing the design state technical metadata and the production state technical metadata in the data asset management system 21, updating the design state technical metadata based on the production state technical metadata when the two states of technical metadata are inconsistent, and generating a task to be handled and sending the task to the target terminal.

Example III

Fig. 3 is a schematic structural diagram of a data management device according to a third embodiment of the present invention. As shown in fig. 3, the apparatus includes: a technical metadata acquisition module 310, a technical metadata retrieval module 320, and a technical metadata update module 330.

The technical metadata collection module 310 is configured to collect production state technical metadata corresponding to a target production state system under the condition that a production change of the target production state system is detected to be finished, and store the production state technical metadata based on a preset data storage form, wherein the target production state system is an application system located in a production environment; a technical metadata retrieving module 320, configured to retrieve pre-stored design state technical metadata of a target design state system corresponding to the target production state system, where the target design state system is an application system located in a test environment; and a technology metadata updating module 330, configured to update the design state technology metadata based on the production state technology metadata and feed back the updated design state technology metadata to the target design state system, if it is determined that the production state technology metadata and the design state technology metadata are inconsistent.

Optionally, the XX module includes:

optionally, the apparatus further includes: a technical metadata storage module.

And acquiring at least one design state technical metadata corresponding to the design state system to be acquired according to a preset period, and storing each design state technical metadata according to a preset data storage form.

Optionally, the apparatus further includes: the system comprises a page display module and a data entry module.

The page display module is used for displaying a data input page;

the data input module is used for responding to input triggering operation aiming at design state metadata input items in the data input page, acquiring the input design state technology metadata and storing the input design state technology metadata based on a preset data storage form.

Optionally, the apparatus further includes: and a data editing module.

And the data editing module is used for responding to an editing triggering operation aiming at the design state technology metadata and updating the stored corresponding design state technology metadata based on the edited design state technology metadata, wherein the editing triggering operation comprises at least one of a data deleting triggering operation, a data adding triggering operation and a data changing triggering operation.

Optionally, the technical metadata retrieval module 320 includes: the system comprises a system identification acquisition unit, a target design state system determination unit and a technical metadata calling unit.

A system identifier obtaining unit, configured to obtain a production state system identifier corresponding to the target production state system;

the system comprises a target design state system determining unit, a target design state system determining unit and a target production state system determining unit, wherein the target design state system determining unit is used for determining a design state system to be acquired, which corresponds to the target production state system, based on prestored system corresponding information and the production state system identifier, and obtaining the design state system identifier corresponding to the target design state system, wherein the system corresponding information is used for indicating the corresponding relation between the design state system identifier of the design state system to be acquired and the production state system identifier of the production state system to be acquired;

and the technical metadata calling unit is used for calling the design state technical metadata corresponding to the target design state system from the prestored design state technical metadata based on the design state system identification.

Optionally, the technical metadata update module 330 includes: and a data detection unit. The data detection unit is used for executing at least one of the following operations: detecting that the field positions of the production state technology metadata and the design state technology metadata are inconsistent; detecting that the field types of the production state technology metadata and the design state technology metadata are inconsistent; and detecting that the field lengths of the production state technology metadata and the design state technology metadata are inconsistent.

Optionally, the apparatus further includes: and a task generating module.

And the task generating module is used for generating a task to be handled and sending the task to a target terminal under the condition that the production state technology metadata and the design state technology metadata are detected to be inconsistent.

Optionally, the data storage form is a nested key value pair storage form.

The data management device provided by the embodiment of the invention can execute the data management method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example IV

Fig. 4 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 4, 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., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may 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. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various 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, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, 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.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of 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 running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as a data management method.

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

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out 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, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here 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 a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, 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: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A method of data management, comprising:

2. The method as recited in claim 1, further comprising:

3. The method as recited in claim 1, further comprising:

displaying a data entry page;

and responding to the input triggering operation aiming at the design state metadata input items in the data input page, acquiring the input design state technology metadata, and storing the input design state technology metadata based on a preset data storage form.

4. A method according to claim 2 or 3, further comprising:

and in response to an editing trigger operation for the design state technology metadata, updating the stored corresponding design state technology metadata based on the edited design state technology metadata, wherein the editing trigger operation comprises at least one of a data deletion trigger operation, a data addition trigger operation and a data change trigger operation.

5. The method of claim 1, wherein retrieving pre-stored design state technology metadata for a target design state system corresponding to the target production state system comprises:

acquiring a production state system identifier corresponding to the target production state system;

determining a to-be-acquired design state system corresponding to the target production state system based on prestored system corresponding information and the production state system identification, taking the to-be-acquired design state system as a target design state system, and acquiring a design state system identification corresponding to the target design state system, wherein the system corresponding information is used for indicating a corresponding relation between the design state system identification of the to-be-acquired design state system and the production state system identification of the to-be-acquired production state system;

and calling the design state technology metadata corresponding to the target design state system from the prestored design state technology metadata based on the design state system identification.

6. The method of claim 1, wherein determining that the production state technology metadata and the design state technology metadata are inconsistent comprises at least one of:

detecting that the field positions of the production state technology metadata and the design state technology metadata are inconsistent;

Detecting that the field types of the production state technology metadata and the design state technology metadata are inconsistent;

and detecting that the field lengths of the production state technology metadata and the design state technology metadata are inconsistent.

7. The method as recited in claim 1, further comprising:

and generating a task to be handled and sending the task to a target terminal under the condition that the production state technology metadata and the design state technology metadata are detected to be inconsistent.

8. The method of claim 1, wherein the data storage form is a nested key-value pair storage form.

9. A data management apparatus, comprising:

10. An electronic device, the electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the data management method of any one of claims 1-8.