Text matching checking method and device, electronic equipment and storage medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHERY AUTOMOBILE CO LTD
- Filing Date
- 2023-06-26
- Publication Date
- 2026-08-07
Smart Images

Figure CN116701958B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a text matching verification method, apparatus, electronic device, and storage medium. Background Technology
[0002] As internet technology becomes increasingly integrated into daily work, more and more employees need to process large amounts of text information, including comparing different texts. During text comparison, employees need to maintain high concentration to avoid information bias. At the same time, the urgency of the task often requires them to speed up, making it difficult to balance speed and accuracy.
[0003] In related technologies, the most common method for comparing text information is manual comparison. In order to speed up the task progress and complete the task delivery in a timely manner, more manpower will be invested to complete the comparison of text information.
[0004] However, increasing the manpower required for text information comparison can lead to increased business costs and wasted human resources for the group, which is detrimental to the development of the company or other groups. For individuals, the large amount of repetitive document comparison work can make staff feel bored and discourage them from working, thus reducing the efficiency and accuracy of text information comparison. This issue urgently needs to be addressed.
[0005] Application content
[0006] This application provides a text matching verification method, apparatus, electronic device, and storage medium to solve the problems of high cost, high error, and low efficiency caused by manually comparing text information.
[0007] The first aspect of this application provides a text matching verification method, including the following steps:
[0008] Obtain the event tracking requirement file and the event tracking data table triggered by the event tracking requirement file;
[0009] Add at least one preset column name to the event tracking requirement file to obtain the target event tracking requirement document, and use a preset file comparison tool to compare the target event tracking requirement document and the event tracking data table to obtain the comparison result; and
[0010] When the comparison result is successful, the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table are displayed in each preset column name.
[0011] According to one embodiment of this application, after obtaining the comparison result, the method further includes:
[0012] When the comparison result is a failure, a modification strategy is generated based on the comparison result;
[0013] The target tracking point requirement document, and / or the tracking point data table, and / or the preset file comparison tool are modified according to the modification strategy.
[0014] The modified target tracking point requirement document and the modified tracking point data table are compared using the modified preset file comparison tool until the comparison result is successful.
[0015] According to one embodiment of this application, the step of comparing the target tracking point requirement document and the tracking point data table using the preset document comparison tool to obtain the comparison result includes:
[0016] Using the comparison program in the preset file comparison tool, search the tracking data table according to at least one parameter in the target tracking requirement document to obtain the search results in the tracking data table;
[0017] The search results are compared with at least one parameter in the target tracking point requirement document to obtain the comparison result between the target tracking point requirement document and the tracking point data table.
[0018] According to one embodiment of this application, before comparing the target tracking point requirement document and the tracking point data table using the preset document comparison tool to obtain the comparison result, the method further includes:
[0019] Determine the folder to be stored;
[0020] Store the preset file comparison tool, the target tracking point requirement document, and the tracking point data table in the folder to be stored.
[0021] According to one embodiment of this application, obtaining the event tracking requirement file and the event tracking data table triggered by the event tracking requirement file includes:
[0022] Obtain the event tracking requirements from the event tracking requirement file;
[0023] Based on the stated tracking requirements, the tracking requirement file is triggered to obtain the tracking data table.
[0024] According to one embodiment of this application, after displaying the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name, the method further includes:
[0025] Verify the format of the target tracking point requirement document and display the verification results in the target tracking point requirement document type list and result list;
[0026] Based on the verification result, determine whether the format of the target tracking point requirement document has been successfully reported. If the verification result fails to report, display the reason for the reporting failure in the target tracking point requirement document type list and the result list.
[0027] According to the text matching verification method of this application embodiment, a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file are obtained. At least one preset column name is added to the tracking point requirement file to obtain a target tracking point requirement document. A preset file comparison tool is used to compare the target tracking point requirement document and the tracking point data table to obtain a comparison result. When the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name. This solves the problems of high cost, high error, and low efficiency caused by manual text information comparison. By using automated program technology, multiple comparison files are formatted and then compared and verified to achieve comparison of different text data content and data formats, thereby improving comparison efficiency and accuracy.
[0028] A second aspect of this application provides a text matching verification device, comprising:
[0029] The acquisition module is used to acquire the tracking point requirement file and the tracking point data table triggered by the tracking point requirement file.
[0030] The comparison module is used to add at least one preset column name to the tracking point requirement file to obtain a target tracking point requirement document, and to compare the target tracking point requirement document and the tracking point data table using a preset file comparison tool to obtain a comparison result; and
[0031] The display module is used to display the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name when the comparison result is successful.
[0032] According to one embodiment of this application, after obtaining the comparison result, the comparison module is further configured to:
[0033] When the comparison result is a failure, a modification strategy is generated based on the comparison result;
[0034] The target tracking point requirement document, and / or the tracking point data table, and / or the preset file comparison tool are modified according to the modification strategy.
[0035] The modified target tracking point requirement document and the modified tracking point data table are compared using the modified preset file comparison tool until the comparison result is successful.
[0036] According to one embodiment of this application, the comparison module is specifically used for:
[0037] Using the comparison program in the preset file comparison tool, search the tracking data table according to at least one parameter in the target tracking requirement document to obtain the search results in the tracking data table;
[0038] The search results are compared with at least one parameter in the target tracking point requirement document to obtain the comparison result between the target tracking point requirement document and the tracking point data table.
[0039] According to one embodiment of this application, before comparing the target tracking point requirement document and the tracking point data table using the preset document comparison tool to obtain the comparison result, the comparison module is further configured to:
[0040] Determine the folder to be stored;
[0041] Store the preset file comparison tool, the target tracking point requirement document, and the tracking point data table in the folder to be stored.
[0042] According to one embodiment of this application, the acquisition module is specifically used for:
[0043] Obtain the event tracking requirements from the event tracking requirement file;
[0044] Based on the stated tracking requirements, the tracking requirement file is triggered to obtain the tracking data table.
[0045] According to one embodiment of this application, after displaying the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name, the display module is further configured to:
[0046] Verify the format of the target tracking point requirement document and display the verification results in the target tracking point requirement document type list and result list;
[0047] Based on the verification result, determine whether the format of the target tracking point requirement document has been successfully reported. If the verification result fails to report, display the reason for the reporting failure in the target tracking point requirement document type list and the result list.
[0048] According to the text matching verification device of this application embodiment, a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file are obtained. At least one preset column name is added to the tracking point requirement file to obtain a target tracking point requirement document. A preset file comparison tool is used to compare the target tracking point requirement document and the tracking point data table to obtain a comparison result. When the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name. This solves the problems of high cost, high error, and low efficiency caused by manual text information comparison. By using automated program technology, multiple comparison files are formatted and then compared and verified to achieve comparison of different text data content and data formats, thereby improving comparison efficiency and accuracy.
[0049] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the text matching verification method as described in the above embodiments.
[0050] A fourth aspect of this application provides a computer-readable storage medium storing computer instructions for causing the computer to perform a text matching verification method as described in the above embodiments.
[0051] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description
[0052] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:
[0053] Figure 1 This is a flowchart of a text matching verification method provided according to an embodiment of this application;
[0054] Figure 2 This is a flowchart of a method for formatted text matching and verification based on automated program comparison technology according to an embodiment of this application;
[0055] Figure 3 A block diagram illustrating a text matching verification device according to an embodiment of this application;
[0056] Figure 4 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. Detailed Implementation
[0057] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.
[0058] The following describes a text matching verification method, apparatus, electronic device, and storage medium according to embodiments of this application with reference to the accompanying drawings. Addressing the high cost, high error rate, and low efficiency issues caused by manual text information comparison mentioned in the background art, this application provides a text matching verification method. In this method, a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file are obtained. At least one preset column name is added to the tracking point requirement file to obtain a target tracking point requirement document. A preset file comparison tool is used to compare the target tracking point requirement document and the tracking point data table to obtain a comparison result. When the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name. This solves the problems of high cost, high error rate, and low efficiency caused by manual text information comparison. By using automated program technology, multiple comparison files are formatted and then compared and verified to achieve comparison of different text data content and data formats, thereby improving comparison efficiency and accuracy.
[0059] Specifically, Figure 1 This is a flowchart illustrating a text matching verification method provided in an embodiment of this application.
[0060] like Figure 1 As shown, the text matching verification method includes the following steps:
[0061] In step S101, the tracking point requirement file and the tracking point data table triggered by the tracking point requirement file are obtained.
[0062] According to one embodiment of this application, obtaining a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file includes: obtaining the tracking point requirements of the tracking point requirement file; and triggering the tracking point requirement file based on the tracking point requirements to obtain the tracking point data table.
[0063] With the rapid development of computer communication technology, in order to improve the efficiency and accuracy of file comparison, this application adopts an automated program method to compare multiple embedded point requirement files, thereby solving the problems of low efficiency and high error rate that occur in manual comparison.
[0064] Specifically, such as Figure 2As shown in the embodiment of this application, when comparing multiple tracking point requirement files through an automated program, the first step is to obtain a tracking point requirement file with a standardized format. The tracking point requirement file includes column names such as keyName and Field, with each row representing one tracking point. The second step is to obtain the tracking point requirements from the tracking point requirement file, trigger tracking point data based on the tracking point requirements, and upload the tracking point data in the tracking point requirement file to the cloud. The tracking point data is then downloaded and saved using HUE (Hadoop User Experience, an editor for Hive, Pig, ClouderaImpala, and Sqoop2) to obtain a tracking point data table.
[0065] In step S102, at least one preset column name is added to the tracking point requirement file to obtain the target tracking point requirement document, and the target tracking point requirement document and the tracking point data table are compared using a preset file comparison tool to obtain the comparison result.
[0066] According to one embodiment of this application, before comparing the target tracking point requirement document and the tracking point data table using a preset file comparison tool to obtain the comparison result, the method further includes: determining the folder to be stored; and storing the preset file comparison tool, the target tracking point requirement document, and the tracking point data table in the folder to be stored.
[0067] According to one embodiment of this application, a preset document comparison tool is used to compare a target tracking point requirement document and a tracking point data table to obtain a comparison result. This includes: using the comparison program in the preset document comparison tool to search the tracking point data table according to at least one parameter in the target tracking point requirement document to obtain a search result in the tracking point data table; and comparing the search result with at least one parameter in the target tracking point requirement document to obtain a comparison result between the target tracking point requirement document and the tracking point data table.
[0068] The preset file comparison tools and preset column names can be selected by those skilled in the art based on the actual comparison requirements of the data collection files, and no specific limitations are made here.
[0069] Specifically, in this embodiment, after obtaining the formatted tracking requirement file, the tracking requirement file is first modified, and at least one preset column name is added, such as adding a type column name (type) and a result column name (result) to the tracking requirement file and saved, thereby obtaining the target tracking requirement document; at the same time, the parameters of the preset file comparison tool are modified, such as modifying the tracking data list file name and the reporting data table name; secondly, the modified preset file comparison tool, the tracking data table, and the target tracking requirement document are stored in a pre-determined storage folder; finally, the comparison program in the preset file comparison tool is used to search the tracking data table according to at least one parameter in the target tracking requirement document, and the search results in the tracking data table are obtained. The search results are then compared with at least one parameter in the target tracking requirement document to obtain the comparison result of the target tracking requirement document and the tracking data table.
[0070] According to one embodiment of this application, after obtaining the comparison result, the method further includes: if the comparison result fails, generating a modification strategy based on the comparison result; modifying the target tracking point requirement document, and / or tracking point data table, and / or a preset file comparison tool according to the modification strategy; comparing the modified target tracking point requirement document and the modified tracking point data table according to the modified preset file comparison tool until the comparison result is successful.
[0071] Specifically, in this embodiment of the application, after obtaining the comparison results of the target tracking point requirement document and the tracking point data table, if the comparison result is successful, the results of the type list and result list can be viewed, and a prompt indicating successful comparison will be provided; if the comparison result fails, a modification strategy is generated based on the comparison result, and the parameter information is located and modified using the script with parameters set in the preset file comparison tool, that is, the target tracking point requirement document, and / or the tracking point data table, and / or the preset file comparison tool and other parameter information are modified, and then the modified target tracking point requirement document and the modified tracking point data table are compared again based on the modified preset file comparison tool until the comparison result is successful.
[0072] In step S103, when the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name.
[0073] Specifically, in this embodiment of the application, when the comparison result is successful, the character type and specific character value of the keyName and Field values in the target tracking point requirement document in each type list and result list are displayed.
[0074] According to one embodiment of this application, after displaying the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name, the method further includes: verifying the format of the target tracking requirement document and displaying the verification result in the target tracking requirement document type list and the result list; determining whether the format of the target tracking requirement document has been successfully reported based on the verification result, and displaying the reason for the reporting failure in the target tracking requirement document type list and the result list when the verification result fails to report.
[0075] Specifically, in this embodiment, after obtaining the character type and specific character value of the keyName and Field values in the tracking data table of the target tracking requirement document, it is also necessary to verify the format of the target tracking requirement document and provide prompts through relevant colors. For example, green indicates that the format is correct, red indicates that the keyName is correct but the Field is missing, and other colors represent corresponding problems. The verification results are displayed in the target tracking requirement document type list and result list to determine whether the format of the target tracking requirement document has been successfully reported based on the content displayed in the type list and result list. If the verification result fails to be reported, the reason for the reporting failure is displayed and the reporting result is noted.
[0076] To make the discussion of the embodiments in this application more complete, this application will further illustrate with a specific embodiment.
[0077] For example, in this application embodiment, the formatted data tracking requirement document "Model A Data Tracking Requirement Table" is obtained through the product department or other means, as shown in Table 1. After the data tracking scenario is triggered on the vehicle's infotainment system of Model A, the data tracking data will be uploaded to the cloud. The data tracking data is downloaded using the HUE tool and renamed "Model A Reported Data Tracking".
[0078] Table 1
[0079]
[0080] Further, after obtaining the formatted event tracking requirement file, firstly, modify the requirement file by adding column names "type" and "result" and saving it. The positions of the "type" and "result" columns are not restricted; choose any position you prefer. Secondly, modify the event tracking data list file name and the reported data table name, and save the modified preset file comparison tool, the "A Model Event Tracking Requirement Table," and the "A Model Reported Event Tracking Data" to a pre-determined folder. Finally, use the comparison program in the preset file comparison tool to search for entries in the "A Model Reported Event Tracking Data" table according to the keyName and Field keywords in the "A Model Event Tracking Requirement Table." For example... The first data point in the "Model A Data Point Requirement Form" document has a keyName of APPS.Screensaver.NewContentPushPopupClick and a Field of Seeflg. After starting the data point program, the program will first search for the keyword APPS.Screensaver.NewContentPushPopupClick in "Model A Data Point Report". After finding it, it will search for Seeflg under APPS.Screensaver.NewContentPushPopupClick and return the character type and specific character value of Seeflg in the type and result columns.
[0081] Furthermore, after obtaining the character types and specific character values of the keyName and Field values in the target event tracking requirement document in the event tracking data table, the format of the target event tracking requirement document is validated, and relevant colors are used to provide hints. For example, in type and result, green indicates that the format is correct, red indicates that the keyName is correct but the Field is missing, and other colors represent corresponding issues. The specific validation results are shown in Table 2:
[0082] Table 2
[0083]
[0084] Furthermore, the obtained verification results are displayed in the `type` and `result` fields of the target tracking point requirement document. The content displayed in `type` and `result` determines whether the target tracking point requirement document was successfully submitted. If the submission fails, the reason for the failure is displayed. For example, if `type` and `result` contain data and are green, it indicates successful submission and that the submitted target tracking point requirement document and tracking point data table are in the correct format. If `type` and `result` contain no data, it indicates upload failure, meaning the tracking point was not found in the submitted data table. The submission result is noted, as shown in Table 3.
[0085] Table 3
[0086]
[0087] Therefore, through the above comparison process, the comparison between the entire data collection requirement document and the data collection point table was completed. This automated comparison method replaced the manual search and data type judgment, simplified a lot of repetitive work, improved the efficiency of document comparison, and reduced errors caused by human judgment.
[0088] According to the text matching verification method of this application embodiment, a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file are obtained. At least one preset column name is added to the tracking point requirement file to obtain a target tracking point requirement document. A preset file comparison tool is used to compare the target tracking point requirement document and the tracking point data table to obtain a comparison result. When the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name. This solves the problems of high cost, high error, and low efficiency caused by manual text information comparison. By using automated program technology, multiple comparison files are formatted and then compared and verified to achieve comparison of different text data content and data formats, thereby improving comparison efficiency and accuracy.
[0089] Next, a text matching verification device according to an embodiment of this application is described with reference to the accompanying drawings.
[0090] Figure 3 This is a block diagram of a text matching verification device according to an embodiment of this application.
[0091] like Figure 3 As shown, the text matching verification device 10 includes: an acquisition module 100, a comparison module 200, and a display module 300.
[0092] Among them, the acquisition module 100 is used to acquire the tracking point requirement file and the tracking point data table triggered by the tracking point requirement file.
[0093] The comparison module 200 adds at least one preset column name to the tracking requirement file to obtain the target tracking requirement document, and uses a preset file comparison tool to compare the target tracking requirement document and the tracking data table to obtain the comparison result; and
[0094] Display module 300 is used to display the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table in each preset column name when the comparison result is successful.
[0095] According to one embodiment of this application, after obtaining the comparison result, the comparison module 200 is further configured to:
[0096] When the comparison result fails, a modification strategy is generated based on the comparison result;
[0097] Modify the target tracking point requirement document, and / or tracking point data table, and / or the preset file comparison tool according to the modification strategy;
[0098] The modified target tracking point requirement document and the modified tracking point data table are compared using the modified preset file comparison tool until the comparison result is successful.
[0099] According to one embodiment of this application, the comparison module 200 is specifically used for:
[0100] Using the comparison program in the preset file comparison tool, search the tracking data table according to at least one parameter in the target tracking point requirement document to obtain the search results in the tracking data table.
[0101] The comparison results of the target tracking point requirement document and the tracking point data table are obtained by comparing the search results with at least one parameter in the target tracking point requirement document.
[0102] According to one embodiment of this application, before comparing the target tracking point requirement document and the tracking point data table using a preset document comparison tool and obtaining the comparison result, the comparison module 200 is further configured to:
[0103] Determine the folder to be stored;
[0104] Save the preset file comparison tool, target tracking point requirement document, and tracking point data table to the folder to be stored.
[0105] According to one embodiment of this application, the acquisition module 100 is specifically used for:
[0106] Obtain the event tracking requirements from the event tracking requirement file;
[0107] Based on the data tracking requirements, the data tracking requirement file is triggered, and the data tracking data table is obtained.
[0108] According to one embodiment of this application, after displaying the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table in each preset column name, the display module 300 is further configured to:
[0109] Validate the format of the target tracking point requirement document and display the validation results in the target tracking point requirement document type list and result list;
[0110] Based on the verification results, determine whether the format of the target tracking point requirement document has been successfully reported. If the verification result fails to report, display the reason for the reporting failure in the target tracking point requirement document type list and the result list.
[0111] According to the text matching verification device of this application embodiment, a tracking point requirement file and a tracking point data table triggered by the tracking point requirement file are obtained. At least one preset column name is added to the tracking point requirement file to obtain a target tracking point requirement document. A preset file comparison tool is used to compare the target tracking point requirement document and the tracking point data table to obtain a comparison result. When the comparison result is successful, the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table are displayed in each preset column name. This solves the problems of high cost, high error, and low efficiency caused by manual text information comparison. By using automated program technology, multiple comparison files are formatted and then compared and verified to achieve comparison of different text data content and data formats, thereby improving comparison efficiency and accuracy.
[0112] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:
[0113] The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.
[0114] When the processor 402 executes the program, it implements the text matching verification method provided in the above embodiments.
[0115] Furthermore, electronic devices also include:
[0116] Communication interface 403 is used for communication between memory 401 and processor 402.
[0117] The memory 401 is used to store computer programs that can run on the processor 402.
[0118] Memory 401 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.
[0119] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0120] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.
[0121] Processor 402 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.
[0122] This embodiment also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the text matching verification method described above.
[0123] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0124] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0125] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.
[0126] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.
[0127] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.
[0128] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium. When executed, the program includes one or a combination of the steps of the method embodiments.
[0129] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.
[0130] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.
Claims
1. A text matching verification method, characterized in that, Includes the following steps: Obtain the event tracking requirement file and the event tracking data table triggered by the event tracking requirement file; Add at least one preset column name to the event tracking requirement file to obtain the target event tracking requirement document, and use a preset file comparison tool to compare the target event tracking requirement document and the event tracking data table to obtain the comparison result; as well as When the comparison result is successful, the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table are displayed in each preset column name; The step of comparing the target tracking point requirement document and the tracking point data table using the preset file comparison tool to obtain the comparison result includes: Using the comparison program in the preset file comparison tool, search the tracking data table according to at least one parameter in the target tracking requirement document to obtain the search results in the tracking data table; The search results are compared with at least one parameter in the target tracking point requirement document to obtain the comparison result between the target tracking point requirement document and the tracking point data table. The process of obtaining the event tracking requirement file and the event tracking data table triggered by the event tracking requirement file includes: Obtain the event tracking requirements from the event tracking requirement file; Based on the aforementioned tracking requirements, the tracking requirement file is triggered to obtain the tracking data table. After displaying the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name, the method further includes: Verify the format of the target tracking point requirement document and display the verification results in the target tracking point requirement document type list and result list; Based on the verification result, determine whether the format of the target tracking point requirement document has been successfully reported. If the verification result fails to report, display the reason for the reporting failure in the target tracking point requirement document type list and the result list.
2. The method according to claim 1, characterized in that, After obtaining the comparison results, the following is also included: When the comparison result is a failure, a modification strategy is generated based on the comparison result; The target tracking point requirement document, and / or the tracking point data table, and / or the preset file comparison tool are modified according to the modification strategy. The modified target tracking point requirement document and the modified tracking point data table are compared using the modified preset file comparison tool until the comparison result is successful.
3. The method according to claim 1, characterized in that, Before using the preset file comparison tool to compare the target tracking point requirement document and the tracking point data table to obtain the comparison result, the process further includes: Determine the folder to be stored; Store the preset file comparison tool, the target tracking point requirement document, and the tracking point data table in the folder to be stored.
4. A text matching verification device, characterized in that, include: The acquisition module is used to acquire the tracking point requirement file and the tracking point data table triggered by the tracking point requirement file. The comparison module is used to add at least one preset column name to the tracking point requirement file to obtain the target tracking point requirement document, and use a preset file comparison tool to compare the target tracking point requirement document and the tracking point data table to obtain the comparison result. as well as The display module is used to display the character type and character value of at least one parameter in the target tracking point requirement document in the tracking point data table in each preset column name when the comparison result is successful. The step of comparing the target tracking point requirement document and the tracking point data table using the preset file comparison tool to obtain the comparison result includes: Using the comparison program in the preset file comparison tool, search the tracking data table according to at least one parameter in the target tracking requirement document to obtain the search results in the tracking data table; The search results are compared with at least one parameter in the target tracking point requirement document to obtain the comparison result between the target tracking point requirement document and the tracking point data table. The process of obtaining the event tracking requirement file and the event tracking data table triggered by the event tracking requirement file includes: Obtain the event tracking requirements from the event tracking requirement file; Based on the aforementioned tracking requirements, the tracking requirement file is triggered to obtain the tracking data table. After displaying the character type and character value of at least one parameter in the target tracking requirement document in the tracking data table in each preset column name, the method further includes: Verify the format of the target tracking point requirement document and display the verification results in the target tracking point requirement document type list and result list; Based on the verification result, determine whether the format of the target tracking point requirement document has been successfully reported. If the verification result fails to report, display the reason for the reporting failure in the target tracking point requirement document type list and the result list.
5. The apparatus according to claim 4, characterized in that, After obtaining the comparison result, the comparison module is further configured to: When the comparison result is a failure, a modification strategy is generated based on the comparison result; The target tracking point requirement document, and / or the tracking point data table, and / or the preset file comparison tool are modified according to the modification strategy. The modified target tracking point requirement document and the modified tracking point data table are compared using the modified preset file comparison tool until the comparison result is successful.
6. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the text matching verification method as described in any one of claims 1-3.
7. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the text matching verification method as described in any one of claims 1-3.
Citation Information
Patent Citations
Buried point data quality treatment method
CN114817171A
Buried point data detection method and device, electronic equipment and storage medium
CN114818968A