CN112632928B - Table data processing method and device and computer readable storage medium - Google Patents

Table data processing method and device and computer readable storage medium Download PDF

Info

Publication number
CN112632928B
CN112632928B CN202010485914.7A CN202010485914A CN112632928B CN 112632928 B CN112632928 B CN 112632928B CN 202010485914 A CN202010485914 A CN 202010485914A CN 112632928 B CN112632928 B CN 112632928B
Authority
CN
China
Prior art keywords
data
collaboration
account
target
cell
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010485914.7A
Other languages
Chinese (zh)
Other versions
CN112632928A (en
Inventor
徐俏云
尹邵龙
秦银
彭康伟
鄢贤卿
熊飞
黄丽涵
于涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202010485914.7A priority Critical patent/CN112632928B/en
Priority to CN202111124081.2A priority patent/CN113779942B/en
Publication of CN112632928A publication Critical patent/CN112632928A/en
Application granted granted Critical
Publication of CN112632928B publication Critical patent/CN112632928B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Operations Research (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Bioethics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • Document Processing Apparatus (AREA)

Abstract

The application discloses a table data processing method, a device and a computer readable storage medium, wherein the method comprises the following steps: acquiring initial form data, and acquiring at least two collaboration accounts corresponding to the initial form data; responding to triggering operation aiming at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial table data to obtain target table data; and synchronizing the target form data to the cooperation terminals to which the at least two cooperation accounts belong, so that the cooperation terminals to which the at least two cooperation accounts belong respectively edit the corresponding permission cooperation areas in the target form data. By the aid of the method and the device, filling accuracy of target form data can be improved, and adding efficiency of the permission cooperation area is improved.

Description

Table data processing method and device and computer readable storage medium
Technical Field
The present application relates to the field of document data processing technologies, and in particular, to a method and an apparatus for processing table data, and a computer-readable storage medium.
Background
With the development of computer networks, there are more and more office-online matters, wherein matters involving the cooperation of a plurality of persons to complete the filling of forms are involved.
Typically, for a shared online form document, the online form document will typically have multiple filling out persons who will together complete the filling out for the online form document. When the multiple filling persons fill in the online form document, the multiple filling persons may all fill in the same row in the online form document, which may cause the content filled in the online form document by the following filling persons to cover the content filled in the online form document by the preceding filling persons, thereby causing a problem of data loss.
Therefore, in the prior art, when a plurality of persons complete the filling of the online form document together, filling errors are easily caused.
Disclosure of Invention
The application provides a form data processing method, a form data processing device and a computer-readable storage medium, which can improve filling accuracy of target form data, and simultaneously improve adding efficiency of authority cooperation areas due to the fact that corresponding authority cooperation areas can be added to a plurality of cooperation accounts in batches.
One aspect of the present application provides a table data processing method, including:
acquiring initial form data, and acquiring at least two collaboration accounts corresponding to the initial form data;
responding to triggering operation aiming at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial table data to obtain target table data;
and synchronizing the target form data to the cooperation terminals to which the at least two cooperation accounts belong, so that the cooperation terminals to which the at least two cooperation accounts belong respectively edit the corresponding permission cooperation areas in the target form data.
One aspect of the present application provides a table data processing apparatus, including:
the table acquisition module is used for acquiring initial table data and acquiring at least two collaboration accounts corresponding to the initial table data;
the region adding module is used for responding to triggering operation aiming at least two collaboration accounts, and adding a permission collaboration region for each of the at least two collaboration accounts in the initial table data to obtain target table data;
and the synchronization module is used for synchronizing the target form data to the collaboration terminals to which the at least two collaboration accounts belong so that the collaboration terminals to which the at least two collaboration accounts belong respectively edit the corresponding permission collaboration areas in the target form data.
Wherein the initial form data is created based on the document application;
a form acquisition module comprising:
a table acquisition unit for acquiring initial table data;
the batch response unit is used for responding to batch adding operation aiming at the initial form data in the document application and acquiring at least two communication accounts in the communication application;
the mapping account number obtaining unit is used for obtaining mapping document account numbers of at least two communication account numbers in the document application respectively;
and the account number determining unit is used for determining the mapping document account numbers corresponding to the at least two communication account numbers into at least two collaboration account numbers.
The communication application comprises a first communication application and a second communication application; the at least two communication accounts comprise a first communication account in the first communication application and a second communication account in the second communication application; the first communication account and the second communication account have account binding relation in the document application; the first communication account and the second communication account which have the account binding relationship correspond to the same mapping document account.
Wherein, the region adds the module, includes:
the quantity setting unit is used for acquiring the area quantity of each collaboration account aiming at the permission collaboration area;
the area adding unit is used for adding a corresponding permission collaboration area for each collaboration account in the initial table data according to the number of the areas corresponding to each collaboration account;
the mapping relation adding unit is used for adding the mapping relation between the account identification of each collaboration account and the corresponding permission collaboration area in the initial form data to obtain target form data; the mapping relation is used for indicating that each collaboration account number has the region editing authority of the affiliated authority collaboration region.
Wherein the at least two collaboration accounts comprise a collaboration account siWherein i is a positive integer less than or equal to the total number of the accounts of the at least two collaborative accounts, and the initial value of i is 1;
a region adding module further configured to:
in the initial table data, collaboration accounts s are arranged in sequenceiAnd adding the permission cooperation area until i is equal to the total number of the accounts, and obtaining target table data.
The at least two collaboration accounts comprise a first collaboration account;
the table data processing apparatus further includes:
the table expansion module is used for responding to the expansion operation of the first collaboration account on the target table data and expanding the target table data;
and the position positioning module is used for positioning the area position of the authority cooperation area corresponding to the first cooperation account in the expanded target table data and highlighting the authority cooperation area on the positioned area position.
Wherein, the target table data includes the header data, the table data processing device, still include:
the form output module is used for responding to form editing operation of a permission cooperation area corresponding to the first cooperation account, and outputting a form page corresponding to the first cooperation account according to header data of the target form data and the permission cooperation area corresponding to the first cooperation account;
the form entry module is used for responding to data entry operation aiming at the form page and acquiring form entry data;
and the data adding module is used for inputting the form into data and adding the data into the permission cooperation area corresponding to the first cooperation account in the target form data.
The permission collaboration area corresponding to the first collaboration account is a unit row in the target table data; the unit row corresponding to the first collaboration account number comprises an authority unit grid;
a form output module, comprising:
the existing data acquisition unit is used for acquiring existing data of cells in at least two target cells in the target table data; the target cell and the authority cell are cells in the same cell column; the data of the cells in the at least two target cells are data recorded in at least two target cells by the collaboration account numbers except the first collaboration account number in the at least two collaboration account numbers;
the cell determining unit is used for determining the target cells with the same cell existing data in at least two target cells as calling cells;
the form output unit is used for outputting a form page corresponding to the first collaboration account according to the existing cell data in the calling cells, the header data of the target form data and the permission collaboration area corresponding to the first collaboration account when the number of the calling cells is larger than the calling number threshold; and calling the existing data of the cells in the cells to be displayed in a data entry area in the form page.
The header data of the target table data comprises at least two unit table header data;
a form output module, comprising:
the format identification unit is used for acquiring data entry formats corresponding to the header data of at least two cells;
the format form output unit is used for outputting a form page corresponding to the first collaboration account according to the data entry format corresponding to the head data of each cell, the head data of each cell and the permission collaboration area corresponding to the first collaboration account; the form page comprises a data entry area corresponding to each unit form header data; and each data entry area in the form page is respectively provided with a data entry format corresponding to the head data of the corresponding cell.
Wherein, the format recognition unit includes:
the data type identification subunit is used for identifying the data type of the head data of each cell and determining a data entry format corresponding to the head data of each cell according to the data type of the head data of each cell; or
And the format acquisition unit is used for acquiring the target entry format added for the head data of each cell respectively as the data entry format corresponding to the head data of each cell respectively.
Wherein, the region adds the module, includes:
the transition acquisition unit is used for synchronously adding permission collaboration areas for at least two collaboration accounts in the initial table data to obtain transition table data corresponding to the at least two collaboration accounts;
a prompt output unit for outputting setting prompt information for the transition form data;
the prompt response unit is used for responding to the confirmation operation aiming at the set prompt information, setting a form editing function for the transition form data and obtaining target form data; the form editing function is used to trigger a form editing operation in the target form data.
Wherein, suggestion output unit includes:
the first entry response subunit is used for responding to data entry operation aiming at the cells in the transition table data and acquiring cell entry data;
the combined cell detection subunit is used for determining the target cell bar as a head cell bar when detecting that the transition table data comprises combined cells according to the cell entry data and the combined cells are in the target cell bar of the transition table data; the unit cells contained in the combined unit cells are adjacent unit cells which are not empty; the number of cells contained in the combined cells is greater than or equal to a first number threshold; the target cell bar is a cell row or a cell column at the starting position of the transition table data;
and the first prompt output subunit is used for outputting the setting prompt information aiming at the transition table data according to the position of the cell bar of the head cell bar.
Wherein, suggestion output unit includes:
the second entry response subunit is used for responding to data entry operation aiming at the cells in the transition table data and acquiring cell entry data;
the key cell detection subunit is used for determining the target cell bar as a header cell bar when the number of key cells in the target cell bar in the transition table data is detected to be greater than or equal to a second number threshold according to the cell entry data; the target cell bar is a cell row or a cell column at the starting position in the transition table data; the key cell is a cell which contains the table head key words and contains the non-table head key words of which the number is less than a third number threshold;
and the second prompt output subunit is used for outputting the setting prompt information aiming at the transition table data according to the position of the cell bar of the head cell bar.
Wherein the key cells are detected based on a keyword library; the keyword library comprises at least two table head keywords; at least two table head keywords are obtained by word segmentation of table head data in the historical table data.
Wherein, the table data processing device is further configured to:
responding to the editing operation of the first collaboration account aiming at the non-permission collaboration area in the target table data, and outputting prompt information without editing permission; the non-permission cooperation area refers to a permission cooperation area in the target table data except for the permission cooperation area corresponding to the first cooperation account.
The at least two collaboration accounts comprise a second collaboration account; the table data processing device is further used for:
and adding a newly-added region authority for the second collaboration account, and synchronizing the newly-added region authority to the collaboration terminal to which the second collaboration account belongs, so that the collaboration terminal to which the second collaboration account belongs adds a corresponding authority collaboration region for the newly-added collaboration account in the target form data according to the newly-added region authority.
An aspect of the application provides a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform a method as in an aspect of the application.
An aspect of the application provides a computer-readable storage medium having stored thereon a computer program comprising program instructions which, when executed by a processor, cause the processor to perform a method of an aspect.
The method includes the steps that initial form data are obtained, and at least two collaboration accounts corresponding to the initial form data are obtained; responding to triggering operation aiming at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial table data to obtain target table data; and synchronizing the target form data to the cooperation terminals to which the at least two cooperation accounts belong, so that the cooperation terminals to which the at least two cooperation accounts belong respectively edit the corresponding permission cooperation areas in the target form data. Therefore, by the method, the permission cooperation areas of at least two cooperation accounts can be added in place in one step in the initial form data, and the adding efficiency of the permission cooperation areas is improved. Meanwhile, each cooperation account number is respectively allocated with a corresponding authority cooperation area, and each cooperation account number can edit the authority cooperation area belonging to the cooperation account number in the target form data, so that the filling accuracy of the target form data is improved.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a system architecture provided herein;
FIG. 2a is a schematic diagram of a scenario of table data processing provided in the present application;
FIG. 2b is a diagram illustrating a table data processing scenario provided herein;
FIG. 3 is a flow chart of a table data processing method provided by the present application;
FIG. 4a is a schematic page diagram of a terminal page provided in the present application;
FIG. 4b is a schematic page diagram of a terminal page provided in the present application;
FIG. 5a is a schematic page diagram of a terminal page provided in the present application;
FIG. 5b is a schematic diagram of a terminal page for form editing provided by the present application;
FIG. 5c is a schematic page diagram of a terminal page provided in the present application;
FIG. 6 is a schematic diagram of a terminal page of data recommendation provided by the present application;
FIG. 7 is a schematic page diagram of a terminal page provided in the present application;
FIG. 8 is a page view of a form page provided herein;
FIG. 9 is a schematic diagram illustrating a scenario for acquiring a header cell bar according to the present application;
FIG. 10 is a flow chart illustrating a method of form generation provided herein;
FIG. 11a is a flowchart illustrating a method for obtaining a keyword library according to the present application;
FIG. 11b is a schematic flow chart of a key cell detection method provided herein;
FIG. 11c is a schematic flow chart of an intelligent recommendation method provided herein;
FIG. 12 is a schematic flow chart diagram illustrating a region adding method provided herein;
FIG. 13 is a flow chart illustrating a method for processing tabular data provided herein;
FIG. 14 is a framework diagram of a technical framework provided by the present application;
FIG. 15 is a schematic diagram of a table data processing apparatus provided in the present application;
fig. 16 is a schematic structural diagram of a computer device provided in the present application.
Detailed Description
The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Please refer to fig. 1, which is a schematic diagram of a system architecture provided in the present application. As shown in fig. 1, the system architecture diagram may include a plurality of terminal devices including a terminal device 200a, a terminal device 200b, and a terminal device 200c, and a server 100. Among them, the terminal device 200a, the terminal device 200b, and the terminal device 200c can communicate with the server 100 each other. The terminal device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a virtual device, or a wearable device (e.g., a smart watch, a smart bracelet, etc.), and the like. The description of the present application is made by taking the communication between the terminal device 200a and the server 100 as an example, and please refer to the following procedure.
Referring to fig. 2a and fig. 2b, fig. 2a is a schematic view of a scenario of table data processing provided by the present application, and fig. 2b is a schematic view of a scenario of table data processing provided by the present application. As shown in fig. 2a, a document application or a search engine (e.g. a browser) capable of opening a web page may be installed in the terminal device 200a, the terminal page 121a is a terminal page in the terminal device 200a, the terminal page 121a may be an application page in the installed document application, or may be a web application page of the document application opened in the search engine. As shown in the terminal page 121a, a form document having a document name of "personal information collection" has been created in the terminal page 121a, and header contents including "name", "school number", "class", "telephone number", "home address", and "identification number" have been added in the first line in the form document. The header content may also be referred to as header data.
Furthermore, a control 100a is further provided in the terminal page 121a, where the control 100a is used to add corresponding permission collaboration areas to collaborators of the tabular document in batches, and a permission collaboration area corresponding to a collaborator may be one column, multiple columns, one row or multiple rows in the tabular document. Collaborators of a form document refer to the filling out person of the form document, which may be multiple, in this application multiple refers to at least two. The method specifically comprises the following steps: the terminal device 200a may display the terminal page 122a in response to a click operation of the user with respect to the control 100a in the terminal page 121 a. It is understood that the control 100a may be triggered by a voice command instead of a click operation, which is not limited to this. The terminal page 122a has one more selection box 101a than the terminal page 121a, and the selection box 101a includes an option "filling person for specified row" and an option "filling person for specified column". Wherein, the appointed row filling person indicates that the authority collaboration area added for each collaborator is one or more rows in the form document. And specifying column filling persons, wherein the authority collaboration area added for each collaborator is one column or multiple columns in the form document. The description of the present application is made here by taking the specified row fill-in person as an example.
The terminal device 200a may display the terminal page 123a in response to a user's click operation for the option "specify row writer" in the selection box 101 a. As shown in the terminal page 123a, the terminal page 123a adds the column 102a compared to the terminal page 122 a. The added column 102a is the column preceding the header content in the table document. That is, the terminal device 200a adds the column 102a at the 1 st column (i.e., column a) of the form document by responding to the user's clicking operation on the option "specify row writer" in the selection box 101 a.
Corresponding collaborators can be added to each row in the table document through the column 102a, for example, the position of the 2 nd row in the column 102a includes "small red (example)", which indicates that the 2 nd row of the table document can only be edited by small red, and other people can not edit the 2 nd row of the table document. Also included in column 102a are a plurality of "add filler" controls, each row being assigned to a respective collaborator by each "add filler" control in column 102 a.
Here, the terminal device 200a may display the terminal page 124a in response to a user's click operation on the "add filler" control 103a in the column 102a, the control 103a being in row 3 in the column 102 a. The terminal page 124a has more pages 104a than the terminal page 123a, and it is understood that the page 104a may be a popup window or a sub-page independently displayed on the terminal page 123 a. A search box 112a, an area 111a, and a "batch add writer" control 105a are included in the page 104 a. Wherein, the search box 112a is used to support that the user can search for collaborators corresponding to row 3. If the document account logged in the document application of the terminal device 200a is the document account of the target user, the search box 112a may be configured to support the target user to search the corresponding friend in the address book of the document account of the target user as a collaborator in row 3, where the document application of the terminal device 200a may be a document application installed in the terminal device 200a, or a document application entered in a search engine of the terminal device 200 a. The user displayed in the area 111a is a friend in the address book of the document account of the target user, and the friend searched by the user through the search box 112a may also be displayed in the area 111 a. The terminal device 200a may take the selected friend as a collaborator in the current row in response to the user's selection operation for the friend in the area 111 a. The terminal device 200a may acquire the friend selected by the user through the search box 112a or the area 111a, and use the friend as a collaborator in row 3, so as to add a corresponding collaborator for each row in the form document row by row.
In addition, the "add fill in bulk" control 105a in page 104a may be used to add corresponding rights collaboration areas for multiple collaborators in a form document at once. The terminal device 200a may display the terminal page 125a in response to a user clicking operation on the control 105 a. The terminal page 125a is added with one more page 106a than the terminal page 124a, and the page 106a may be a sub-page independently displayed on the terminal page 124 a. Supporting the target user, selecting a plurality of collaborators for the form document in the terminal page 124a, specifically: supporting the target user to search the friends in the address book as collaborators of the form document in the search box 120 a; or, the area 113a displays the friends in the address list of the document account of the target user, which total 32 friends, supports the target user to slide up and down in the area 113a to find more friends in the document account, and supports the target user to select one or more friends from the friends displayed in the area 113a as collaborators of the form document; alternatively, the terminal device 200a may respond to the click operation of the target user on the "invite friend" control 107a in the page 106a, start the third-party application, and invite friends in the address book of the third-party application as collaborators of the form document. The third-party application is an application different from the document application, and the third-party application may be an instant messaging application or multiple third-party applications. And supporting the target user to invite friends in the address book of different third-party applications as collaborators of the form document.
All collaborators selected by the target user, including 13 collaborators such as user "day", user "music", user "flowers" and user "flowers" are displayed in the area 110a in the page 106a, enabling the target user to slide up and down in the area 110a to see more collaborators selected. When the target user completes the collaborator selection on the form document in the page 106a, the terminal device 200a may add a permission collaboration area, which is referred to herein as a permission collaboration area editable by each collaborator, to each selected collaborator in the form document in sequence in response to the target user's selection operation on the "send work form to the other party" control 108a in the page 106a and in response to the target user's click operation on the "complete" control 109a in the page 106 a. After the addition of the authority collaboration area of each collaborator is completed, the terminal device 200a may display the terminal page 126a, and the form document displayed in the terminal page 126a is the form document whose creation is completed. Since the terminal device 200a may detect that the target user has previously selected the "send work form to partner" control 108a in the page 106a, the terminal device 200a may send the created form document to each collaborator, which may be a document account held by each collaborator, respectively.
As shown in the terminal page 126a, the created form document displayed in the terminal page 126a includes the header content and the right collaboration area corresponding to each added collaborator, and the form document sent by the terminal device 200a to each collaborator is the form document displayed in the terminal page 126 a. Since the specified writer of line 2 (i.e., collaborator, i.e., pinkish red (example)) displayed in the terminal page 124a is the example given by the document application, and not the collaborator added by the target user, when the form document in the terminal page 126a is generated, the example given by the document application is automatically deleted, i.e., the collaborator "pinkish red (example)" is deleted, and the right collaboration area is added for each selected collaborator separately from line 2. As shown in a terminal page 126a, a permission cooperation area 115a is added for the collaborator "day and day", and the permission cooperation area 115a is a 2 nd row in the created form document, which indicates that only the collaborator "day and day" has editing permission for the 2 nd row; a permission collaboration area 116a is added for the collaborator "music", and the permission collaboration area 116a is the 3 rd row in the created form document, which indicates that only the collaborator "music" has editing permission for the 3 rd row; an authority collaboration area 117a is added to the collaborator "duo", and the authority collaboration area 117a is the 4 th row in the created form document, which indicates that only the collaborator "duo" has editing authority for the 4 th row; a permission collaboration area 118a is added for the collaborator 'flower', and the permission collaboration area 118a is the 5 th row in the created form document, which indicates that only the collaborator 'flower' has editing permission for the 5 th row; a rights collaboration area 119a is added for the collaborator "cocoa", the rights collaboration area 119a being line 6 in the created form document, indicating that only the collaborator "cocoa" has editing rights for line 6, … ….
The server 100 is a background server of the document application, and when the terminal device 200a responds to the user operation of the target user to generate the form document in the terminal page 126a, the terminal device 200a sends a corresponding operation instruction generated by responding to the user operation of the target user to the server 100, so that the server 100 can generate the corresponding form document according to the acquired operation instruction. When the server 100 completes generation of the corresponding form document, the server 100 may transmit the generated form document to the terminal device 200a, and the terminal device 200a may display the acquired form document, for example, the form document displayed in the terminal page 121a, the terminal page 123a, and the terminal page 126a described above. In other words, the form document displayed by the terminal device 200a is generated by the server 100. More specifically, when the terminal device 200a sends the created form data to each collaborator, the terminal device 200a may send a related operation instruction to the server 100, and the server 100 sends the created form document to the document account of each collaborator according to the operation instruction.
Alternatively, the terminal device 200a may also independently generate a form document and send the created form document to the document account of each collaborator. In other words, the terminal device 200a may generate a corresponding form document without passing through the server 100 and transmit the created form document to the document account of each collaborator. Therefore, the executing entity of the document account for generating the corresponding form document and sending the created form document to the collaborator may be the server 100 or the terminal device 200a, which is determined according to the actual application scenario, and is not limited thereto.
By adopting the method provided by the application, the corresponding permission cooperation areas can be synchronously added to the selected multiple collaborators in the form document, so that the user operation is simplified, and the efficiency of adding the permission cooperation areas to the multiple collaborators in the form document is improved.
Please refer to fig. 3, which is a flowchart illustrating a table data processing method provided in the present application, and as shown in fig. 3, the method may include:
step S101, acquiring initial form data, and acquiring at least two collaboration accounts corresponding to the initial form data;
specifically, the execution subject in this embodiment may be any terminal device. Here, the target terminal device is described as an example of the execution subject in the present embodiment. The target terminal device may have installed therein a document application, which is an application that can generate and edit a form document. Suppose that the target terminal device is held by the target user, and a document account registered by the target user in the document application is logged in the document application installed in the target terminal device. The target terminal device may respond to a user operation of the target user, and generate the initial form data in the document application, where the initial form data is generated to be empty, that is, no content is added. In other words, the initial table data is the empty table data generated.
Optionally, the initial table data may also be a table data imported into the target terminal device by the target user, in other words, the initial table data may not be empty.
Next, the target terminal device may obtain at least two collaboration accounts corresponding to the initial form data in response to a batch addition operation of the target user on the initial form data, where a button of a batch addition collaborator may be provided in the document application, and the batch addition operation may refer to a click operation of the target user on the button of the batch addition collaborator, for example, the click operation described above with respect to the "batch addition writer" button 105a in fig. 2 b. The acquisition sources of the at least two collaboration accounts of the initial form data may be:
the target terminal device can respond to batch adding operation of the target user for the initial form data, obtain a plurality of contacts in an address book of a document account of the target user, and take the document accounts to which the contacts belong as at least two collaboration accounts of the initial form data.
Or, the target terminal device may also respond to a batch adding operation of the target user for the initial form data, and jump from the document application to the third-party application, and because the user account of the target user is logged in the third-party application, the target terminal device may obtain a plurality of contacts of the target user in an address book of the third-party application, and take the document accounts of the plurality of contacts corresponding to the document application as at least two collaboration accounts of the initial form data. In this case, a plurality of contacts acquired from the address book of the third-party application need to register corresponding document accounts in the document application through the user accounts in the third-party application. In other words, at least two collaboration accounts corresponding to the initial form data are document accounts in the document application. For example, it is assumed that the plurality of contacts acquired by the target terminal device in the third-party application include contact music, and at this time, equivalent to acquiring the user account of the contact music in the third-party application, the document account corresponding to the user account of the contact music in the third-party application may be used as the collaboration account of the initial form data. The document account corresponding to the user account of the contact music in the third-party application is the document account obtained by registering the user account of the contact music in the third-party application in the document application.
The third-party application may refer to a communication application, the communication application may be an instant communication application, and a user account of the user in the third-party application may be referred to as a communication account. Therefore, the acquiring of the multiple contacts of the target user in the address book of the third-party application means acquiring multiple communication accounts corresponding to the multiple contacts of the target user in the address book of the third-party application. The document account obtained by mapping and registering in the document application by using the communication account of the user in the communication application can be called as a mapped document account. A plurality of mapping document accounts corresponding to the plurality of communication accounts acquired in the communication application may be used as a plurality of collaboration accounts of the initial table data.
Furthermore, there may be a plurality of third-party applications, for example, two third-party applications, where the two third-party applications are the first communication application and the second communication application. If the first communication account registered in the first communication application and the second communication account registered in the second communication application have an account binding relationship in the document application, the first communication account and the second communication account correspond to the same mapping document account in the document application. Therefore, if the target user selects the mapping document account corresponding to the first communication account and the second communication account as the collaboration account of the initial table data at the same time, only the same mapping document account corresponding to the first communication account and the second communication account can be obtained, and this way, the situation that the corresponding permission collaboration area is repeatedly added to the collaboration account of the same collaborator can be avoided.
The multiple collaboration accounts of the initial form data may only include the document accounts of the contacts in the address list of the document account of the target user; or only including the document account of the contact person of the target user in the address book of the third-party application; or the document account of the contact in the address list of the document account of the target user is included, and the document account of the contact of the target user in the address list of the third-party application is also included; and if the plurality of third-party applications exist, the plurality of collaboration accounts of the initial form data can also simultaneously comprise document accounts of contacts of the target user in address lists of different third-party applications.
Step S102, responding to trigger operation aiming at least two collaboration accounts, and adding an authority collaboration area for each of the at least two collaboration accounts in the initial form data to obtain target form data;
specifically, after acquiring the multiple collaboration accounts of the initial form data, the target terminal device may respond to a trigger operation of the target user for the multiple collaboration accounts, and add a corresponding permission collaboration area to each collaboration account in the initial form data, so as to obtain the target form data. Wherein the trigger operation may refer to the click operation described above with respect to the "done" control 109a in fig. 2 b. In the initial table data, the process of adding the permission collaboration area to each collaboration account respectively may be: a random sequence can be determined among a plurality of collaboration accounts of the initial form data, and a corresponding permission collaboration area can be added to each collaboration account in the initial form data in sequence according to the random sequence; or, according to the selection sequence of the target user for the multiple collaboration accounts, a corresponding permission collaboration area may be sequentially added to each collaboration account in the initial table data, and a previously selected collaboration account is preferentially generated. The permission collaboration area added by one collaboration account in the initial table data can be one column, one row, multiple rows or multiple columns.
The collaboration account may be denoted as a collaboration account siI is a positive integer less than or equal to the total number of accounts of the collaboration account of the initial table data, and the initial value of i is 1. The total number of the cooperative accounts can be recorded as n, i is greater than or equal to 1 and less than or equal to n, and n cooperative accounts are provided. May take 1 from i, i.e. the collaboration account number s1At the beginning, the collaboration accounts s are arranged in the initial table dataiAdding a corresponding permission collaboration area, and adding 1 to the current i each time until the final i is equal to n, namely indicating that the current i is a collaboration account s1And a collaboration account number s2… … and collaboration account number snA corresponding rights collaboration zone is added.
The target terminal device adds a corresponding permission collaboration area for each collaboration account in the initial form data, and may also complete the addition through a background server (hereinafter referred to as a server) of the document application. The terminal device can synchronize a plurality of collaboration accounts selected by the user to the server, and the server can add corresponding permission collaboration areas to each collaboration account in sequence, after the addition is completed. The server can synchronize the permission cooperation area corresponding to each cooperation account to the target terminal device, and the target terminal device can correspondingly generate the permission cooperation area corresponding to each cooperation account in the terminal page according to the permission cooperation area corresponding to each cooperation account acquired from the server.
More, after the target terminal device obtains the multiple collaboration accounts selected by the target user for the initial form data, the target user is further supported to set the corresponding area number for each collaboration account. One row in the table data may be referred to as a cell row, and one column may be referred to as a cell column. If a corresponding permission collaboration area is added to each collaboration account according to the "row", one permission collaboration area may refer to one row, and the number of areas is also the number of rows of a unit, and the number of areas corresponding to each collaboration account is that the number of areas of the permission collaboration area that needs to be added to each collaboration account, that is, the number of rows of a unit row that needs to be added to each collaboration account, is indicated. If a corresponding permission cooperation area is added to each cooperation account according to a column, one permission cooperation area may refer to one column, and the number of areas is also the number of columns of unit columns. More, a default value of the number of the areas corresponding to each collaboration account may also be set, where the default value may be 1, and the like. If the target terminal device obtains the number of the areas set by the target user for the collaboration account, the target terminal device may add a corresponding permission collaboration area for the collaboration account in the initial table data according to the number of the areas set by the target user for the collaboration account, and the number of rows of a unit row or the number of columns of a unit column in the permission collaboration area added by the collaboration account in the initial table data is the number of the areas corresponding to the collaboration account. If the target terminal device does not acquire the number of the areas set for the collaboration account by the target user, the target terminal device may add a corresponding permission collaboration area to the collaboration account according to a default value of the number of the areas. The method and the device support that the target user sets the corresponding area number for each collaboration account of the initial table data, or sets the corresponding area number for part of collaboration accounts of the initial table data, or does not need to add the corresponding area number to any collaboration account of the multiple collaboration accounts.
After the corresponding permission collaboration area is added to each collaboration account in the initial table data, an account identifier (i.e., an account ID) of each collaboration account needs to be bound to a corresponding area identifier (i.e., an area ID) of the permission collaboration area, which can be understood as a mapping relationship between the account identifier added with the collaboration account and the corresponding area identifier of the permission collaboration area. By binding the account identifier of the collaboration account with the area identifier of the corresponding permission collaboration area, only the collaboration account corresponding to the account identifier bound with the area identifier of the permission collaboration area can have the area editing permission for the corresponding permission collaboration area. For example, the area identifier of the permission cooperation area may be a position identifier of a row or a column, for example, if the permission cooperation area is on the 2 nd row, the area identifier of the permission cooperation area may be 2, and if the permission cooperation area is on the 5 th row, the area identifier of the permission cooperation area may be 5. If the mapping relation between the account identifier 1 and the area identifier 2 of the collaboration account is added, indicating that only the collaboration account corresponding to the account identifier 1 in the 2 nd row in the initial table data has the area editing permission; if the mapping relationship between the account id 2 added with the collaborative account, the area id 3 and the area id 4 is added, it indicates that the 3 rd row and the 4 th row in the initial table data are present, and only the collaborative account corresponding to the account id 3 has the area editing right for the collaborative account.
The binding process of the account id and the area id may also be completed by the target terminal device through the server. When the server generates the authority collaboration area corresponding to each collaboration account, the area identifier of each authority collaboration area and the account identifier of the collaboration account to which the area identifier belongs can be bound. The server may synchronize the binding relationship between the area identifier and the account identifier to the target terminal device, and the target terminal device may also bind the area identifier of each rights collaboration area generated in the terminal page and the account identifier of the corresponding collaboration account, which is a process of giving the area editing rights to the collaboration account of each rights collaboration area.
It should be noted that the creator of the initial form data may have all the operation rights for the initial form data, for example, an assignment right including the operation right for the initial form data. The allocation authority may refer to that a certain collaboration account or a certain number of collaboration accounts in a plurality of collaboration accounts of the initial table data may be set, and a part of or all of the operation authorities for the initial table data may also be provided, or all of the authorities for editing the initial table data may be included. It can be understood that, a creator of the initial form data refers to a document account of a target user in a document application, and therefore, in addition to the region editing right that the corresponding collaboration account has, the document account of the target user may also have the region editing right to the rights collaboration region corresponding to each added collaboration account in the initial form data.
The initial table data added with the permission collaboration area of each collaboration account may be referred to as transition table data. The target terminal device may further output setting prompt information in the transition form data, the setting prompt information being used to prompt the target user to set a form editing function for the transition form data. The setting prompt information can include a setting confirmation control, and the target terminal device can respond to the confirmation operation of the target user aiming at the setting confirmation control and set a form editing function for the transition form data. The confirmation operation for the setting confirmation control may refer to a click operation for the setting confirmation control. Transition form data to which the form editing function has been set may be set as target form data. The form editing function is used for enabling the collaborators of the target form data to trigger form editing operation aiming at the target form data, and the form editing operation enables the collaborators of the target form data to edit the authority collaboration area with the area editing authority in the target form data in a form mode. Wherein the collaborators of the target form data are collaborators of the initial form data. It is understood that the initial table data, the transition table data and the target table data are all the same table data, but the initial table data, the transition table data and the target table data correspond to different table states of the same table data, and the different table states may refer to different functions or different contents added in the table data. In the specific process that the collaborator of the target form data edits the permission collaboration area, which has the area editing permission, in the target form data in the form of the form, refer to the following step S103.
Because the collaborator of the target table data can edit the authority collaboration area, which has the area editing authority, in the target table data in the form of a form, the process needs to be implemented through a header cell strip in the target table data, the setting prompt information is output when the target terminal device detects the header cell strip in the transition table data, the header cell strip is a header in the transition table data, and the header cell strip can be a cell row, a cell column, a plurality of cell rows or a plurality of cell columns in the transition table data. The head cell strip in the target table data is also the head cell strip in the transition table data.
The process of detecting the header cell bar in the transition table data by the target terminal device may be as follows:
the first method comprises the following steps: the transition table data includes a plurality of rows/columns, and a row/column may include a plurality of cells. When the target user fills data in the transition form data, the target terminal device may respond to a data entry operation of the target user for the cells in the transition form data, acquire the content entered in the cells by the target user, and may refer to the content entered in the cells by the target user as cell entry data.
The target terminal device may detect whether a combination cell exists in the transition table data according to the acquired cell entry data. The combination cells include a plurality of adjacent cells, and the plurality of cells in the combination cells may be in a cell row or a cell column. All the cells in the combined cells are not empty, in other words, the cells in the combined cells have corresponding cell entry data. The number of cells included in the combined cell needs to be greater than or equal to a first number threshold, which may be set by itself, for example, to 3 or 5, etc. The cell row or cell column at the start position of the transition table data may be referred to as a target cell bar, and the start position of the transition table data may refer to the first 3 rows or the first 3 columns in the transition table data, where the first 3 rows or the first 3 columns may be set to other values according to the actual application scenario, for example, the first 5 rows or the first 5 columns may also be used. If the target terminal device detects that the combined cell is in the target cell bar, the target terminal device may determine the target cell bar in which the combined cell is located as a head cell bar in the transition table data. The target terminal device may output the setting prompt information at the detected unit bar position of the header unit bar. The cell bar position of the head cell bar may refer to a position near the head cell bar or a position where the head cell is located, and for example, the setting hint information may be output at a position of column 3 in the head cell bar.
And the second method comprises the following steps: the target terminal device can also respond to the data entry operation of the target user for the cells in the transition form data to acquire the cell entry data. If the target terminal device detects that the target cell bars in the transition table data include the key cells whose number is greater than or equal to the second number threshold according to the cell data, the target cell bar in which the key cells are located may also be determined as the head cell bar of the transition table data. The second number threshold may be set by itself, for example to 3 or 5, etc. Also, the target terminal device may output the above-described setting prompt information at the detected unit bar position of the head unit bar.
The key unit grids are unit grids which contain table head keywords and non-table head keywords of which the number is smaller than a third number threshold, and the table head keywords and the non-table head keywords in the key unit grids are obtained by performing word segmentation on unit grid entry data in the key unit grids. The third number threshold may be set by itself, for example to 3, etc. Whether the cells in the transition table data are key cells can be detected through a keyword library, and the keyword library may include a plurality of header keywords, for example, 1 ten thousand or 10 ten thousand. The header keywords in the keyword library are obtained by segmenting header data of the historical table data, and words which do not belong to the keyword library can be used as non-header keywords. Historical tabular data refers to tabular data created by other document accounts heretofore. Optionally, the keywords in the keyword library may also be set manually, for example, a fixed plurality of header keywords may be set.
The keyword library may be maintained by a server, and the target terminal device may detect the key cells in the transition table data through the server. Namely, the target terminal device can synchronize cell entry data entered by the target user in the transition form data to the server, and the server can detect the obtained cell entry data. When the server detects the head unit strip in the transition form data according to the cell entry data, the server can send the detection result to the target terminal device, and the target terminal device can output the setting prompt information according to the position of the head unit strip in the detection result.
It should be noted that the target form data may be understood as the finally created form data, and the form data (for example, the initial form data and the transition form data) to which the target form data belongs before the target form data is obtained may be referred to as the previous form data. Therefore, it can be understood that the setting prompt information for the form editing function may be output when the target terminal device detects the head cell bar in the previous table data, instead of outputting when the head cell bar is detected in the transition table data. In other words, in the process of creating the table data to which the target table data belongs, as long as the target terminal device detects that the head cell bar exists in the table data, the setting prompt information may be output at the cell bar position of the detected head cell bar, and the target terminal device may further respond to the confirmation operation of the user for the setting prompt information to set the form editing function for the current table data.
Please refer to fig. 4a, which is a schematic page diagram of a terminal page provided in the present application. As shown in fig. 4a, the table data in the terminal page 100b belongs to the previous table data of the target table data. The target terminal device may respond to a data entry operation of the target user for the cells in the row 1 and the column a, and obtain cell entry data "names" of the target user entered in the cells in the row 1 and the column a. In addition, the target terminal device may further detect that the cell entry data "name" includes a head keyword "name" and includes 0 non-head keywords, and assuming that the third number threshold for the non-head keywords is 3 and 0 is less than 3, the target terminal device may determine that the cell in row 1 and column a is the key cell. The target terminal device can also respond to data entry operation of the target user for the cells in the 1 st row and the B th column, and acquire cell entry data 'school number' of the target user entered in the cells in the 1 st row and the B th column. In addition, the target terminal device may further detect that the table-head keyword "school number" is included in the cell entry data "school number" and 0 non-table-head keyword is included, and the target terminal device may determine that the cell in row 1 and column B is the key cell. The target terminal device can also respond to data entry operation of the target user for the cells in the 1 st row and the C th column, and acquire cell entry data 'class' of the target user entered in the cells in the 1 st row and the C th column. In addition, the target terminal device may further detect that the cell entry data "class" includes the top keyword "class" and includes 0 non-top keywords, and the target terminal device may determine that the cell in row 1, column C is the key cell.
Assuming that the second number threshold for the key cells is 3, since 3 key cells have been detected at this time, the 3 key cells include a cell in the 1 st row and the a th column, a cell in the 1 st row and the B th column, and a cell in the 1 st row and the C th column. And, the 3 key cells are all in the 1 st row (i.e. cell row 101b) of the table data in the terminal page 100b, and assuming that the start position of the table data refers to the position of the first 3 rows in the table data, it can be determined that the cell row 101b belongs to the target cell bar. Therefore, the 3 key cells are all in the target cell bar 101b, and therefore, the target terminal device can determine the target cell bar 101b as the head cell bar of the table data in the terminal page 100 b. The target terminal device may output the setting hint information 102b at the cell bar position of the head cell bar 101b, where the setting hint information 102b is output in the form of a hint box. The setup prompt 102b may include the prompt "recommend use [ intelligent fill ], more convenient fill using form" and "set up immediately" control 103b, which may be a button. The target terminal device may set a form editing function for the form data in the terminal page 100b in response to a click operation of the target user on the control 103 b. Here, the confirmation operation for the space 103b may be referred to as a confirmation operation for setting the presentation information.
Please refer to fig. 4b, which is a schematic page diagram of a terminal page provided in the present application. As shown in fig. 4b, the terminal page 105b is the same terminal page as the terminal page 100b in fig. 4 a. The target terminal device may display the terminal page 109b in response to a click operation of the target user on the question mark control 104b in the setting prompt information 102 b. The terminal page 109b includes a page 108b, and the page 108b may be a sub-page independently displayed on the terminal page 105b or may be a popup page. The page 1089 shows the description and examples of filling in the form, wherein the description of filling in the form is "let collaborators fill in the form using the form, fill in more concentration", and the example of filling in the form is to convert the form 106b into the form 107b for filling in.
It is to be understood that the form editing function of the target form data may be set for the target form data by the target terminal device in response to a confirmation operation of the target user for setting the prompt information. Optionally, the target user may also select a certain row/column or certain rows/columns in the previous table data to which the target table data belongs by himself, and use the selected row/column as the head unit bar, and then set the form editing function for the selected head unit bar.
In addition, the target user can set different operation permissions on the target table data for the collaboration account. For example, it is assumed that the plurality of collaboration accounts corresponding to the target form data include a second collaboration account, and since the plurality of collaboration accounts corresponding to the target form data may also include the document account of the target user, it is described here that the second collaboration account is not the document account of the target user. The target terminal device may respond to the relevant user operation of the target user and add a newly added region permission to the second collaboration account. After the second collaboration account is added with the newly added region authority, the second collaboration account can continue to add a corresponding authority collaboration region for the newly added collaboration account in the target form data according to the newly added region authority. The newly added collaboration account refers to a document account other than the collaboration account that has been selected as the target form data. For example, the target terminal device may respond to a user operation related to the target user, so that the second collaboration account may also edit an authority collaboration area that does not belong to the second collaboration account in the target form data. For another example, the target terminal device may also respond to a user operation related to the target user, so that the second collaboration account may add or delete an authorization collaboration area in the target form data.
Step S103, synchronizing the target form data to the collaboration terminals to which the at least two collaboration accounts belong, so that the collaboration terminals to which the at least two collaboration accounts belong respectively edit the corresponding permission collaboration areas in the target form data;
specifically, the target terminal device may synchronize the target form data to a collaboration terminal to which a collaboration account of the target form data belongs. The collaboration terminal to which the collaboration account belongs may refer to a terminal device in which the corresponding collaboration account is logged. The above process of creating the target form data may be implemented by the server, that is, the target form data is created by the server, and after the creation of the target form data by the server is completed, the created target form data may be sent to the target terminal device, and the target terminal device may output the target form data in the terminal page. Therefore, the target terminal device synchronizes the target table data to the collaboration terminal to which each collaboration account belongs, and may refer to that the target terminal device may respond to the synchronization operation of the target user for the target table data, and generate the synchronization instruction. The target terminal device may send the synchronization instruction to the server, so that the server may send the target table data to the collaboration terminal of each collaboration account according to the synchronization instruction.
After the collaboration terminal of the collaboration account acquires the target table data, the collaboration terminal can respond to user operation of the user on the target table data to edit the target table data. The following describes how to edit the target form data in the target terminal device, and it should be noted that the collaboration terminal to which each collaboration account belongs can edit the target form data by using the process. And when all the collaboration accounts finish editing the target form data, the target terminal equipment can obtain the filled final target form data. Since the filled target form data includes the cell rows or cell columns (for example, the column a in the terminal page 100c in fig. 5 a) corresponding to the "specified row filling persons" newly added by the batch-adding filling persons, the target terminal device may also respond to the user operation of the target user to delete the cell rows or cell columns corresponding to the "specified row filling persons" in the filled target form data. Or, the target terminal device may respond to a confirmation operation of the target user on the currently filled target form data, and delete the cell row or cell column corresponding to the "specified row filling person" in the target form data by itself.
Assume that the first collaboration account is included in the multiple collaboration accounts of the target form data, and the first collaboration account may be any collaboration account different from the document account of the target user. Besides the document account of the target user, the target terminal device can also log in a first collaboration account. Since the target table data has been sent to each collaboration account, the target terminal device may obtain the target table data in the first collaboration account. The target terminal device may expand the target table data in response to an expansion operation for the target table data in the first collaboration account. The step of expanding the target table data refers to opening the target table data, namely entering a terminal page where the target table data is located.
When the target terminal device opens the target table data in the first collaboration account, the target table data includes a permission collaboration area corresponding to the first collaboration account, and the area identifier of the permission collaboration area of the first collaboration account is already bound with the account identifier of the first collaboration account, so that the binding has a mapping relationship. The target terminal device can be positioned through the area identifier, the area position of the permission cooperation area corresponding to the first cooperation account in the target table data, and the target terminal device can also highlight the permission cooperation area at the positioned area position.
The permission cooperation area at the located area position is the permission cooperation area of the first cooperation account, and the highlight display of the permission cooperation area may be color change display of the permission cooperation area, for example, color change display of an area background color of the permission cooperation area for 1 second; the permission coordination area can also be subjected to flicker display, for example, the background color of the area of the permission coordination area is subjected to flicker display for 2 seconds, and the like; the permission coordination area may be displayed by light emission, for example, 1 second.
Through the above process, it can be understood that when target form data is entered into any one of the collaboration accounts, the area position of the permission collaboration area corresponding to the collaboration account can be automatically located, and the located permission collaboration area can be highlighted. By the method, the user can be quickly positioned to the region position of the authority cooperation region which needs to be edited, and the editing efficiency of the user for the target table data is improved.
After the target form data is entered into the first collaboration account, the target terminal device may respond to a form editing operation in the target form data for the permission collaboration area of the first collaboration account, and output a form page corresponding to the first collaboration account according to header data of the target form data and the permission collaboration area of the first collaboration account. For example, a form editing entry or a form editing button may be provided, and the target terminal device may output a form page corresponding to the first collaboration account in response to a click operation of the user on the form editing entry or the form editing button. The header data of the target table data refers to cell entry data in a header cell bar in the target table data. Since the head cell bar may include a plurality of cells, the data entered in each cell in the head cell bar may be referred to as cell head data. The target terminal device may respond to a data entry operation in a form page of the first collaboration account by the user, acquire data entered in the form page by the user, and may refer to the data entered in the form page by the user, acquired by the target terminal device, as form entry data. The target terminal device can correspondingly add the acquired form entry data to the permission cooperation area of the first cooperation account in the target form data, and the process realizes that the user finishes editing the target form data in a form of the form. Specific procedures can be seen in the following examples.
Please refer to fig. 5a, which is a schematic page diagram of a terminal page provided in the present application. As shown in fig. 5a, assume that a user's flowers hold a first collaboration account. The target form data opened in the first collaboration account is displayed in the terminal page 100c, and since the right collaboration area corresponding to each collaboration account is added in the target form data, the prompt information 115c may also be displayed in the terminal page where the target form data is located. The prompt message 115c is "specify row writer: only a specified person can edit a certain line, for example, a specified little red can edit the second line, and other persons cannot modify the line, "the prompt information 115c is used for prompting the collaborators, the target table data is the authority collaboration area allocated to each collaborator according to the rule of the unit line, and each collaborator can only edit the authority collaboration area belonging to the collaborator, that is, can only edit one line or a plurality of lines belonging to the collaborator.
Since the target form data opened in the first collaboration account is displayed in the terminal page 100c, the permission collaboration area 101c is the 4 th row in the target form data at the area position of the permission collaboration area corresponding to the first collaboration account, that is, at the permission collaboration area 101c corresponding to the user. Here, the right cooperation area 101c may also be highlighted, and here, the area background of the right cooperation area 101c is displayed in gray.
The name of the collaboration account set for each row is indicated in column a in the terminal page 100c, and the names of the collaboration accounts displayed in column a (the names displayed here include "music," "duo," "flower," and "cacao") may be names remarked for contacts to which the collaboration accounts belong in an address book of a target user (which may be an address book of a third party application, or an address book in a document application), or account names of original collaboration accounts.
More specifically, the target form data is the form data set with the form editing function set by the creator of the target form data, see step S102 described above. When the target terminal device detects that the user has an editing operation for the permission cooperation area 101c, for example, a clicking operation or a data entry operation for the permission cooperation area 101c, the target terminal device may display the terminal page 105 c. The terminal page 105c includes therein a prompt box 103c for prompting the user to edit the target form data in the form of a form. The prompt box 103c includes an "enter intelligent form filling" button 104c, and the target terminal device may respond to a click operation of the user on the button 104c, and output a form page corresponding to the first collaboration account according to header data of the target form data and the permission collaboration area 101c, that is, display the terminal page 106 c. The header cell bar of the target form data is determined when the creator (i.e., the document account of the target user) sets the form editing function for the target form data, and therefore, the header cell bar in the target form data does not need to be re-detected here. Here, the head cell bar of the target table data is the cell row 102c in the terminal page 105c, and the cell row 102c is the 1 st row in the target table data. Thus, as shown in the terminal page 105c, the data in each cell in the head cell bar may be referred to as cell header data, and the header data of the target table data includes the cell header data "name", the cell header data "school number", the cell header data "class", the cell header data "telephone number", and the cell header data "home address" in the header cell row 102 c. The form page further comprises a data entry area corresponding to each unit form header data, and the data entry area corresponding to each unit form header data is obtained according to the authority cooperation area 101 c.
As shown in the terminal page 106c, the form page 107c is included in the terminal page 106 c. The form page 107c includes a data entry region k1 corresponding to the cell header data "name", a data entry region k2 corresponding to the cell header data "school number", a data entry region k3 corresponding to the cell header data "class", a data entry region k4 corresponding to the cell header data "telephone number", and a data entry region k5 corresponding to the cell header data "home address". Here, the data entry region k1 corresponds to the cell at the column B position on the 4 th row in the rights cooperation region 101c, that is, the data entered in the data entry region k1 is added to the cell at the column B position on the 4 th row in the rights cooperation region 101 c. The data entry area k2 corresponds to the cell at the column C position on the 4 th row in the rights cooperation area 101C, i.e., the data entered in the data entry area k2 is added to the cell at the column C position on the 4 th row in the rights cooperation area 101C. The data entry region k3 corresponds to the cell at the column position D of row 4 in the rights cooperation region 101c, i.e., the data entered in the data entry region k3 is added to the cell at the column position D of row 4 in the rights cooperation region 101 c. The data entry area k4 corresponds to the cell at the E-th column position on the 4 th row in the rights cooperation area 101c, i.e., the data entered in the data entry area k4 is added to the cell at the E-th column position on the 4 th row in the rights cooperation area 101 c. The data entry area k5 corresponds to the cell at the column F position on the 4 th row in the rights cooperation area 101c, i.e., the data entered in the data entry area k5 is added to the cell at the column F position on the 4 th row in the rights cooperation area 101 c. It can be understood that the form entry data entered in the form page by the user, acquired by the target terminal device, is automatically added to the corresponding cell in the target form data in real time, and the user does not need to have an operation of saving data in the form page in the process.
Please refer to fig. 5b, which is a schematic diagram of a terminal page for form editing according to the present application. A data entry operation for a form page may refer to a data entry operation for a data entry area in the form page. The target terminal device may respond to a data entry operation of the user for the form page 107c in the terminal page 106c, acquire form entry data entered by the user in the form page, and display the terminal page 108 c. As shown in the terminal page 108c, the form page 109c in the terminal page 108c is a form page in which form entry data is entered in the form page 107 c. The form page 109c specifically includes form entry data "duo" in the data entry region k1, form entry data "12345678" in the data entry region k2, "2 shifts higher" in the form entry data "k 3," form entry data "12345123451" in the data entry region k4, and form entry data "xx town xx province xx city xx" in the data entry region k 5. The target terminal device may display the terminal page 110c in response to a user closing operation for the form page 109 c. As shown in terminal page 110c, the target terminal device has added the form entry data obtained from form page 109c to the target form data, as seen in line 4 of the target form data in terminal page 110 c. In addition, in the terminal page 110c, the target terminal device may further respond to the expansion operation of the user on the form page, and then output the form page, where the output form page may include data that has been previously entered in the target form data by the user, and the output form page may be the same as the form page 109 c.
The target terminal device can also respond to the editing operation of the non-permission collaboration area in the target table data in the first collaboration account, and output prompt information without editing permission, wherein the prompt information without editing permission is used for prompting a user that the non-permission collaboration area does not have the area editing permission. The non-permission cooperation area refers to a permission cooperation area in the target table data except for a permission cooperation area corresponding to the first cooperation account, in other words, the non-permission cooperation area is a permission cooperation area not belonging to the first cooperation account, and the area identifier of the non-permission cooperation area and the account identifier of the first cooperation account do not have a mapping relation.
Please refer to fig. 5c, which is a schematic page diagram of a terminal page provided in the present application. Assuming that the first collaboration account logged in the terminal page is a document account held by each of the users, the permission collaboration area 113c is a non-permission collaboration area for the first collaboration account. The target terminal device may input the no-editing-right prompt information 112c in response to the editing operation of the user with respect to the non-right cooperation area 113c in the terminal page 111 c. The editing operation for the non-permission cooperation area 113c in the terminal page 111c may refer to an operation of trying to record data in the non-permission cooperation area 113c, and the prompt information without editing permission is "row 5 only has editing permission, and you have no editing permission".
Furthermore, the permission collaboration area of the first collaboration account may be a unit row in the target table data, and each cell in the unit row may be referred to as a permission cell. Because the target form data is online form data completed by cooperation of multiple persons, if other collaboration accounts except the first collaboration account of the target form data enter new data in the target form data, new data entered by other collaboration accounts can be newly added in the target form data opened by the first collaboration account in real time. In other words, because the target table data is online shared table data, data entered by each collaboration account in the target table data is synchronized to target table data opened by each other collaboration account, and the data operated by each collaboration account is the same target table data.
Therefore, the target terminal device can acquire data in the target cell of the target table data. The target cell may refer to a cell in the same cell column as the authority cell, and different authority cells are in different cell columns, so that different authority cells correspond to different target cells. The target cell also refers to a cell in an authority collaboration area not belonging to the current collaboration account, where the current collaboration account refers to the first collaboration account, and thus, the target cell refers to a cell in the authority collaboration area not belonging to the first collaboration account. In other words, the data in the target cell is not entered by the current collaboration account but by other collaboration accounts, and the data entered by other collaboration accounts in the target cell may be referred to as cell existing data.
The target terminal device can use the target cells with the same existing data of the cells in the detected multiple target cells corresponding to the same authority cell as calling cells, when the number of the calling cells is larger than a calling number threshold, the target terminal device can output a form page corresponding to a first collaboration account through header data of target form data, the authority collaboration area of the first collaboration account and the existing data of the cells in the calling cells, and the existing data of the cells in the calling cells exist in a data entry area at a corresponding position in the form page. The call number threshold may be set by itself, e.g., to 2, etc. However, this method is limited to the first collaboration account not having entered any data in the data entry area of the form page corresponding to the calling cell. In other words, in this way, data entered by most other collaboration accounts in the target form data can be used as data recommended to the first collaboration account in the target form data, but if the first collaboration account already enters data at the corresponding position of the target form data, the data entered by the first collaboration account is used as a reference, that is, the data entered by the first collaboration account is kept unchanged.
For example, please refer to fig. 6, which is a schematic diagram of a terminal page for data recommendation provided by the present application. As shown in fig. 6, it is assumed that the first collaboration account held by each of the users logs in the terminal page 100D, the permission collaboration area corresponding to the first collaboration account is the 3 rd row where each of the users is located, the cell at the D th column in the 3 rd row may be used as a permission cell, the target cell in the same cell column as the permission cell includes a cell at the D th column in the 2 nd row, a cell at the D th column in the 4 th row, and a cell at the D th column in the 5 th row, and as can be seen from the cell column 101D, the existing data of the cell in the target cell at the D th column in the 2 nd row is "1 shift higher", the existing data of the cell in the target cell at the D column in the 4 th row is "1 shift higher", and the existing data of the cell in the target cell at the D column in the 5 th row is "1 shift higher". The target cell at the line 2, column D, the target cell at the line 4, column D, and the target cell at the line 5, column D may be taken as a calling cell, and the number of cells of the calling cell is 3. Assuming that the calling number threshold is 2, if the cell number 3 of the calling cell is greater than the calling number threshold 2, the target terminal device may respond to the expansion operation of the user for the form page, and output the form page for the first collaboration account through the existing cell data, the header data, and the permission collaboration area corresponding to the first collaboration account in the calling cell, as shown in the terminal page 102 d. In the form page 103d in the terminal page 102d, the data entry area 104d corresponding to the cell header data "class" originally has no data, but at this time, the cell existing data "1 class higher" in the calling cell has been filled into the data entry area 104 d.
By the method, the data which can be entered by the first collaboration account is recommended to be 1 shift higher in the data entry area 104d, and the first collaboration account can modify the 1 shift higher in the data entry area 104d and can also be kept unchanged.
Furthermore, when the target terminal device is a mobile terminal and the mobile terminal is not provided with a solid-state keyboard, the target terminal device responds to the user operation of the user, and when the form entry data is entered in the form page, the input keyboard opened in the target terminal device may include function keys related to the entry of data in the form page, such as a function key of a next item, a function key of a line feed, a function key of an inserted picture, and the like.
Please refer to fig. 7, which is a schematic page diagram of a terminal page provided in the present application. As shown in fig. 7, when the target terminal device is a mobile terminal, the terminal page 100e is a terminal page in the target terminal device. The opened target form data is displayed in the terminal page 100e, and the target terminal device may display the terminal page 101e in response to a user's click operation on the "enter intelligent fill" button 102e in the terminal page 100 e. A form page 107e is included in the terminal page 101e, and the target terminal device may display the input keyboard 105e in response to a data entry operation by the user for the form page 107 e. The input keyboard 105e includes function keys related to data entry in the form page, and specifically includes a next function key 106e, where the next function key 106e is used to jump from a data entry area where data is currently entered to a next data entry area, and then to enter form entry data in the next data entry area. Also included is an insert function key 103e, which insert function key 103e is used to add pictures, video or documents, etc. in the data entry area. A linefeed function key 104e is also included for linefeeding in the current data entry area.
When the form page is generated, different data entry formats may be set for each data entry area in the form page, where the data entry formats may be target entry formats that a creator (here, the document account of the target user) adds to each cell header data in a header cell bar of the target form data, and the target entry formats may include a date entry format, a picture entry format, a video entry format, a document entry format, a drop-down selection entry format, and the like. One cell header data corresponds to one data entry region, and one data entry region corresponds to one data entry format.
Or, the data entry format may also be a data entry format corresponding to each cell header data obtained by the target terminal device by detecting the data type of each cell header data. For example, when the cell header data includes a keyword related to a date, the data type of the cell header data may be considered as a date type, and the data entry format corresponding to the cell header data may be obtained as a date entry format, where the date entry format may refer to a format in which all the entered dates are 0000 (year)/00 (month)/00 (day). For another example, when the cell header data includes a keyword related to a picture, the data type of the cell header data may be considered as a picture type, and the data entry format corresponding to the obtained cell header data may be an image entry format. Optionally, the data entry format of each data entry area in the form page may also be set to a default format, where the default format may be a text entry format.
Please refer to fig. 8, which is a page diagram of a form page provided in the present application. As shown in fig. 8, the form page 100f includes a data entry area 107f in which the data entry format is a text entry format, and the text entry format refers to that characters can be entered into the data entry area 107 f; the form page 100f further includes a data entry area 108f in which the data entry format is a drop-down selection entry format, and the drop-down selection entry format refers to that corresponding form header entry data can be directly selected from drop-down options set by a creator. Here, for example, the target terminal device may display the form page 105f in response to a user's clicking operation on the pull-down selection button 101f in the data entry area 108 f. The form page 105f includes a pull-down option 106f, and the pull-down option 106f specifically includes an option "one shift higher by 1 shift", an option "one shift higher by 2 shifts", and an option "one shift higher by 3 shifts". The target terminal device may select a corresponding option (which may be single-selected or multiple-selected) as the form entry data in the data entry area 108f in response to a selection operation of the user for an option in the pull-down options 106 f. Also included in the form page 100f is a data entry area 102f in a data entry format that is a picture entry format that allows pictures to be added to the data entry area 102 f. Also included in the form page 100f is a data entry area 103f in a data entry format, which is a document entry format, to which documents may be added to the data entry area 103 f. Also included in the forms page 100f is a data entry area 104f in a data entry format, which refers to a format in which video may be added to the data entry area 104 f.
Furthermore, the header cell bar of the target table data may include more than one cell row or one cell column, and may also include a plurality of cell rows or a plurality of cell columns. When the header cell strip of the target table data includes a plurality of cell rows or a plurality of cell columns, the plurality of cell rows or the plurality of cell columns need to be merged to obtain the header cell strip of the target table data.
Please refer to fig. 9, which is a schematic view of a scene for acquiring a header cell bar according to the present application. As shown in fig. 9, when the target form data is opened in the first collaboration account and the terminal page 100g expanded by the target form data is displayed, a prompt box 104g may also be displayed at the bottom of the terminal page 100 g. Also included in this prompt box 104g is an "enter intelligent fill" button 102g, which button 102g is used to display a form page 103 g. When detecting a head cell strip of the target form data, the target terminal device may merge cell rows where cells occupying the largest number of rows in the head cell strip are located, and the merged cell rows are used as cell head data in the form page. For example, here, the target terminal device may detect that the head cell bar in the terminal page 100g is the cell bar 101g, and the cell bar 101g includes the 1 st line and the 2 nd line of the target table data, and may merge the cell entry data in the 1 st line and the 2 nd line to serve as the cell head data in the form page. As shown in the terminal page 105g, the 1 st row and the 2 nd row in the cell bar 101g are merged, and when merging, the cell entry data in the 1 st row and the cell entry data in the 2 nd row may be connected by "-" or a blank space or the like. The unit form header data "name", the unit form header data "school number", the unit form header data "1 month 1 day-monday", the unit form header data "1 month 2 day-tuesday", and the unit form header data "1 month 3 day-wednesday" in the form page 103g can be obtained. By the method, the user can quickly check and write complete data in the head unit bar through the form page.
The method includes the steps that initial form data are obtained, and at least two collaboration accounts corresponding to the initial form data are obtained; responding to triggering operation aiming at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial table data to obtain target table data; and synchronizing the target form data to the cooperation terminals to which the at least two cooperation accounts belong, so that the cooperation terminals to which the at least two cooperation accounts belong respectively edit the corresponding permission cooperation areas in the target form data. Therefore, by the method, the permission cooperation areas of at least two cooperation accounts can be added in place in one step in the initial form data, and the adding efficiency of the permission cooperation areas is improved. Meanwhile, each cooperation account number is respectively allocated with a corresponding authority cooperation area, and each cooperation account number can edit the authority cooperation area belonging to the cooperation account number in the target form data, so that the filling accuracy of the target form data is improved.
Please refer to fig. 10, which is a flowchart illustrating a form generating method according to the present application. As shown in fig. 10, the method includes:
step S201, entering an intelligent filling form by a collaborator;
specifically, the collaborator may be any collaborator of the target form data, and the target terminal device may expand the target form data, that is, enter the target form data, in response to an expansion operation of the collaborator on the target form data. The target form data is provided with form editing functionality and entry into the target form data is also referred to as entry into the intelligent fill-in form.
Step S202, obtaining lines required to be filled in by a user according to the user identification;
specifically, the user identification is an account identification of the collaboration account of the collaborator. Since the permission cooperation area in the target form data is bound with the account id of the cooperation account to which the permission cooperation area belongs, the permission cooperation area corresponding to the account id can be found according to the account id of the cooperation account, the found permission cooperation area can be a unit row, and the found permission cooperation area is a row which needs to be filled by the user.
Step S203, jumping to a designated line, and clicking 'intelligent filling' by a user;
specifically, the designated line is the line that the user needs to fill in, and the specified line is jumped to, that is, the area position of the right collaboration area corresponding to the user identifier found in step S202 is located. The user may click on the "intelligent fill" button for the specified line, which is the button used to enter the form page.
Step S204, analyzing the header keywords and generating an intelligent form;
specifically, after the user clicks the "intelligent filling" button, the target terminal device may analyze the header keywords, that is, analyze the keywords in the cell header data in the header cell strip. The keywords in the cell header data can be analyzed one at a time until the keywords in the cell header data are all analyzed.
Step S205, whether the keyword is a date type;
specifically, if the keyword in the certain cell header data in the header cell strip is analyzed as the date type, the following step S206 is performed, and if the keyword in the certain cell header data in the header cell strip is analyzed as not the date type, the following step S207 is performed. If the keyword includes a word related to a date, such as a year, a month, and the like, it may be determined that the keyword is a date type.
Step S206, adding a date input format to the form;
specifically, the data entry format of the data entry area corresponding to the cell header data of the keyword including the date type in the form (i.e., the form in the form page, which can be understood as the form page) may be set as the date entry format, which is the date entry format. Next, step S217 is performed.
Step S207, whether the keyword is a time type or not;
specifically, if the keyword is not a date type, it is continuously determined whether the keyword is a time type. If the keyword is determined to be of the time type, the following step S208 is executed, and if the keyword is determined not to be of the time type, the following step S209 is executed. If the keyword includes time, a word related to time, etc., the keyword may be determined to be a time type.
Step S208, adding a time input format to the form;
specifically, the data entry format of the data entry area corresponding to the cell header data of the keyword including the time type in the form may be set as the time input format. Next, step S217 is performed.
Step S209, whether the keyword is a picture type or not;
specifically, if the keyword is not the time type, it is continuously determined whether the keyword is the picture type. If the keyword is determined to be of the picture type, the following step S210 is performed, and if the keyword is determined not to be of the picture type, the following step S211 is performed. If the keyword includes a screenshot, a imported picture, a drawing and other words related to the picture, it may be determined that the keyword is a picture type.
Step S210, adding an image input format to the form;
specifically, the data entry format of the data entry region corresponding to the cell header data of the keyword including the picture type in the form may be set as the picture input format, so that the collaborator may add a picture in the data entry region having the picture input format. Next, step S217 is performed.
Step S211, whether the keyword is a geographical position type or not;
specifically, if the keyword is not the picture type, it is continuously determined whether the keyword is the geographical location type. If the keyword is determined to be of the geographical location type, the following step S212 is performed, and if the keyword is determined not to be of the geographical location type, the following step S213 is performed. If the keyword includes a word related to a geographic location, such as a location, a region, a position, and the like, the keyword may be determined to be of the geographic location type.
Step S212, adding a position input format to the form;
specifically, the data entry format of the data entry area corresponding to the cell header data of the keyword including the geographic location type in the form may be set as a location input format, and the location input format may be an input format of "xx province/xx city/xx area" or a format of map positioning, or the like. Next, step S217 is performed.
Step S213, whether the keyword is pulled down to select the type;
specifically, if the keyword is not the geographic location type, it is continuously determined whether the keyword is a pull-down selection type. If the keyword is determined to be of the pull-down selection type, the following step S214 is executed, and if the keyword is determined not to be of the pull-down selection type, the following step S215 is executed. If the keyword comprises the keyword in the pull-down option set by the user for the cell table header data, the keyword can be judged to be the pull-down selection type.
Step S214, adding a pull-down input format to the form;
specifically, the data entry format of the data entry area corresponding to the cell header data including the keyword of the pull-down selection type in the form may be set as the pull-down input format, for example, the data entry format of the data entry area 1018f in fig. 8 is the pull-down input format. Next, step S217 is performed.
Step S215, the default type of the keyword;
specifically, if the keyword is not the above-mentioned pull-down selection type, the default type may be used as the keyword type of the keyword, and the following step S216 is executed. For example, the default type may be a text type, or the like.
Step S216, adding a default input format to the form;
specifically, the data entry format of the corresponding data entry area, which includes the cell header data of the default type of the keyword in the form, may be set as the default input format. If the default type is a text type, the default input format may be a text input format. Next, step S217 is performed.
Step S217, whether the keyword is processed or not is judged;
specifically, it is determined whether the processing of the keyword is completed, that is, whether the keyword in the header data of all the cells in the header cell bar has been analyzed. If all the data have been analyzed, the following step S218 is executed, and if the data have not been analyzed, the step S204 is executed to continue analyzing the keywords in the cell header data.
Step S218, after the generation of the intelligent form is finished, the user starts to fill in the intelligent form;
specifically, after the keyword in the header data of each cell is analyzed, the intelligent form, that is, the form indicates that the data entry format of each data entry area in the form has been set, indicates that the form is successfully generated, and can output a form page including the form. The user can fill in the form page, namely, the form entry data is recorded, and the target form data is edited.
Please refer to fig. 11a, which is a flowchart illustrating a method for obtaining a keyword library according to the present application. As shown in fig. 10, the method includes:
step S301, a user submits a new form/form;
specifically, the execution subject in this embodiment may be a background server (hereinafter referred to as a server) of the document application, and the server may obtain a new form and form submitted by the user. The new forms and forms submitted by the user herein may refer to forms and forms submitted by all users of the document application (i.e., all document accounts), for example, the target terminal device may also submit the target form data to the server. The form or form submitted by the user and acquired by the server can be called historical form data or historical form data.
Step S302, extracting header data of the form input question/form;
specifically, the server may extract form entry questions in the historical form data, i.e., corresponding to the cell header data displayed in the form page. The server may also extract header data in the historical table data, i.e., cell header data in the header cell bar of the historical table data.
Step S303, adopting maximum forward matching word segmentation based on the existing dictionary;
specifically, the server may perform word segmentation on the extracted form input question and the form header data by using a maximum forward matching word segmentation method to obtain a plurality of word segmentation words. The server can match each participle word in the existing dictionary, and if the participle word exists in the existing dictionary, the participle word is indicated as a keyword. And if the segmented word does not exist in the existing dictionary, the segmented word is not a keyword. The existing dictionary may be a dictionary that the developer has created in advance.
Step S304, extracting keywords, and updating a keyword database;
specifically, the server can extract and obtain the form input problem and the keywords in the form header data through the process. The server may update the keyword database with the extracted keywords, e.g. by adding the extracted keywords directly to the keyword database.
Step S305, judging whether to update the ranking list;
specifically, the server may determine whether the ranking list needs to be updated at this time, where the ranking list is a ranking list of the keyword. Here, the update time of the ranking list may be set, for example, once every 24 hours. Therefore, when 24 hours have elapsed since the time measurement, it indicates that the ranking list needs to be updated, and when 24 hours have not elapsed since the time measurement, it indicates that the ranking list does not need to be updated. Or, the user may manually trigger the update of the ranking list, where the user may refer to a developer, and if the developer triggers the update of the ranking list at this time, it indicates that the ranking list needs to be updated at this time.
The ranking list may include a daily keyword ranking list, a monthly keyword ranking list and an annual keyword ranking list. The daily keyword ranking list is obtained by ranking keywords appearing in one day in the keyword database, the monthly keyword ranking list is obtained by ranking keywords appearing in one month in the keyword database, and the annual keyword ranking list is obtained by ranking keywords appearing in one year in the keyword database. The more times a keyword appears, the more forward the position of the keyword in the ranking list.
The intelligent filling keyword library can be obtained through a plurality of keywords with the most front positions in the ranking list, for example, the intelligent filling keyword library may include 1 ten thousand keywords with the most front positions in the ranking list. The intelligent filling keyword library is the keyword library in step S102, and the keyword library may be used to detect the key cells in the form data, and the header in the form data may be detected by detecting the key cells in the form data, which is specifically referred to in step S102. The keywords in the keyword library may be referred to as header keywords.
Please refer to fig. 11b, which is a schematic flow chart of a key cell detection method provided in the present application. As shown in fig. 10, the method includes:
step S401, a user finishes inputting a cell text;
specifically, when the user enters data into a certain cell in the initial form data, the target terminal device may obtain the data entered by the user in the cell, that is, the cell entry data, that is, the cell text in the cell.
Step S402, whether the line is from the 1 st line to the 3 rd line;
specifically, the target terminal device may determine whether the current cell is in the 1 st row to the 3 rd row in the initial table data. If so, the following step S404 is executed, and if not, the following step S403 is executed.
Step S403, not the key cell;
specifically, the target terminal device determines that the current cell is not the keyword cell, and the process is ended. For an explanation of the key cells, see step S102 above.
Step S404, whether the cell contains the keyword or not;
specifically, the target terminal device may determine whether the current cell includes a keyword, where the keyword may refer to the header keyword, and may determine through the keyword library obtained in fig. 11 a. If the current cell does not contain the keyword, the following step S405 is performed, and if the current cell does contain the keyword, the following step S406 is performed.
Step S405, not the key cell;
specifically, the target terminal device detects that the current cell is not a key cell, and the current process is ended.
Step S406, whether a plurality of non-keywords are contained before and after;
specifically, the target terminal device continues to determine whether a plurality of non-keywords are included before and after the keyword in the current cell, where the non-keywords are the non-header keywords, that is, words that are not included in the keyword library. If it is determined that a plurality of non-keywords are included, the following step S407 is executed, and if it is determined that a plurality of non-keywords are not included, the following step S408 is executed.
Step S407, not a key cell;
specifically, the target terminal device detects that the current cell is not a key cell, and the current process is ended.
Step S408, key cells;
specifically, the target terminal device detects that the current cell is a key cell, and the current process is finished.
Please refer to fig. 11c, which is a flowchart illustrating an intelligent recommendation method provided in the present application. As shown in fig. 11c, the method includes:
step S501, user operation type;
specifically, the target terminal device may detect a user operation type when the user enters data in the form data. The user operation type may include a copy and paste operation type and may also include an input operation type.
Step S502, whether copying and pasting;
specifically, the target terminal device may determine whether the user operation type is copy-paste. If yes, go to step S504, otherwise go to step S503.
Step S503, whether input is required;
specifically, the target terminal device may determine whether the user operation type is the input type again, and generally, the user operation type is not the copy-paste type, but is the input type. When the target terminal device determines that the user operation type is the input type, step S505 may be performed.
Step S504, analyzing the copied and pasted content;
specifically, the target terminal device may parse copy and paste contents entered in the form data by the user through the copy and paste operation. Wherein copying the pasted content may include copying the pasted content in a plurality of cells.
Step S505, analyzing the input content and detecting key cells;
specifically, the target terminal device may analyze the content input by the user in the cell through the input operation, and further determine whether the key cell exists in the table data according to the analysis result. If yes, go to step S507.
Step S506, whether the position is smaller than the 3 rd line or not;
specifically, the target terminal device may determine whether the position of the cell where the copy and paste content is located is smaller than the 3 rd row, that is, whether the position is in the 1 st row to the 3 rd row.
Step S507, the number of the key cells is larger than or equal to a specified value;
specifically, the target terminal device may determine whether the number of the key cells belonging to the same cell row is greater than or equal to a specified value, that is, the second number threshold for the key cells in step S102. If yes, it indicates that the head cell strip in the table data is detected, step S508 is executed, otherwise, the process is ended and no operation is performed.
Step S508, triggering intelligent filling recommendation;
specifically, triggering the intelligent filling recommendation means outputting the setting prompt information at the position of the unit bar where the header unit bar is located. The target terminal device may set a form editing function for the form data in response to a confirmation operation of the user for the setting prompt information.
Please refer to fig. 12, which is a flowchart illustrating a region adding method according to the present application. As shown in fig. 12, the method includes:
step S701, a user selects batch adding filling persons;
specifically, the user may select the batch addition writer, for example, the user may click the "batch addition writer" control 105a in the terminal page 124a in fig. 2b to realize the batch addition writer.
Step S702, removing repeated addition to obtain newly added filling persons;
specifically, the newly added filling person is a collaboration account selected for the form data, if the multiple collaboration accounts of the form data are selected from third-party applications, and the third-party applications include a first communication application and a second communication application, a mapping document account of the first communication account in the first communication application in the document application and a mapping document account of the second communication account in the second communication application in the document application have an account binding relationship in the document application. If the first communication account in the first communication application and the second communication account in the second communication application are selected from the added filling persons at the same time, the newly added filling persons corresponding to the first communication account and the second communication account are the same finally, that is, the first communication account and the second communication account correspond to the same collaboration account. By the method, the repeated addition can be removed, namely only one collaboration account can be obtained through the first communication account and the second communication account, and two repeated collaboration accounts cannot be obtained.
Step S703, filling in an appointed line;
specifically, for example, if the user selects "specified line writer" in the selection box 101a in the terminal page 122a in fig. 2a, it indicates that the specified line is filled in the form data. The filling of the designated row indicates that each collaboration account is allocated with a corresponding permission collaboration area according to the behavior in the form data. If the specified row is filled, step S704 is executed, and if the specified row is not filled, indicating that the specified column is filled, step S705 is executed. The specified column filling indicates that corresponding permission collaboration areas are allocated to each collaboration account according to columns in the form data.
Step S704, processing line distribution;
specifically, a unit line unit is used for allocating an authority collaboration area for the collaboration account.
Step S705, processing column assignment;
specifically, a permission collaboration area is allocated to the collaboration account by taking a unit column as a unit.
Step S706, adding a new line of protection area;
specifically, each time a row of protection regions is added, the protection regions are also the added rights cooperation regions.
Step S707, endowing the area with a newly added filler editing authority;
specifically, the newly added authority collaboration area is randomly allocated to a collaboration account, that is, the area editing authority of the newly added authority collaboration area is given to a collaboration account.
Step S708, whether newly added filling persons remain unprocessed or not is judged;
specifically, whether a collaboration account is not assigned with an authority collaboration area is judged. If yes, the step S706 is executed to continue allocating a corresponding permission collaboration area to the collaboration account to which no permission collaboration area is allocated. If not, it indicates that the right collaboration areas of all collaboration accounts are completely allocated, then step S712 is executed.
Step S709, adding a row of protection areas;
specifically, each time a row of protection regions is added, the protection regions are also the added rights cooperation regions.
Step S710, endowing the area with a newly added filler editing authority;
specifically, the newly added authority collaboration area is randomly allocated to a collaboration account, that is, the area editing authority of the newly added authority collaboration area is given to a collaboration account.
Step 711, whether newly added filling persons remain unprocessed or not is judged;
specifically, whether a collaboration account is not assigned with an authority collaboration area is judged. If yes, the step S709 is executed, and a corresponding permission cooperation area is continuously allocated to the cooperation account to which the permission cooperation area is not allocated. If not, it indicates that the right collaboration areas of all collaboration accounts are completely allocated, then step S712 is executed.
Step S712, completing the allocation;
specifically, the permission collaboration areas of all collaboration accounts are assigned completely, and the assignment is finished.
Please refer to fig. 13, which is a flowchart illustrating a table data processing method according to the present application. As shown in fig. 12, the method includes:
step S601, rapidly distributing row/column permission;
specifically, the creator a data layer refers to data interaction between a creator a (referred to as the document account of the target user) and a server (a backend server of the document application), and the server identifies the creator a through an account identifier of a collaboration account of the creator a. The target terminal device (which may be understood as creator a) may send the obtained collaboration account of the table data to a server (a backend server of the document application), and the server may start to allocate a corresponding row/column permission to each collaboration account, that is, allocate a corresponding permission collaboration area to each collaboration account, where the permission collaboration area may be a unit row or a unit column.
Step S602, traversing the users to be added;
specifically, the user to be added refers to a collaboration account of the table data, and the server may sequentially traverse a plurality of collaboration accounts synchronized by the target terminal device.
Step S603, generate a row of "area" on the table;
specifically, when the server traverses to the first collaboration account, a row of "area" may be generated in the table data, that is, an authority collaboration area is generated.
Step S604, appointing authority for the area;
specifically, the server may designate a corresponding collaboration account for the generated row of permission collaboration area, that is, assign the area editing permission of the row of permission collaboration area to the traversed collaboration account.
Step S605, whether the user finishes setting;
specifically, whether all the collaboration accounts have been traversed is detected, and a corresponding permission collaboration area is allocated to each collaboration account. If not, the step S603 is executed to continue generating areas in the table data, and allocate the generated areas to the collaboration accounts which are not allocated to the right collaboration areas. If so, indicating that the permission cooperation areas of all the cooperation accounts are allocated, and ending the process of allocating the permission cooperation areas for the cooperation accounts.
In the above process, the terminal device allocates the right collaboration area of each collaboration account through the server, and the data layer in the server may store all data generated in the table data in the generation process, including which line in the table data is allocated to which collaboration account, and the like.
Step S606, storing the data in a background and broadcasting the received data;
specifically, the data background belongs to a data layer of the server, and the data background may store each generated region in the table data and broadcast each generated region (i.e., each authorized collaboration region) to each collaboration account, where the generated region includes the collaboration account of the collaborator B and the collaboration account of the collaborator C.
Step S607, the authority background stores and broadcasts the set authority;
specifically, the authority background also belongs to the data layer of the server. The permission background can store the binding relationship between each region in the table data and the collaboration account, that is, store which regions in the table data have region editing permission for each collaboration account. The authority background can broadcast the collaboration account corresponding to each region to each collaboration account.
Step S608, receiving the synchronized data, and generating an "area";
specifically, the collaborator B data layer refers to data interaction between the collaborator B document account and the server. The terminal device where the document account of the collaborator B is located may receive each region in the table data synchronized by the data in the background, and generate each region in the same table data in the terminal page of the terminal device correspondingly.
Step S609, receiving the synchronized authority and assigning the authority to the region;
specifically, the terminal device where the document account of the collaborator B is located may also receive a collaboration account having a region editing right for each region synchronized by the authority background, and may specify a corresponding collaboration account for each region generated in the terminal page according to the obtained collaboration account corresponding to each region, that is, assign a region editing right of the corresponding collaboration account to each region.
Step S610, whether the current row/column has the authority or not;
specifically, the terminal device where the document account of the collaborator B is located may determine whether the current collaboration account has a region editing right on the row/column that is trying to be operated (i.e., edited) according to the region editing right given to each region in the terminal page. If so, step S612 is executed, otherwise, step S613 is executed.
Step S611, may be operated;
specifically, the terminal device where the document account of the collaborator B is located determines that the document account of the collaborator B has a regional editing right for the row/column which is attempted to be operated, and the terminal device where the document account of the collaborator B is located can respond to the data editing operation of the user and edit the currently operated row/column.
Step S612, no operation is performed, and no permission is informed;
specifically, the terminal device where the document account of the collaborator B is located determines that the document account of the collaborator B does not have the regional editing right on the row/column which is attempted to be operated, and the terminal device where the document account of the collaborator B is located may output no-right prompt information to inform that the collaborator B does not have the regional editing right on the currently operated row/column.
Step S613, receiving the synchronized data, and generating an "area";
specifically, the collaborator C data layer refers to data interaction between the collaborator C document account and the server. The terminal device where the document account of the collaborator C is located may receive each region in the table data synchronized by the data background, and generate each region in the same table data correspondingly in the terminal page of the terminal device.
Step S614, receiving the synchronized authority and assigning the authority to the region;
specifically, the terminal device where the document account of the collaborator C is located may also receive a collaboration account having a region editing right for each region, which is synchronized by the authority background, and may specify a corresponding collaboration account for each region generated in the terminal page according to the obtained collaboration account corresponding to each region, that is, assign a region editing right of the corresponding collaboration account to each region.
Step S615, whether the current row/column has the authority;
specifically, the terminal device where the document account of the collaborator C is located may determine whether the current collaboration account has a region editing right on the row/column that is trying to be operated (i.e., edited) according to the region editing right given to each region in the terminal page. If yes, step S617 is executed, and if not, step S618 is executed.
Step S616, may be operated;
specifically, the terminal device where the document account of the collaborator C is located determines that the document account of the collaborator C has a regional editing right for the row/column which is attempted to be operated, and the terminal device where the document account of the collaborator C is located can respond to the data editing operation of the user and edit the currently operated row/column.
Step S617, no operation is performed, and no permission is notified;
specifically, the terminal device where the document account of the collaborator C is located determines that the document account of the collaborator C does not have the area editing right for the row/column which is attempted to be operated, and the terminal device where the document account of the collaborator C is located may output no-right prompt information to inform that the collaborator C does not have the area editing right for the currently operated row/column.
More, the technical framework for implementing the method provided by the present application includes three layers, which are a rendering layer, a control layer and a data layer. The rendering layer is responsible for rendering the data of the user, displaying the data in a terminal page and displaying the data for the user to view. The rendering layer may include two perspectives, one perspective being the creator's perspective and one perspective being the collaborator's perspective. The visual angle of the creator may include adding permission collaboration areas corresponding to multiple collaborators in batch in the table data, and the like. The perspective of the collaborator may include editing the form data through the form page, etc.
Wherein a control layer may be understood as a bridge between a rendering layer and a data layer. The control layer may be responsible for processing and then synchronizing the data of the user to the rendering layer, that is, the control layer may acquire data related to the table data from the data layer and may resynchronize the acquired data to the rendering layer, so that the rendering layer may display the data related to the table data for the user in the terminal page. The control layer may also synchronize operation behaviors (for example, editing behaviors of a form page, or behaviors of adding collaboration accounts in batches) of the user acquired at a front end (for example, a terminal device) and data (for example, data filled in form data by the selected multiple collaboration accounts and the user) to the data layer, and the data layer may store the data synchronized by the control layer.
As can be seen from the above, the data layer is responsible for storing the data and the behavior after the user operation in the background, and can synchronize the data after the user operation to other users. For example, since the target form data is the form data shared online, the content filled in the target form data by each collaborator is synchronized with the target form data of other collaborators. The logic of the data layer can be seen in the corresponding embodiment of fig. 13 described above.
Please refer to fig. 14, which is a schematic diagram of a technical framework provided in the present application. As shown in fig. 14, the technical framework includes a rendering layer, a control layer, and a data layer. The rendering layer is used for rendering the table data to be presented to a user, the control layer is used for transmitting the required table data related data for the rendering layer and the data layer, and the data layer is used for storing the table data related data. The control layer acts as a bridge between the render layer and the data layer, otherwise known as an intermediary. The control layer needs to include functions including: adding new authority (for example, assigning additional authority to a certain collaboration account), setting keywords (for example, setting a keyword library), intelligently identifying the keywords, recommending and filling forms, rapidly assigning row/column authority, and intelligently converting forms into forms.
Please refer to fig. 15, which is a schematic structural diagram of a table data processing apparatus provided in the present application. As shown in fig. 15, the table data processing apparatus 1 may include: the table acquisition module 11, the area adding module 12 and the synchronization module 13;
the form obtaining module 11 is configured to obtain initial form data, and obtain at least two collaboration accounts corresponding to the initial form data;
the region adding module 12 is configured to add, in response to a trigger operation for at least two collaboration accounts, a permission collaboration region for each of the at least two collaboration accounts in the initial table data, to obtain target table data;
the synchronization module 13 is configured to synchronize the target form data to the collaboration terminals to which the at least two collaboration accounts belong, so that the collaboration terminals to which the at least two collaboration accounts belong respectively edit the corresponding permission collaboration areas in the target form data.
For specific functional implementation manners of the table obtaining module 11, the area adding module 12 and the synchronizing module 13, please refer to steps S101 to S103 in the embodiment corresponding to fig. 3, which is not described herein again.
Wherein the initial form data is created based on the document application;
the table acquisition module 11 includes: a table acquisition unit 111, a batch response unit 112, a mapping account acquisition unit 113, and an account determination unit 114;
a table acquisition unit 111 for acquiring initial table data;
a batch response unit 112, configured to respond to a batch addition operation for the initial form data in the document application, and obtain at least two communication accounts in the communication application;
a mapping account number obtaining unit 113, configured to obtain mapping document account numbers of at least two communication account numbers in a document application, respectively;
the account determining unit 114 is configured to determine, as at least two collaboration accounts, mapping document accounts corresponding to the at least two communication accounts, respectively.
For specific functional implementation manners of the table obtaining unit 111, the batch response unit 112, the mapping account obtaining unit 113, and the account determining unit 114, please refer to step S101 in the embodiment corresponding to fig. 3, which is not described herein again.
The communication application comprises a first communication application and a second communication application; the at least two communication accounts comprise a first communication account in the first communication application and a second communication account in the second communication application; the first communication account and the second communication account have account binding relation in the document application; the first communication account and the second communication account which have the account binding relationship correspond to the same mapping document account.
The region adding module 12 includes: a number setting unit 121, an area adding unit 122, and a mapping relationship adding unit 123;
a quantity setting unit 121, configured to obtain the quantity of each collaboration account in the area corresponding to the right collaboration area;
the area adding unit 122 is configured to add, according to the number of areas corresponding to each collaboration account, a corresponding permission collaboration area for each collaboration account in the initial table data;
a mapping relation adding unit 123, configured to add a mapping relation between the account id of each collaboration account and the corresponding permission collaboration area in the initial table data, to obtain target table data; the mapping relation is used for indicating that each collaboration account number has the region editing authority of the affiliated authority collaboration region.
For a specific function implementation manner of the number setting unit 121, the area adding unit 122, and the mapping relationship adding unit 123, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.
Wherein the at least two collaboration accounts comprise a collaboration account siWherein i is a positive integer less than or equal to the total number of the accounts of the at least two collaborative accounts, and the initial value of i is 1;
a region adding module 12, further configured to:
in the initial table data, collaboration accounts s are arranged in sequenceiAnd adding the permission cooperation area until i is equal to the total number of the accounts, and obtaining target table data.
The at least two collaboration accounts comprise a first collaboration account;
the form data processing apparatus 1 further includes: a table expansion module 14 and a position location module 15;
the table expanding module 14 is configured to respond to an expanding operation of the first collaboration account on the target table data, and expand the target table data;
and the position positioning module 15 is configured to position an area position of the permission cooperation area corresponding to the first collaboration account in the expanded target form data, and highlight the permission cooperation area on the positioned area position.
For a specific implementation manner of the functions of the table expanding module 14 and the position locating module 15, please refer to step S103 in the embodiment corresponding to fig. 3, which is not described herein again.
Wherein, the target table data includes the header data, the table data processing device 1 further includes: a form output module 16, a form input module 17 and a data adding module 18;
the form output module 16 is configured to respond to a form editing operation for a permission cooperation area corresponding to the first collaboration account, and output a form page corresponding to the first collaboration account according to header data of the target form data and the permission cooperation area corresponding to the first collaboration account;
the form entry module 17 is configured to respond to a data entry operation for a form page and obtain form entry data;
and the data adding module 18 is used for adding the form entry data to the permission collaboration area corresponding to the first collaboration account in the target form data.
For specific functional implementation manners of the form output module 16, the form entry module 17, and the data adding module 18, please refer to step S103 in the embodiment corresponding to fig. 3, which is not described herein again.
The permission collaboration area corresponding to the first collaboration account is a unit row in the target table data; the unit row corresponding to the first collaboration account number comprises an authority unit grid;
a form output module 16, comprising: an existing data acquisition unit 161, a cell determination unit 162, and a form output unit 163;
an existing data acquiring unit 161, configured to acquire existing data of cells in at least two target cells in the target table data; the target cell and the authority cell are cells in the same cell column; the data of the cells in the at least two target cells are data recorded in at least two target cells by the collaboration account numbers except the first collaboration account number in the at least two collaboration account numbers;
the cell determining unit 162 is configured to determine, as a calling cell, a target cell having the same existing data of the cell among the at least two target cells;
the form output unit 163 is configured to, when the number of cells of the called cells is greater than the calling number threshold, output a form page corresponding to the first collaboration account according to the existing data of the cells in the called cells, the header data of the target form data, and the permission collaboration area corresponding to the first collaboration account; and calling the existing data of the cells in the cells to be displayed in a data entry area in the form page.
For a specific implementation manner of functions of the existing data obtaining unit 161, the cell determining unit 162, and the form output unit 163, please refer to step S103 in the corresponding embodiment of fig. 3, which is not described herein again.
The header data of the target table data comprises at least two unit table header data;
a form output module 16, comprising: a format recognition unit 164 and a format form output unit 165;
the format identification unit 164 is configured to obtain data entry formats corresponding to the header data of at least two cells;
a format form output unit 165, configured to output a form page corresponding to the first collaboration account according to the data entry format corresponding to each unit form header data, and the permission collaboration area corresponding to the first collaboration account; the form page comprises a data entry area corresponding to each unit form header data; and each data entry area in the form page is respectively provided with a data entry format corresponding to the head data of the corresponding cell.
For a specific implementation manner of the functions of the format recognition unit 164 and the format form output unit 165, please refer to step S103 in the corresponding embodiment of fig. 3, which is not described herein again.
The format recognition unit 164 includes: a data type identification subunit 1641 and a format acquisition unit 1642;
a data type identifying subunit 1641, configured to identify a data type of the header data of each cell, and determine, according to the data type of the header data of each cell, a data entry format corresponding to each of the header data of each cell; or
A format obtaining unit 1642, configured to obtain target entry formats respectively added to each cell header data, as data entry formats respectively corresponding to each cell header data.
For a specific implementation manner of the data type identifying subunit 1641 and the format obtaining unit 1642, please refer to step S103 in the corresponding embodiment of fig. 3, which is not described herein again.
The region adding module 12 includes: a transition acquisition unit 124, a prompt output unit 125, and a prompt response unit 126;
a transition obtaining unit 124, configured to add an authority collaboration area to at least two collaboration accounts in the initial table data synchronously to obtain transition table data corresponding to the at least two collaboration accounts;
a prompt output unit 125 for outputting setting prompt information for the transition table data;
a prompt response unit 126, configured to respond to a confirmation operation for setting prompt information, and set a form editing function for the transition form data to obtain target form data; the form editing function is used to trigger a form editing operation in the target form data.
For specific functional implementation manners of the transition obtaining unit 124, the prompt output unit 125, and the prompt response unit 126, please refer to step S102 in the corresponding embodiment of fig. 3, which is not described herein again.
The prompt output unit 125 includes: a first entry response subunit 1251, a combination cell detection subunit 1252, and a first prompt output subunit 1253;
a first entry response subunit 1251, configured to respond to a data entry operation for a cell in the transition table data, and obtain cell entry data;
a combined cell detecting subunit 1252, configured to determine, when it is detected that the transition table data includes a combined cell according to the cell entry data, and the combined cell is in a target cell bar of the transition table data, the target cell bar as a head cell bar; the unit cells contained in the combined unit cells are adjacent unit cells which are not empty; the number of cells contained in the combined cells is greater than or equal to a first number threshold; the target cell bar is a cell row or a cell column at the starting position of the transition table data;
the first prompt output subunit 1253 is configured to output the setting prompt information for the transition table data according to the cell bar position of the head cell bar.
For specific functional implementation manners of the first entry response subunit 1251, the combined cell detection subunit 1252, and the first prompt output subunit 1253, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.
The prompt output unit 125 includes: a second entry response subunit 1254, a key cell detection subunit 1255, and a second prompt output subunit 1256;
a second entry response subunit 1254, configured to respond to a data entry operation for a cell in the transition table data, and obtain cell entry data;
a key cell detection subunit 1255, configured to determine, when detecting that, according to the cell entry data, a target cell in the transition table data includes key cells whose number is greater than or equal to the second number threshold, the target cell is a head cell; the target cell bar is a cell row or a cell column at the starting position in the transition table data; the key cell is a cell which contains the table head key words and contains the non-table head key words of which the number is less than a third number threshold;
and a second prompt output subunit 1256, configured to output setting prompt information for the transition table data according to the cell bar position of the head cell bar.
For specific functional implementation manners of the second entry response subunit 1254, the key cell detection subunit 1255, and the second prompt output subunit 1256, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.
Wherein the key cells are detected based on a keyword library; the keyword library comprises at least two table head keywords; at least two table head keywords are obtained by word segmentation of table head data in the historical table data.
Wherein, the table data processing device 1 is further configured to:
responding to the editing operation of the first collaboration account aiming at the non-permission collaboration area in the target table data, and outputting prompt information without editing permission; the non-permission cooperation area refers to a permission cooperation area in the target table data except for the permission cooperation area corresponding to the first cooperation account.
The at least two collaboration accounts comprise a second collaboration account; the form data processing apparatus 1 is further configured to:
and adding a newly-added region authority for the second collaboration account, and synchronizing the newly-added region authority to the collaboration terminal to which the second collaboration account belongs, so that the collaboration terminal to which the second collaboration account belongs adds a corresponding authority collaboration region for the newly-added collaboration account in the target form data according to the newly-added region authority.
The method includes the steps that initial form data are obtained, and at least two collaboration accounts corresponding to the initial form data are obtained; responding to triggering operation aiming at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial table data to obtain target table data; and synchronizing the target form data to the cooperation terminals to which the at least two cooperation accounts belong, so that the cooperation terminals to which the at least two cooperation accounts belong respectively edit the corresponding permission cooperation areas in the target form data. Therefore, by the method, the permission cooperation areas of at least two cooperation accounts can be added in place in one step in the initial form data, and the adding efficiency of the permission cooperation areas is improved. Meanwhile, each cooperation account number is respectively allocated with a corresponding authority cooperation area, and each cooperation account number can edit the authority cooperation area belonging to the cooperation account number in the target form data, so that the filling accuracy of the target form data is improved.
Please refer to fig. 16, which is a schematic structural diagram of a computer device provided in the present application. As shown in fig. 16, the computer apparatus 1000 may include: the processor 1001, the network interface 1004, and the memory 1005, and the computer device 1000 may further include: a user interface 1003, and at least one communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display) and a Keyboard (Keyboard), and optionally, the user interface 1003 may also include a standard wired interface and a standard wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may optionally be at least one memory device located remotely from the processor 1001. As shown in fig. 16, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.
In the computer device 1000 shown in fig. 16, the network interface 1004 may provide a network communication function; the user interface 1003 is an interface for providing a user with input; and the processor 1001 may be configured to invoke a device control application stored in the memory 1005 to implement the description of the table data processing method in the corresponding embodiment of fig. 3 above. It should be understood that the computer device 1000 described in this application can also perform the description of the table data processing apparatus 1 in the embodiment corresponding to fig. 15, and the description is not repeated here. In addition, the beneficial effects of the same method are not described in detail.
Further, here, it is to be noted that: the present application further provides a computer-readable storage medium, and the computer-readable storage medium stores therein the computer program executed by the aforementioned table data processing apparatus 1, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the table data processing method in the embodiment corresponding to fig. 3 can be performed, and therefore, details will not be repeated here. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in the embodiments of the computer storage medium referred to in the present application, reference is made to the description of the embodiments of the method of the present application.
It will be understood by those skilled in the art that all or part of the processes of the embodiments may be implemented by the computer program, which may be stored in a computer-readable storage medium, and when executed, may include processes such as those of the embodiments of the methods. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto but rather by the claims appended hereto.

Claims (17)

1. A method for processing tabular data, comprising:
acquiring initial table data; the initial form data is created based on a document application;
responding to batch adding operation aiming at the initial form data in the document application, and acquiring at least two communication accounts in the communication application;
acquiring mapping document accounts of the at least two communication accounts in the document application respectively, and determining the mapping document accounts corresponding to the at least two communication accounts as at least two collaboration accounts corresponding to the initial form data;
responding to triggering operation aiming at the at least two collaboration accounts, and respectively adding an authority collaboration area for each collaboration account in the at least two collaboration accounts in the initial form data to obtain target form data;
and synchronizing the target form data to the collaboration terminals to which the at least two collaboration accounts belong, so that the collaboration terminals to which the at least two collaboration accounts belong respectively edit the corresponding permission collaboration areas in the target form data.
2. The method of claim 1, wherein the communication application comprises a first communication application and a second communication application; the at least two communication accounts comprise a first communication account in the first communication application and a second communication account in the second communication application; the first communication account and the second communication account have an account binding relationship in the document application; and the first communication account and the second communication account which have account binding relationship correspond to the same mapping document account.
3. The method according to claim 1, wherein the adding, in the initial table data, an authority collaboration area for each of the at least two collaboration accounts to obtain target table data includes:
acquiring the number of areas of each collaboration account aiming at the permission collaboration area;
adding a corresponding permission cooperation area for each cooperation account in the initial table data according to the number of the areas corresponding to each cooperation account;
adding a mapping relation between the account identification of each collaboration account and the corresponding permission collaboration area in the initial table data to obtain the target table data; the mapping relation is used for indicating that each collaboration account number has the region editing permission of the right collaboration region.
4. The method of claim 1, wherein the at least two collaboration accounts comprise collaboration account siWherein i is a positive integer less than or equal to the total number of the accounts of the at least two collaborative accounts, and the initial value of i is 1;
adding an authority collaboration area to each of the at least two collaboration accounts in the initial table data to obtain target table data, wherein the method comprises the following steps:
in the initial form data, the collaboration accounts s are sequentiallyiAdding an authority cooperation area until i is equal to the total number of the accounts to obtain the targetTable data.
5. The method of claim 1, wherein the at least two collaboration accounts include a first collaboration account;
the method further comprises the following steps:
responding to the expansion operation of the first collaboration account on the target table data, and expanding the target table data;
and positioning the area position of the authority cooperation area corresponding to the first cooperation account in the expanded target table data, and highlighting the authority cooperation area on the positioned area position.
6. The method of claim 5, wherein the target table data includes header data, and further comprising:
responding to form editing operation aiming at the permission cooperation area corresponding to the first cooperation account, and outputting a form page corresponding to the first cooperation account according to header data of the target form data and the permission cooperation area corresponding to the first cooperation account;
responding to the data entry operation aiming at the form page, and acquiring form entry data;
and adding the form entry data to an authority cooperation area corresponding to the first cooperation account in the target form data.
7. The method according to claim 6, wherein the permission collaboration area corresponding to the first collaboration account is a cell row in the target table data; the unit row corresponding to the first collaboration account number comprises an authority unit grid;
the outputting a form page corresponding to the first collaboration account according to the header data of the target form data and the permission collaboration area corresponding to the first collaboration account includes:
acquiring existing cell data in at least two target cells in the target table data; the target cell and the authority cell are cells in the same cell column; the existing data of the cells in the at least two target cells are data recorded in the at least two target cells by the collaboration account except the first collaboration account in the at least two collaboration accounts;
determining the target cells with the same cell existing data in the at least two target cells as calling cells;
when the number of the cells of the calling cells is larger than a calling number threshold, outputting the form page corresponding to the first collaboration account according to the existing cell data in the calling cells, the header data of the target form data and the permission collaboration area corresponding to the first collaboration account; and the data existing in the cells in the calling cells are displayed in the data entry area of the form page.
8. The method according to claim 6, wherein the header data of the target table data comprises at least two cell header data;
the outputting a form page corresponding to the first collaboration account according to the header data of the target form data and the permission collaboration area corresponding to the first collaboration account includes:
acquiring data entry formats corresponding to the at least two cell header data respectively;
outputting the form page corresponding to the first collaboration account according to a data entry format corresponding to each cell header data, each cell header data and a permission collaboration area corresponding to the first collaboration account; the form page comprises data entry areas corresponding to the header data of each cell respectively; and each data entry area in the form page is respectively provided with a data entry format corresponding to the form head data of the corresponding cell.
9. The method according to claim 8, wherein the obtaining of the data entry formats corresponding to the at least two cell header data respectively comprises:
identifying the data type of the head data of each cell, and determining the data entry format corresponding to the head data of each cell according to the data type of the head data of each cell; or
And acquiring target entry formats respectively added to the head data of each cell, and taking the target entry formats as data entry formats respectively corresponding to the head data of each cell.
10. The method according to claim 6, wherein the adding, in the initial table data, an authority collaboration area for each of the at least two collaboration accounts to obtain target table data includes:
synchronously adding permission collaboration areas for the at least two collaboration accounts in the initial form data to obtain transition form data corresponding to the at least two collaboration accounts;
outputting setting prompt information aiming at the transition table data;
responding to the confirmation operation aiming at the setting prompt information, and setting a form editing function for the transition form data to obtain the target form data; the form editing function is used for triggering the form editing operation in the target form data.
11. The method of claim 10, wherein outputting the setting hint information for the transition table data comprises:
responding to data entry operation aiming at the cells in the transition table data, and acquiring cell entry data;
when detecting that the transition table data comprises combined cells according to the cell entry data and the combined cells are in a target cell bar of the transition table data, determining the target cell bar as a head cell bar; the unit cells contained in the combined unit cells are adjacent unit cells which are not empty; the number of the cells contained in the combined cell is greater than or equal to a first number threshold; the target cell bar is a cell row or a cell column at a starting position of the transition table data;
and outputting the setting prompt information aiming at the transition table data according to the position of the cell bar of the head cell bar.
12. The method of claim 10, wherein outputting the setting hint information for the transition table data comprises:
responding to data entry operation aiming at the cells in the transition table data, and acquiring cell entry data;
when a target cell bar in the transition table data is detected according to the cell entry data and comprises key cells with the number larger than or equal to a second number threshold, determining the target cell bar as a head cell bar; the target cell bar is a cell row or a cell column at a starting position in the transition table data; the key cell is a cell which contains the table head key words and contains non-table head key words of which the number is less than a third number threshold;
and outputting the setting prompt information aiming at the transition table data according to the position of the cell bar of the head cell bar.
13. The method of claim 5, further comprising:
responding to the editing operation of the first collaboration account aiming at the non-permission collaboration area in the target table data, and outputting prompt information without editing permission; the non-permission cooperation area refers to a permission cooperation area in the target table data except for the permission cooperation area corresponding to the first cooperation account.
14. The method of claim 1, wherein the at least two collaboration accounts include a second collaboration account;
the method further comprises the following steps:
and adding a newly-added region authority to the second collaboration account, and synchronizing the newly-added region authority to a collaboration terminal to which the second collaboration account belongs, so that the collaboration terminal to which the second collaboration account belongs adds a corresponding authority collaboration region to the newly-added collaboration account in the target form data according to the newly-added region authority.
15. A form data processing apparatus, comprising:
the table acquisition module is used for acquiring initial table data; the initial form data is created based on a document application;
the form acquisition module is further used for responding to batch adding operation aiming at the initial form data in the document application and acquiring at least two communication accounts in the communication application;
the form obtaining module is further configured to obtain mapping document accounts of the at least two communication accounts in the document application, and determine mapping document accounts corresponding to the at least two communication accounts as at least two collaboration accounts corresponding to the initial form data;
the area adding module is used for responding to triggering operation aiming at the at least two collaboration accounts, and adding an authority collaboration area for each of the at least two collaboration accounts in the initial table data to obtain target table data;
and the synchronization module is used for synchronizing the target form data to the collaboration terminals to which the at least two collaboration accounts belong so that the collaboration terminals to which the at least two collaboration accounts belong respectively edit the corresponding permission collaboration areas in the target form data.
16. A computer arrangement comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1-14.
17. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program adapted to be loaded by a processor and to perform the method of any of claims 1-14.
CN202010485914.7A 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium Active CN112632928B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010485914.7A CN112632928B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium
CN202111124081.2A CN113779942B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010485914.7A CN112632928B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202111124081.2A Division CN113779942B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN112632928A CN112632928A (en) 2021-04-09
CN112632928B true CN112632928B (en) 2021-09-28

Family

ID=75300071

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202111124081.2A Active CN113779942B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium
CN202010485914.7A Active CN112632928B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202111124081.2A Active CN113779942B (en) 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium

Country Status (1)

Country Link
CN (2) CN113779942B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114528816B (en) * 2022-01-27 2023-03-17 北京飞书科技有限公司 Collaborative editing information display method and device, electronic equipment and readable medium
CN114282503A (en) * 2022-03-04 2022-04-05 中铁第一勘察设计院集团有限公司 Method, system and storage medium for generating technical record book of railway communication equipment
CN115344163A (en) * 2022-07-07 2022-11-15 珠海金山办公软件有限公司 Form cooperation method and device, electronic equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105023188A (en) * 2015-01-07 2015-11-04 泰华智慧产业集团股份有限公司 Digitized city management data sharing system based on cloud data
CN107680690A (en) * 2016-08-02 2018-02-09 四川智康科技有限责任公司 A kind of clinic information system based on metadata
US10565404B2 (en) * 2015-11-02 2020-02-18 Microsoft Technology Licensing, Llc Autodetection of types and patterns
US10565403B1 (en) * 2018-09-12 2020-02-18 Atlassian Pty Ltd Indicating sentiment of text within a graphical user interface

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11203177A (en) * 1998-01-12 1999-07-30 Matsushita Electron Corp Data management device, data management method and computer readable recording medium recording data management program
US9330080B2 (en) * 2011-06-27 2016-05-03 Sap Se Methods and systems to facilitate providing spreadsheet and database data to users via a social network
US10133720B2 (en) * 2013-06-15 2018-11-20 Microsoft Technology Licensing, Llc Showing presence of multiple authors in a spreadsheet
KR20160062565A (en) * 2014-11-25 2016-06-02 삼성전자주식회사 Device and method for providing handwritten content
US9798889B1 (en) * 2015-08-12 2017-10-24 Workday, Inc. Spreadsheet shared region and cell permissions
US10083162B2 (en) * 2016-11-28 2018-09-25 Microsoft Technology Licensing, Llc Constructing a narrative based on a collection of images
EP4231137A1 (en) * 2017-12-03 2023-08-23 Thomas Stachura Spreadsheet-based software application development
CN109522533A (en) * 2018-10-12 2019-03-26 平安科技（深圳）有限公司 Table edit method, apparatus, equipment and medium based on web data
CN111144074B (en) * 2018-11-05 2022-04-22 腾讯科技（深圳）有限公司 Document cooperation method and device, computer readable storage medium and computer equipment
CN109814944A (en) * 2018-12-25 2019-05-28 深圳云天励飞技术有限公司 Configuring management method and Related product
CN110008447A (en) * 2019-03-26 2019-07-12 湖南华美信息系统有限公司 The processing method and processing device of electrical form
CN110019279B (en) * 2019-04-11 2020-12-04 北京字节跳动网络技术有限公司 Online document collaborative updating method, device, equipment and storage medium
CN111126022A (en) * 2020-01-06 2020-05-08 深圳维格智数科技有限公司 Data synchronization protocol and method for real-time cooperation on-line electronic form

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105023188A (en) * 2015-01-07 2015-11-04 泰华智慧产业集团股份有限公司 Digitized city management data sharing system based on cloud data
US10565404B2 (en) * 2015-11-02 2020-02-18 Microsoft Technology Licensing, Llc Autodetection of types and patterns
CN107680690A (en) * 2016-08-02 2018-02-09 四川智康科技有限责任公司 A kind of clinic information system based on metadata
US10565403B1 (en) * 2018-09-12 2020-02-18 Atlassian Pty Ltd Indicating sentiment of text within a graphical user interface

Also Published As

Publication number Publication date
CN113779942B (en) 2023-08-18
CN112632928A (en) 2021-04-09
CN113779942A (en) 2021-12-10

Similar Documents

Publication Publication Date Title
CN112632928B (en) Table data processing method and device and computer readable storage medium
CN112866785B (en) Picture generation method, device, equipment and storage medium
CN106682219B (en) Associated document acquisition method and device
CN112632942A (en) Document processing method, device, equipment and medium
CN110475140B (en) Bullet screen data processing method and device, computer readable storage medium and computer equipment
JP5642890B2 (en) Method, terminal and computer-readable recording medium for supporting collection of objects contained in a generated image
CN117668402A (en) System and method for applying layout to document
CN104252359A (en) Systems and methods for presentations with live application integration
CN111541946A (en) Automatic video generation method and system for resource matching based on materials
US20220222310A1 (en) Method and apparatus for generating web page
CN104252442A (en) Systems and methods for presentations with live application integration
CN112965701A (en) Front-end code generation method and device
CN112131837B (en) Service report configuration method, device, computer equipment and storage medium
US20230409816A1 (en) Document update method and apparatus, device, and medium
CN114861623A (en) Protocol template generation method and device, electronic equipment and storage medium
CN115329131A (en) Material label recommendation method and device, electronic equipment and storage medium
CN109189293B (en) Evaluation interaction method and device for rich media content, electronic equipment and storage medium
CN110134920B (en) Pictogram compatible display method, device, terminal and computer readable storage medium
CN114239524A (en) Questionnaire generation method, questionnaire generation device, computer equipment and storage medium
CN107133204B (en) Terminal shortcut input method
CN112035113A (en) Navigation bar loading method, device, equipment and medium of H5 page
CN112528204B (en) Method and device for manufacturing thematic webpage
CN114691926A (en) Information display method and electronic equipment
CN110609968B (en) Image-text information sorting processing method, device and equipment
CN114443022A (en) Method for generating page building block and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40042481

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant