Paper file content access method and device and storage medium

Abstract

The invention provides a paper file content access method and device and a storage medium. The method comprises the steps that a file type table is created in a database through a user-defined form; according to the file type table, defining a content structure table corresponding to the corresponding file type; dynamically generating a content entity table corresponding to the file type according to a preset field in the content structure table; scanning a to-be-archived paper file, generating a target electronic file, and setting a target file type of the target electronic file; mounting the target electronic file into the target content entity table, and generating an entity table record; reading the target content structure table on the front-end query page, and generating an editing form page according to a preset field in the target content structure table; inputting the content of the target electronic file into a corresponding field on an editing form page, and storing the input file content into a target content entity table; and associatively storing the target content entity table and the target electronic file in a database.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method and device for accessing paper document content and a storage medium. Background Art

[0002] In daily work, various paper documents are usually generated, especially in government systems or archives, such as document archives, scientific and technological research archives, basic construction archives, equipment and instrument archives, product archives, accounting archives, personnel archives, audit archives, etc. These paper documents are easily damaged over the years, so it is very important to store paper documents electronically.

[0003] At present, paper documents are usually scanned into image files or PDF files for electronic storage. However, in this storage method, since paper documents may be handwritten, and different types of paper documents have different file formats, different fields, and different positions of field values ​​and corresponding content values, it is impossible to identify the corresponding content of the paper documents for storage. In addition, there is also a problem of difficulty in retrieval after paper documents are scanned into electronic files for storage. For example, you want to retrieve the electronic file of a certain paper document, but you cannot retrieve it by the file content or a certain field. You can only retrieve it by the stored electronic file name. Such a search makes it difficult to locate the document you want to find. Moreover, different people pay attention to different paper documents. Even if the paper documents they pay attention to are the same, the content of the paper documents they pay attention to may be different. Summary of the invention

[0004] The present application provides a method, device and storage medium for accessing the contents of a paper document to solve the problems existing in the related art. The technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a method for accessing the contents of a paper document, comprising:

[0006] Creating a file type table in a database through a custom form, wherein the file type table is used to record the file type of each electronic file stored in the database;

[0007] According to the file type table, a content structure table corresponding to the corresponding file type is defined, wherein the content structure table includes a preset field corresponding to the corresponding file type that is configured by a custom configuration, and the preset field is used to define the field content that can be searched and displayed on the front-end query page;

[0008] Dynamically generate a content entity table corresponding to the file type according to the preset fields in the content structure table;

[0009] Scan the paper document to be archived, generate a target electronic file, and set the target file type of the target electronic file;

[0010] Mounting the target electronic file into a target content entity table to generate an entity table record, wherein the target content entity table corresponds to the target file type;

[0011] Reading a target content structure table on the front-end query page, and generating an edit form page according to preset fields in the target content structure table, wherein the target content structure table corresponds to the target file type;

[0012] Entering the content of the target electronic file into the corresponding field on the edit form page, and saving the entered file content into the target content entity table;

[0013] The target content entity table is associated with the target electronic file and stored in the database.

[0014] In one implementation, according to the file type table, defining a content structure table corresponding to a corresponding file type includes:

[0015] Define a type field corresponding to a corresponding file type in the file type table;

[0016] According to the type field, define a blank content structure table corresponding to the file type;

[0017] Obtaining the preset field;

[0018] The preset field is inserted into the blank content structure table to obtain the content structure table.

[0019] In one implementation, the preset fields are obtained by custom configuration in the following manner:

[0020] Open the structure editing page of the corresponding file type;

[0021] Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page;

[0022] The preset field is obtained according to the default field.

[0023] In one implementation, the preset fields are obtained by custom configuration in the following manner:

[0024] Open the structure editing page of the corresponding file type;

[0025] Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page;

[0026] In response to a user opening a front-end query page of a corresponding file type, dynamically encapsulating a form on the front-end query page to display the search field and the list display field;

[0027] In response to a user clicking a personalized setting control on the front-end query page, displaying a personalized setting page for a corresponding file type;

[0028] Receiving a personalized field that is customized and configured by a user on the personalized setting page, and saving the personalized field, wherein the personalized field is obtained by performing personalized configuration on the search field and the list display field;

[0029] The preset field is obtained according to the personalized field.

[0030] In one embodiment, the preset fields include: field name, field comment, field type and field length; dynamically generating a content entity table of a corresponding file type according to the preset fields in the content structure table includes:

[0031] According to the field name, field comment, field type and field length in the preset field, a content entity table of the corresponding file type is dynamically generated.

[0032] In one embodiment, the method further comprises:

[0033] Entering relevant content of the target electronic file in the file storage system page according to the preset fields in the target content structure table;

[0034] Saving the relevant content into the target content entity table;

[0035] The target electronic file is uploaded, and the target content entity table is associated with the target electronic file and stored in a database.

[0036] In one embodiment, the method further comprises:

[0037] The target content entity table is associated with the target electronic file and stored in the database, and the target content entity table is saved in Elasticsearch.

[0038] In a second aspect, the embodiment of the present application further provides a device for accessing the contents of a paper document, including:

[0039] The processing unit is used to create a file type table in a database through a custom form, wherein the file type table is used to record the file type of each electronic file stored in the database; based on the file type table, a content structure table corresponding to the corresponding file type is defined, wherein the content structure table includes a custom configured preset field corresponding to the corresponding file type, wherein the preset field is used to define the field content that can be retrieved and displayed on the front-end query page; based on the preset field in the content structure table, a content entity table corresponding to the file type is dynamically generated;

[0040] A scanning unit, used for scanning a paper document to be archived, generating a target electronic document, and setting a target file type of the target electronic document;

[0041] The access unit is used to mount the target electronic file into a target content entity table to generate an entity table record, wherein the target content entity table corresponds to the target file type; read the target content structure table on the front-end query page, and generate an edit form page according to preset fields in the target content structure table, wherein the target content structure table corresponds to the target file type; enter the content of the target electronic file into the corresponding field on the edit form page, and save the entered file content into the target content entity table; and associate the target content entity table with the target electronic file and store them in the database.

[0042] In one implementation, when the processing unit is used to define a content structure table corresponding to a corresponding file type according to the file type table, it is specifically used to:

[0043] Define a type field corresponding to a corresponding file type in the file type table;

[0044] According to the type field, define a blank content structure table corresponding to the file type;

[0045] Obtaining the preset field;

[0046] The preset field is inserted into the blank content structure table to obtain the content structure table.

[0047] In one implementation, the preset field is obtained by the processing unit through custom configuration in the following manner:

[0048] Open the structure editing page of the corresponding file type;

[0049] Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page;

[0050] The preset field is obtained according to the default field.

[0051] In one implementation, the preset field is obtained by the processing unit through custom configuration in the following manner:

[0052] Open the structure editing page of the corresponding file type;

[0053] Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page;

[0054] In response to a user opening a front-end query page of a corresponding file type, dynamically encapsulating a form on the front-end query page to display the search field and the list display field;

[0055] In response to a user clicking a personalized setting control on the front-end query page, displaying a personalized setting page for a corresponding file type;

[0056] Receiving a personalized field that is customized and configured by a user on the personalized setting page, and saving the personalized field, wherein the personalized field is obtained by performing personalized configuration on the search field and the list display field;

[0057] The preset field is obtained according to the personalized field.

[0058] In one embodiment, the preset fields include: field name, field comment, field type and field length; when the processing unit is used to dynamically generate a content entity table of a corresponding file type according to the preset fields in the content structure table, it is specifically used to:

[0059] According to the field name, field comment, field type and field length in the preset field, a content entity table of the corresponding file type is dynamically generated.

[0060] In one implementation, the access unit is further configured to:

[0061] Entering relevant content of the target electronic file in the file storage system page according to the preset fields in the target content structure table;

[0062] Saving the relevant content into the target content entity table;

[0063] The target electronic file is uploaded, and the target content entity table is associated with the target electronic file and stored in a database.

[0064] In one implementation, the access unit is further configured to:

[0065] The target content entity table is associated with the target electronic file and stored in the database, and the target content entity table is saved in Elasticsearch.

[0066] In a third aspect, an embodiment of the present application further provides a computer device, comprising: a memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement a method in any one of the above-mentioned aspects, wherein the memory and the processor communicate with each other through an internal connection path.

[0067] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method in any one of the above-mentioned embodiments is implemented.

[0068] The advantages or beneficial effects of the above technical solution include at least:

[0069] This application creates corresponding fields for different types of paper document contents through custom forms, and records the file contents of paper documents through file scanning, mounting and entry. It can realize dynamic field generation and editing storage of paper documents of different file types, facilitate the viewing and retrieval of file contents, and thus realize dynamic access to paper document contents.

[0070] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in the present application and should not be regarded as limiting the scope of the present application.

[0072] Figure 1 A flowchart of a method for accessing paper document content provided in an embodiment of the present application;

[0073] Figure 2 A flowchart of another method for accessing paper document content provided in an embodiment of the present application;

[0074] Figure 3 A structural block diagram of a device for accessing paper document content provided in an embodiment of the present application;

[0075] Figure 4 A structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0077] Various technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0078] Before introducing the embodiments of the present application, some terms in the present application are first explained to facilitate understanding by those skilled in the art.

[0079] Elasticsearch: is a distributed, highly scalable, and highly real-time search and data analysis engine. It can easily enable large amounts of data to be searched, analyzed, and explored. Taking full advantage of the horizontal scalability of Elasticsearch can make data more valuable in a production environment.

[0080] The following will be combined Figure 1 and Figure 2 The method for accessing the content of a paper document provided in the embodiment of the present application is specifically described.

[0081] Figure 1 FIG. 1 is a flow chart showing a method for accessing paper document content according to an embodiment of the present application. Figure 1 As shown, the method may include the following steps:

[0082] S110. Create a file type table in the database through a custom form.

[0083] In one embodiment, the file type table is used to record the file type of each electronic file stored in the database. It can be understood that, for each electronic file stored in the database, the file type table will automatically add a record related to the file type of the electronic file. The file type can be a file or an archive.

[0084] In one embodiment, the primary key of the file type table may be an auto-incrementing primary key. It can be understood that the id field in the file type table is a numeric auto-incrementing key.

[0085] As an example, when an electronic file is stored in a database, a new record id will be added to the file type table. For example, if the id field corresponding to the archive is 1, and the field corresponding to the document file in the archive is 1, when the electronic file is a document file, and it is the first electronic file whose file type is archive stored in the database, then the record id can be 1-1-1 (file type-file subcategory-storage sequence number). For another example, if the id field corresponding to the file is 2, and the field corresponding to the document in the file is 1, when the electronic file is a document file, and it is the first electronic file whose file type is document stored in the database, then the record id can be 2-1-1 (file type-file subcategory-storage sequence number).

[0086] S120. According to the file type table, define a content structure table corresponding to the corresponding file type.

[0087] In one implementation, the content structure table may include a preset field that is custom configured to correspond to the corresponding file type, and the preset field is used to define the field content that can be searched and displayed on the front-end query page.

[0088] In one implementation, the implementation process of step S120 may include the following steps:

[0089] S121. Define a type field corresponding to a corresponding file type in a file type table.

[0090] As an example, in the file type table, the file type table name may be defined as "f_type", and the type field of the file type may be defined as the field "id".

[0091] S122. Define a blank content structure table corresponding to the file type according to the type field.

[0092] It can be understood that, according to each file type defined in the file type table, a content structure table corresponding to the file type is defined. For example, if the file type has archives and files, then the blank content structure table can be a blank archive structure table and a blank file structure table.

[0093] In specific implementation, the blank content structure table may be defined with its corresponding table name. For example, the blank archive structure table may be defined with the table name "f_d_file+code", and the blank file structure table may be defined with the table name "f_e_file+code". Among them, code corresponds to the record id in the file type table.

[0094] S123: Obtain the preset field.

[0095] In one implementation, the preset field can be customized by the following configuration:

[0096] S123a. Open the structure editing page of the corresponding file type.

[0097] As an example, if the file type is archive, the structure editing page of the archive can be opened. If the file type is file, the structure editing page of the file can be opened.

[0098] S123b. Customize and configure default fields on the structure editing page, and save the default fields.

[0099] In specific implementation, the default field can be used to define the search field and list display field displayed by default on the front-end query page.

[0100] In specific implementation, the default field may include: field name, field comment, field type, field length, whether to display in the list, width in the list, whether it is a query item (i.e., the search field when the form is encapsulated), field query conditions (i.e., the query conditions encapsulated during background query), whether to display during editing, regular (i.e., the restrictions on field content input when the form is encapsulated), remarks (i.e., text prompts for the restrictions on field content input when the form is encapsulated), sorting (i.e., the order in which fields are displayed when the form is encapsulated) and element type (i.e., the form in which fields are displayed when the form is encapsulated) and other field information.

[0101] Exemplarily, the default fields may be as shown in Table 1 below.

[0102] Table 1

[0103]

[0104]

[0105] In specific implementation, the default fields corresponding to the document and the default fields corresponding to the archive can be configured the same or differently, and the present application embodiment does not limit this. In the present application embodiment, the default fields corresponding to the document and the default fields corresponding to the archive are configured the same as an example.

[0106] In the embodiment of the present application, by executing step S123b, the corresponding default fields can be customized according to different file types.

[0107] S123c. Obtain the preset field according to the default field.

[0108] It can be understood that the preset field is composed of the custom configured default fields.

[0109] In this embodiment, by executing steps S123a to S123c, the retrieval and display fields can be customized in the content structure table of the corresponding file type to define the retrieval and displayable field contents by default.

[0110] In another embodiment, the preset field can be obtained by custom configuration in the following manner:

[0111] S123A. Open the structure editing page of the corresponding file type.

[0112] In specific implementation, the implementation of step S123A is the same as or similar to the implementation of the above-mentioned step S123a, and the embodiment of the present application is not limited here.

[0113] S123B. Customize the default fields on the structure editing page and save the default fields.

[0114] In specific implementation, the implementation of step S123B is the same as or similar to the implementation of the above-mentioned step S123b, and the embodiment of the present application is not limited here.

[0115] In the embodiment of the present application, by executing step S123B, the corresponding default fields can be customized according to different file types.

[0116] S123C. In response to the user opening the front-end query page of the corresponding file type, dynamically encapsulate the form on the front-end query page to display the search fields and the list display fields.

[0117] In specific implementation, when the front-end query page of the corresponding file type is opened, the form can be dynamically encapsulated on the front-end query page to display the search fields and list display fields according to the set default fields.

[0118] S123D. In response to the user clicking on the personalized setting control on the front-end query page, a personalized setting page for the corresponding file type is displayed.

[0119] In specific implementation, the user can click on the personalized setting control (which can be displayed in the form of a virtual button) on the front-end query page to open the personalized setting page that displays the corresponding file type.

[0120] S123E. Receive the personalized fields customized by the user on the personalized setting page, and save the personalized fields.

[0121] In specific implementation, the personalized field can be obtained by personalizing the search field and the list display field in the default field. That is, on the personalized setting page, for the search field and the list display field, the user can configure which fields to display in the page list and which fields can be searched on the search conditions to obtain the personalized field.

[0122] S123F. Obtain the preset field according to the personalized field.

[0123] It can be understood that the preset field is composed of the personalized field.

[0124] In this embodiment, by executing steps S123A to S123F, the retrieval and display fields can be customized in the content structure table of the corresponding file type. In this process, different users can define the retrieval and display field content according to their own personalized needs. In this way, it is possible to facilitate the viewing and retrieval of paper file content and meet the personalized needs of different users.

[0125] That is, in step S123, when the user opens the front-end query page, it will read whether the user has saved the configuration information of the personalized field, and return the personalized field if yes, otherwise return the default field. After that, the front-end query page will dynamically encapsulate the form through the returned field content to display the list display field and the search field.

[0126] S124: Insert the preset field into the blank content structure table to obtain the content structure table.

[0127] In specific implementation, the backend interface may be called to insert the preset field into the blank content structure table to obtain the content structure table.

[0128] In an embodiment of the present application, by executing step S120, the field structure of different types of paper content can be stored through the corresponding content structure table, so that it is convenient to use the preset fields in the content structure table to encapsulate the search conditions and display content fields in a dynamic form, so that different types of paper documents can have different field contents.

[0129] That is, in the present application, the form can be dynamically encapsulated to display the paper document content fields to be displayed and retrieved based on the field information defined in the content structure table, such as whether the list is displayed, the width in the list, whether it is a query item, field query conditions, etc. Users can also personalize the paper document content fields to be displayed and retrieved according to their own needs. This not only facilitates the viewing and retrieval of paper document content, but also meets the personalized needs of different users.

[0130] S130: Dynamically generate a content entity table corresponding to the file type according to the preset fields in the content structure table.

[0131] For example, the archive entity table can be dynamically generated according to the preset fields in the archive structure table. Also, the file entity table can be dynamically generated according to the preset fields in the file structure table.

[0132] In one implementation, a content entity table of the corresponding file type may be dynamically generated based on fields such as the field name, field comment, field type, and field length in the preset field.

[0133] As an example, the table name of the archive entity table can be defined as "d_file+code". The table name of the file entity table can be defined as "e_file+code".

[0134] In the embodiment of the present application, by executing step S130, entity data of different types of paper document contents can be stored through the content entity table.

[0135] In an embodiment of the present application, through the above steps S110 to S130, corresponding fields of different types of paper document contents can be created through custom forms to define, generate and store field structures and entity data of different types of paper document contents.

[0136] That is, in the present application, corresponding content structure tables can be defined according to various file types, and then content entity tables of corresponding file types can be dynamically generated according to field information such as field names, field comments, field types, and field lengths defined in the content structure table. Then, dynamic forms can be encapsulated according to field information such as editable fields in the content structure table (including whether to display in the list, width in the list, whether it is a query item and field query conditions), regular expressions, remarks, sequences, and element types to store paper file contents, thereby realizing dynamic field generation and editing and storage of different types of paper files, avoiding the situation in traditional situations where only tables can be created in the database and fixed form fields can be used to store data, thereby improving the electronic conversion rate of paper files.

[0137] S140 , scanning the paper document to be archived, generating a target electronic file, and setting a target file type of the target electronic file.

[0138] In one embodiment, a document scanning system may be installed in the integrated machine, and the document scanning system may scan paper documents and generate electronic documents. The electronic documents may be image files or PDF files.

[0139] In one embodiment, the paper document to be archived can be scanned by the file scanning system to generate a target electronic file, and the target file type of the target electronic file can be set, such as archive or document. Specific file subcategories can also be set, such as document archives in archives.

[0140] In specific implementation, you can first set the file type and then scan the paper documents to be archived, or you can first scan the paper documents to be archived and then set the file type. This embodiment of the present application is not limited to this.

[0141] S150: Mount the target electronic file into the target content entity table to generate an entity table record.

[0142] In one implementation, the target content entity table corresponds to the target file type.

[0143] In one implementation, the target electronic file may be mounted into the target content entity table through an interface of the archive file management system to generate an entity table record.

[0144] S160: Read the target content structure table on the front-end query page, and generate an edit form page according to preset fields in the target content structure table.

[0145] In one implementation, the target content structure table corresponds to the target file type.

[0146] In one embodiment, the target file type of the target electronic file can be read on the front-end query page, and then the target content structure table is called according to the target file type. After that, the preset fields to be displayed during editing in the target content structure table are queried, and an edit form page is generated according to the preset fields. It can be understood that the preset fields are dynamically encapsulated and displayed through the edit form page.

[0147] S170: Enter the content of the target electronic file into the corresponding field on the edit form page, and save the entered file content into the target content entity table.

[0148] In one embodiment, the preset fields in the target content structure can be displayed on the edit form page. Afterwards, the relevant contents of the target electronic file can be entered into the corresponding fields in the preset fields on the edit form page, and then the entered file contents can be saved in the target content entity table to store the contents of the target electronic file.

[0149] S180: Associate the target content entity table with the target electronic file and store them in a database.

[0150] In a specific implementation, the target content entity table and the target electronic file are associated and stored in a database, so that the file content stored in the target content entity table can be associated with the target electronic file.

[0151] In an applicable scenario provided in the embodiment of the present application, combined with Figure 1 and Figure 2 As shown, after step S140, the method for accessing the paper document content provided by the embodiment of the present application may further include the following steps:

[0152] S150a, entering the relevant content of the target electronic file in the file storage system page according to the preset fields in the target content structure table.

[0153] S160a: Save the relevant content into the target content entity table.

[0154] S170a, upload the target electronic file, and associate the target content entity table with the target electronic file and store them in the database.

[0155] That is, in this applicable scenario, the relevant content of the target electronic file can be directly entered into the file storage system page according to the preset fields in the target content structure table without mounting.

[0156] In an embodiment of the present application, by executing steps S140-S180, or steps S1110-S140 and steps S150a-S170a, paper documents can be stored electronically through file scanning, mounting and entering, and the content of the paper documents can be matched with the electronic documents, which can facilitate the management of paper documents, the storage of paper document content and improve the efficiency of file retrieval. When there is an error in the file content, it can also facilitate tracing the source and compare and correct it with the corresponding electronic file.

[0157] In another applicable scenario provided by an embodiment of the present application, the target content entity table can be saved in Elasticsearch while being associated with the target electronic file and stored in a database. This can facilitate improving file retrieval efficiency when the amount of data is large.

[0158] In summary, the method for accessing paper document content provided in the embodiments of the present application can create corresponding fields for different types of paper document content through custom forms, and record the file content of paper documents through file scanning, mounting and entry, thereby realizing dynamic field generation and editing and storage of paper documents of different file types, facilitating the viewing and retrieval of file content, thereby realizing dynamic access to paper document content.

[0159] Figure 3FIG. 1 is a block diagram showing a structure of a device for accessing paper document content according to an embodiment of the present application. Figure 3 As shown, the device may include:

[0160] The processing unit 210 is used to create a file type table in the database through a custom form, the file type table is used to record the file type of each electronic file stored in the database; according to the file type table, define a content structure table corresponding to the corresponding file type, the content structure table includes a custom configuration corresponding to the corresponding file type preset field, the preset field is used to define the field content that can be searched and displayed on the front-end query page; according to the preset field in the content structure table, dynamically generate a content entity table corresponding to the file type;

[0161] A scanning unit 220 is used to scan a paper document to be archived, generate a target electronic document, and set a target file type for the target electronic document;

[0162] The access unit 230 is used to mount the target electronic file into the target content entity table and generate entity table records, wherein the target content entity table corresponds to the target file type; read the target content structure table on the front-end query page, and generate an edit form page according to the preset fields in the target content structure table, wherein the target content structure table corresponds to the target file type; enter the content of the target electronic file into the corresponding fields on the edit form page, and save the entered file content into the target content entity table; and associate the target content entity table with the target electronic file and store them in a database.

