Document repairing method and device, equipment and medium

Abstract

The invention discloses a document repairing method and device, equipment and a medium, and the method comprises the steps: scanning a target document of a target monitoring point, and determining each error field in the target document and an error type corresponding to the error field, the error type comprising a time format, content, field missing, an IP address and boundary overrun; generating an error report of the target document according to the plurality of error fields and the error types corresponding to the error fields; determining a coverage field corresponding to each error field according to the error report; and overwriting the corresponding error field based on the coverage field, and updating the target document to obtain a repaired target document. The invention belongs to the field of document repair. Based on the method provided by the invention, the problem of attribute confusion in the archive management system is effectively solved, the repaired archive attribute fields are complete and accurate, the effectiveness of archive data is ensured, manual operation is reduced, and the operation efficiency of the system is improved.

Description

Technical Field

[0001] The present invention relates to the field of document repair, and in particular to a document repair method, device, equipment and medium. Background Art

[0002] Documents in computers refer to various files created, edited, stored, and managed on computers. Documents are one of the main ways to record information. Whether it is personal notes or business plans within an enterprise, documents are the basic tools for information storage. Documents can easily share information and knowledge between team members, departments, and even organizations, promoting cooperation and communication. In many business processes, documents play a key supporting role, such as contracts, reports, operating manuals, etc., which are indispensable for the smooth operation of the business. Technical documents (such as software manuals, API documents) are very important for software development and IT support. Documents help users understand how to use the system and also help technicians troubleshoot.

[0003] In traditional monitoring point document management systems, document attribute records are often confused, and some documents are missing key attribute fields, resulting in incomplete information. The content of some document attribute fields is wrong and does not conform to the actual situation. The logical relationship between attribute fields is inconsistent, resulting in data contradictions. Document attribute information is inconsistent with the directory information to which it belongs, affecting the effective management of documents. Therefore, how to repair the problematic fields in documents is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present invention solve the technical problem of low efficiency in repairing problematic fields in documents in the prior art by providing a document repair method, device, equipment and medium, and achieve the technical effect of efficiently repairing problematic fields in documents.

[0005] In a first aspect, the present invention provides a document repair method, the method comprising:

[0006] Scan the target document of the target monitoring point to determine the error fields in the target document and the error types corresponding to the error fields. The error types include time format, content, field missing, IP address, and boundary exceeded.

[0007] Generate an error report for a target document according to a number of error fields and the error types corresponding to the error fields;

[0008] According to the error report, determine the coverage field corresponding to each error field;

[0009] The corresponding error field is overwritten based on the coverage field, and the target document is updated to obtain a repaired target document.

[0010] Furthermore, the target document is scanned to determine each error field in the target document and the error type corresponding to the error field, including:

[0011] According to the order of fields in the target document, the real-time network data of the target monitoring point is compared with the target document to determine the differences between the fields;

[0012] According to the difference between the fields, determining whether the field in the target document is an error field;

[0013] If the field is an error field, the error type of the error field is determined based on the difference.

[0014] Further, according to the error report, the coverage field corresponding to each error field is determined, including:

[0015] Determine if there is a data source for the error field;

[0016] If it exists, determine whether the number of data sources is 1;

[0017] If the number of data sources is 1, the coverage field corresponding to the error field is determined based on the data source and the error report.

[0018] Further, determining the coverage field corresponding to each error field according to the error report also includes:

[0019] If the number of data sources is greater than 1, then the target data source is determined from among the several data sources;

[0020] According to the target data source error report, determine the coverage field corresponding to the error field.

[0021] Furthermore, it also includes:

[0022] If the data source does not exist in the error field, a reminder message is sent to the target client.

[0023] Furthermore, the method further comprises:

[0024] Record the operation information of each overwrite, including: attribute field information before and after the overwrite, overwrite time, overwrite reason and overwrite basis;

[0025] After the repaired target document is obtained, some operation information is stored in the system log.

[0026] Furthermore, overwriting the corresponding error field also includes:

[0027] Determine the overwriting accuracy rate according to a number of overwritten fields and a number of fields to be checked after overwriting the erroneous fields;

