Relationship document generation method and device, electronic equipment and storage medium

Abstract

The invention discloses a relation document generation method and device, electronic equipment and a storage medium, and relates to the technical field of data processing. The method comprises the following steps: reading an investigation configuration table to obtain metadata in the investigation configuration table; wherein the investigation configuration table is used for indicating an association relationship between a target system and an investigation document; obtaining an investigation document based on the metadata, traversing the investigation document, and extracting respective table names and source field information of N types of tables; based on a field mapping rule, determining a field mapping relationship of respective source field information of the N types of tables; wherein the field mapping rule is used for matching each piece of source field information with corresponding target field information; generating a target relation document based on a relation document name in the metadata, the field mapping relation and a verification rule; wherein the verification rule is used for verifying whether the field mapping relation is abnormal or not, so that the efficiency and the accuracy of relation document generation are improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, electronic device and storage medium for generating a relational document. Background Art

[0002] During data system transformation, business research involves multiple systems, complex logic, and extensive table and field mapping. Traditionally, this approach relies on manual maintenance of research templates and the generation of relationship documents. For example, logical content obtained through researching related business systems is manually compiled into corresponding relationship documents (also known as mapping documents) for subsequent developers to use and complete feature development.

[0003] However, the MAPPING documents generated by traditional methods are prone to errors due to manually written field mappings, which leads to errors in the MAPPING documents. They need to be reworked by relevant personnel for inspection and correction, which will cause the development work of developers to be put on hold, consuming a lot of time and energy. Summary of the Invention

[0004] The present application provides a relational document generation method, device, electronic device and storage medium to improve the efficiency and accuracy of relational document generation.

[0005] In a first aspect, a method for generating a relational document is provided, comprising:

[0006] Reading a survey configuration table to obtain metadata in the survey configuration table; wherein the survey configuration table is used to indicate an association relationship between a target system and a survey document;

[0007] Acquire a research document based on the metadata, and traverse the research document to extract table names and source field information of N tables; wherein N is an integer greater than 0;

[0008] Determine, based on field mapping rules, field mapping relationships of source field information of each of the N tables; wherein the field mapping rules are used to match each source field information to corresponding target field information;

[0009] A target relationship document is generated based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule; wherein the verification rule is used to verify whether the field mapping relationship is abnormal.

[0010] In an embodiment of the present application, metadata can be directly read from the survey configuration table and the survey document can be automatically loaded, avoiding spelling errors, path errors and other problems that may occur when manually entering the path or name; then, the survey document is traversed to extract the table name and source field information of each table, and based on the field mapping rules, the field mapping relationship corresponding to the source field information in each table is determined in batches, which can improve the efficiency and accuracy of field mapping; then, based on the relationship document name and field mapping relationship in the data, as well as the verification rules, the target relationship document is generated, which can further reduce the error rate of the target relationship document and ensure the integrity and accuracy of the field mapping relationship in the target relationship document.

[0011] In some embodiments, determining the field mapping relationship of the source field information of each of the N tables based on the field mapping rule includes:

[0012] Based on the field mapping rules, target field names and target field types that match the source field names and source field types in the first table are matched, and a mapping relationship is formed between the source field names, source field types, the target field names, and the target field types; wherein the first table is any one of the N tables.

[0013] Through the above method, the mapping of each source field can be ensured to be independent and accurate in batches, avoiding field mapping omissions or errors caused by coarse-grained operations (such as table-level mapping). Compared with manual operations, the efficiency and accuracy of subsequent relational document generation can be significantly improved.

[0014] In some embodiments, generating a target relationship document based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule, includes:

[0015] Verify the field mapping relationship based on the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the verification rules;

[0016] If the field mapping relationship is found to be abnormal, a prompt box will pop up, which includes the source field information of the field mapping relationship abnormality and the cause of the abnormality;

[0017] If the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and the target relationship document is generated based on the target relationship document template, the field mapping relationship and the relationship document name in the metadata.

[0018] By performing verification of different dimensions on the field mapping relationship through the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the above verification rules, the error rate of subsequent relationship documents can be further reduced, while balancing the efficiency of automation and the reliability of manual review. In addition, the target relationship document template that matches the target system is used to generate the target relationship document, which ensures the uniform format of the relationship document and facilitates team collaboration and subsequent development.

