A method and system for document data entry

Abstract

The present invention relates to the technical field of computer document editing, and specifically to a method and system for document data entry. The method includes: a method for making a document template, establishing a document data input control library, a storage structure of document data, establishing a document data description message, establishing a visual weaving method for the document data description message, establishing a document grammar to define the document data description message, encapsulating the document template, the document data description message, and the already-entered data set into one body to form a custom document type, establishing a parsing engine to parse the format of the WRS document, and generating an operable human-machine delivery function module to support the entry of document data in any format. The present invention can quickly and effectively meet the enterprise's data entry requirements for any key documents, achieve fine-grained control over the entered data, and collect the entered data of each document in real time to support the data interaction requirements between documents and between documents and systems.

Description

Technical Field

[0001] The present invention relates to the technical field of computer document editing, and specifically to a method and system for document data entry. Background Art

[0002] The basis for digitalization to improve enterprise efficiency is to turn everything into analyzable data, which necessarily includes the documents that appear in the enterprise production and operation processes. By efficiently and accurately extracting the data in the documents, it can effectively accelerate the operation of enterprise business. For example, if the enterprise finance can obtain the data of the sales contract in real time, it will help to more timely control the enterprise cash flow; if the testing agency can obtain the data of the test report in real time, it will help to more timely notify the sample submitting unit; and so on. There are numerous application scenarios that rely on the data carried in various key documents. It can be seen that the technology for extracting data from documents is very crucial.

[0003] However, the existing document editing systems only support the data entry of documents in any format, but cannot support the fine-grained control of document data field entry (such as numerical type, size range, and numerical enumeration), and do not have the data interaction ability of documents. And the existing systems with data interaction ability are not document systems in essence and cannot support the data entry of documents in any format. Therefore, those skilled in the art provide a method and system for document data entry to solve the problems raised in the above background art. Summary of the Invention

[0004] The purpose of the present invention is to provide a method and system for document data entry to solve the problems raised in the above background art.

[0005] To achieve the above purpose, the present invention provides the following technical solutions: A method and system for document data entry, and the document entry system includes:

[0006] A document template for an operator to enter data in the part of the document where data needs to be entered based on the semantic background of the document content structure;

[0007] A rule set for defining the entry rules of all data items to be entered in the document template and dividing the rules into different rule files based on the page number value of the data item in the document;

[0008] A parameter set for saving the entry parameters corresponding to the data items to be entered in the document template and dividing the entry parameters into different parameter files based on the page number value of the data item in the document;

[0009] A data document set for saving various format documents generated after the document entry data is completed;

[0010] A control library is used to ensure that for each data type defined in the centralized label data type, there is a corresponding data input control in the document data type input control library;

[0011] A parsing engine is used to parse the format of the document and generate an operable human-machine delivery function module to support the data entry function for document data in any format;

[0012] The method for document data entry includes the following steps:

[0013] S1. Document template production method;

[0014] Establish a unique label containing semantics, define it to form a set of label data types, and the data types required for the input data items can be identified through the implied semantics;

[0015] S2. Establish a document data input control library;

[0016] Based on the above set of label data types, implement the corresponding verification-type data entry controls to form a document data input control library;

[0017] S3. Storage structure of document data;

[0018] Locate the document data using a multi-dimensional coordinate system, use the multi-dimensional coordinate values to form the key of the storage item, and the data values to form the value of the storage item, specifically including: single-dimensional entry type, two-dimensional entry type, picture type;

[0019] S4. Establish a document data description message to clearly express the various data verification rules and delivery rules involved in the document data entry process;

[0020] S5. Establish a visualization weaving method for the document data description message and establish a document grammar to define the above document data description message;

[0021] S6. Package the document template, document data description message, and the entered data set into one to form a custom document type, namely the WRS document;

[0022] S7. Design and establish a parsing engine to parse the format of the WRS document and generate an operable human-machine delivery function module to support the data entry function for document data in any format;

[0023] S8. Use the WRS document as the operation object to implement both the WEB system and the PC system modes for the above WRS document parsing engine to support two usage scenarios: with network and without network.

[0024] As a further solution of the present invention: The specific operation in S1 is: using the document content structure as the semantic background, data entry is performed in the part of the document where data needs to be entered;

[0025] Among them, the label data type set includes: integer, decimal, text, multi - option, single - option, date, time, table, picture, which can cover various data types involved in the existing document data entry process and support the extension of new data types.

[0026] As a further solution of the present invention: Each verification - type data entry control in S2 embeds various business verification rules that may appear according to the data types it supports;

[0027] Specifically: integer entry control, decimal entry control, text entry control, multi - option entry control, single - option entry control, date entry control, time entry control, table and picture entry control, new data type entry control.

[0028] As a further solution of the present invention: The message in S4 contains the following content:

[0029] ① The data field identifier of the document to be filled;

[0030] ② The data type constraint of the data field of the document to be filled;

[0031] ③ The data relationship constraint of the data field of the document to be filled;

[0032] ④ The data verification constraint of the data field of the document to be filled;

[0033] ⑤ Data field interaction constraint: Define two data delivery constraints for the input and output of document data.

[0034] As a further solution of the present invention: The document grammar in S5 includes:

[0035] ① Data field definition section, specifically: field order, field identifier, field name, field data type, basic constraints required by the field data type, and field semantics;

[0036] ② Data relationship definition section, specifically: linkage type, relationship source field, relationship target field, trigger condition on which the target field value depends, and data field value pairing relationship;

[0037] ③ Data verification definition section: Define the business verification that needs to be performed when submitting document data, corresponding to the content of the document data description message, including: data value null verification and business - related calculation verification;

[0038] ④ Data interaction definition section, specifically: the mapping relationships of interface address, interface type, request type, request data structure and the involved data field coordinates, response data structure and document data field coordinates.

[0039] As a further solution of the present invention: in step S7, the WRS document is further rendered by a document parsing engine to complete data entry and data interaction of the WRS document. The specific operations include:

[0040] ① Generate a preview view of the WRS document template;

[0041] ② Dynamically draw the data entry view corresponding to the document template;

[0042] ③ Save the entered data in real time with the data coordinates as the key and the data value as the value;

[0043] ④ Provide an interaction ability to complete data initialization when the document is opened and push data when the document is submitted according to the interaction constraints indicated by the rules;

[0044] ⑤ Provide traceability. Each time it is submitted, the WRS document saves the data modification difference in sequence;

[0045] ⑥ Provide a conversion ability to support the conversion of the WRS document into WORD, WPS, and PDF documents.

[0046] As a further solution of the present invention: the specific operation in step S8 is as follows:

[0047] ① In an environment with network: operate the WRS document through the WEB system to complete data entry and support the export of the WRS document to a certain storage device. Then, in an environment without network, support the import of the WRS document from the certain storage device into the PC system to complete the relevant operations of the WRS document;

[0048] ② In an environment without network, operate the WRS document through the PC system to complete data import and support the export of the WRS document to a certain storage device. Then, in an environment with network, support the import of the WRS document from the certain storage device into the WEB system to complete the relevant operations of the WRS document.

[0049] Compared with the prior art, the beneficial effects of the present invention are: a method and system for document data entry designed by the present invention, when actually applied;

[0050] Compared with traditional documents that only contain the content context, document format and document data of the document, the WRS document designed by the present invention adds data constraint rules, data interaction rules and data positioning rules on this basis. It already supports the verification and interaction logic required during the data entry process from the content composition of the document itself. It can be considered that the WRS document is a business self-check document;

[0051] In addition, the parsing engine implemented around the WRS document uses dynamic parsing technology to generate its corresponding human-machine delivery function. This method can solve the problem of endless workload brought by the implementation method of developing a front-end interface for each template in the traditional technical mode from the technical bottom layer, thus effectively supporting data entry for documents in any format. Brief Description of the Drawings

[0052] Figure 1 It is a structural diagram of the WRS document in a method and system for document data entry;

[0053] Figure 2 It is a schematic execution diagram of a method and system for document data entry;

[0054] Figure 3 It is a step diagram of compiling a document data description message through a document template in a method and system for document data entry;

[0055] Figure 4 It is a schematic diagram of data verification for the WRS document in a method and system for document data entry;

[0056] Figure 5 It is a schematic diagram of data interaction for the WRS document in a method and system for document data entry;

[0057] Figure 6 It is a schematic diagram of the WRS document supporting network environment switching operation in a method and system for document data entry. Detailed Description of the Preferred Embodiment

[0058] Next, in combination with the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0059] Please refer to Figures 1-6 , in the embodiments of the present invention, a document data entry system, the document entry system includes:

[0060] A document template for an operator to enter data in the part of the document where data needs to be entered based on the semantic background of the document content structure;

[0061] A rule set for defining the entry rules for all data items to be entered in the document template and dividing the rules into different rule files based on the page number values of the data items in the document;