[0163] In one implementation, when the processing unit 210 is used to define a content structure table corresponding to a corresponding file type according to the file type table, it is specifically used to:

[0164] Define the type field corresponding to the corresponding file type in the file type table;

[0165] According to the type field, define a blank content structure table corresponding to the file type;

[0166] Get the preset fields;

[0167] Insert the preset fields into the blank content structure table to obtain the content structure table.

[0168] In one implementation, the preset fields are obtained by the processing unit 210 through custom configuration in the following manner:

[0169] Open the structure editing page of the corresponding file type;

[0170] Customize and configure default fields on the structure editing page and save the default fields. The default fields are used to define the search fields and list display fields that are displayed by default on the front-end query page.

[0171] Based on the default fields, get the preset fields.

[0172] In one implementation, the preset fields are obtained by the processing unit 210 through custom configuration in the following manner:

[0173] Open the structure editing page of the corresponding file type;

[0174] Customize and configure default fields on the structure editing page and save the default fields. The default fields are used to define the search fields and list display fields that are displayed by default on the front-end query page.

[0175] In response to the user opening the front-end query page of the corresponding file type, dynamically encapsulating the form on the front-end query page to display the search fields and the list display fields;

[0176] In response to a user clicking a personalized setting control on a front-end query page, displaying a personalized setting page for a corresponding file type;

[0177] Receive the personalized fields that the user has customized on the personalized settings page, and save the personalized fields, where the personalized fields are obtained by personalized configuration of the search fields and the list display fields;

[0178] Based on the personalized fields, get the preset fields.

[0179] In one embodiment, the preset fields include: field name, field comment, field type and field length; when the processing unit 210 is used to dynamically generate a content entity table of a corresponding file type according to the preset fields in the content structure table, it is specifically used to:

[0180] Based on the field name, field comment, field type and field length in the preset fields, a content entity table of the corresponding file type is dynamically generated.

[0181] In one implementation, the access unit 230 is further configured to:

[0182] According to the preset fields in the target content structure table, enter the relevant content of the target electronic file in the file storage system page;

[0183] Save the relevant content into the target content entity table;

[0184] Upload the target electronic file, and associate the target content entity table with the target electronic file and store them in the database.

[0185] In one implementation, the access unit 230 is further configured to:

[0186] The target content entity table is associated with the target electronic file and stored in the database, and the target content entity table is saved in Elasticsearch.

[0187] The functions of each unit in the device for accessing paper document content in the embodiment of the present application can refer to the corresponding description in the above method, and will not be repeated here.

[0188] Figure 4 FIG. 2 shows a block diagram of a computer device according to an embodiment of the present application. Figure 4 As shown, the computer device includes: a memory 310 and a processor 320. The memory 310 stores instructions, and the instructions are loaded and executed by the processor 320 to implement the method for accessing the paper document content in the above embodiment. The number of the memory 310 and the processor 320 can be one or more.

[0189] The computer device also includes:

[0190] The communication interface 330 is used to communicate with external devices and perform data exchange transmission.

[0191] If the memory 310, the processor 320 and the communication interface 330 are implemented independently, the memory 310, the processor 320 and the communication interface 330 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0192] Optionally, in a specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can communicate with each other through an internal interface.

[0193] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method provided in the embodiment of the present application is implemented.

[0194] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in a memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.

[0195] An embodiment of the present application also provides a chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0196] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.

[0197] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory, and may also include a non-volatile random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0198] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0199] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0200] In the description of the present application, “plurality” means two or more than two, unless otherwise clearly and specifically defined.

[0201] Any process or method description in the flow chart or otherwise described herein can be understood to represent a module, fragment or portion of a code including one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0202] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processor or other system that can fetch instructions from an instruction execution system, apparatus or device and execute instructions), or used in combination with these instruction execution systems, apparatuses or devices.

