A method, device and medium for managing ledger documents

Abstract

This application discloses a method, device, and medium for managing ledger documents. The method includes: constructing ledger documents through online documents; generating a data mapping relationship between the ledger documents and database tables; wherein one ledger document corresponds to one database table; acquiring operation data from the online documents and storing the operation data in the ledger documents; and storing the operation data in the database tables through an asynchronous thread according to the data mapping relationship. Integrating ledger documents with online documents enables the business-oriented management of traditional ledger hosting systems. Editing of online documents is updated in real time, and operation data is saved to the ledger documents in real time. Simultaneously, operation data is asynchronously synchronized to the database, achieving asynchronous updates of database data, ensuring page response speed, enabling collaborative online editing of data, and achieving dual storage. This improves both the security and flexibility of ledger document management.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, device and medium for managing ledger documents. Background Technology

[0002] A ledger is a record of transactions or detailed information kept for a specific area of ​​business, designed to achieve refined management. Unlike financial vouchers, ledgers do not have the same strict requirements, standardized formats, or document specifications. Therefore, ledgers are a more personalized design, allowing for flexible design based on actual needs. In other words, ledger data has no fixed format.

[0003] Currently, the primary tool for creating ledgers is Excel, and ledger systems mainly manage Excel spreadsheets. However, simply providing ledger system hosting cannot meet the increasing business demands, resulting in low flexibility in ledger document management and failing to meet user needs. Summary of the Invention

[0004] This application provides a method, device, and medium for managing ledger documents, which addresses the problem that the low flexibility of ledger document management fails to meet user needs.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] On one hand, embodiments of this application provide a ledger document management method, which includes: constructing a ledger document through an online document; generating a data mapping relationship between the ledger document and a database table; wherein, one ledger document corresponds to one database table; obtaining operation data from the online document and storing the operation data in the ledger document; and storing the operation data in the database table through an asynchronous thread according to the data mapping relationship.

[0007] In one example, the construction of the ledger document from the online document specifically includes: determining the header area of ​​the online document; constructing corresponding header information in the header area; and storing the header information in the corresponding ledger document to construct the ledger document based on the header information.

[0008] In one example, generating the data mapping relationship between the ledger document and the database table specifically includes: when storing the header information to the corresponding ledger document, an asynchronous thread creates the database table corresponding to the ledger document; based on the header information, table fields of the database table are created; and the data mapping relationship between the header information and the table fields is constructed.

[0009] In one example, storing the operation data into the database table via an asynchronous thread according to the data mapping relationship specifically includes: if the operation data is record operation data, parsing the online document to obtain the header area of ​​the online document; distinguishing the header information and record data of the online document based on the header area; and storing the record data of the header information into the database table via an asynchronous thread according to the data mapping relationship.

[0010] In one example, storing the operation data in the database table via an asynchronous thread according to the data mapping relationship specifically includes: if the operation data is modified data, parsing the online document to obtain the header area of ​​the online document; determining the corresponding data table information to be modified by the operation data via an asynchronous thread based on the header information of the header area and the data mapping relationship, and clearing the corresponding data table information; and storing the operation data in the database table.

[0011] In one example, after storing the operation data in the database table via an asynchronous thread according to the data mapping relationship, the method further includes: obtaining a user's request to generate a new table through online documents; parsing the request to generate a new table to obtain the fields to be generated in the new table; identifying the stored tables related to the new table to be generated in the ledger document library; retrieving the stored fields that match the fields to be generated in the stored tables; and generating a new table based on the record data of the stored fields.

[0012] In one example, determining the stored tables related to the new table to be generated in the ledger document library specifically includes: retrieving tables that have a mapping relationship with the new table to be generated in a pre-built ledger document mapping table; matching the tables with the mapping relationship in the ledger document library to obtain matching stored tables; and determining the matching stored tables as stored tables related to the new table to be generated.

[0013] In one example, after storing the operation data in the database table via an asynchronous thread according to the data mapping relationship, the method further includes: obtaining a user's query request; parsing the query request to obtain the ledger document to be queried corresponding to the query request; retrieving corresponding data information in the ledger document to be queried according to the query request; determining whether the corresponding data information is retrieved; if not, retrieving the corresponding data information in the database table of the ledger document to be queried according to the query request.

[0014] On the other hand, embodiments of this application provide a ledger document management device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: construct a ledger document from an online document; generate a data mapping relationship between the ledger document and a database table; wherein one ledger document corresponds to one database table; acquire operation data from the online document and store the operation data in the ledger document; and store the operation data in the database table via an asynchronous thread according to the data mapping relationship.

[0015] On the other hand, embodiments of this application provide a non-volatile computer storage medium for ledger document management, storing computer-executable instructions, wherein the computer-executable instructions are configured to: construct ledger documents through online documents; generate a data mapping relationship between the ledger documents and database tables; wherein one ledger document corresponds to one database table; obtain operation data from the online documents and store the operation data in the ledger documents; and store the operation data in the database tables through an asynchronous thread according to the data mapping relationship.

[0016] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects:

[0017] Integrating ledger documents with online documents enables the business-oriented transformation of traditional ledger management systems. Online document editing is updated in real time, and operation data is saved to the ledger document in real time. At the same time, operation data is asynchronously synchronized to the database, enabling asynchronous updates of database data, ensuring page response speed, enabling collaborative online editing of data, and achieving dual storage, which is conducive to data traceability, backup, and prevention of data loss. This not only improves the security of ledger document management but also enhances its flexibility. Attached Figure Description

[0018] To more clearly illustrate the technical solution of this application, some embodiments of this application will be described in detail below with reference to the accompanying drawings, in which:

[0019] Figure 1 A schematic diagram of the framework of a ledger document management system provided in an embodiment of this application;

[0020] Figure 2 A flowchart illustrating a ledger document management method provided in this application embodiment;

[0021] Figure 3 This is a schematic diagram of the structure of a ledger document management device provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] Some embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0024] Figure 1 This is a schematic diagram of the framework of a ledger document management system provided in an embodiment of this application.

[0025] like Figure 1 As shown, the system includes a ledger system, online documents, and a database. The ledger system comprises a ledger document library and primarily manages ledger documents. The online documents store operational data in real-time within the ledger system. The online documents and database perform data synchronization, updates, queries, and data conversions. In other words, the ledger documents and online documents are integrated, enabling data exchange between the ledger documents and database tables. One ledger document corresponds to one online document, and one ledger document corresponds to one database table.

[0026] More intuitively, the specific integration method in the embodiments of this application will be achieved through... Figure 2 The methods and related content will be explained.

[0027] Figure 2 This is a flowchart illustrating a ledger document management method provided in this application embodiment. This method can be applied to different business areas, such as internet finance, e-commerce, instant messaging, gaming, and government affairs. Certain input parameters or intermediate results in this process can be manually adjusted to help improve accuracy.

[0028] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0029] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0030] Figure 2 The process may include the following steps:

[0031] S201: Build ledger documents using online documents.

[0032] In some embodiments of this application, the header area of ​​the online document is first determined, and then the corresponding header information is constructed within the header area. The header information is then stored in the corresponding ledger document to construct the ledger document based on the header information.

[0033] The header information includes document identifier, the location information of the cell containing the header, the text content of the cell containing the header, sheet page index, cell identifier, and text attributes.

[0034] In other words, based on the online spreadsheet, operators set the header area on the spreadsheet page, confirm the cell where the header is located, and then the front end sends the header information to the back end. This allows the creation of ledger documents based on the header information.

[0035] It should be noted that the front-end page needs to provide a button entry for setting the table header, guiding operators to make settings and determine the content and scope of the table header.

[0036] S202: Generate the data mapping relationship between the ledger document and the database table.

[0037] In some embodiments of this application, when storing header information to the corresponding ledger document, an asynchronous thread creates a database table corresponding to the ledger document, and then creates table fields for the database table based on the header information. Then, a data mapping relationship between the header information and the table fields is established.

[0038] In other words, when the header information is stored in the ledger document, an asynchronous thread creates a new database table and generates the database table fields based on the stored header information.

[0039] It should be noted that because database table fields have formatting requirements and do not allow duplicates, while ledger documents have no formatting requirements for header information, it is necessary to customize and generate database table fields based on the header information, and establish a mapping relationship between the database table fields and the ledger document headers to ensure that the database table fields meet the formatting requirements. This mapping relationship is one-to-one.