[0062] A parameter set, which is used to save the parameters corresponding to the data items to be entered in the document template, and based on the page number value of the data item in the document, the entered parameters are divided into different parameter files;

[0063] A data document set, which is used to save various format documents generated after the document entry data is completed;

[0064] A control library, which is used to ensure that for each data type defined in the label data type set, there is a corresponding data input control in the document data type input control library;

[0065] A parsing engine, which is used to parse the format of the document and generate an operable human-machine delivery function module to support the data entry function of any format document data;

[0066] A method for document data entry, the method includes the following steps:

[0067] The first step, the document template making method;

[0068] Compared with the traditional document template making method that only uses a unique label to define the data items to be entered in the document, the present invention re-establishes a unique label containing semantics for definition, forms a label data type set, and can identify the data type required for the entered data item through the contained semantics;

[0069] The above-mentioned unique label is “ $ {[data type] Data identifier}”;

[0070] Taking the document fragment “Name: __, Age: __, Gender: __;” as an example to make a document template, the corresponding fragment in the document template is as follows:

[0071] Name: $ {[str] t1}, Age: $ {[int] t2}, Gender: $ {[select] t3};

[0072] Among them, [XXX] in the document label represents the data type of the data field, and the data type required for the entered data item can be identified through the contained semantics;

[0073] Moreover, a set of tag data type sets is defined within this method, specifically including: integer [int], decimal [dec], text [str], multi - option [select], single - option [bool], date [date], time [time], table [table], image [image], which can cover various data types involved in the existing document data entry process and support the extension of new data types. The definition method of new data types is "[type]". For example: capital amount [money];

[0074] Step 2: Establish a document data input control library;

[0075] Based on the above - mentioned tag data type sets, corresponding validation - type data entry controls are implemented to form a document data input control library;

[0076] Among them, for each validation - type data entry control, various business validation rules that may appear for its supported data type are embedded according to the data type. Specifically:

[0077] The integer entry control only supports the entry of legal integers and includes the validation of the integer range;

[0078] The decimal entry control only supports the entry of legal decimals and includes the validation of the decimal range and decimal precision;

[0079] The text entry control includes the validation of the text length range, illegal characters, and legal characters;

[0080] The multi - option entry control is not editable and is restricted to selecting among specified multiple data items;

[0081] The single - option entry control only supports two options: selection and non - selection;

[0082] The date entry control only supports the entry of legal dates and automatically transforms the date into a specified format;

[0083] The time entry control only supports the entry of legal times and automatically transforms the time into a specified format;

[0084] The table entry control supports the entry of table data with any cell merging style;

[0085] The image entry control only supports the entry of images in legal formats and includes the scaling adjustment of the image size and dimensions;

[0086] The new data type entry control is extended according to its data type. For example, the capital amount entry control restricts the entered text to conform to the capital description of the amount;

[0087] Among them, the label data type set and the document data entry control library form a one-to-one correspondence relationship, that is, for each data type defined in the label data type set, there is a corresponding data entry control in the document data input control library;

[0088] S3. The storage structure of document data;

[0089] The document data is located by using a multi-dimensional coordinate system "{x, y, z,...}", and the multi-dimensional coordinate values are used to form the key of the storage item, and the data value forms the value of the storage item; specifically including:

[0090] Single-dimensional entry type, including data types such as integer [int], decimal [dec], text [str], multi-selection [select], single-selection [bool], date [date], etc. The positioning coordinates of the data item are composed of the document ID, page number value, data identifier, and data type. The corresponding storage item key is {wrsID, pageNum, dataMark, dataType}, and the corresponding storage item value is the data value;

[0091] Two-dimensional entry type, corresponding to the table [table] data type. The positioning coordinates of the data item are composed of the document ID, page number value, data identifier, data type, row index, and column index. The corresponding storage item key is {wrsID, pageNum, dataMark, dataType, rowIndex, colIndex}, and the corresponding storage item value is the data value of the table cell;

[0092] Picture type; corresponding to the picture [image] data type. The positioning coordinates of the data item are composed of the document ID, page number value, data identifier, and data type. The corresponding storage item key is {wrsID, pageNum, dataMark, dataType}, and the corresponding storage item value is the storage path of the picture in the WRS document;

[0093] Furthermore, the composition structure of {wrsID, pageNum, dataMark, dataType, rowIndex, colIndex} as the key of the storage item is further elaborated as follows:

[0094] wrsID is the document ID of the WRS document. This ID is dynamically generated and built into the WRS document when the WRS document is created and cannot be changed;