[0019] In some embodiments, before reading the survey configuration table, the method further includes:

[0020] The survey configuration table is created based on an Excel tool; wherein the header information in the survey configuration table includes at least a system name field, a survey document name field, a relationship document name field, a survey document path field, and a survey configuration table generation time field.

[0021] Through the above method, the survey configuration table is used as the core input for generating relationship documents (MAPPING documents), and key metadata such as the system names of different systems, the names and paths of their associated survey documents, and the names of their output relationship documents are centrally stored. The header information is used to force a unified input format to ensure consistency during tool parsing. Subsequently, MAPPING documents for multiple systems can be generated at one time, significantly improving processing efficiency. Furthermore, by modifying the system name or survey document name and path in the survey configuration table, the same tool can quickly switch to different systems without modifying the underlying code.

[0022] In some embodiments, the metadata includes at least the system name of the target system, the research document name of the research document, and the generation time of the research configuration table.

[0023] In a second aspect, a relationship document generation device is provided, comprising:

[0024] A reading module, configured to read a survey configuration table and obtain metadata in the survey configuration table; wherein the survey configuration table is used to indicate an association relationship between a target system and a survey document;

[0025] a field mapping module, configured to obtain a research document based on the metadata, traverse the research document, extract table names and source field information of each of N tables, wherein N is an integer greater than 0; and determine a field mapping relationship of the source field information of each of the N tables based on a field mapping rule, wherein the field mapping rule is configured to match each source field information to corresponding target field information;

[0026] A generation module is used to generate a target relationship document based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule; wherein the verification rule is used to verify whether the field mapping relationship is abnormal.

[0027] In some embodiments, the field mapping module is specifically configured to:

[0028] Based on the field mapping rules, target field names and target field types that match the source field names and source field types in the first table are matched, and a mapping relationship is formed between the source field names, source field types, the target field names, and the target field types; wherein the first table is any one of the N tables.

[0029] In some embodiments, the generating module is specifically configured to:

[0030] Verify the field mapping relationship based on the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the verification rules;

[0031] If the field mapping relationship is found to be abnormal, a prompt box will pop up, which includes the source field information of the field mapping relationship abnormality and the cause of the abnormality;

[0032] If the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and the target relationship document is generated based on the target relationship document template, the field mapping relationship and the relationship document name in the metadata.

[0033] According to a third aspect, an electronic device is provided, including:

[0034] A memory for storing a computer program; a processor for implementing any one of the method steps in the first aspect when executing the computer program stored in the memory.

[0035] According to a fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method steps according to any one of the first aspects are implemented.

[0036] For each of the above-mentioned aspects from the second to the fourth aspects and the technical effects that may be achieved by each of the aspects, please refer to the above-mentioned description of the technical effects that can be achieved by the first aspect or various possible solutions in the first aspect, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 Schematic diagram of application scenarios applicable to the embodiments of this application;

[0038] Figure 2 A flowchart of a method for generating a relationship document provided in an embodiment of the present application;

[0039] Figure 3 A schematic diagram of the structure of a relationship document generation device provided in an embodiment of the present application;

[0040] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. Unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other in any way. In addition, although a logical order is shown in the flowchart, in some cases, the steps shown or described can be performed in an order different from that here.

[0042] The terms "first" and "second" in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of its variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in this application can mean at least two, for example, two, three or more, and the embodiments of this application are not limited thereto.

[0043] The following description of exemplary embodiments of the present application is made in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and they should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope disclosed in this application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0044] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are first explained below.

[0045] A mapping document records the relationships between data, primarily describing the mapping or correspondence between two or more datasets. It facilitates data integration, data conversion, or data migration between different data sources. For example, it specifies how a field in one dataset is mapped to a corresponding field in another dataset.

[0046] The following briefly introduces the application scenarios to which the technical solutions of the embodiments of the present application can be applied. It should be noted that the application scenarios described below are only used to illustrate the embodiments of the present application and are not limiting. In specific implementation, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.

[0047] Figure 1 The following is a schematic diagram of an application scenario applicable to an embodiment of the present application. As shown in the figure, the application scenario mainly includes: a terminal 10 and a server 11. The terminal 10 and the server 11 can exchange information via a communication network, and the communication methods used by the communication network may include: wireless communication methods and wired communication methods.

