System and method for collecting information of primary table and secondary table

Abstract

The invention discloses a master-sub table information collection system and method. The system comprises a table definition module used for defining parameter information of a main table; the permission configuration module is used for configuring permissions of the main table and the sub-table, so that a user enters the main table and the sub-table according to the configured permissions; the release configuration module is used for sharing the sub-table to a sub-table editing user according to the authority; the data collection module is used for transmitting frame content to the coordinate conversion module when each sub-table editing user edits the corresponding sub-table when the sub-table editing user edits the corresponding sub-table; the coordinate conversion module is used for determining a coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information in the main table cell, and synchronizing the information of each sub-table into the main table based on the information submission type of each sub-table and the coordinate conversion relationship; the version control module is used for generating main table version information and sub-table version information. According to the technical scheme, the security and accuracy of data sharing and collection processing of the online collaborative table can be ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of data collection and aggregation, and in particular to a master-subtable information collection system and method. Background Art

[0002] With the development of the Internet, the ways of collecting information are becoming more and more diverse. However, there is currently no good solution for collecting lower-level information within an organization and ensuring the security and reliability of the information.

[0003] Currently, the most common data collection method is online collaborative spreadsheets, where multiple users access and edit the spreadsheet collaboratively, filling in and collecting information. However, this approach allows the information to be viewed and modified at will by everyone who enters the spreadsheet. Users who submit information cannot guarantee its accuracy, and the information also presents serious reliability and security issues. Another approach is to set up viewing and editing areas within the spreadsheet, such as setting sections from row 1, column 1 to row 3, column 10 as viewable by some users and editable by others. This method of collecting information is very flexible, but manually maintaining viewing and editing permissions for specific users within a large spreadsheet is cumbersome for large groups, and cannot guarantee the security and accuracy of the information. Furthermore, this editing method also fails to address information reliability issues. Summary of the Invention

[0004] In view of this, the present invention provides a master-subtable information collection system and method, which can ensure the security and accuracy of data sharing and collection processing of online collaborative tables.

[0005] According to one aspect of the present invention, an embodiment of the present invention provides a master-subtable information collection system, wherein the master-subtable includes: a master table and at least two subtables; the master-subtable information collection system includes: a table definition module, a permission configuration module, a publishing configuration module, a data collection module, a coordinate conversion module, and a version control module;

[0006] The table definition module is used to define parameter information corresponding to the main table; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area;

[0007] The permission configuration module is used to configure the main table creator, main table manager and sub-table sharer corresponding to the main table, and the sub-table creator and sub-table manager corresponding to the sub-table, so that users can access the main table and the sub-table according to the configured permissions;

[0008] The publishing configuration module is used to configure the same header as the main table for each sub-table, and share the sub-table with the sub-table editing user according to the configured permissions; wherein, the rows where the sub-table header is located are not editable, and all rows except the sub-table header are editable;

[0009] The data collection module is configured to transmit, when each sub-table editing user edits a corresponding sub-table, the corresponding frame content of the sub-table editing user to the coordinate conversion module in a prescribed data frame format; wherein the frame content includes at least: coordinate information of the sub-table cell and the edit content corresponding to the coordinate information;

[0010] The coordinate conversion module is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type of each sub-table and the coordinate conversion relationship;

[0011] The version control module is used to generate main table version information corresponding to the main table and sub-table version information corresponding to each of the sub-tables.

[0012] According to one aspect of the present invention, an embodiment of the present invention provides a master-sub-table information collection method, which is applied to a master-sub-table information collection system. The method includes:

[0013] The parameter information corresponding to the main table is defined by a table definition module; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area;

[0014] The main table creator, main table manager and sub-table sharer corresponding to the main table and the sub-table creator and sub-table manager corresponding to the sub-table are configured through the permission configuration module, so that users can access the main table and the sub-table according to the configured permissions;

[0015] Configure the same header as the main table for each sub-table through the publishing configuration module, and share the sub-table to the sub-table editing user according to the configured permissions; wherein, the rows where the sub-table header is located are not editable, and all rows except the sub-table header are editable;