[0095] pageNum is the page number value of the page where the data item to be entered is located in the WRS document template;

[0096] dataMark is the data identifier defined for the data item to be entered in the WRS document template;

[0097] dataType is the data type defined for the data item to be entered in the WRS document template, and this type determines the processing method of the value of this data item;

[0098] rowIndex is used to locate the row index of the cell corresponding to the tabular data to be entered in the WRS document template;

[0099] colIndex is used to locate the column index of the cell corresponding to the tabular data to be entered in the WRS document template;

[0100] As described above, within the system, by locating the WRS document through wrsID, the template page through pageNum, and the data item through dataMark, a specific type of data item to be entered in the document can be accurately located. Further, the specific cell data item of the tabular data can be located through rowIndex and colIndex;

[0101] As described above, when the WRS document performs data interaction, the system determines the processing method of the value of the storage item according to dataType, specifically:

[0102] For character types: including integer [int], decimal [dec], text [str], multi - option [select], single - option [bool], date [date], time [time], table [table], the value is used to participate in data interaction;

[0103] For byte types: including picture [image], the original picture file is obtained according to the value to participate in data interaction;

[0104] Step 4: Establish a document data description message, which is used to clearly express various data verification rules and delivery rules involved in the process of document data entry;

[0105] And the message includes the following content:

[0106] ① The data field identifier of the document to be filled

[0107] The data field identifier includes: data identifier, data type, and data semantics;

[0108] Among them, the data identifier indicates the unique identifier of the data in the document. For example, the identifier of the first data item to be entered in the document is t1, and the identifier of the second data item to be entered is t2. The data identifier is used to form the coordinates of the data item in the document;

[0109] Among them, the data type indicates whether the data field belongs to the text data, table data, or picture data to be filled in the document. For example, the text type data in the document is marked as str, the table type data in the document is marked as table, and the image type data in the document is marked as image. The data type is used to indicate the processing method adopted when entering the document data;

[0110] ② Data type constraints for data fields in the document to be filled

[0111] The data types include: integer [int], decimal [dec], text [str], multi - option [select], single - option [bool], date [date], time [time], table [table], picture [image], and new types at other extensions; specifically:

[0112] Integer: minimum value constraint, maximum value constraint, default value constraint;

[0113] Decimal: minimum value constraint, maximum value constraint, default value constraint, precision constraint;

[0114] Text: length constraint, illegal character constraint, legal character constraint, default value constraint;

[0115] Multi - option: available option constraint, default value constraint;

[0116] Single - option: available option constraint, default value constraint;

[0117] Date: date range constraint, date format constraint, default value constraint;

[0118] Time: time range constraint, time format constraint, default value constraint;

[0119] Table: format constraint; Picture: picture size constraint; New type: Define specific constraint methods according to the business needs of the extended type;

[0120] ③ Data relationship constraints for data fields in the document to be filled

[0121] Define the limited types of relationship constraints between multiple data fields in the document as actions, and define a keyword for each action to form an associated action set; specifically: conversion action, selection action, and calculation action; which can cover various linkage relationships involved in the existing document data entry process and support the extension of new action types;

[0122] Among them, the explanation of the conversion action is as follows: When there is a one-to-one correspondence between the amount numerical field and the amount in capital letters description field in the document, this relationship can be specified as the amount in capital letters conversion action. In the document data description message, use the amount in capital letters conversion association action to add data relationship constraints to these two fields. When the amount numerical value changes, the amount in capital letters will automatically change according to the amount numerical value;

[0123] The explanation of the selection action is as follows: When there is a one-to-one correspondence among the three fields of the company name, the opening bank, and the account number in the document, this relationship can be specified as the multi-level linked selection action. In the document data description message, use the multi-level linked selection association action to add data relationship constraints to these three fields. When the company changes, the opening bank and the account number will automatically change according to the company name;

[0124] The explanation of the calculation action is as follows: When there is a calculation relationship where the sum of the paid amount and the remaining amount in the document is equal to a certain fixed value, this relationship can be specified as the summation calculation action. In the document data description message, use the summation calculation association action to add data relationship constraints to these two fields. When the paid amount value changes, the remaining amount will automatically change according to the summation fixed value;

[0125] Furthermore, define new action types according to the business needs of the extended data relationship;

[0126] ④ Data field data verification constraints for the document to be filled

[0127] Design two types of data verification constraints, and define a keyword for each verification rule in each type of data verification constraint as the constraint action to form a data verification constraint set, which are respectively:

[0128] Judgment type constraint: Judge that the value of a single field conforms to a certain rule, for example: non-empty judgment;

[0129] Calculation type constraint: Calculate that the values of multiple fields conform to a certain result, for example: summation operation;

[0130] Among them, defining data verification constraints includes two parts, which are respectively:

[0131] Constraint action: Identify the execution method of the data verification constraint;

[0132] Constraint field set: Identify the field set to be verified by the data verification constraint action;

[0133] ⑤ Data field interaction constraints

[0134] Define two types of data delivery constraints for the input and output of document data, specifically:

[0135] Data acquisition: Obtain data from external data sources and initialize the content of the document data;

[0136] Data push: After the document data is correctly entered, submit the data to an external system;

[0137] Among them, the specific content defined for the data delivery constraint includes: data interface, interface type, request type, parameter body, and response conversion relationship;

[0138] Step 5: Establish a visual weaving method for the document data description message and establish a document grammar to define the above document data description message;

[0139] Among them, the document grammar includes:

[0140] ① Data field definition section, specifically: field order, field identifier, field name, field data type, basic constraints required by the field data type, and field semantics;

[0141] ② Data relationship definition section, specifically: linkage type, relationship source field, relationship target field, trigger condition on which the target field value depends, and data field value pairing relationship;

[0142] ③ Data verification definition section: Define the business verification that needs to be performed when submitting document data. Corresponding to the content of the document data description message, it includes: data value null verification and business-related calculation verification;

[0143] ④ Data interaction definition section, specifically: interface address, interface type, request type, mapping relationship between the request data structure and the involved data field coordinates, and the response data structure and the document data field coordinates;

[0144] Furthermore, obtain the content text of the document template. According to the order from top to bottom and from left to right, parse the tag text in the format of $ {[data type] Data identifier}. Extract the five Chinese characters on the left side of the tag as the data field name, parse the data type and data identifier represented by the tag to generate the first part of the above document grammar, and the first part of the above document grammar is a mandatory item. Whether the latter three parts of the content are required can be determined according to the document data entry business;

[0145] Step 6: Package the document template, document data description message, and the entered dataset into one, forming a custom document type, namely the WRS document;

[0146] Step 7: Design and establish a parsing engine to parse the format of the WRS document and generate an operable human-machine delivery function module to support the data entry function of documents in any format;

[0147] Furthermore, render the WRS document through the document parsing engine to complete data entry and data interaction for the WRS document. The specific operations include:

[0148] ① Generate a preview view of the WRS document template;

[0149] ② Dynamically draw the data entry view corresponding to the document template;

[0150] ③ Save the entered data in real time with the data coordinates as the key and the data values as the value in a structure;

[0151] ④ Provide interaction capabilities. According to the interaction constraints indicated by the rules, complete data initialization when the document is opened and push data when the document is submitted;

[0152] ⑤ Provide traceability. Each time it is submitted, the WRS document saves the data modification difference in sequence;

[0153] ⑥ Provide conversion capabilities to support the conversion of WRS documents to WORD, WPS, and PDF documents;

[0154] The eighth step: Take the WRS document as the operation object and implement the WEB system and PC system modes for the above-mentioned WRS document parsing engine to support two usage scenarios: with network and without network;

[0155] The specific operations for the two usage scenarios are as follows:

[0156] ① In a networked environment: Operate the WRS document through the WEB system to complete data entry and support the export of the WRS document to a certain storage device. After that, in a non-networked environment, support the import of the WRS document from the certain storage device to the PC system to complete the relevant operations of the WRS document;

[0157] ② In a non-networked environment, operate the WRS document through the PC system to complete data import and support the export of the WRS document to a certain storage device. After that, in a networked environment, support the import of the WRS document from the certain storage device to the WEB system to complete the relevant operations of the WRS document.

[0158] For those skilled in the art, it is obvious that the present invention is not limited to the details of the above exemplary embodiments, and without departing from the spirit or basic characteristics of the present invention, the present invention can be implemented in other specific forms. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of the present invention is defined by the appended claims rather than the above description. Therefore, it is intended to embrace all changes falling within the meaning and scope of the equivalent elements of the claims in the present invention.

[0159] In addition, it should be understood that although this specification is described in terms of embodiments, not every embodiment contains only one independent technical solution. This narrative manner of the specification is only for clarity. Those skilled in the art should regard the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

Claims