[0048] In some scenarios, the terminal 10 can access the network and communicate with the server 11 through cellular mobile communication technology, which may include fifth generation mobile communication (5th Generation Mobile Networks, 5G) technology and 6G technology.

[0049] In some scenarios, the terminal 10 may access the network and communicate with the server 11 via short-range wireless communication. The short-range wireless communication may include Wireless Fidelity (Wi-Fi) technology.

[0050] The present application embodiment does not impose any restrictions on the number of the above devices. Figure 1 As shown, only the terminal 10 and the server 11 are described as examples, and the above devices and their respective functions are briefly introduced below.

[0051] The terminal 10 is a device that can provide voice and / or data connectivity to the user, including: a handheld terminal device with wireless connection function, a vehicle-mounted terminal device, etc. For example, the terminal 10 includes but is not limited to: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile Internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, a wireless terminal device in smart grids, a wireless terminal device in transportation safety, a wireless terminal device in smart cities, or a wireless terminal device in smart homes, etc.

[0052] In addition, a client related to relationship document generation may be installed on the terminal 10, and the client may be software (e.g., an APP, a browser, etc.), or a web page, a small program, etc. In the embodiment of the present application, the terminal 10 may use the client related to relationship document generation, and may interact with the server 11 for field mapping, field mapping relationship verification, and the like.

[0053] Furthermore, server 11 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0054] Furthermore, in an embodiment of the present application, the server 11 may be equipped with a relational document generation device corresponding to the client, and the code scanning device is used to process relational document generation tasks for different systems (or projects) initiated by the user on the user interface of the terminal 10; specifically, it is used to read the survey configuration table and obtain the metadata in the survey configuration table; wherein the survey configuration table is used to indicate the association relationship between the target system and the survey document; based on the metadata, the survey document is obtained, and the survey document is traversed to extract the table name and field information of each of N tables; wherein N is an integer greater than 0; based on the field mapping rules, the field mapping relationship of the source field information of each of the N tables is determined; wherein the field mapping rules are used to match each source field information to the corresponding target field information; based on the relational document name and field mapping relationship in the metadata, and the verification rules, a target relational document is generated; wherein the verification rules are used to verify whether the field mapping relationship is abnormal.

[0055] To further illustrate the technical solutions provided by the embodiments of the present application, this is described in detail below with reference to the accompanying drawings and specific implementation methods. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or no creative labor. In the steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiments of the present application. The method may be executed or executed in parallel in the order of the methods shown in the embodiments or drawings during the actual processing process or when the device is executed.

[0056] Figure 2 This is a flow chart of a method for generating a relationship document provided in an embodiment of the present application. This process can be executed by a relationship document generating device, such as Figure 1 The relationship document generation device carried by the server 11 shown is used to improve the efficiency and accuracy of relationship document generation. Figure 2 As shown, the process includes the following steps:

[0057] 201: Read the survey configuration table and obtain the metadata in the survey configuration table.

[0058] In this step, the survey configuration table is used to indicate the association relationship between the target system and the survey document.

[0059] In some embodiments, the survey configuration table can be created by creating a survey configuration table using Excel; wherein the header information in the survey configuration table includes at least a system name field, a survey document name field, a relationship document name field, a survey document path field, and a survey configuration table generation time field. Table 1 illustrates an example survey configuration table provided in an embodiment of the present application.

[0060] Table 1: Survey configuration example

[0061]

[0062] By creating a survey configuration table with a unified format, the survey configuration table can be used as the core input for generating relationship documents (MAPPING documents), centrally storing key metadata such as the system names of different systems, the names and paths of their associated survey documents, and the names of their output relationship documents. The header information is used to force a unified input format to ensure consistency during tool parsing. Subsequently, MAPPING documents for multiple systems can be generated at one time, significantly improving processing efficiency. Furthermore, by modifying the system name or survey document name and path in the survey configuration table, the same tool can quickly switch to different systems without modifying the underlying code.

[0063] In other embodiments, the survey configuration table itself can serve as a record file of the generation process, retaining the specific parameters of each task (such as the survey document version used and the generation time) to facilitate subsequent backtracking and auditing.

[0064] In some embodiments, the metadata includes at least the system name of the target system, the research document name of the research document, the generation time of the research configuration table, and the research document path, so as to facilitate automatic reading of the required research document.