[0203] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0204] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0205] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for accessing the contents of a paper document, characterized in that: include: Creating a file type table in a database through a custom form, wherein the file type table is used to record the file type of each electronic file stored in the database; According to the file type table, a content structure table corresponding to the corresponding file type is defined, wherein the content structure table includes a preset field corresponding to the corresponding file type that is configured by a custom configuration, and the preset field is used to define the field content that can be searched and displayed on the front-end query page; Dynamically generate a content entity table corresponding to the file type according to the preset fields in the content structure table; Scan the paper document to be archived, generate a target electronic file, and set the target file type of the target electronic file; Mounting the target electronic file into a target content entity table to generate an entity table record, wherein the target content entity table corresponds to the target file type; Reading a target content structure table on the front-end query page, and generating an edit form page according to preset fields in the target content structure table, wherein the target content structure table corresponds to the target file type; Entering the content of the target electronic file into the corresponding field on the edit form page, and saving the entered file content into the target content entity table; The target content entity table is associated with the target electronic file and stored in the database.

2. The method according to claim 1, characterized in that According to the file type table, defining a content structure table corresponding to a corresponding file type includes: Define a type field corresponding to a corresponding file type in the file type table; According to the type field, define a blank content structure table corresponding to the file type; Obtaining the preset field; The preset field is inserted into the blank content structure table to obtain the content structure table.

3. The method according to claim 1, characterized in that The preset fields are obtained by custom configuration in the following way: Open the structure editing page of the corresponding file type; Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page; The preset field is obtained according to the default field.

4. The method according to claim 1, characterized in that: The preset fields are obtained by custom configuration in the following way: Open the structure editing page of the corresponding file type; Customize and configure default fields on the structure editing page and save the default fields, wherein the default fields are used to define the search fields and list display fields displayed by default on the front-end query page; In response to a user opening a front-end query page of a corresponding file type, dynamically encapsulating a form on the front-end query page to display the search field and the list display field; In response to a user clicking a personalized setting control on the front-end query page, displaying a personalized setting page for a corresponding file type; Receiving a personalized field that is customized and configured by a user on the personalized setting page, and saving the personalized field, wherein the personalized field is obtained by performing personalized configuration on the search field and the list display field; The preset field is obtained according to the personalized field.

5. The method according to claim 1, characterized in that The preset fields include: field name, field comment, field type and field length; according to the preset fields in the content structure table, dynamically generating a content entity table of the corresponding file type includes: According to the field name, field comment, field type and field length in the preset field, a content entity table of the corresponding file type is dynamically generated.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Entering relevant content of the target electronic file in the file storage system page according to the preset fields in the target content structure table; Saving the relevant content into the target content entity table; The target electronic file is uploaded, and the target content entity table is associated with the target electronic file and stored in a database.

7. The method according to claim 6, characterized in that The method further comprises: The target content entity table is associated with the target electronic file and stored in the database, and the target content entity table is saved in Elasticsearch.

8. A device for storing and accessing paper document content, characterized in that: include: The processing unit is used to create a file type table in a database through a custom form, wherein the file type table is used to record the file type of each electronic file stored in the database; based on the file type table, a content structure table corresponding to the corresponding file type is defined, wherein the content structure table includes a custom configured preset field corresponding to the corresponding file type, wherein the preset field is used to define the field content that can be retrieved and displayed on the front-end query page; based on the preset field in the content structure table, a content entity table corresponding to the file type is dynamically generated; A scanning unit, used for scanning a paper document to be archived, generating a target electronic document, and setting a target file type of the target electronic document; An access unit, used for mounting the target electronic file into a target content entity table to generate an entity table record, wherein the target content entity table corresponds to the target file type; The target content structure table is read on the front-end query page, and an edit form page is generated according to preset fields in the target content structure table, wherein the target content structure table corresponds to the target file type; the content of the target electronic file is entered into the corresponding field on the edit form page, and the entered file content is saved in the target content entity table; the target content entity table is associated with the target electronic file and stored in the database.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement the method according to any one of claims 1 to 7.

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

Images