[0016] When each sub-table editing user edits a corresponding sub-table, the data collection module transmits the corresponding frame content of the sub-table editing user to the coordinate conversion module in a prescribed data frame format; wherein the frame content includes at least: coordinate information of the sub-table cell and the edit content corresponding to the coordinate information;

[0017] Determine, by means of a coordinate conversion module, a coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table into the main table based on the information submission type of each sub-table and the coordinate conversion relationship;

[0018] The version control module is used to generate first version information of the main table and second version information of each sub-table.

[0019] The technical effect of the present invention is that the table definition module is used to define the parameter information of the main table; the permission configuration module is used to configure the permissions of the main table and the sub-table, so that users can enter the main table and the sub-table according to the configured permissions; the publishing configuration module is used to share the sub-table to the sub-table editing user according to the permissions; the data collection module is used to transmit the frame content of the sub-table editing user when editing the corresponding sub-table to the coordinate conversion module when the sub-table editing user edits the corresponding sub-table; the coordinate conversion module is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information in the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type and coordinate conversion relationship of each sub-table; the version control module is used to generate main table version information and sub-table version information, which can meet more detailed business needs and improve the security and accuracy of data sharing and collection processing of online collaborative tables.

[0020] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 A schematic diagram of the architecture of a master-sub-table information collection system provided by one embodiment of the present invention;

[0023] Figure 2 A structural diagram of user permissions for a master-sub-table provided in one embodiment of the present invention;

[0024] Figure 3 A flow chart of "automatic synchronization" data collection provided by one embodiment of the present invention;

[0025] Figure 4 A flowchart of "commit-type synchronization" data collection provided by one embodiment of the present invention;

[0026] Figure 5 A schematic flow chart of a method for collecting master-sub-table information provided in one embodiment of the present invention;

[0027] Figure 6 This is a flowchart of another method for collecting master-subtable information provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] In one embodiment, Figure 1 This is a schematic diagram of the architecture of a master-sub-table information collection system provided by an embodiment of the present invention. This embodiment is applicable to situations where master-sub-table information is collected and summarized. Figure 1 As shown, the master-subtable includes: a master table and at least two subtables; the master-subtable information collection system in this embodiment includes: a table definition module 110, a permission configuration module 120, a publishing configuration module 130, a data collection module 140, a coordinate conversion module 150 and a version control module 160;

[0031] The table definition module 110 is used to define parameter information corresponding to the main table; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area;

[0032] The permission configuration module 120 is used to configure the main table creator, main table manager and sub-table sharer corresponding to the main table, and the sub-table creator and sub-table manager corresponding to the sub-table, so that users can access the main table and sub-table according to the configured permissions;

[0033] The publishing configuration module 130 is used to configure the same header as the main table for each sub-table and share the sub-table with the sub-table editing user according to the configured permissions; wherein, the rows containing the sub-table header are not editable, and all rows except the sub-table header are editable;

[0034] The data collection module 140 is configured to transmit, when each sub-table editing user edits a corresponding sub-table, the corresponding frame content of the sub-table editing user to the coordinate conversion module in a prescribed data frame format; wherein the frame content includes at least: the coordinate information of the sub-table cell and the edit content corresponding to the coordinate information;

[0035] A coordinate conversion module 150 is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type of each sub-table and the coordinate conversion relationship;

[0036] The version control module 160 is configured to generate main table version information corresponding to the main table and sub-table version information corresponding to each sub-table.

[0037] Among them, the editing content includes at least: the table name, row and column where the sub-table cell is located, the modified user information, and the modification timestamp; the information submission type includes: the information filled in each sub-table is automatically and synchronously submitted to the main table, and the information filled in each sub-table is submitted to the main table after receiving the submit instruction to be clicked.

[0038] In this embodiment, the table definition module 110 is used to define the parameter information corresponding to the main table; wherein the parameter information includes at least: a header, a header style, an information collection area style, and data verification rules corresponding to the information collection area. It can be understood that the module can specify the data rules for the header area and the area below the header of the main table, and verify whether the header area is set before the main table is shared and whether the content of the header area is correct. During the sub-table filling process, it is verified whether the content of the sub-table filling complies with the data verification rules to ensure that the main table collects accurate data. It should be noted that the data verification rules can include verification rules for text, numbers, dates, and drop-down boxes. It can be understood that the row and column are required items, and the row and column are optional items. They need to be filled in as required. If they are not filled in as required, they cannot be submitted. In this embodiment, the main table defines the header, style and data verification, and distributes sub-tables. Each sub-table is isolated from each other, ensuring the isolation and security of the collected data.

[0039] In this embodiment, the permission configuration module 120 is used to configure the main table creator, main table manager and sub-table sharer corresponding to the main table, and the sub-table creator and sub-table manager corresponding to the sub-table, so that users can enter the main table and sub-table according to the configured permissions. In this embodiment, the main table corresponds to the corresponding main table topic; the sub-table corresponds to the corresponding sub-table topic; the main table topic includes at least two sub-table topics. The main table creator manages the sub-tables corresponding to the main table; the editing user of each sub-table is automatically set as the sub-table creator; the creators of each sub-table cannot access the content edited in each sub-table. It can be understood that the permission configuration module 120 is used to set the creators, managers and sharers in the main table and sub-tables, and at the same time control the user's permissions to enter the main table and sub-tables. Specifically, when a user enters the main table and sub-table, the user's permissions must be determined first. The creator of the main table can set the administrator of the main table. The creator and administrator of the main table can enter the main table to view the information collected by the main table; the creator of the main table can set the sub-table sharing user and share the table as the main-sub-table. The sharing user is set to the sub-table creator by default; the creator of the main table can enter the sub-table corresponding to the main table to view the reporting status of the sub-table; the main table cannot be edited after being shared through the main-sub-table, because if the editor does not know which data is currently collected or edited by the main table, it will cause information confusion; the creator of the sub-table can continue to share the sub-table with other sub-table sharers for collaborative editing; the creator and administrator of the sub-table can add / delete sub-table administrators.

[0040] It can be understood that for the main table, only the main table creator and administrator can access the main table, while for the sub-table, the sub-table creator, administrator, sharer and main table creator can all access the sub-table. To better understand the permission configuration, Figure 2 A structural diagram of user rights of a master-sub-table provided by an embodiment of the present invention, such as Figure 2 As shown, each subtable has a corresponding subtable administrator, who can verify the correctness of the subtable's information. If correct, the subtable's information submission type is configured so that the information entered in the subtable is submitted to the main table after receiving the "Submit" indication. Clicking the Submit button submits the information entered in the subtable. If there are any issues, the information cannot be submitted. Furthermore, the subtable administrator has a main table creator under him. This creator can be a higher-level department and can access each subtable to check the progress of the corresponding subtable.

[0041] In this embodiment, by setting up flexible master-sub-table permission control, the master table creator can configure the master table administrator; after the master table is distributed into sub-tables, the sub-table sharing user is automatically set as the sub-table creator; the master table creator and administrator can view the sub-table content; the sub-table creators cannot access the content filled in each sub-table; this permission control ensures the flexibility of access to the master and sub-tables, while also ensuring the isolation of data between each sub-table.

[0042] In this embodiment, the publishing configuration module 130 is used to configure each sub-table with the same header as the main table and share the sub-table with the sub-table editing user according to the configured permissions. The rows containing the sub-table headers are non-editable, while all rows except the sub-table headers are editable. In this embodiment, after the main table creator shares the main table as a master-sub-table, each main table corresponds to multiple sub-tables, i.e., a 1-to-N relationship. A sub-table creator is assigned to each sub-table. Each sub-table copies the main table's header. The header and the row containing the header are non-modifiable, while other rows are editable. The main table cannot be edited, and only data can be collected.