[0065] It should be noted that the version of the Excel tool is not specifically limited in the embodiments of the present application.

[0066] 202: Based on the above metadata, obtain the research document, traverse the research document, and extract the table name and source field information of each of the N tables.

[0067] In this step, N is an integer greater than 0. Based on the research document name or research document path in the metadata, the corresponding research document is retrieved, and then the N tables under the research document are traversed. Each table is read row by row to extract the table name of each table, as well as the source field information contained in each table, such as the source field name and source field type.

[0068] 203: Determine the field mapping relationship of the source field information of each of the N tables based on the field mapping rule. The field mapping rule is used to match each source field information to the corresponding target field information.

[0069] In this step, based on the field mapping rules, the target field name and target field type that match the source field name and source field type in the first table can be matched, and the source field name, source field type, target field name and target field type form a mapping relationship; the first table is any one of the N tables.

[0070] In some embodiments, the field mapping rule can define target fields corresponding to different source fields. For example, the source field is a mobile phone number, and the target field to be mapped is a contact number; for another example, the source field is a user ID, and the target field to be mapped is a customer ID; for another example, the source field is a registration date, and the target field to be mapped is a creation time. Furthermore, the field mapping rule can also define corresponding format conversion rules. For example, the registration date of the source field is a numeric type and needs to be converted to a text type, and the order amount of the source field needs to be converted to a unit, level mapping), etc., so as to ensure that the mapping of each source field is independent and accurate, avoid omissions or errors in field mapping caused by coarse-grained operations (such as table-level mapping), and significantly improve the efficiency and accuracy of subsequent relational document generation compared to manual operations.

[0071] 204: Generate a target relationship document based on the relationship document name and field mapping relationship in the above metadata, as well as the verification rules.

[0072] In this step, the verification rules are used to check whether the field mapping relationship is abnormal.

[0073] In some embodiments, generating a target relationship document may include:

[0074] First, based on the field mapping missing check, field mapping format check, field mapping error check, and field mapping duplication check in the verification rules, the field mapping relationship is verified.

[0075] The field mapping missing check is used to verify whether there is a source field without a corresponding target field; the field mapping format check is used to verify whether the field naming is standardized (such as prohibiting special characters, length restrictions), whether the field type is inconsistent, etc. The field mapping error check is used to verify whether the target field mapped by the source field is misplaced; the field mapping duplication check is used to verify whether the source field is repeatedly mapped to multiple target fields.

[0076] It should be noted that other verification rules can be expanded in the verification rules, such as field conversion result verification, etc., which can be configured according to actual needs and are not limited in the embodiments of the present application.

[0077] Secondly, if the field mapping relationship is checked for anomalies, a prompt box will pop up, including the source field information and the cause of the anomaly. For example, if a source field in the field mapping relationship is not mapped to the corresponding target field, a prompt box will pop up, including the specific source field and the cause of the anomaly, so that users can take appropriate measures to correct it.

[0078] Furthermore, the content in the prompt box can also be transmitted to the associated terminal in the form of text messages or emails, so as to remind the user to handle it in time.

[0079] Alternatively, if the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and a target relationship document is generated based on the target relationship document template, the field mapping relationship, and the relationship document name in the metadata. As shown in Table 2, an example relationship document table provided in an embodiment of the present application is exemplified.

[0080] Table 2: Example table of relationship documents

[0081]

[0082]

[0083] The relationship document template set may include relationship document templates corresponding to different systems to adapt to and be compatible with different systems.

[0084] By performing verification of different dimensions on the field mapping relationship through the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the above verification rules, the error rate of subsequent relationship documents can be further reduced, while balancing the efficiency of automation and the reliability of manual review. In addition, the target relationship document template that matches the target system is used to generate the target relationship document, which ensures the uniform format of the relationship document and facilitates team collaboration and subsequent development.

[0085] In an embodiment of the present application, metadata can be directly read from the survey configuration table and the survey document can be automatically loaded, avoiding spelling errors, path errors and other problems that may occur when manually entering the path or name; then, the survey document is traversed to extract the table name and source field information of each table, and based on the field mapping rules, the field mapping relationship corresponding to the source field information in each table is determined in batches, which can improve the efficiency and accuracy of field mapping; then, based on the relationship document name and field mapping relationship in the data, as well as the verification rules, the target relationship document is generated, which can further reduce the error rate of the target relationship document and ensure the integrity and accuracy of the field mapping relationship in the target relationship document.

[0086] Based on the same technical concept, an embodiment of the present application also provides a relationship document generation device, which can implement the above-mentioned relationship document generation method process in the embodiment of the present application.

[0087] Figure 3 This is a schematic diagram of the structure of a relational document generation device provided in an embodiment of the present application. The device includes a reading module 301, a field mapping module 302, and a generation module 303.

[0088] The reading module 301 is used to read the survey configuration table and obtain metadata in the survey configuration table; wherein the survey configuration table is used to indicate the association relationship between the target system and the survey document;

[0089] A field mapping module 302 is configured to obtain a research document based on the metadata, traverse the research document, extract the table name and source field information of each of N tables, where N is an integer greater than 0, and determine a field mapping relationship between the source field information of each of the N tables based on a field mapping rule, where the field mapping rule is configured to match each source field information to corresponding target field information.

[0090] The generation module 303 is used to generate a target relationship document based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule; wherein the verification rule is used to verify whether the field mapping relationship is abnormal.

[0091] In some embodiments, the field mapping module 302 is specifically configured to:

[0092] Based on the field mapping rules, target field names and target field types that match the source field names and source field types in the first table are matched, and a mapping relationship is formed between the source field names, source field types, the target field names, and the target field types; wherein the first table is any one of the N tables.

[0093] In some embodiments, the generating module 303 is specifically configured to:

[0094] Verify the field mapping relationship based on the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the verification rules;

[0095] If the field mapping relationship is found to be abnormal, a prompt box will pop up, which includes the source field information of the field mapping relationship abnormality and the cause of the abnormality;

[0096] If the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and the target relationship document is generated based on the target relationship document template, the field mapping relationship and the relationship document name in the metadata.

[0097] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0098] Based on the same technical concept, an electronic device is also provided in an embodiment of the present application, which can realize the functions of the aforementioned relationship document generation device.

[0099] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0100] At least one processor 401, and a memory 402 connected to the at least one processor 401. The specific connection medium between the processor 401 and the memory 402 is not limited in the embodiment of the present application. Figure 4 In the example, the processor 401 and the memory 402 are connected via a bus 400. Figure 4 The bus 400 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 The diagram is represented by only one thick line, but this does not mean that there is only one bus or one type of bus. Alternatively, the processor 401 may also be referred to as a controller, without limitation to the name.

[0101] In the embodiment of the present application, the memory 402 stores instructions that can be executed by at least one processor 401. The at least one processor 401 can execute a relational document generation method discussed above by executing the instructions stored in the memory 402. The processor 401 can implement Figure 3 The functions of each module in the device shown.

[0102] Among them, the processor 401 is the control center of the device, which can use various interfaces and lines to connect the various parts of the entire control device, and monitor the device as a whole by running or executing instructions stored in the memory 402 and calling data stored in the memory 402, the various functions of the device and processing data.

[0103] In the embodiment of the present application, the processor 401 may include one or more processing units. The processor 401 may integrate an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs, while the modem processor primarily processes wireless communications. It is understood that the modem processor may not be integrated into the processor 401. In some embodiments, the processor 401 and the memory 402 may be implemented on the same chip. In some embodiments, they may also be implemented on separate chips.

[0104] The processor 401 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the relational document generation method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0105] The memory 402 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 402 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 402 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 402 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0106] By programming the processor 401, the code corresponding to the relational document generation method described in the above embodiment can be fixed into the chip, so that the chip can execute the code when running. Figure 2 The embodiment shown is a method for generating a relational document. How to design and program the processor 401 is a technique well known to those skilled in the art and will not be described in detail here.

[0107] It should be noted here that the above-mentioned electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0108] Based on the same technical concept, embodiments of the present application provide a computer storage medium comprising computer program code. When the computer program code is executed on a computer, the computer executes any of the methods for generating a relational document discussed above. Because the principles underlying the problem solved by the computer storage medium are similar to those of the method for generating a relational document, the implementation of the computer storage medium can be referred to as the implementation of the method, and any repetitions will not be repeated.