[0028] When the overwriting accuracy rate is lower than the threshold, an alarm message is sent to the target client.

[0029] In a second aspect, the present invention provides a document repair device, the device comprising:

[0030] The error analysis module is used to scan the target document of the target monitoring point, determine the error fields in the target document and the error types corresponding to the error fields, and the error types include time format, content, field missing, IP address and boundary exceeding;

[0031] A report generation module, used for generating an error report of a target document according to a number of error fields and error types corresponding to the error fields;

[0032] An overwriting module, used for determining an overwriting field corresponding to each error field according to the error report;

[0033] The update module is used to overwrite the corresponding error field based on the overwriting field and update the target document to obtain a repaired target document.

[0034] In a third aspect, the present invention provides an electronic device, comprising:

[0035] processor;

[0036] a memory for storing processor-executable instructions;

[0037] The processor is configured to execute to implement a document repair method as provided in the first aspect.

[0038] In a fourth aspect, the present invention provides a non-temporary computer-readable storage medium, which, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to implement a document repair method as provided in the first aspect.

[0039] One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:

[0040] The present invention provides a document repair method, which includes: scanning a target document at a target monitoring point, determining each error field in the target document and the error type corresponding to the error field, the error type including time format, content, field missing, IP address and boundary overrun; generating an error report of the target document according to the error fields and the error types corresponding to the error fields; determining the coverage field corresponding to each error field according to the error report; overwriting the corresponding error field based on the coverage field, and updating the target document to obtain a repaired target document. Based on the method provided by the present invention, the attribute confusion problem in the archive management system is effectively solved, the restored archive attribute field is complete and accurate, the validity of the archive data is ensured, manual operations are reduced, the operating efficiency of the system is improved, the later maintenance work caused by archive attribute errors is reduced, and the overall maintenance cost of the system is reduced. Through intelligent repair, the consistency and reliability of the archive data are effectively guaranteed, and the overall performance of the system is improved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0042] Figure 1 A schematic diagram of a flow chart of a document repair method provided by the present invention;

[0043] Figure 2 A schematic diagram of the structure of a document repair device provided by the present invention;

[0044] Figure 3 The present invention provides a schematic structural diagram of an electronic device. DETAILED DESCRIPTION

[0045] The embodiment of the present invention solves the technical problem of low efficiency in repairing problematic fields in a document in the prior art by providing a document repair method.

[0046] The technical solution of the embodiment of the present invention is to solve the above technical problems, and the overall idea is as follows:

[0047] A document repair method comprises: scanning a target document at a target monitoring point, determining each error field in the target document and the error type corresponding to the error field, wherein the error type includes time format, content, field missing, IP address and boundary overrun; generating an error report of the target document according to a number of error fields and the error types corresponding to the error fields; determining a coverage field corresponding to each error field according to the error report; overwriting the corresponding error field based on the coverage field, and updating the target document to obtain a repaired target document.

[0048] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0049] First of all, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0050] The present invention provides Figure 1 A document repair method shown includes steps S11-S14:

[0051] Step S11, scanning the target document of the target monitoring point, determining each error field in the target document and the error type corresponding to the error field, the error type including time format, content, field missing, IP address and boundary overrun.

[0052] Step S12: Generate an error report for the target document according to the error fields and the error types corresponding to the error fields.

[0053] Step S13: Determine the coverage field corresponding to each error field according to the error report.

[0054] Step S14, overwrite the corresponding error field based on the coverage field, and update the target document to obtain a repaired target document.

[0055] Regarding step S11, the target document of the target monitoring point is scanned to determine the error fields in the target document and the error types corresponding to the error fields. The error types include time format, content, field missing, IP address and boundary overrun.

[0056] The detection point may refer to a monitoring device, which is used for monitoring, shooting videos and images. Each monitoring point may correspond to a document, and the document that needs to be repaired is the target document.

[0057] The target document or the target range in the target document may be scanned by script or other means to determine various errors in the attribute fields in the target document.

[0058] For example, regular expressions can be used to retrieve errors such as incorrect time format, non-standard MAC address, excessive content length, no required items, and non-unique IP address. Longitude and latitude boundary algorithms can also be used to discover errors in administrative divisions where longitude and latitude exceed the limits. Inconsistent errors can be identified by extracting the device to which the document belongs and comparing it with the actual device code.

[0059] The following describes the error types:

[0060] Time format: refers to whether the information representing time in the document conforms to the predetermined format. For example, if the time format is required to be "YYYY-MM-DD HH:MM:SS", then if it does not conform to this format, it is a time format error.

[0061] Content: refers to whether the text information in the document is reasonable and accurate, and whether there are obvious grammatical errors or illogical statements.

[0062] Missing fields: Check if a document is missing a required section or piece of information. For example, if a table should contain fields such as name, age, and gender, but a record only provides name and age, then "gender" is a missing field.

[0063] IP Addresses: Check that all IP addresses listed in the document are in the correct format (IPv4 or IPv6). For example, "192.168.1.1" is a valid IPv4 address, and "2001:0db8:85a3:0000:0000:8a2e:07a0:0378" is a valid IPv6 address.

[0064] Boundary out of limit: refers to some numerical data exceeding the preset range. For example, if a field is used to record age, the reasonable range may be from 0 to 120 years old, then any value outside this range is wrong.

[0065] The specific detection method includes: comparing the real-time network data of the target monitoring point with the target document according to the order of fields in the target document to determine the differences between the fields; determining whether the field in the target document is an error field based on the differences between the fields; if the field is an error field, determining the error type of the error field based on the differences.

[0066] Specifically, make sure that the fields in the live online data and the target document are arranged in the same order, and compare the data in each field one by one. If you find differences in the corresponding fields in the two data sources, record these differences. : Once the differences between the fields are determined, you can further analyze whether these differences mean that there are errors in the data in the target document. If the differences indicate that the data in the target document does not meet the expected standards or specifications, then these fields can be considered "error fields". For fields marked as errors, you can determine which error type they belong to based on the error types mentioned above (time format, content, missing fields, IP addresses, and boundary exceeds). For example:

[0067] If the time format is inconsistent, it will be marked as "wrong time format".

[0068] If the content does not make sense or is not logical, it will be marked as "Content Error".

[0069] If a field in the target document is empty or missing, it is marked as "field missing".

[0070] If the IP address format is incorrect, it will be marked as "Wrong IP address".

[0071] If the value is outside the reasonable range, it is marked as "boundary violation".

[0072] Through step S11, not only can the problems in the document be discovered, but the specific nature of the problems can also be clearly pointed out, thereby helping to carry out subsequent data correction or other corresponding processing measures. It is suitable for scenarios that require high-precision data, such as financial transaction systems, real-time monitoring systems, etc.

[0073] Regarding step S12, an error report of the target document is generated according to a number of error fields and the error types corresponding to the error fields.

[0074] Specifically, create the basic structure of the report, including document overview, error type description, error field list, etc. For each error field, record its location, actual value, expected value and error type in detail, count the number and distribution of various error types, and provide an overall error overview.

[0075] Regarding step S13, based on the error report, the coverage field corresponding to each error field is determined.

[0076] Specifically, based on the error report, the document that needs to be repaired and its related attribute data are extracted.

[0077] Before collection, the data source is manually configured in advance, usually by forming a database through an actual networking platform or file import, and the key attributes of the document data are clearly specified one-to-one with the attributes in the corresponding data source to establish a corresponding relationship between the collection attributes.

[0078] During the collection process, by comparing the attributes in the document model with the device attribute fields in the configured data source, and finding the current device information document that meets the conditions through primary key device code matching, key information such as device name, device type, project, manufacturer, etc. are converted one-to-one and collected into the document.

[0079] Specifically, it can include the following three forms: 【1】

[0081] Determine whether there is a data source for the error field; if so, determine whether the number of data sources is 1; if the number of data sources is 1, determine the coverage field corresponding to the error field based on the data source and the error report.

[0082] For example, field A is an error field. Field A records the device type of the monitoring device. The source of field A is data B in the database. Then, based on data B and the error report, the coverage field is determined, and field A is overwritten again. 【2】

[0084] If the number of data sources is greater than 1, a target data source is determined from the plurality of data sources; and a coverage field corresponding to the error field is determined based on an error report of the target data source.