[0043] In this embodiment, the data collection module 140 is used to transmit the corresponding frame content of the sub-table editing user to the coordinate conversion module through the prescribed data frame format when each sub-table editing user edits the corresponding sub-table; wherein the frame content at least includes: the coordinate information of the sub-table cell, and the corresponding editing content under the coordinate information. It should be noted that there are two ways to synchronize information of the main table: one is "automatic synchronization", that is, once the sub-table is filled in, the information is synchronized to the main table in real time; the other is "submit-type synchronization", that is, after the sub-table is filled in, the sub-table creator or administrator clicks the "Submit" button, and the sub-table information is automatically synchronized to the main table. In this embodiment, the default order of the main table displaying sub-table information is the order of the sub-table sharers selected when the main and sub-tables are shared; in the main table, each sub-table filled-in information is divided into areas using the sub-table id.

[0044] In this embodiment, the coordinate conversion module 150 is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type of each sub-table and the coordinate conversion relationship. In this embodiment, the coordinate information of the sub-table cell is converted to the coordinate information of the main table cell. Specifically, the coordinate conversion relationship is expressed by the formula: the row coordinate of the main table cell The total number of rows in sub-table i - (n-1) the number of table header rows + the sub-table cell row coordinate ri, where i represents the i-th sub-table; n represents a variable with a value range of 0 to i-1; the main table cell column coordinate ci = the sub-table cell column coordinate ci.

[0045] In this embodiment, the version control module 160 is used to generate master table version information corresponding to the master table and sub-table version information corresponding to each sub-table. This module is primarily used to generate version information for the master table and sub-tables. This module is divided into master table version control and sub-table version control. The master table version control summarizes the reporting records for each sub-table in chronological order. Master table creators and administrators can search for version records in the master table by reporting person, reporting time range, reporting cell coordinates, and other factors. Sub-table versions include a summary of sub-table edit records.

[0046] The above technical solution in this embodiment is used to define the parameter information of the main table through the table definition module; the permission configuration module is used to configure the permissions of the main table and the sub-table, so that users can enter the main table and the sub-table according to the configured permissions; the publishing configuration module is used to share the sub-table to the sub-table editing user according to the permissions; the data collection module is used to transmit the frame content of the sub-table editing user when editing the corresponding sub-table to the coordinate conversion module; the coordinate conversion module is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information in the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type and coordinate conversion relationship of each sub-table; the version control module is used to generate main table version information and sub-table version information, which can meet more detailed business needs and improve the security and accuracy of data sharing and collection processing of online collaborative tables.

[0047] In one embodiment, the table definition module includes: a table definition unit and a data verification unit;

[0048] The table definition unit is used to define the data rules of the header area and the area below the header of the main table;

[0049] The data verification unit is used to verify whether the header area is set before the main table is shared into various sub-tables and whether the content of the header area is correct. During the reporting process of each sub-table, it is also used to verify whether the reported content of each sub-table complies with the data verification rules.

[0050] In this embodiment, the table definition unit is used to define the data rules for the header area and the area below the header of the main table. The data verification unit is used to verify whether the header area is set before the main table is shared into each sub-table and whether the content of the header area is correct. During the reporting process of each sub-table, it is also used to verify whether the content of each sub-table complies with the data verification rules. For example, the data verification rules can be expressed in code as follows:

[0051] rules:{0:{ / / ci: column sequence, starting from 0; column 1

[0052] type:'text', / / Must be text, type supports text, numbers, dates, and drop-down box validation rules required:true, / / Is it required?

[0053] message:'The *th row and *th column are required' / / prompt message.

[0054] In one embodiment, the data collection module includes: a first data collection unit or a second data collection unit; the coordinate conversion module includes: a master-subtable coordinate conversion unit;

[0055] The first data collection unit is configured to receive the coordinate information of the sub-table cells modified by each sub-table and the edited content under the coordinate information, convert the coordinate information and the edited content under the coordinate information into corresponding frame content, and broadcast the frame content to the sub-table coordinate conversion unit;

[0056] a main-sub-table coordinate conversion unit, configured to convert the coordinate information of the sub-table cells in the sub-table coordinate system in the frame content into the coordinate information of the main-table cells in the main-table coordinate system according to the coordinate conversion relationship, so that the first data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs the coordinate conversion;

[0057] or,

[0058] The second data collection unit is configured to transmit the current frame content corresponding to the submission instruction to the sub-table coordinate conversion unit after receiving the submission instruction after the current frame content of each sub-table is correct;

[0059] The main-sub-table coordinate conversion unit is used to obtain the content of the previous frame submitted, compare the current frame content with the previous frame content, and convert the coordinate information of the sub-table cells under the sub-table coordinate system in the frame content where the content of the current frame content has changed into the coordinate information of the main table cells under the main table coordinate system, so that the second data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs the coordinate conversion.

[0060] In this embodiment, when the data collection module includes a first data collection unit, the first data collection unit is used to receive the coordinate information of the sub-table cells modified by each sub-table and the editing content under the coordinate information, form the coordinate information and the editing content under the coordinate information into corresponding frame content, and broadcast the frame content to the sub-table coordinate conversion unit; at this time, the main-sub-table coordinate conversion unit is used to convert the coordinate information of the sub-table cells under the sub-table coordinate system in the frame content into the coordinate information of the main table cells under the main table coordinate system based on the coordinate conversion relationship, so that the first data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs coordinate conversion.

[0061] In this embodiment, when the data collection module includes a second data collection unit, the second data collection unit is used to transmit the current frame content corresponding to the submission instruction to the sub-table coordinate conversion unit after receiving the submission instruction after the current frame content of each sub-table is correct; the main-sub-table coordinate conversion unit is used to obtain the submitted previous frame content, compare the current frame content with the previous frame content, and convert the coordinate information of the sub-table cell under the sub-table coordinate system in the frame content where the current frame content has changed into the coordinate information of the main table cell under the main table coordinate system, so that the second data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs the coordinate conversion.

[0062] For example, to better understand the logic of the sub-table coordinate conversion unit, the code example is as follows:

[0063] ri:1, / / row coordinates

[0064] ci:2, / / column coordinates

[0065] type:'modify_context', / / Modification type, including modify (modify content), delete (delete content), insert (insert content), etc.

[0066] before Change:'old value',

[0067] after Change:'new value',

[0068] style:{

[0069] color:'red'}

[0070] timestamp:'****' / / Timestamp.

[0071] This example supports two master table synchronization modes: automatic synchronization and commit-based synchronization. Automatic synchronization ensures real-time synchronization of sub-table and master table data; commit-based synchronization is suitable for scenarios where sub-table content requires specific personnel to review. This ensures multiple ways to synchronize master table data, adapting to a wider range of scenarios.

[0072] In one embodiment, to facilitate a better understanding of "auto-sync" data collection, Figure 3 This is a flow chart of "automatic synchronization" data collection provided by one embodiment of the present invention. Figure 3As shown, in the "auto-sync" scenario, the master table subscribes to the topics of each sub-table. Once a sub-table modifies a cell, the modified frame information is broadcast to the master-sub-table coordinate unit. The cell coordinates of the frame information are converted and merged into the master table data, which is then pushed to the user client. At this point, the client synchronizes all sub-table data in real time. The modified frame information can include the table name, row and column where the cell is located, the modifier, and the modification timestamp.

[0073] In another embodiment, to facilitate better "commit sync" data collection, Figure 4 This is a flow chart of a "submit type synchronization" data collection provided by an embodiment of the present invention. Figure 4 As shown in the figure, in the "submit-type synchronization" scenario, the master table also needs to subscribe to the topic of each sub-table. However, only after the sub-table creator or administrator confirms the sub-table content is correct and clicks the "Submit" button, and the "submit-type frame information" is generated, the master-sub-table coordinate conversion unit will process the coordinate conversion of the data between the previous "submit frame information" and the current "submit frame information", summarize this part of the content in the master table, and then push it to the master table client.

[0074] In one embodiment, the version control module includes: a main table version control unit and a sub-table version control unit;

[0075] The main table version control unit aggregates the reporting records of each sub-table in chronological order; the main table creator and the main table administrator search for version records in the main table according to the reporting person, reporting time range, and reporting cell coordinates;

[0076] The sub-table version control unit is used to summarize the edit records of each sub-table, where each edit record contains: changes to cell content, changes to cell style, and changed cell auxiliary information.

[0077] In one embodiment, changes to cell content include at least: modifying or deleting cell content; changes to cell style include at least: modifying cell background color and text color; and changes to cell auxiliary information include at least: the table name, row and column where the cell is located, information about the modifier, and modification timestamp.

[0078] In this embodiment, the main table version control unit summarizes the reporting records of each sub-table in chronological order; wherein, the main table creator and the main table administrator search for version records in the main table according to the reporter, reporting time range and reporting cell coordinates. It can be understood that the reporting records of each sub-table are summarized in chronological order; the main table creator and administrator can search for version records in the main table according to the reporter, reporting time range, reporting cell coordinates, etc.

[0079] In this embodiment, the sub-table version control unit is used to summarize the edit records of each sub-table, where each edit record includes: changes in cell content, changes in cell style, and changed cell auxiliary information. It can be understood that the edit records of the sub-table are summarized, where each edit record includes changes in cell content: such as modification and deletion of cell content, etc.; changes in cell style: such as modification of cell background color, text color, etc.; changed cell auxiliary information, such as the table name, row and column where the cell is located, information about the modifier, modification timestamp, etc.

[0080] In this embodiment, each sub-table records its own edit and submission records, and then summarizes the historical records into the main table, realizing comprehensive version records. This method ensures that users of each sub-table and the main table can view the source and history of the data, ensuring the correctness and integrity of the data, that is, summarizing the sub-table edit records into the main table records; the historical records can be viewed and searched, ensuring the correctness and integrity of each piece of data.

[0081] In one embodiment, Figure 5 This is a flow chart of a method for collecting master-sub-table information provided by an embodiment of the present invention. This embodiment is applicable to situations where master-sub-table information is collected and summarized. Figure 5 As shown, the method is applied to the master-sub-table information collection system described in any one of the embodiments of the present invention, and the method specifically includes the following steps:

[0082] S510. Define parameter information corresponding to the main table through a table definition module; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area.

[0083] S520 , configuring the main table creator, main table manager, and sub-table sharer corresponding to the main table and the sub-table creator and sub-table manager corresponding to the sub-table through the permission configuration module, so that users can access the main table and sub-table according to the configured permissions.

[0084] S530. Configure the same header as the main table for each sub-table through the publishing configuration module, and share the sub-table to the sub-table editing user according to the configured permissions; wherein, the rows where the sub-table header is located are not editable, and all rows except the sub-table header are editable.

[0085] S540. When each sub-table editing user edits the corresponding sub-table, the data collection module transmits the corresponding frame content when the sub-table editing user edits the corresponding sub-table to the coordinate conversion module through a prescribed data frame format; wherein the frame content at least includes: the coordinate information of the sub-table cell and the corresponding editing content under the coordinate information.

[0086] S550: Determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information in the main table cell through the coordinate conversion module, and synchronize the information of each sub-table to the main table based on the information submission type of each sub-table and the coordinate conversion relationship.

[0087] S360: Generate first version information of the main table and second version information of each sub-table through the version control module.

[0088] In one embodiment, to facilitate a better understanding of the master-subtable information collection method, Figure 6 A flowchart of another method for collecting information of a master-subtable provided in an embodiment of the present invention. In this embodiment, parameter information corresponding to the master table is defined; wherein the parameter information includes at least: a table header, a table header style, an information collection area style, and a data verification rule corresponding to the information collection area; the sub-table editing user of the sub-table to be shared is obtained, and the sub-table corresponding to the master table is shared with each of the sub-table editing users; the master table is verified according to the data verification rule, and if the verification passes, the main table header is copied as the sub-table header of the N sub-tables created; the edits of each sub-table editing user are received so that each sub-table editing user can edit the corresponding sub-table, determine the coordinate conversion relationship between the position information of each sub-table cell and the corresponding position information in the master table cell, and synchronize the information of each sub-table to the master table based on the information submission type of each sub-table and the coordinate conversion relationship.

[0089] like Figure 6 As shown, the specific steps are as follows:

[0090] a1. The master table creator defines the master table header, style, collection area style, and collection area data validation rules.

[0091] a2. The creator of the main table selects N (N>0) sharing users. After the selection is completed, the main table is shared in the form of master and sub-tables.

[0092] a3. The system verifies whether the main table's header, header style, collection area style, and collection area data verification rules meet the requirements. If so, the system automatically creates N sub-tables. If not, the main table creator redefines the main table's header, header style, collection area style, and collection area data verification rules.

[0093] a4. After the system creates N sub-tables, the sub-table headers are automatically generated based on the main table header. The rows where the sub-table headers are located are not editable, while all rows except the headers are editable.

[0094] a5. The default user for sharing a sub-table is the creator of the sub-table.

[0095] a6. The subtable creator can set the subtable as a "submit-type subtable". The default subtable is "auto-synchronization type".

[0096] a7. The subtable creator can share the subtable with other users for collaborative editing. Each subtable co-editor can edit the contents of the subtable except the header.

[0097] a8. After a sub-table is edited, the system determines whether it is a "submit-type sub-table". If it is, you must click the "Submit" button after editing the sub-table before the main table can synchronize the sub-table's contents. If the sub-table is not a "submit-type sub-table", the main table can automatically synchronize the sub-table's contents after editing the sub-table.

[0098] a9. The master table can synchronize not only the edited content of the sub-table, but also the edit and submission records of the sub-table. The master table creator or administrator can view and search the sub-table edit history to locate the author of the submitted information.

[0099] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0100] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A master-sub-table information collection system, characterized in that: The master-subtable includes: a master table and at least two subtables; the master-subtable information collection system includes: a table definition module, a permission configuration module, a publishing configuration module, a data collection module, a coordinate conversion module and a version control module; The table definition module is used to define parameter information corresponding to the main table; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area; The permission configuration module is used to configure the main table creator, main table manager and sub-table sharer corresponding to the main table, and the sub-table creator and sub-table manager corresponding to the sub-table, so that users can access the main table and the sub-table according to the configured permissions; The publishing configuration module is used to configure the same header as the main table for each sub-table, and share the sub-table with the sub-table editing user according to the configured permissions; wherein, the rows where the sub-table header is located are not editable, and all rows except the sub-table header are editable; The data collection module is configured to transmit, when each sub-table editing user edits a corresponding sub-table, the corresponding frame content of the sub-table editing user to the coordinate conversion module in a prescribed data frame format; wherein the frame content includes at least: coordinate information of the sub-table cell and the edit content corresponding to the coordinate information; The coordinate conversion module is used to determine the coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table to the main table based on the information submission type of each sub-table and the coordinate conversion relationship; The version control module is used to generate main table version information corresponding to the main table and sub-table version information corresponding to each of the sub-tables.

2. The system according to claim 1, wherein: The table definition module includes: a table definition unit and a data verification unit; The table definition unit is used to define data rules for the header area and the area below the header of the main table; The data verification unit is used to verify whether the main table is set with a header area before sharing it into each sub-table and whether the content of the header area is correct, and to verify whether the content of each sub-table complies with the data verification rules during the filling process of each sub-table.

3. The system according to claim 1, wherein: The editing content includes at least: the table name, row and column where the sub-table cell is located, modification user information, and modification timestamp; The information submission type includes: the information filled in each sub-table is automatically and synchronously submitted to the main table, and the information filled in each sub-table is submitted to the main table after receiving a submit instruction.

4. The system according to claim 3, characterized in that The data collection module includes: a first data collection unit or a second data collection unit; the coordinate conversion module includes: a master-subtable coordinate conversion unit; The first data collection unit is configured to receive the coordinate information of the sub-table cells modified by each sub-table and the edited content under the coordinate information, convert the coordinate information and the edited content under the coordinate information into corresponding frame content, and broadcast the frame content to the sub-table coordinate conversion unit; The main-sub-table coordinate conversion unit is configured to convert the coordinate information of the sub-table cells in the sub-table coordinate system in the frame content into the coordinate information of the main-table cells in the main-table coordinate system according to the coordinate conversion relationship, so that the first data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs the coordinate conversion; or, The second data collection unit is configured to, after receiving a submission instruction indicating that the current frame content of each sub-table is correct, transmit the current frame content corresponding to the submission instruction to the sub-table coordinate conversion unit; The main-sub-table coordinate conversion unit is used to obtain the content of the previous frame submitted, compare the current frame content with the previous frame content, and convert the coordinate information of the sub-table cells under the sub-table coordinate system in the frame content where the content of the current frame content has changed into the coordinate information of the main table cells under the main table coordinate system, so that the second data collection unit merges all the converted sub-table cells into the data of the main table after the main-sub-table coordinate conversion unit performs coordinate conversion.

5. The system according to claim 4, characterized in that The coordinate conversion relationship is expressed as follows: the row coordinates of the main table cell The total number of rows in subtable i - (n-1) the number of header rows + the row coordinate ri of the subtable cell, where i represents the i-th subtable; n represents a variable with a value range of 0 to i-1; The cell column coordinate ci of the main table = the cell column coordinate ci of the sub-table.

6. The system according to claim 1, wherein: The version control module includes: a main table version control unit and a sub-table version control unit; The master table version control unit aggregates the reporting records of each sub-table in chronological order; the master table creator and the master table administrator search for version records in the master table according to the reporting person, reporting time range, and reporting cell coordinates; The sub-table version control unit is used to summarize the editing records of each sub-table, wherein each editing record includes: changes in cell content, changes in cell style, and changed cell auxiliary information.

7. The system according to claim 6, characterized in that The change of the cell content includes at least: modifying or deleting the cell content; the change of the cell style includes at least: modifying the cell background color and text color; the changed cell auxiliary information includes at least: the table name, row and column where the cell is located, the modifier information, and the modification timestamp.

8. The system according to claim 1, wherein: The main table corresponds to the corresponding main table topic; the sub-table corresponds to the corresponding sub-table topic; the main table topic includes at least two sub-table topics.

9. The system according to claim 1, wherein: The main table creator manages the sub-tables corresponding to the main table; the sub-table editing user is automatically set as the sub-table creator; and the sub-table creators cannot access the edited content in each sub-table.

10. A method for collecting master-subtable information, characterized in that: The method applied to the master-sub-table information collection system according to any one of claims 1 to 9 includes: The parameter information corresponding to the main table is defined by a table definition module; wherein the parameter information at least includes: a table header, a table header style, an information collection area style, and data verification rules corresponding to the information collection area; The main table creator, main table manager and sub-table sharer corresponding to the main table and the sub-table creator and sub-table manager corresponding to the sub-table are configured through the permission configuration module, so that users can access the main table and the sub-table according to the configured permissions; Configure the same header as the main table for each sub-table through the publishing configuration module, and share the sub-table to the sub-table editing user according to the configured permissions; wherein, the rows where the sub-table header is located are not editable, and all rows except the sub-table header are editable; When each sub-table editing user edits a corresponding sub-table, the data collection module transmits the corresponding frame content of the sub-table editing user to the coordinate conversion module in a prescribed data frame format; wherein the frame content includes at least: coordinate information of the sub-table cell and the edit content corresponding to the coordinate information; Determine, by means of a coordinate conversion module, a coordinate conversion relationship between the coordinate information of each sub-table cell and the corresponding coordinate information of the main table cell, and synchronize the information of each sub-table into the main table based on the information submission type of each sub-table and the coordinate conversion relationship; The version control module is used to generate first version information of the main table and second version information of each sub-table.

Images