[0040] S203: Obtain the operation data of the online document and store the operation data in the ledger document.

[0041] S204: Based on the data mapping relationship, the operation data is stored in the database table via an asynchronous thread.

[0042] In some embodiments of this application, if the operation data is record operation data, the online document is parsed to obtain the header area of ​​the online document. Then, based on the header area, the header information and record data of the online document are distinguished. Then, according to the data mapping relationship, the record data of the header information is stored in the database table through an asynchronous thread, thereby realizing the asynchronous synchronization of the ledger document data to the database table.

[0043] If the data to be modified is to be parsed, the online document is parsed to obtain its header area. Then, based on the header information and data mapping relationship, an asynchronous thread determines the corresponding data table information to be modified, clears the corresponding data table information, and finally stores the data to be modified in the database table.

[0044] If the operation involves adding or deleting data, the online document is parsed to obtain its header area. Then, based on the mapping relationship between the header information and the data in the header area, the data table information is added or deleted via an asynchronous thread.

[0045] In other words, when operators perform add, delete, or modify operations on the online document page, the save mechanism is triggered, saving the document to the ledger document while simultaneously saving it to the corresponding database table in an asynchronous thread.

[0046] In some embodiments of this application, the integration method is combined with business logic, enabling the free combination to generate new tables.

[0047] Specifically, the process involves obtaining user requests to generate new tables through online documentation. These requests are then parsed to obtain the fields to be generated in the new table. Next, the stored tables related to the new table are identified in the ledger document library. Specifically, tables with mapping relationships to the new table are retrieved from a pre-built ledger document mapping table. These mapped tables are then matched against each other in the ledger document library to obtain the matching stored tables. Finally, the matching stored tables are determined as the only stored tables related to the new table to be generated.

[0048] Then, in the existing stored tables, retrieve the stored fields that match the field to be generated. Finally, generate the new table based on the record data of the stored fields.

[0049] For example, if a user wants to generate an Excel spreadsheet of student grades but doesn't want to manually enter student IDs, names, home addresses, and other records, they can select the student ID and name columns from an existing Excel file (e.g., a student list Excel file) and select the address column from a student contact information Excel file by matching the name, thus generating a new table, i.e., the student gradesheet.

[0050] In some embodiments of this application, the ledger document data is stored in duplicate, which facilitates data traceability and backup, prevents data loss, and improves data security.

[0051] Specifically, the process involves obtaining the user's query request. Then, the query request is parsed to obtain the corresponding ledger document to be queried. Next, the corresponding data information is retrieved from the ledger document based on the query request. Finally, it is determined whether the corresponding data information was found. If not, the corresponding data information is retrieved from the database table of the ledger document based on the query request.

[0052] It should be noted that if the corresponding data information can be retrieved, no further query will be performed on the database table.

[0053] In other words, if the corresponding data cannot be retrieved from the ledger document to be queried, it means that the data in the ledger document may be lost.

[0054] The query request enables functions such as data sharing and reuse between different ledger documents, as well as data flow and aggregation of the same ledger document between different departments.

[0055] It should be noted that data between ledger documents and databases can also be converted to each other, enabling data reuse and backup recovery.

[0056] It should be noted that, although the embodiments in this application are based on... Figure 2 Steps S201 to S204 will be described sequentially, but this does not mean that steps S201 to S204 must be performed in a strict order. The reason this embodiment follows this order is... Figure 2 The order in which steps S201 to S204 are described is provided to facilitate understanding of the technical solutions of the embodiments of this application by those skilled in the art. In other words, in the embodiments of this application, the order of steps S201 to S204 can be appropriately adjusted according to actual needs.

[0057] pass Figure 2 This method integrates ledger documents with online documents, enabling the business-oriented transformation of traditional ledger management systems. Online document editing is updated in real-time, and operation data is saved to the ledger document in real-time. Simultaneously, operation data is asynchronously synchronized to the database, achieving asynchronous updates of database data, ensuring page responsiveness, enabling collaborative online data editing, and providing dual storage for data traceability, backup, and prevention of data loss. This enhances both the security and flexibility of ledger document management.