[0085] Specifically, there are many ways to determine the target data source from several data sources. For example, the data source with the highest usage rate can be used as the target data source. 【3】

[0087] If the error field does not have a data source, a reminder message is sent to the target client to remind relevant personnel to overwrite the error field in time.

[0088] Regarding step S14, the corresponding error field is overwritten based on the coverage field, and the target document is updated to obtain a repaired target document.

[0089] The present invention mainly adopts a batch overwrite mode to compare document attributes with data on a real network platform, mark inconsistent content, and perform batch repairs through a comparison-correction method.

[0090] According to the preset rules, the attribute fields are checked and corrected, including:

[0091] Set attribute conversion rules (such as MAC address). After the MAC address format is not standardized through error recognition, it can be converted and corrected with one click, and then checked after error recognition;

[0092] Set the automatic completion of the network parent device code specification, and automatically complete the actual parent device code in the document through the existing association relationship on the network platform;

[0093] Set the automatic device type judgment rules, mark the device as a key document by fixing the IP segment and the special beginning of the first N bits of the code or in a special designated directory;

[0094] Set the national standard digit-based cutting and conversion rules, and use the different digits in the code to represent different rules and attributes, and automatically assign the corresponding attributes;

[0095] Set the channel relationship rules by associating the same capability set, and associate the relationship under the same device document through the capability set actually used on the networking platform.

[0096] Directory inference: Use the information represented by the directory to which the document belongs to infer and complete missing or incorrect attribute fields. For example, the longitude and latitude must not exceed the administrative area represented in the directory, and the encoding specification must comply with the administrative area code.

[0097] Automatic verification: By establishing an automatic verification mechanism for the existing type of data fields in the model; the verification rule relationship includes: rule type, indicator field, adding built-in rules for the indicator field, verification rule table field id, and verification rule name; the rule includes: verification rule ID, document type, indicator field, and verification type array. The verification rule setting function is provided to ensure that the modified attribute field meets the system requirements.

[0098] After each overwrite of the error field, also include

[0099] Record the operation information of each overwrite, including: attribute field information before and after the overwrite, overwrite time, overwrite reason and overwrite basis; after obtaining the repaired target document, store some operation information in the system log to ensure the traceability and transparency of the repair process.

[0100] In addition, in order to verify the overwriting effect and ensure the accuracy of the document, it also includes: overwriting the corresponding error fields, and also includes: determining the overwriting accuracy based on a number of overwritten fields and a number of fields to be checked after overwriting the error fields; when the overwriting accuracy is lower than a threshold, sending an alarm message to the target client.

[0101] For example, there are 100 fields to be covered and 100 fields to be checked. The fields to be checked are compared with the covered fields. If there are 5 differences, the overwriting accuracy is 95%, and the threshold is 98%. An alarm message is sent to the target client to remind relevant personnel that the accuracy of this batch of documents is still insufficient.

[0102] In summary, the present invention provides a document repair method, which includes: scanning the target document of the target monitoring point, determining the error fields in the target document and the error types corresponding to the error fields, the error types including time format, content, field missing, IP address and boundary overrun; generating an error report of the target document according to the error fields and the error types corresponding to the error fields; determining the coverage fields corresponding to the error fields according to the error report; overwriting the corresponding error fields based on the coverage fields, and updating the target document to obtain the repaired target document. Based on the method provided by the present invention, the attribute confusion problem in the archive management system is effectively solved, the repaired archive attribute fields are complete and accurate, the validity of the archive data is ensured, the manual operation is reduced, the operation efficiency of the system is improved, the later maintenance work caused by the archive attribute errors is reduced, and the overall maintenance cost of the system is reduced. Through intelligent repair, the consistency and reliability of the archive data are effectively guaranteed, and the overall performance of the system is improved.

[0103] Based on the same inventive concept, the present invention provides a document repair device, the device comprising:

[0104] The error analysis module 21 is used to scan the target document of the target monitoring point, determine the error fields in the target document and the error types corresponding to the error fields, and the error types include time format, content, field missing, IP address and boundary overrun;