[0109] In a specific implementation process, computer storage media may include: Universal Serial Bus Flash Drive (USB), mobile hard disk, Read-Only Memory (ROM), Random Access Memory (RAM), magnetic disk or optical disk, and other storage media that can store program code.

[0110] Based on the same technical concept, embodiments of the present application also provide a computer program product, comprising: computer program code, which, when executed on a computer, causes the computer to execute any of the methods for generating a relationship document discussed above. Because the principles underlying the problems solved by the aforementioned computer program product are similar to those of the method for generating a relationship document, the implementation of the aforementioned computer program product can be referenced to the implementation of the method, and any repetitions will not be repeated.

[0111] The computer program product can employ any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0112] The methods described herein can be implemented in whole or in part using software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described herein are performed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, a core network device, an OAM, or other programmable device.

[0113] The computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0114] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0115] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the instructions in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0116] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0117] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of the present invention fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for generating a relational document, characterized in that: include: Reading a survey configuration table to obtain metadata in the survey configuration table; wherein the survey configuration table is used to indicate an association relationship between a target system and a survey document; Acquire a research document based on the metadata, and traverse the research document to extract table names and source field information of N tables; wherein N is an integer greater than 0; Determine, based on field mapping rules, field mapping relationships of source field information of each of the N tables; wherein the field mapping rules are used to match each source field information to corresponding target field information; A target relationship document is generated based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule; wherein the verification rule is used to verify whether the field mapping relationship is abnormal.

2. The method according to claim 1, wherein The determining, based on the field mapping rules, the field mapping relationship of the source field information of each of the N types of tables includes: Based on the field mapping rules, target field names and target field types that match the source field names and source field types in the first table are matched, and a mapping relationship is formed between the source field names, source field types, the target field names, and the target field types; wherein the first table is any one of the N tables.

3. The method according to claim 1, wherein The generating of the target relationship document based on the relationship document name in the metadata and the field mapping relationship, as well as the verification rules, includes: Verify the field mapping relationship based on the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the verification rules; If the field mapping relationship is found to be abnormal, a prompt box will pop up, which includes the source field information of the field mapping relationship abnormality and the cause of the abnormality; If the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and the target relationship document is generated based on the target relationship document template, the field mapping relationship and the relationship document name in the metadata.

4. The method according to claim 1, wherein Before reading the survey configuration table, the method further includes: The survey configuration table is created based on an Excel tool; wherein the header information in the survey configuration table includes at least a system name field, a survey document name field, a relationship document name field, a survey document path field, and a survey configuration table generation time field.

5. The method according to any one of claims 1 to 4, characterized in that The metadata at least includes the system name of the target system, the research document name of the research document, and the generation time of the research configuration table.

6. A relational document generation device, characterized in that: include: A reading module, configured to read a survey configuration table and obtain metadata in the survey configuration table; wherein the survey configuration table is used to indicate an association relationship between a target system and a survey document; a field mapping module, configured to obtain a research document based on the metadata, traverse the research document, extract table names and source field information of each of N tables, wherein N is an integer greater than 0; and determine a field mapping relationship of the source field information of each of the N tables based on a field mapping rule, wherein the field mapping rule is configured to match each source field information to corresponding target field information; A generation module is used to generate a target relationship document based on the relationship document name in the metadata and the field mapping relationship, as well as a verification rule; wherein the verification rule is used to verify whether the field mapping relationship is abnormal.

7. The device according to claim 6, characterized in that The field mapping module is specifically used to: Based on the field mapping rules, target field names and target field types that match the source field names and source field types in the first table are matched, and a mapping relationship is formed between the source field names, source field types, the target field names, and the target field types; wherein the first table is any one of the N tables.

8. The device according to claim 6, wherein The generation module is specifically used to: Verify the field mapping relationship based on the field mapping missing verification, field mapping format verification, field mapping error verification, and field mapping duplication verification in the verification rules; If the field mapping relationship is found to be abnormal, a prompt box will pop up, which includes the source field information of the field mapping relationship abnormality and the cause of the abnormality; If the field mapping relationship is verified to be normal, a target relationship document template that matches the target system is obtained from the relationship document template set, and the target relationship document is generated based on the target relationship document template, the field mapping relationship and the relationship document name in the metadata.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the method according to any one of claims 1 to 5 when executing the computer program stored in the memory.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images