1. A document data entry system, characterized in that, it includes: A document template, which is used for an operator to enter data in the part of the document where data needs to be entered based on the document content structure as the semantic background; A rule set, which is used to define the entry rules for all data items to be entered in the document template, and based on the page number value of the data item in the document, divide the rules into different rule files; A parameter set, which is used to save the parameters corresponding to all data items to be entered in the document template, and based on the page number value of the data item in the document, divide the entry parameters into different parameter files, A data document set, which is used to save various formatted documents generated after the document entry data is completed; A control library, which is used to ensure that for each data type defined in the label data type set, there is a corresponding data input control in the document data type input control library; A parsing engine, which is used to parse the format of the document and generate an operable human-computer interaction function module to support the data entry function of any formatted document; The method of this document data entry system includes the following steps: S1. Document template production method; Establish a unique label containing semantics, define it to form a label data type set, and the data type required for the entered data item can be identified through the contained semantics; S2. Establish a document data input control library; Based on the above label data type set, implement the corresponding verification type data entry control to form a document data input control library; S3. Storage structure of document data; Locate the document data using a multi-dimensional coordinate system, use the multi-dimensional coordinate values to form the key of the storage item, and the data value to form the value of the storage item, specifically including: single-dimensional entry type, two-dimensional entry type, picture type; S4. Establish a document data description message, which is used to clearly express various data verification rules and interaction rules involved in the document data entry process; among them, the message includes the following content: ① The data field identifier of the document to be filled; ② The data type constraint of the data field of the document to be filled; ③ The data relationship constraint of the data field of the document to be filled; ④ The data verification constraint of the data field of the document to be filled; ⑤ Data field interaction constraint: Define two data interaction constraints for the input and output of document data; S5. Establish a visual weaving method for the document data description message, and establish a document grammar to define the above document data description message; among them, the document grammar includes: ① Data field definition section, specifically: field order, field identifier, field name, field data type, basic constraints required by the field data type, and field semantics; ② Data relationship definition section, specifically: linkage type, relationship source field, relationship target field, trigger condition on which the target field value depends, data field value pairing relationship; ③ Data verification definition section: Define the business verification that needs to be executed when the document data is submitted, corresponding to the content of the document data description message, including: data value null verification and business-related calculation verification; ④ Data interaction definition section, specifically: the mapping relationships of interface address, interface type, request type, request data structure and the involved data field coordinates, response data structure and document data field coordinates; S6. Package the document template, document data description message, and the entered data set into one, forming a custom document type, namely the WRS document; S7. Design and establish a parsing engine to parse the format of the WRS document and generate an operable human-computer interaction function module to support the data entry function for documents in any format; S8. Use the WRS document as the operation object, implement the WEB system and PC system modes for the above WRS document parsing engine to support two usage scenarios of having network and not having network; among them, ① In the networked environment: Operate the WRS document through the WEB system, complete data entry and support exporting the WRS document to a certain storage device. Then, in the non-networked environment, support importing the WRS document from a certain storage device into the PC system to complete the relevant operations of the WRS document; ② In the non-networked environment, operate the WRS document through the PC system, complete data import and support exporting the WRS document to a certain storage device. Then, in the networked environment, support importing the WRS document from a certain storage device into the WEB system to complete the relevant operations of the WRS document.

2. The method for a document data entry system according to claim 1, characterized in that, the specific operation in S1 is: Using the document content structure as the semantic background, perform data entry in the parts of the document where data needs to be entered; Among them, the label data type set includes: integer, decimal, text, multi-choice, single-choice, date, time, table, picture, which can cover various data types involved in the existing document data entry process and support the extension of new data types.

3. The method for a document data entry system according to claim 1, characterized in that, each verification-type data entry control in S2 embeds various business verification rules according to the data types it supports; Specifically: integer entry control, decimal entry control, text entry control, multi-choice entry control, single-choice entry control, date entry control, time entry control, table and picture entry control, new data type entry control.

4. The method for a document data entry system according to claim 1, characterized in that, in S7, further render the WRS document through the document parsing engine to complete data entry and data interaction for the WRS document. The specific operations include: ① Generate a preview view of the WRS document template; ② Dynamically draw the data entry view corresponding to the document template; ③ Real-time save the entered data with the data coordinates as the key and the data value as the value; ④ Provide interaction capabilities, and complete data initialization when the document is opened and push data when the document is submitted according to the interaction constraints indicated by the rules; ⑤ Provide traceability. Each time it is submitted, the WRS document saves the difference in data modification once; ⑥ Provide conversion capabilities to support converting the WRS document into WORD, WPS, and PDF documents.

Images