[0105] A report generating module 22, for generating an error report of a target document according to a number of error fields and error types corresponding to the error fields;

[0106] An overwriting module 23, used to determine an overwriting field corresponding to each error field according to the error report;

[0107] The updating module 24 is used to overwrite the corresponding error field based on the overwriting field and update the target document to obtain a repaired target document.

[0108] Based on the same inventive concept, the present invention also provides Figure 3 An electronic device as shown includes:

[0109] Processor 31;

[0110] A memory 32 for storing instructions executable by the processor 31;

[0111] The processor 31 is configured to execute to implement a document repair device as provided above.

[0112] Based on the same inventive concept, the present invention also provides a non-temporary computer-readable storage medium. When the instructions in the storage medium are executed by the processor 31 of the electronic device, the electronic device can execute a document repair device as provided above.

[0113] Since the electronic device introduced in this embodiment is an electronic device used to implement the information processing method in the embodiment of the present invention, based on the information processing method introduced in the embodiment of the present invention, a person skilled in the art can understand the specific implementation of the electronic device of this embodiment and its various variations, so how the electronic device implements the method in the embodiment of the present invention is not described in detail here. As long as the electronic device used by a person skilled in the art to implement the information processing method in the embodiment of the present invention, it belongs to the scope of protection of the present invention.

[0114] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0115] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks 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 processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0116] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1A function specified in one or more boxes.

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

[0118] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

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

Claims

1. A document repair method, characterized in that: The method comprises: Scan the target document of the target monitoring point to determine each error field in the target document and the error type corresponding to the error field, wherein the error type includes time format, content, field missing, IP address and boundary overrun; Generate an error report for the target document according to a number of error fields and error types corresponding to the error fields; Determine, according to the error report, a coverage field corresponding to each error field; The corresponding error field is overwritten based on the overwritten field, and the target document is updated to obtain a repaired target document.

2. A document repair method as claimed in claim 1, characterized in that: Scan the target document to determine each error field in the target document and the error type corresponding to the error field, including: According to the order of fields in the target document, the real-time networked data of the target monitoring point is compared with the target document to determine the difference between the fields; Determine whether the field in the target document is an error field according to the difference between the fields; If the field is an error field, the error type of the error field is determined according to the difference.

3. A document repair method as claimed in claim 1, characterized in that: The determining, according to the error report, a coverage field corresponding to each error field comprises: Determine if there is a data source for the error field; If it exists, determine whether the number of data sources is 1; If the number of data sources is 1, the coverage field corresponding to the error field is determined based on the data source and the error report.

4. A document repair method as claimed in claim 3, characterized in that: The determining, according to the error report, a coverage field corresponding to each error field further comprises: If the number of data sources is greater than 1, then the target data source is determined from among the several data sources; According to the error report of the target data source, a coverage field corresponding to the error field is determined.

5. A document repair method as claimed in claim 3, characterized in that: Also includes: If the data source does not exist in the error field, a reminder message is sent to the target client.

6. A document repair method as claimed in claim 1, characterized in that: The method further comprises: Recording the operation information of each overwriting operation, the operation information includes: attribute field information before and after the overwriting, overwriting time, overwriting reason and overwriting basis; After the repaired target document is obtained, some operation information is stored in the system log.

7. A document repair method as claimed in claim 1, characterized in that: Overwrite the corresponding error field, including: Determine the overwriting accuracy rate according to a number of overwritten fields and a number of fields to be checked after overwriting the erroneous fields; When the overwriting accuracy rate is lower than a threshold, an alarm message is sent to the target client.

8. A document repair device, characterized in that: The device comprises: An error analysis module is used to scan the target document of the target monitoring point, determine each error field in the target document and the error type corresponding to the error field, and the error type includes time format, content, field missing, IP address and boundary overrun; A report generation module, used for generating an error report of the target document according to a number of error fields and error types corresponding to the error fields; An overwriting module, used for determining, according to the error report, an overwriting field corresponding to each error field; The update module is used to overwrite the corresponding error field based on the overwriting field and update the target document to obtain a repaired target document.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute to implement a document repair method as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to implement a document repair method as described in any one of claims 1 to 7.

Images