[0058] Based on the same idea, some embodiments of this application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0059] Figure 3 A schematic diagram of a ledger document management device provided in this application embodiment includes:

[0060] At least one processor; and,

[0061] A memory communicatively connected to the at least one processor; wherein,

[0062] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0063] Build ledger documents using online documentation;

[0064] Generate a data mapping relationship between the ledger documents and database tables; wherein, one ledger document corresponds to one database table;

[0065] Obtain the operation data of the online document and store the operation data in the ledger document;

[0066] Based on the data mapping relationship, the operation data is stored in the database table via an asynchronous thread.

[0067] Some embodiments of this application provide a non-volatile computer storage medium for ledger document management, storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0068] Build ledger documents using online documentation;

[0069] Generate a data mapping relationship between the ledger documents and database tables; wherein, one ledger document corresponds to one database table;

[0070] Obtain the operation data of the online document and store the operation data in the ledger document;

[0071] Based on the data mapping relationship, the operation data is stored in the database table via an asynchronous thread.

[0072] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0073] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

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

[0075] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0076] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0077] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0078] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0079] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0080] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0081] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0082] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the technical principles of this application should fall within the protection scope of this application.

Claims

1. A method of managing a ledger document, characterized by, The method comprises: building an account document through an online document; generating a data mapping relationship between the account document and a database table; wherein one account document corresponds to one database table; obtaining operation data of the online document and storing the operation data into the account document; storing the operation data into the database table through an asynchronous thread according to the data mapping relationship; the building of the account document through the online document specifically comprises: determining a table header area of the online document; building corresponding table header information in the table header area; storing the table header information into the corresponding account document to build the account document according to the table header information; the generating of the data mapping relationship between the account document and the database table specifically comprises: when the table header information is stored into the corresponding account document, an asynchronous thread creates the database table corresponding to the account document; creating table fields of the database table according to the table header information; building a data mapping relationship between the table header information and the table fields; after the storing of the operation data into the database table through the asynchronous thread according to the data mapping relationship, the method further comprises: obtaining a new table generation request of a user through the online document; analyzing the new table generation request to obtain to-be-generated fields of a to-be-generated new table; determining a stored table related to the to-be-generated new table in an account document library; searching for stored fields matching the to-be-generated fields in the stored table; generating a new table according to record data of the stored fields; the determining of the stored table related to the to-be-generated new table in the account document library specifically comprises: searching for a table having a mapping relationship with the to-be-generated new table in a pre-built account document mapping table; matching the table having the mapping relationship in the account document library to obtain a matched stored table; determining the matched stored table as the stored table related to the to-be-generated new table.

2. The method of claim 1, wherein, the storing of the operation data into the database table through the asynchronous thread according to the data mapping relationship specifically comprises: if the operation data is record operation data, analyzing the online document to obtain a table header area of the online document; distinguishing table header information and record data of the online document based on the table header area; storing record data of the table header information into the database table through an asynchronous thread according to the data mapping relationship.

3. The method of claim 1, wherein, the storing of the operation data into the database table through the asynchronous thread according to the data mapping relationship specifically comprises: if the operation data is modification data, analyzing the online document to obtain a table header area of the online document; determining corresponding data table information to be modified by the operation data through an asynchronous thread according to table header information of the table header area and the data mapping relationship, and clearing the corresponding data table information; storing the operation data into the database table.

4. The method of claim 1, wherein, after the storing of the operation data into the database table through the asynchronous thread according to the data mapping relationship, the method further comprises: obtaining a query request of a user; The query request is parsed to obtain a to-be-queried account document corresponding to the query request; In the to-be-queried account document, corresponding data information is retrieved according to the query request; It is judged whether the corresponding data information is retrieved or not; If not, the corresponding data information is retrieved in a database table of the to-be-queried account document according to the query request.

5. A ledger document management apparatus, characterized by, Comprise: At least one processor; And, The memory is in communication connection with the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the account document management method of any one of claims 1-4.

6. A non-transitory computer storage medium storing computer-executable instructions that, when executed by a computer, perform a method comprising: The computer executable instructions are configured to execute the account document management method of any one of claims 1-4.

Images