CN113779942B - 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
CN113779942B
CN113779942B CN202111124081.2A CN202111124081A CN113779942B CN 113779942 B CN113779942 B CN 113779942B CN 202111124081 A CN202111124081 A CN 202111124081A CN 113779942 B CN113779942 B CN 113779942B
Authority
CN
China
Prior art keywords
data
account
target
cell
collaboration
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
CN202111124081.2A
Other languages
Chinese (zh)
Other versions
CN113779942A (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 CN202111124081.2A priority Critical patent/CN113779942B/en
Publication of CN113779942A publication Critical patent/CN113779942A/en
Application granted granted Critical
Publication of CN113779942B publication Critical patent/CN113779942B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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)
  • Bioethics (AREA)
  • Computational Linguistics (AREA)
  • Artificial Intelligence (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Document Processing Apparatus (AREA)

Abstract

The application discloses a method and a device for processing table data and a computer readable storage medium, wherein the method comprises the following steps: acquiring initial table data, and acquiring at least two cooperative accounts corresponding to the initial table data; responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial form data to obtain target form data; synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively. By adopting the method and the device, the filling accuracy of the target form data can be improved, and the adding efficiency of the authority cooperation area can be improved.

Description

Table data processing method and device and computer readable storage medium
The present application is a divisional application of chinese patent application filed on month 01 of 2020, filed in chinese patent office with application number 2020104859147, application name "a form data processing method, apparatus, and computer-readable storage medium", the entire contents of which are incorporated herein by reference.
Technical Field
The present application relates to the field of document data processing, and in particular, to a method and apparatus for processing table data, and a computer readable storage medium.
Background
With the development of computer networks, more and more things are being handled online, which involves the collaboration of multiple people to complete the filling of a form.
Typically, for a shared online form document, the online form document will typically have multiple fillers that together complete the filling of the online form document. When the plurality of filling persons fill in the online form document, the plurality of filling persons may fill in the same line in the online form document, which may cause the content filled in by the subsequent filling persons in the online form document to overlap the content filled in by the previous filling persons in the online form document, thereby causing a problem of data loss.
Thus, in the prior art, when a plurality of people finish filling the online form document together, filling errors are easy to cause.
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, as corresponding authority cooperation areas can be added for a plurality of cooperation accounts in batches, the adding efficiency of the authority cooperation areas is improved.
One aspect of the present application provides a method for processing table data, including:
acquiring initial table data, and acquiring at least two cooperative accounts corresponding to the initial table data;
responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial form data to obtain target form data;
synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively.
In one aspect, the present application provides a form data processing apparatus, including:
the table acquisition module is used for acquiring initial table data and acquiring at least two cooperative accounts corresponding to the initial table data;
the region adding module is used for responding to the triggering operation aiming at the at least two cooperative accounts, and adding an authority cooperation region for each cooperative account in the at least two cooperative accounts in the initial table data to obtain target table data;
and the synchronization module is used for synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively.
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 addition 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 acquisition unit is used for acquiring mapping document accounts of at least two communication accounts 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 as at least two cooperative 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 a first communication application and a second communication account in a second communication application; the first communication account number and the second communication account number have account number binding relation in the document application; the first communication account number and the second communication account number with account number binding relation correspond to the same mapping document account number.
Wherein, the region adding module includes:
the quantity setting unit is used for acquiring the quantity of the areas of each cooperative account aiming at the authority cooperation areas respectively;
The region adding unit is used for adding a corresponding authority cooperation region for each cooperative account in the initial table data according to the number of regions respectively corresponding to each cooperative account;
the mapping relation adding unit is used for adding the mapping relation between the account identification of each cooperative account and the corresponding authority cooperation area in the initial table data respectively to obtain target table data; the mapping relationship is used for indicating that each cooperative account has the region editing authority for the affiliated authority cooperation region.
Wherein the at least two cooperative accounts include a cooperative account s i Wherein i is a positive integer less than or equal to the total number of the accounts of the at least two cooperative accounts, and the initial value of i is 1;
the region adding module is further used for:
in the initial table data, the collaboration account number s is in turn i And adding the authority cooperation area until i is equal to the total number of the accounts, and obtaining target table data.
Wherein the at least two collaborative accounts include a first collaborative account;
the form data processing apparatus further includes:
the form unfolding module is used for responding to the unfolding operation of the first collaborative account for the target form data and unfolding the target form data;
the position locating module is used for locating the region position of the authority cooperation region corresponding to the first cooperation account in the expanded target table data and highlighting the authority cooperation region in the located region position.
Wherein, the target table data comprises table head data, and the table data processing device further comprises:
the form output module is used for responding to a form editing operation aiming at the authority cooperation area corresponding to the first cooperation account, and outputting a form page corresponding to the first cooperation account according to the header data of the target form data and the authority cooperation area corresponding to the first cooperation account;
the form input module is used for responding to the data input operation aiming at the form page and acquiring form input data;
the data adding module is used for adding the form input data into the authority cooperation area corresponding to the first cooperation account in the target form data.
The authority collaboration area corresponding to the first collaboration account is a unit row in the target table data; the unit row corresponding to the first collaborative account comprises authority unit cells;
a form output module comprising:
the existing data acquisition unit is used for acquiring cell existing 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 cell existing data in the at least two target cells are the collaborative account numbers except the first collaborative account number in the at least two collaborative account numbers, and the data is recorded in the at least two target cells;
The cell determining unit is used for determining 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 data of the cells in the calling cell, the header data of the target form data and the authority collaboration area corresponding to the first collaboration account when the number of the cells of the calling cell is larger than the threshold value of the calling number; the cells in the calling cell have data displayed in the data entry area in the form page.
Wherein, the header data of the target table data comprises at least two cell header data;
a form output module comprising:
the format identification unit is used for acquiring data input formats respectively corresponding to the at least two cell header data;
the format form output unit is used for outputting a form page corresponding to the first collaborative account according to the data input format corresponding to each cell header data, each cell header data and the authority collaboration area corresponding to the first collaborative account; the form page comprises data input areas corresponding to the header data of each unit cell respectively; each data entry area in the form page is provided with a data entry format corresponding to the data of the corresponding cell header.
Wherein the format recognition unit includes:
the data type identification subunit is used for identifying the data type of each cell header data and determining the data entry format respectively corresponding to each cell header data according to the data type of each cell header data; or alternatively
The format acquisition unit is used for acquiring the target input format respectively added for each piece of cell header data as the data input format respectively corresponding to each piece of cell header data.
Wherein, the region adding module includes:
the transition acquisition unit is used for synchronously adding authority cooperation areas for at least two cooperation accounts in the initial table data to obtain transition table data corresponding to the at least two cooperation accounts;
the prompt output unit is used for outputting setting prompt information aiming at the transition form data;
the prompt response unit is used for responding to the confirmation operation aiming at the setting prompt information, setting a form editing function for the transition form data and obtaining target form data; the form editing function is used for triggering a form editing operation in the target form data.
Wherein, the suggestion output unit includes:
the first input response subunit is used for responding to the data input operation aiming at the cells in the transition form data and acquiring the cell input data;
A combined cell detection subunit, configured to determine, when it is detected that the transition form data includes a combined cell according to the cell entry data and the combined cell is in a target cell stripe of the transition form data, the target cell stripe as a header cell stripe; the unit cells included in the combined unit cell are adjacent unit cells which are not empty; the number of cells included 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 the starting position of the transition table data;
the first prompt output subunit is used for outputting setting prompt information aiming at the transition form data according to the cell bar position of the header cell bar.
Wherein, the suggestion output unit includes:
the second input response subunit is used for responding to the data input operation aiming at the cells in the transition form data and acquiring the cell input data;
the key cell detection subunit is used for determining the target cell bar as a header cell bar when the target cell bar in the transition table data is detected according to the cell entry data and the number of the key cells is larger than or equal to a second number threshold value; the target cell bar is a cell row or a cell column at a starting position in the transition table data; the key cells are cells containing header keywords and containing non-header keywords with the number smaller than a third number threshold;
And the second prompt output subunit is used for outputting setting prompt information aiming at the transition form data according to the cell bar position of the header cell bar.
Wherein the key cells are detected based on a keyword library; the keyword library comprises at least two header keywords; the at least two header keywords are obtained by word segmentation of header data in the historical table data.
Wherein, the table data processing device is further used for:
responding to the editing operation of the first collaboration account aiming at the non-authority collaboration area in the target form data, and outputting prompt information without editing authority; the non-authority cooperation area refers to an authority cooperation area except the authority cooperation area corresponding to the first cooperation account in the target table data.
Wherein the at least two collaborative accounts include a second collaborative account; the table data processing device is further used for:
adding a new region authority for the second cooperative account, synchronizing the new region authority to a cooperative terminal to which the second cooperative account belongs, so that the cooperative terminal to which the second cooperative account belongs adds a corresponding authority cooperative region for the new cooperative account in the target table data according to the new region authority.
In one aspect 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 one aspect of the application.
An aspect of the application provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of the aspect.
The method comprises the steps of obtaining initial form data, and obtaining at least two cooperative accounts corresponding to the initial form data; responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial form data to obtain target form data; synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively. Therefore, according to the method provided by the application, the authority 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 authority cooperation areas is improved. Meanwhile, as the corresponding authority cooperation areas are respectively allocated to each cooperation account, each cooperation account can edit the authority cooperation areas belonging to the user 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 application or the technical solutions of the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it being obvious that the drawings in the description below are only some embodiments of the application, and that other drawings can be obtained from them without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system architecture according to the present application;
FIG. 2a is a schematic diagram of a scenario for table data processing provided by the present application;
FIG. 2b is a schematic diagram of a scenario for table data processing provided by the present application;
FIG. 3 is a schematic flow chart of a method for processing table data according to the present application;
fig. 4a is a schematic page diagram of a terminal page according to the present application;
fig. 4b is a schematic page diagram of a terminal page according to the present application;
fig. 5a is a schematic page diagram of a terminal page according to 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 according to the present application;
FIG. 6 is a schematic diagram of a terminal page for data recommendation provided by the present application;
FIG. 7 is a schematic diagram of a terminal page according to the present application;
FIG. 8 is a schematic diagram of a form page provided by the present application;
fig. 9 is a schematic view of a scenario for obtaining a header unit bar provided by the present application;
FIG. 10 is a flow chart of a form generating method provided by the application;
FIG. 11a is a schematic flow chart of a method for obtaining keyword libraries according to the present application;
FIG. 11b is a schematic flow chart of a method for detecting a critical cell according to the present application;
FIG. 11c is a schematic flow chart of an intelligent recommendation method provided by the application;
FIG. 12 is a schematic flow chart of a method for adding regions according to the present application;
FIG. 13 is a flow chart of a method for processing tabular data provided by the present application;
FIG. 14 is a schematic diagram of a technical framework provided by the present application;
FIG. 15 is a schematic diagram of a form data processing apparatus according to the present application;
fig. 16 is a schematic structural diagram of a computer device according to the present application.
Detailed Description
The following description of the embodiments of the present application will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the application are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a schematic diagram of a system architecture according to 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. Wherein the terminal device 200a, the terminal device 200b, and the terminal device 200c are all capable of communicating with the server 100. The terminal device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (mobile internet device, MID), a virtual device or a wearable device (e.g., a smart watch, a smart bracelet, etc.), etc. The description of the present application is made here by taking the communication between the terminal device 200a and the server 100 as an example, please refer to the following procedure.
Referring to fig. 2a and fig. 2b, fig. 2a is a schematic view of a table data processing scenario provided by the present application, and fig. 2b is a schematic view of a table data processing scenario 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 one terminal page in the terminal device 200a, and the terminal page 121a may be one application page in the installed document application or may be one 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", "number of study", "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.
Further, a control 100a is provided in the terminal page 121a, where the control 100a is configured to add, in a form document, a corresponding authority collaboration area for a collaborator of the form document in batches, and the authority collaboration area corresponding to the collaborator may be one column, multiple columns, one line, or multiple lines in the form document. A collaborator of a form document refers to a person filling in the form document, which person may be plural, and plural in the present application refers to at least two. The method comprises the following steps: the terminal device 200a may display the terminal page 122a in response to a click operation of the control 100a in the terminal page 121a by the user. It is understood that the control 100a may be triggered by a clicking operation, or by a voice command, which is not limited thereto. The terminal page 122a includes one more selection frame 101a than the terminal page 121a, and the selection frame 101a includes an option "designate row fill-out" and an option "designate column fill-out". Wherein, the designated row filling person refers to that the authority cooperation area added for each cooperator is one row or a plurality of rows in the form document. The designated column fill-in refers to the rights collaboration area added for each collaborator as one or more columns in the form document. The description of the present application will be made here by taking a designated line-filling person as an example.
The terminal device 200a may display the terminal page 123a in response to a click operation by the user for the option "designate line filler" in the selection frame 101 a. As shown in terminal page 123a, terminal page 123a has a new column 102a as compared to terminal page 122 a. The newly added column 102a is the column preceding the header content in the table document. That is, the terminal apparatus 200a newly adds the column 102a at column 1 (i.e., column a) of the form document by responding to a click operation by the user for the option "designate row filler" in the selection frame 101 a.
A corresponding collaborator may be added separately for each row in the table document via column 102a, e.g., a "reddish (example)" included in column 102a at the location of row 2, indicating that row 2 of the table document can only be edited by reddish, and that no other person can edit row 2 of the table document. Also included in column 102a are a plurality of "Add Filler" controls, each of which can be assigned to a respective collaborator by each of the "Add Filler" controls in column 102a.
Here, the terminal device 200a may display the terminal page 124a in response to a click operation by the user on the "add filler" control 103a in the column 102a, the control 103a being in row 3 in the column 102a. The terminal page 124a has more pages 104a than the terminal page 123a, and it is understood that the pages 104a may be a popup window or may be a sub-page independently displayed on the terminal page 123a. Included in page 104a are search box 112a, region 111a, and "add-in-batch" control 105a. The search box 112a is used to support that the user can search for the collaborators corresponding to line 3. Assuming that the document account registered in the document application of the current terminal device 200a is the document account of the target user, the search box 112a may be used to support the target user to search for the corresponding friend as the 3 rd line collaborator in the address book of the document account of the target user, where the document application of the terminal device 200a may be the document application installed in the terminal device 200a or the document application entered in the 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 respond to the selection operation of the user for the friends in the area 111a, and take the selected friends as the current-row collaborators. The terminal device 200a may obtain the friend selected by the user through the search box 112a or the area 111a, and use the friend as the 3 rd line collaborator, so as to add the corresponding collaborator for each line in the table document line by line.
In addition, the "batch add filler" control 105a in page 104a can 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 click operation of the control 105a by the user. The terminal page 125a has 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. The support target user selects a plurality of collaborators for the form document in the terminal page 124a, specifically: supporting a target user to search friends in the address book in a search box 120a as collaborators of the table document; or, the region 113a displays friends in the address book of the document account of the target user, and 32 friends in total, so that the target user is supported to slide up and down in the region 113a to view more friends in the document account, and the target user is supported to select one or more friends from the friends displayed in the region 113a as the collaborators of the table document; alternatively, the terminal device 200a may initiate the third party application in response to the target user clicking on the "invite friends" control 107a in the page 106a, inviting friends in the address book of the third party application to act as collaborators of the form document. The third party application is different from the document application, and can be an instant messaging application or a plurality of third party applications. And supporting the target user to invite friends in address books of different third-party applications as collaborators of the form document.
In region 110a in page 106a, 13 collaborators selected by the target user, including user "day", user "happy", user "flower" and user "flower" are displayed, supporting the target user to slide up and down in region 110a to see more of the selected collaborators. When the target user completes the selection of the collaborators on the form document in the page 106a, the terminal device 200a may respond to the selection operation of the target user for the "send work form simultaneously to the counterpart" control 108a in the page 106a, and respond to the click operation of the target user for the "complete" control 109a in the page 106a, add the permission collaboration area for each collaborator selected in turn in the form document, here, add a row for each collaborator as its editable permission collaboration area, respectively. After the addition of the authority collaboration area for 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 created form document. Since the terminal device 200a may detect that the target user has previously selected the "send simultaneously working form to opposite" control 108a in page 106a, the terminal device 200a may send the created form document to each of the collaborators, either to the document account held by each of the collaborators, respectively.
As shown in the terminal page 126a, the created form document displayed in the terminal page 126a includes header content and the authority 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 designated fill-in person (i.e., the collaborator, i.e., the reddish color (example)) on line 2 displayed in the terminal page 124a gives examples for the document application that are not the collaborators added by the target user, the examples given by the document application, i.e., the collaborators "reddish color (example)", are automatically deleted when the form document in the terminal page 126a is generated, and the rights collaboration area is added for each of the selected collaborators, respectively, starting from line 2. As shown in the terminal page 126a, a rights coordination area 115a is added for the collaborator "day" and the rights coordination area 115a indicates that only the collaborator "day" has editing rights for the 2 nd row in the created form document; a rights collaboration area 116a is added for the collaborator "music", the rights collaboration area 116a being the 3 rd line in the created form document, indicating that only the collaborator "music" has editing rights for the 3 rd line; a rights cooperation area 117a is added for the collaborator "flower", and the rights cooperation area 117a indicates that only the collaborator "flower" has editing rights for the 4 th row in the created form document; a rights collaboration area 118a is added for the collaborator "flowers", the rights collaboration area 118a indicating that only the collaborator "flowers" have editing rights for line 5 for the 5 th line in the created form document; rights collaboration area 119a is added for the collaborators "cocoa", rights collaboration area 119a being the 6 th row in the created form document, indicating that only the collaborators "cocoa" have editing rights for the 6 th row, … ….
Wherein the server 100 is a background server of the document application, when the terminal device 200a generates a form document in the terminal page 126a in response to a user operation of the target user, the terminal device 200a transmits 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 the 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, form documents displayed in the above-described terminal page 121a, terminal page 123a, and terminal page 126 a. In other words, the form document displayed by the terminal device 200a is generated by the server 100. Further, when the terminal device 200a transmits the created form data to each of the cooperators, the terminal device 200a may transmit a related operation instruction to the server 100, and the server 100 may transmit the created form document to the document account of each of the cooperators according to the operation instruction.
Alternatively, the terminal device 200a may independently generate a form document and transmit the created form document to the document account of each partner. In other words, the terminal device 200a may also generate a corresponding form document without passing through the server 100, and transmit the created form document to the document account of each partner. Therefore, the execution subject for generating the corresponding form document and transmitting the created form document to the document account of the collaborator may be the server 100 or the terminal device 200a, which is not limited specifically according to the actual application scenario.
By adopting the method provided by the application, the corresponding authority cooperation areas can be synchronously added for the selected plurality of collaborators in the form document, the user operation is simplified, and the efficiency of adding the authority cooperation areas for the plurality of collaborators in the form document is improved.
Referring to fig. 3, a flow chart of a table data processing method provided by the present application is shown in fig. 3, where the method may include:
step S101, initial form data are obtained, and at least two cooperative accounts corresponding to the initial form data are obtained;
specifically, the execution body in this embodiment may be any one terminal device. The target terminal device will be described here 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. And assuming that the target terminal equipment is held by the target user, logging in a document application installed in the target terminal equipment to obtain a document account number registered in the document application by the target user. The target terminal device may generate the initial table data in the document application in response to a user operation of the target user, where the initial table data is empty when generated, that is, no content is added. In other words, the initial form data is the generated empty form data.
Alternatively, the initial form data may be one that is imported by the target user into the target terminal device, in other words, the initial form data may not be null.
Then, the target terminal device may respond to the batch adding operation of the target user on the initial form data, and obtain at least two collaborative accounts corresponding to the initial form data, where a button of one batch adding collaborator may be provided in the document application, and the batch adding operation may refer to a clicking operation of the target user on the button of the batch adding collaborator, for example, a clicking operation of the "batch adding fill-in" button 105a in fig. 2b described above. The sources of acquisition of the at least two cooperative account numbers of the initial form data may be:
the target terminal equipment can respond to batch adding operation of the target user on the initial form data, acquire a plurality of contacts in an address book of a document account of the target user, and take the document account of the plurality of contacts as at least two cooperative accounts of the initial form data.
Or, the target terminal device may also jump from the document application to the third party application in response to the batch adding operation of the target user on the initial form data, and because the user account of the target user is logged in the third party application, the target terminal device may obtain multiple contacts of the target user in the address book of the third party application, and take the document account corresponding to the multiple contacts in the document application as at least two collaborative accounts of the initial form data. In this case, the plurality of contacts acquired from the address book of the third party application need to register the corresponding document account in the document application through the user account in the third party application. In other words, at least two cooperative accounts corresponding to the initial table data are all 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 a contact music, which is equivalent to acquiring a user account of the contact music in the third party application, and a document account corresponding to the user account of the contact music in the third party application may be used as the collaborative 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, which may be an instant messaging application, and may refer to a user account of the user in the third party application as a communication account. Therefore, the step of obtaining the plurality of contact persons of the target user in the address book of the third party application refers to obtaining a plurality of communication account numbers corresponding to the plurality of contact persons of the target user in the address book of the communication application. The document account obtained by mapping and registering the communication account of the user in the communication application in the document application can be called as a mapped document account. The plurality of mapping document accounts corresponding to the plurality of communication accounts acquired in the communication application can be used as a plurality of collaborative accounts of the initial form data.
More, there may be a plurality of third party applications, for example, two, the two third party applications being a first communication application and a second communication application. If the first communication account number registered in the first communication application and the second communication account number registered in the second communication application have an account number binding relationship in the document application, the first communication account number and the second communication account number correspond to the same mapping document account number in the document application. Therefore, if the target user selects the mapped document account corresponding to the first communication account and the second communication account as the collaborative account of the initial table data at the same time, only the same mapped document account corresponding to the first communication account and the second communication account can be obtained, and the repeated addition of the corresponding authority collaboration area for the collaborative account of the same collaborator can be avoided in this way.
The plurality of collaborative accounts of the initial form data may only include document accounts of contacts in an address book of the document account of the target user; or only includes the document account number of the contact person of the target user in the address book of the third party application; or the document account numbers of the contacts in the address book of the document account numbers of the target users are included, and the document account numbers of the contacts of the target users in the address book of the third-party application are also included; and if the plurality of third-party applications exist, the plurality of collaborative accounts of the initial form data can also simultaneously comprise document accounts of contacts of the target user in address books of different third-party applications.
Step S102, responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial table data to obtain target table data;
specifically, after acquiring a plurality of collaborative accounts of initial table data, the target terminal device may respond to a triggering operation of the target user on the plurality of collaborative accounts, and respectively add a corresponding authority collaboration area for each collaborative account in the initial table data to obtain the target table data. Wherein the triggering operation may refer to the clicking operation described above with respect to the "done" control 109a in fig. 2 b. In the initial table data, the process of adding the authority collaboration area for each collaboration account may be: a random sequence can be determined among a plurality of cooperative accounts of the initial table data, and a corresponding authority cooperation area can be added for each cooperative account in the initial table data in turn according to the random sequence; or, according to the selection sequence of the target user on the plurality of cooperative accounts, a corresponding authority cooperation area is added for each cooperative account in the initial table data in sequence, and the previously selected cooperative account is preferentially generated. Wherein, the authority collaboration area added by one collaboration account number in the initial table data can be one column, one row, multiple rows or multiple columns.
Wherein the collaborative account may be noted as collaborative account s i I is a positive integer less than or equal to the total number of accounts of the collaborative accounts 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, namely, i is more than or equal to 1 and less than or equal to n, and n cooperative accounts are all used. 1 can be taken from i, i.e. the collaborative account number s 1 Initially, the collaboration account number s is in turn in the initial form data i Adding corresponding authority collaboration areas, adding 1 to the current i each time until the final i is equal to n, namely indicating that the current i is the collaboration account number s 1 Collaborative account number s 2 … … and collaborative account number s n Corresponding authority cooperation areas are addedDomain.
The target terminal device adds a corresponding authority collaboration area for each collaboration account in the initial table data, and may also be completed through a background server (hereinafter referred to as a server) of the document application. The terminal equipment can synchronize a plurality of collaboration accounts selected by the user to the server, and the server can add corresponding authority collaboration areas for each collaboration account in sequence, and after the addition is completed. The server can synchronize the authority collaboration areas corresponding to the collaboration accounts to the target terminal equipment, and the target terminal equipment can correspondingly generate the authority collaboration areas corresponding to the collaboration accounts in the terminal page according to the authority collaboration areas corresponding to the collaboration accounts obtained from the server.
More, after the target terminal device obtains a plurality of collaboration accounts selected by the target user for the initial form data, the target terminal device further supports the target user to set a corresponding area number for each collaboration account. Wherein a row in the table data may be referred to as a cell row and a column may be referred to as a cell column. If the corresponding authority collaboration area is added for each collaboration account according to the row, one authority collaboration area may refer to a row, the number of areas is the number of rows of the unit row, and the number of areas corresponding to each collaboration account is the number of areas of the authority collaboration area that need to be added for each collaboration account, that is, the number of rows of the unit row that need to be added for each collaboration account. If the corresponding authority collaboration area is added to each collaboration account according to the "column", one authority collaboration area may refer to one column, where the number of areas is the number of columns of the unit columns, and the number of areas corresponding to each collaboration account is the number of areas that need to be added to each collaboration account, that is, the number of columns of the unit columns that need to be added to each collaboration account. More, a default value of the number of areas corresponding to each cooperative account may be set, where the default value may be 1, etc. If the target terminal equipment acquires the number of the areas set by the target user for the collaborative account, the target terminal equipment can add the corresponding authority collaboration area for the collaborative account according to the number of the areas set by the target user for the collaborative account, and the number of rows or columns of the unit rows in the authority collaboration area added for the collaborative account in the initial table data is the number of the areas corresponding to the collaborative account. If the target terminal equipment does not acquire the number of the areas set by the target user for the collaborative account, the target terminal equipment can add the corresponding authority collaboration area for the collaborative account according to the default value of the number of the areas. The method comprises the steps that a target user is supported to set the corresponding area quantity for each collaborative account of initial form data, or set the corresponding area quantity for part of collaborative accounts of the initial form data, or the corresponding area quantity does not need to be added to any one of the collaborative accounts of the plurality of collaborative accounts.
After adding the corresponding authority collaboration area for each collaboration account in the initial table data, the account identifier (i.e., account ID) of each collaboration account needs to be bound with the area identifier (i.e., area ID) of the corresponding authority collaboration area, which can be understood as a mapping relationship between the account identifier of the added collaboration account and the area identifier of the corresponding authority collaboration area. By binding the account identifier of the cooperative account with the region identifier of the corresponding authority cooperation region, only the cooperative account corresponding to the account identifier bound with the region identifier of the authority cooperation region can have the region editing authority for the corresponding authority cooperation region. For example, the area identifier of the rights coordination area may be a row or column location identifier, for example, if the rights coordination area is in row 2, the area identifier of the rights coordination area may be 2, and if the rights coordination area is in row 5, the area identifier of the rights coordination area may be 5. If the mapping relation between the account identifier 1 and the region identifier 2 of the collaborative account is added, the fact that only the collaborative account corresponding to the account identifier 1 on the 2 nd row in the initial table data has the region editing authority; if the mapping relation between the account identifier 2 and the region identifier 3 of the collaborative account and the mapping relation between the account identifier and the region identifier 4 are added, the fact that the 3 rd row and the 4 th row in the initial table data are indicated, and only the collaborative account corresponding to the account identifier 3 has the region editing authority for the collaborative account.
The binding process of the account identifier and the area identifier may be completed by the target terminal device through a server. When the server generates the authority cooperation areas corresponding to the cooperation accounts, the area identification of each authority cooperation area and the account identification of the cooperation account to which the area identification belongs can be bound. The server can synchronize the binding relation between the region identifier and the account identifier to the target terminal device, and the target terminal device can bind the region identifier of each authority cooperation region generated in the terminal page with the account identifier of the corresponding cooperation account, which is the process of giving the region editing authority of the cooperation account of each authority cooperation region.
It should be noted that, the creator of the initial table data may have all the operation rights for the initial table data, for example, the allocation rights including the operation rights for the initial table data. The allocation authority may be that a certain cooperative account or a plurality of cooperative accounts in the plurality of cooperative accounts of the initial table data may be set, and some or all of the operation authority of the initial table data may be provided, or all of the authority to edit the initial table data may be included. It can be understood that, the creator of the initial table data refers to the document account number of the target user in the document application, so that the document account number of the target user can also have region editing rights to the corresponding collaboration account number, besides the region editing rights to the corresponding collaboration account number, in the rights collaboration region corresponding to each collaboration account number added in the initial table data.
The initial table data of the authority collaboration area to which each collaboration account is added may be referred to as transition table data. The target terminal device may also output setting prompt information in the transition form data, where the setting prompt information is used to prompt the target user to set a form editing function for the transition form data. The setting prompt information may include a setting confirmation control, and the target terminal device may set a form editing function for the transition form data in response to a confirmation operation of the target user for the setting confirmation control. The validation operation for the set validation control may refer to a click operation on the set validation control. The transition table data to which the form editing function has been set may be regarded as target table data. The form editing function is used for enabling a collaborator of the target form data to trigger a form editing operation aiming at the target form data, and the form editing operation enables the collaborator of the target form data to edit a right collaboration area with region editing rights in the target form data in a form. Wherein, the collaborators of the target table data are the collaborators of the initial table data. It will be appreciated that the initial table data, the transition table data, and the target table data are all the same table data, except that 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 contents added to the table data. The specific process of editing the authority collaboration area with the area editing authority in the target table data by the collaborators of the target table data in the form of a table may be referred to as step S103 below.
Because the collaborators of the target table data can edit the authority collaboration area with the area editing authority in the target table data in a form, the process of editing the authority collaboration area with the area editing authority in the target table data is needed to be realized through the header unit bar in the target table data, and therefore, the setting prompt information is output when the target terminal equipment detects the header unit bar in the transition table data, the header unit bar is the header in the transition table data, and the header unit bar can be one unit row, one unit column, a plurality of unit rows or a plurality of unit columns in the transition table data. The header cell bars in the target table data are also referred to as header cell bars in the transition table data.
The process of detecting the header unit bar in the transition table data by the target terminal device may be:
first kind: 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 can respond to the data input operation of the target user for the cells in the transition form data to acquire the content input by the target user in the cells, and the content input by the target user in the cells can be called cell input data.
The target terminal device can detect whether a combined cell exists in the transition form data according to the acquired cell entry data. The combined unit cell comprises a plurality of adjacent unit cells, and the plurality of unit cells in the combined unit cell can be in one unit row or one unit column. None of the cells in the combined cell is empty, in other words, there is corresponding cell entry data for each of the cells in the combined cell. 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 the cell column at the starting position of the transition table data may be referred to as a target cell bar, and the starting 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, may also be the first 5 rows or the first 5 columns, etc. If the target terminal equipment detects that the combined cell is in the target cell bar, the target terminal equipment can determine the target cell bar in which the combined cell is as the header cell bar in the transition table data. The target terminal device may output the setting prompt information at the detected position of the header unit bar. The cell bar position of the header cell bar may refer to a position near the header cell bar or a position where the header cell is located, and for example, the setting hint information may be output at the position of the 3 rd column in the header cell bar.
Second kind: the target terminal equipment can also respond to the data input operation of the target user on the cells in the transition form data to acquire the cell input data. If the target terminal device detects that the target cell strips in the transition table data include the key cells with the number greater than or equal to the second number threshold according to the cell data, the target cell strip where the key cell is located may also be determined to be the header cell strip of the transition table data. The second number threshold may be set at its own right, e.g. to 3 or 5, etc. Also, the target terminal device may output the setting prompt information at the detected cell bar position of the header cell bar.
The key cells refer to cells containing the header keywords and containing the non-header keywords with the number smaller than a third number threshold, and the header keywords and the non-header keywords in the key cells are obtained by word segmentation of cell entry data in the key cells. The third number threshold may be set at its own discretion, e.g. to 3, etc. Whether the cells in the transition table data are key cells or not can be detected through a keyword library, and a plurality of header keywords, for example, 1 ten thousand or 10 ten thousand, can be included in the keyword library. The header keywords in the keyword library are obtained by word segmentation of header data of the history table data, and words which do not belong to the keyword library can be used as non-header keywords. Historical form data refers to form data created by other document accounts before this time. Alternatively, the keywords in the keyword library may also be manually set, for example, setting a plurality of header keywords that are fixed.
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. The target terminal equipment can synchronize the cell input data input by the target user in the transition form data to the server, and the server can detect the acquired cell input data. When the server detects the header unit bar in the transition table data according to the cell entry data, the server can send the detection result to the target terminal equipment, and the target terminal equipment can output the setting prompt information through the position of the header unit bar in the detection result.
Here, the target table data may be understood as the finally created table data, and the table data to which the target table data belongs (e.g., the initial table data and the transition table data described above) before the target table data is obtained may be referred to as the early table 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 header unit bar in the previous form data, rather than being output when the target terminal device detects the header unit bar in the transition form 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 table header unit bar exists in the table data, the setting prompt information can be output at the position of the detected unit bar of the table header unit bar, and then the target terminal device can respond to the confirmation operation of the user for the setting prompt information to set the table editing function for the current table data.
Fig. 4a is a schematic page diagram of a terminal page according to the present application. As shown in fig. 4a, the form data in the terminal page 100b belongs to the preceding form data of the target form data. The target terminal equipment can respond to the data input operation of the target user for the cells of the 1 st row and the A column, and acquire the cell input data 'name' input by the target user in the cells of the 1 st row and the A column. In addition, the target terminal device may further detect that the cell entry data "name" includes a header keyword "name" and includes 0 non-header keywords, and assuming that the third number threshold for the non-header keywords is 3,0 is less than 3, the target terminal device may determine that the cell of row 1 and column a is a key cell. The target terminal equipment can also respond to the data input operation of the target user for the 1 st row and the B column of the cells, and acquire the cell input data 'number' input by the target user in the 1 st row and the B column of the cells. In addition, the target terminal device may further detect that the cell entry data "number" includes the header keyword "number" and includes 0 non-header keywords, and the target terminal device may determine that the cell in the 1 st row and the B-th column is a key cell. The target terminal equipment can also respond to the data input operation of the target user for the cells of the 1 st row and the C column, and acquire the cell input data "class" input by the target user in the cells of the 1 st row and the C column. In addition, the target terminal device may further detect that the cell entry data "class" includes the header keyword "class" and includes 0 non-header keywords, and the target terminal device may determine that the cell of row 1 and column C is a key cell.
Assuming that the second number of threshold values for the key cells is 3 as described above, since 3 key cells have been detected at this time, the 3 key cells include cells of row 1, column a, cells of row 1, column B, and cells of row 1, column C. And, the 3 key cells are all in the 1 st row (i.e., the cell row 101 b) of the table data in the terminal page 100b, 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 thus, the target terminal device can determine the target cell bar 101b as the header 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 header cell bar 101b, where the setting hint information 102b is output in the form of a hint box. The setup prompt 102b may include a prompt "recommend use [ Smart fill ], more convenient to use form fill," and an "immediate setup" control 103b, which control 103b 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 the click operation of the control 103b by the target user. The confirmation operation for the space 103b may be referred to as a confirmation operation for the setting hint information.
Fig. 4b is a schematic page diagram of a terminal page according to the present application. As shown in fig. 4b, the termination page 105b is the same termination page as the termination page 100b described above 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 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 displays a description and an example of filling the form, wherein the description of filling the form is "let the collaborators of the form fill the form using the form, fill more attention", and the example of filling the form is that the form 106b is converted into the form 107b to be filled.
It may 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 the setting prompt information. Alternatively, the target user may select a certain row/column or a certain number of rows/columns in the preceding table data to which the target table data belongs by himself or herself, and set the above-mentioned table editing function for the selected table header unit bar.
In addition, the target user can set different operation authorities for the target table data for the collaborative account. For example, assuming that the plurality of collaboration accounts corresponding to the target table data includes the second collaboration account, since the plurality of collaboration accounts corresponding to the target table data may also include the document account of the target user, it is explained herein that the second collaboration account is not the document account of the target user. And the target terminal equipment can respond to the related user operation of the target user and add the newly added region authority for the second cooperative account. After the new region authority is added to the second collaboration account, the second collaboration account may further add a corresponding authority collaboration region for the new collaboration account in the target table data according to the new region authority. Wherein the newly added collaborative account refers to a document account other than the collaborative account that has been selected as the target form data. For example, the target terminal device may respond to the related user operation of the target user, so that the second collaboration account may also edit the permission collaboration area that does not belong to the target table data. For another example, the target terminal device may also respond to the related user operation of the target user, so that the second collaboration account may add or delete the rights collaboration area in the target table data.
Step S103, synchronizing the target table data to the collaboration terminals to which at least two collaboration accounts belong, so that the collaboration terminals to which at least two collaboration accounts belong edit the corresponding authority collaboration areas in the target table data respectively;
specifically, the target terminal device may synchronize the target table data to the collaboration terminal to which the collaboration account of the target table data belongs. The collaboration terminal to which the collaboration account belongs may refer to a terminal device that logs in to a corresponding collaboration account. The above-described process of creating the target form data may be implemented by a server, that is, the target form data is created by the server, and after the server completes creation of the target form data, the created target form data may be transmitted 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, which means that the target terminal device can generate a synchronization instruction in response to the synchronization operation of the target user on the target table data. 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 obtains the target form data, the target form data can be edited in response to user operation of a user on the target form data. The following describes how to edit the target table data in the target terminal device, and it should be noted that, the process may be adopted by the collaboration terminal to which each collaboration account belongs to complete editing of the target table data. After all the collaborative accounts complete editing the target form data, the target terminal equipment can obtain the completed final target form data. The filled target form data includes a unit row or a unit column corresponding to the "designated row filler" added by the batch addition filler (for example, the column a in the terminal page 100c in fig. 5 a), so that the target terminal device may also delete the unit row or the unit column corresponding to the "designated row filler" in the filled target form data in response to the user operation of the target user. Or, the target terminal device may respond to the confirmation operation of the target user on the target form data which is currently completed, and delete the cell row or cell column corresponding to the "designated row filling person" in the target form data.
It is assumed that the plurality of collaborative accounts of the target form data includes a first collaborative account, which may be any one of the collaborative accounts different from the document account of the target user. The target terminal device can log in a first collaborative account in addition to the document account of the target user. Since the target table data has been transmitted to each cooperative account, the target terminal device may acquire the target table data in the first cooperative 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 cooperative 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 cooperative account, the target table data comprises the authority cooperation area corresponding to the first cooperative account, and the area identification of the authority cooperation area of the first cooperative account is already bound with the account identification of the first cooperative account, so that the target terminal device can acquire the area identification with the mapping relation with the account identification through the account identification of the first cooperative account. The target terminal device can be positioned at the region position of the authority cooperation region corresponding to the first cooperation account in the target table data through the region identifier, and the target terminal device can also highlight the positioned authority cooperation region at the region position.
The rights coordination area located at the located area position, that is, the rights coordination area of the first collaboration account, may be highlighted by color-changing display of the rights coordination area, for example, color-changing display of an area background color of the rights coordination area for 1 second, etc.; the authority cooperation area can be subjected to scintillation and color change display, for example, the background color of the authority cooperation area is subjected to scintillation and color change display for 2 seconds and the like; the authority cooperation area may be displayed by lighting, for example, for 1 second.
Through the above process, it can be understood that when the target table data is entered in which one of the cooperative accounts, the located authority cooperation area can be automatically located at the area position of the authority cooperation area corresponding to the one of the cooperative accounts, and the located authority cooperation area can be highlighted. By the method, the user can quickly locate 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 entering the target table data in the first cooperative account, the target terminal device can respond to a table editing operation of the permission cooperation region of the first cooperative account in the target table data, and output a table page corresponding to the first cooperative account according to the header data of the target table data and the permission cooperation region of the first cooperative 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 header cell stripe may include a plurality of cells, the data entered in each cell in the header cell stripe may be referred to as cell header data. The target terminal equipment can respond to the data input operation of the user in the form page of the first collaborative account to acquire the data input by the user in the form page, and the data input by the user in the form page acquired by the target terminal equipment can be called form input data. The target terminal equipment can correspondingly add the acquired form input data into the authority collaboration area of the first collaboration account in the target form data, and the process realizes that the user completes editing of the target form data in a form. Specific procedures can be seen by the following examples.
Fig. 5a is a schematic page diagram of a terminal page according to the present application. As shown in fig. 5a, assume that the user has a first collaborative account in his or her possession. The target table data opened in the first cooperative account is displayed in the terminal page 100c, and because the permission cooperation area corresponding to each cooperative account is added in the target table data, the prompt information 115c may also be displayed in the terminal page where the target table data is located. Prompt 115c is "specify line fill: only the appointed person can edit a certain row, such as the appointed red edit second row, and other persons cannot modify, the prompt message 115c is used for prompting the collaborators, the target table data is a permission collaboration area allocated to each collaborator according to the rule of the unit row, and each collaborator can only edit the permission collaboration area belonging to the person, namely can only edit one or more rows belonging to the person.
The terminal page 100c displays the target table data opened in the first collaboration account, so that the located region position of the right collaboration region corresponding to the first collaboration account, that is, the located region 101c of the right collaboration region corresponding to the user flower, where the right collaboration region 101c is the 4 th row in the target table data. Wherein the rights coordination area 101c may also be highlighted, here the area background of the rights coordination area 101c is shown in gray.
The name of the collaboration account set for each row is indicated in column a in the terminal page 100c, and the name of the collaboration account displayed in column a (where the displayed names include "le", "duo", "flower" and "cocoa") may be the name of a contact remarked for the collaboration account in the address book of the target user (may be the address book of the third party application or the address book in the document application) or may be the original account name of each collaboration account.
Further, the target form data is form data provided with a form editing function set by the creator of the target form data, see specifically step S102 described above. When the target terminal device detects that the user has an editing operation with respect to the authority cooperation area 101c, for example, an operation of clicking on the authority cooperation area 101c or an operation of data entry, the target terminal device may display the terminal page 105c. The terminal page 105c includes 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 the clicking operation of the user on the button 104c, and output a form page corresponding to the first collaboration account according to the header data of the target form data and the permission collaboration area 101c, that is, display the terminal page 106c. Wherein the header cell bars of the target form data are determined when the creator (i.e., the document account number of the target user) sets the form editing function for the target form data, and therefore, there is no need to re-detect the header cell bars in the target form data. The header 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 header 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 "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 also comprises a data input area corresponding to each piece of cell header data, and the data input area corresponding to each piece of cell header data is obtained according to the authority cooperation area 101 c.
As shown in the terminal page 106c, the terminal page 106c includes a form page 107c therein. The form page 107c includes a data entry area k1 corresponding to the cell header data "name", a data entry area k2 corresponding to the cell header data "number", a data entry area k3 corresponding to the cell header data "class", a data entry area k4 corresponding to the cell header data "telephone number", and a data entry area k5 corresponding to the cell header data "home address". Wherein the data entry region k1 corresponds to the cell at the 4 th row and column position in the rights coordination region 101c, i.e., the data entered in the data entry region k1 is added to the cell at the 4 th row and column position in the rights coordination region 101 c. The data entry region k2 corresponds to the cell in the 4 th row and column position in the rights coordination region 101C, i.e., the data entered in the data entry region k2 is added to the cell in the 4 th row and column position in the rights coordination region 101C. The data entry region k3 corresponds to the cell in the 4 th row, column, position in the rights coordination region 101c, i.e., the data entered in the data entry region k3 will be added to the cell in the 4 th row, column, position in the rights coordination region 101 c. The data entry region k4 corresponds to the cell in the 4 th row and column position in the rights coordination region 101c, i.e., the data entered in the data entry region k4 is added to the cell in the 4 th row and column position in the rights coordination region 101 c. The data entry region k5 corresponds to the cell in the 4 th row, column, position in the rights coordination region 101c, i.e., the data entered in the data entry region k5 will be added to the cell in the 4 th row, column, position in the rights coordination region 101 c. It can be understood that the form input data input by the user in the form page acquired by the target terminal device can be automatically added into the corresponding cells in the target form data in real time, and the operation of storing the data in the form page by the user is not required in the process.
Fig. 5b is a schematic diagram of a terminal page for editing a form according to the present application. The data entry operation for a form page may refer to a data entry operation for a data entry region in the form page. The target terminal device can respond to the data input operation of the user for the form page 107c in the terminal page 106c, acquire the form input data input by the user in the form page, and display the terminal page 108c. 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 "Zhang Duoduo" in the data entry region k1, form entry data "12345678" in the data entry region k2, form entry data "2 shift higher" in the data entry region k3, form entry data "12345123451" in the data entry region k4, and form entry data "xx, town in the data entry region k 5. The target terminal device may display the terminal page 110c in response to a closing operation of the form page 109c by the user. As shown in the terminal page 110c, the target terminal device has added the form entry data acquired from the form page 109c to the target form data, as seen from line 4 in the target form data in the terminal page 110c. In addition, in the terminal page 110c, the target terminal device may further output the form page in response to the expansion operation of the user with respect to 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-authority cooperation area in the target table data in the first cooperation account, and output prompt information without editing authority, wherein the prompt information without editing authority is used for prompting a user to have no area editing authority for the non-authority cooperation area. The non-authority cooperation area refers to an authority cooperation area except for an authority cooperation area corresponding to the first cooperation account in the target table data, in other words, the non-authority cooperation area is an authority cooperation area which does not belong to the first cooperation account, and a mapping relation is not formed between an area identifier of the non-authority cooperation area and an account identifier of the first cooperation account.
Fig. 5c is a schematic page diagram of a terminal page according to the present application. Assuming that the first collaboration account logged in the terminal page is a document account held by the user's flower, the authority collaboration area 113c is a non-authority collaboration area for the first collaboration account. The target terminal device may input the no-editing-right cue information 112c in response to an editing operation by the user for the no-right cooperation area 113c in the terminal page 111 c. The editing operation for the non-authority collaboration area 113c in the terminal page 111c may refer to an operation of attempting to record data in the non-authority collaboration area 113c, where the no-editing-authority prompt information is "line 5 only flowers have editing authority, and you do not have editing authority".
More, the authority collaboration area of the first collaboration account may be a unit row in the target table data, and each unit cell in the unit row may be referred to as an authority unit cell. Because the target table data is online table data completed by a plurality of persons, if the other collaboration accounts except the first collaboration account of the target table data input new data in the target table data, the new data input by the other collaboration accounts can be newly added in real time in the opened target table data of the first collaboration account. In other words, because the target table data is online shared table data, the data recorded in the target table data by each cooperative account is synchronized to the other target table data opened by each cooperative account, and the operation of each cooperative account is the same target table data.
Thus, the target terminal device can acquire the data in the target cell of the target table data. Wherein, the target cell may refer to a cell in the same cell column as the authority cell, and different authority cells correspond to different target cells because different authority cells are in different cell columns. The target cell also refers to a cell in the authority collaboration area that does not belong 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 that does not belong to the first collaboration account. In other words, the data in the target cell is not recorded by the current cooperative account number, but is recorded by other cooperative account numbers, and the data recorded by other cooperative account numbers in the target cell can be called cell existing data.
The target terminal device can output the form page corresponding to the first collaboration account through the header data of the target form data, the authority collaboration area of the first collaboration account and the cell existing data in the calling cell when the number of the calling cells is larger than the calling number threshold value, and the cell existing data in the calling cell exists in the data entry area at the corresponding position in the form page. The call number threshold may be set by itself, for example to 2, etc. But this way, only the first collaborative account number has not entered any data in the data entry area corresponding to the calling cell in the form page. In other words, the data recorded in the target table data by the most of the other collaborative accounts can be used as the data recorded in the target table data by recommending to the first collaborative account, but if the first collaborative account has recorded the data at the corresponding position of the target table data, the data recorded by the first collaborative account is subject to, that is, the data recorded by the first collaborative account is kept unchanged.
For example, please refer to fig. 6, which is a schematic diagram of a terminal page of data recommendation provided in the present application. As shown in fig. 6, assuming that the first collaboration account number held by the user's flower is registered in the terminal page 100D, the permission collaboration area corresponding to the first collaboration account number is the 3 rd row where the user's flower is located, the cell at the 3 rd row and the D column may be regarded as one permission cell, and the target cell in the same cell column as the permission cell includes the cell at the 2 nd row and the D column, the cell at the 4 th row and the cell at the 5 th row and the D column, and as seen by the cell column 101D, the cell existing data in the target cell at the 2 nd row and the D column is "1 st shift", the cell existing data in the target cell at the 4 th row and the D column is "1 st shift". The target cells at the 2 nd row and the D column, the target cells at the 4 th row and the D column, and the target cells at the 5 th row and the D column can be used as calling cells, and the number of the calling cells is 3. If the calling number threshold is 2, the number of cells 3 of the calling cells is greater than the calling number threshold 2, and the target terminal device may respond to the expansion operation of the user on the form page, and output the form page for the first collaborative account through the existing data of the cells in the calling cells, the header data and the authority collaboration area corresponding to the first collaborative account, as shown by 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" is originally empty, 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.
In this way, it is achieved that the data "1 shift higher" that it can enter is recommended for the first collaborative account in the data entry area 104d, and the first collaborative account can modify the "1 shift higher" in the data entry area 104d, or can remain unchanged.
More, when the target terminal device is a mobile terminal and the mobile terminal does not have a solid keyboard, the target terminal device responds to user operation of a user, and when form input data is input in a form page, an input keyboard opened in the target terminal device may include a function key related to the data input in the form page, for example, a function key of the next item, a function key of line feed, a function key of inserting a picture, and the like.
Fig. 7 is a schematic page diagram of a terminal page according to the present application. As shown in fig. 7, when the target terminal device is a mobile terminal, the terminal page 100e is one of the target terminal devices. In the terminal page 100e, open target form data is displayed, and the target terminal device may display the terminal page 101e in response to a click operation of the user on the "enter smart fill" button 102e in the terminal page 100 e. Included in the terminal page 101e is a form page 107e, and the target terminal device may display an 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 associated with the entry of data in a form page, and specifically includes a next function key 106e, the next function key 106e being used to skip from the data entry area where data is currently being entered to the next data entry area, and then to enter the form in the next data entry area. Also included is an insert function key 103e, the insert function key 103e being used to add pictures, videos, documents, or the like in the data entry area. A wrap function key 104e is also included for wrapping a wrap in the current data entry area.
When the form page is generated, a different data input format can be set for each data input area in the form page, wherein the data input format can be a target input format which is respectively added by a creator (here, a document account number of the target user) for each cell header data in a header cell bar of target form data, and the target input format can comprise a date input format, a picture input format, a video input format, a document input format, a drop-down selection input format and the like. One cell header data corresponds to one data entry area and one data entry area 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 a 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 considered as a picture entry format. Alternatively, the data entry format of each data entry area in the form page may be selected to be set to a default format, which may be a text entry format.
Fig. 8 is a schematic diagram of a form page according to the present application. As shown in fig. 8, a data entry area 107f is included in the form page 100f in which the data entry format is a text entry format, meaning that text can be entered into the data entry area 107 f; also included in the form page 100f is a data entry area 108f in which the data entry format is a drop-down selection entry format, meaning that the corresponding header entry data can be selected directly in the drop-down options set by the creator. For example, here, the target terminal device may display the form page 105f in response to a user clicking operation on the drop down select button 101f in the data entry area 108 f. The form page 105f includes a drop-down option 106f, and the drop-down option 106f specifically includes an option "1 shift higher," an option "2 shift higher," and an option "3 shift higher. The target terminal device may select the corresponding option (either singly or multiply) as form entry data in the data entry area 108f in response to a user selection operation for an option in the drop-down option 106 f. Also included in the form page 100f is a data entry area 102f in a data entry format, which refers to the fact that pictures can be added to the data entry area 102 f. Also included in the form page 100f is a data entry area 103f in which the data entry format is a document entry format, a picture entry format meaning that a document can be added to the data entry area 103 f. Also included in the form page 100f is a data entry area 104f in which the data entry format is a video entry format, which means that video can be added to the data entry area 104 f.
More, the header cell bar of the target table data may include not only one cell row or one cell column, but also a plurality of cell rows or a plurality of cell columns. When the header cell bar 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 combined to obtain the header cell bar of the target table data.
Fig. 9 is a schematic view of a scenario for obtaining a header unit bar according to the present application. As shown in fig. 9, when the target table data is opened in the first collaboration account, and the terminal page 100g with the target table data expanded is displayed, a prompt box 104g may also be displayed at the bottom of the terminal page 100 g. The prompt box 104g further includes an "enter Smart fill" button 102g, and the button 102g is used to display a form page 103g. When the target terminal device detects the header cell bar of the target table data, the cell rows where the cells occupying the most number of rows in the header cell bar are located can be combined to be used as the cell header data in the table page. For example, here, the target terminal device may detect that the header cell bar in the terminal page 100g is the cell bar 101g, where the cell bar 101g includes the 1 st row and the 2 nd row of the target table data, and then the cell entry data in the 1 st row and the 2 nd row may be combined as the cell header data in the form page. As shown in the terminal page 105g, the 1 st and 2 nd lines of the cell bar 101g are combined, and the cell entry data in the 1 st line and the cell entry data in the 2 nd line can be connected by "-" or space or the like at the time of the combination. The cell header data "name", the cell header data "number", the cell header data "1 month 1 day-monday", the cell header data "1 month 2 day-monday" and the cell header data "1 month 3 day-monday" in the form page 103g can be obtained. By the method, a user can quickly check the complete data in the header unit bar through the form page and correspondingly fill in the data.
The method comprises the steps of obtaining initial form data, and obtaining at least two cooperative accounts corresponding to the initial form data; responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial form data to obtain target form data; synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively. Therefore, according to the method provided by the application, the authority 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 authority cooperation areas is improved. Meanwhile, as the corresponding authority cooperation areas are respectively allocated to each cooperation account, each cooperation account can edit the authority cooperation areas belonging to the user in the target form data, so that the filling accuracy of the target form data is improved.
Fig. 10 is a schematic flow chart of a form generating method according to the present application. As shown in fig. 10, the method includes:
Step S201, the collaborators enter an intelligent filling form;
specifically, the collaborator may be any one of the above-mentioned target table data, and the target terminal device may respond to the unfolding operation of the collaborator on the target table data, and unfold the target table data, that is, enter the target table data. The target form data is provided with a form editing function, entering the target form data, i.e., entering the smart fill form.
Step S202, obtaining lines which are required to be filled by a user according to the user identification;
specifically, the user identifier is the account identifier of the collaborative account of the collaborator. Because the authority collaboration area in the target form data is already bound with the account identifier of the collaboration account to which the target form data belongs, the authority collaboration area corresponding to the account identifier can be found according to the account identifier of the collaboration account, and the found authority collaboration area can be a unit row, and the found authority collaboration area is a row which needs to be filled by a user.
Step S203, jumping to a designated row, and clicking "Smart fill in" by a user;
specifically, the designated line is the line that the user needs to fill out, and jumps to the designated line, that is, locates to the region position of the rights coordination region corresponding to the user identifier found in step S202. The user may click on the "Smart fill" button for the specified line, which is a button for entering a form page.
Step S204, analyzing the key words of the header, and generating an intelligent form;
specifically, after the user clicks the "smart fill" button, the target terminal device may parse the header key, that is, parse the key in the header data of the cell in the header cell stripe. The keywords in the cell header data may be parsed one at a time until the keywords in each cell header data are parsed.
Step S205, whether the keyword is of date type;
specifically, if it is analyzed that the keyword in the header data of a certain cell in the header cell is of the date type, the following step S206 is executed, and if it is analyzed that the keyword in the header data of a certain cell in the header cell is not of the date type, the following step S207 is executed. When the keyword includes a date-related word such as year and month, the keyword may be determined to be of 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 form (i.e., the form in the form page may be understood as the form page) containing the keyword of the date type may be set to the date input format, that is, the above-mentioned date input format. Next, step S217 is performed.
Step S207, whether the key word is of a time type;
specifically, if the keyword is not of the date type, then it is continued to determine whether the keyword is of the 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 a time, a word related to time, etc., the keyword may be determined to be of 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 time-type keyword included in the form may be set as the time entry format. Next, step S217 is performed.
Step S209, judging whether the keyword is a picture type;
specifically, if the keyword is not of a time type, continuing to judge whether the keyword is of a picture type. If the keyword is determined to be of the picture type, the following step S210 is executed, and if the keyword is determined not to be of the picture type, the following step S211 is executed. If the keyword includes a word related to a picture, such as a screenshot, an imported picture, a drawing, etc., then the keyword may be determined as a picture type.
Step S210, adding a picture input format to the form;
specifically, the data input format of the data input area corresponding to the cell header data of the keywords containing the picture types in the form can be set to be the picture input format, so that the collaborators can add pictures in the data input area with the picture input format. Next, step S217 is performed.
Step S211, whether the keyword is of a geographic position type;
specifically, if the keyword is not the picture type, continuing to judge whether the keyword is the geographic location type. If it is determined that the keyword is of the geographical location type, the following step S212 is executed, and if it is determined that the keyword is not of the geographical location type, the following step S213 is executed. If the keyword includes words related to the geographic location, such as a location, a region, a positioning, etc., then 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 input format of the data input area corresponding to the cell header data of the keyword containing the geographic position type in the form can be set as a position input format, and the position input format can be an input format of xx province/xx city/xx region or a map positioning format and the like. Next, step S217 is performed.
Step S213, whether the keyword is a pull-down selection type;
specifically, if the keyword is not of the geographic location type, continuing to determine whether the keyword is of the drop-down selection type. If it is determined that the keyword is of the pull-down selection type, the following step S214 is executed, and if it is determined that the keyword is not of the pull-down selection type, the following step S215 is executed. And if the keyword comprises the keyword in the pull-down option set by the user for the cell header data, determining that the keyword is of 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 containing the drop-down selection type keyword in the form may be set to be a drop-down input format, for example, the data entry format of the data entry area 1018f in fig. 8 is the drop-down input format. Next, step S217 is performed.
Step S215, keyword default type;
specifically, if the keyword is not the pull-down selection type, the default type may be used as the keyword type of the keyword, and the following step S216 may be performed. 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 data entry area corresponding to the cell header data of the form containing the keyword of the default type 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;
specifically, whether the processing of the keywords is finished is judged, that is, whether the analysis of the keywords in the header data of all the cells in the header cell bar is finished is judged. If all the analysis is completed, the following step S218 is executed, and if not, the above step S204 is executed to continue the analysis of the keywords in the cell header data.
Step S218, after the intelligent form is generated, the user starts to fill in;
specifically, after the key words in the header data of each cell are analyzed, the intelligent form is indicated that the data input format of each data input area in the form is set, and the form is successfully generated, so that a form page containing the form can be output. The user can fill in the form page, namely, enter the form input data, so as to edit the target form data.
Fig. 11a is a schematic flow chart of a keyword library obtaining method 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 body 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 a new form submitted by the user. The new forms and forms submitted by the user 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 target form data to the server. The form or form submitted by the user and obtained by the server may be referred to as historical form data or historical form data.
Step S302, extracting the header data of the form input problem/form;
specifically, the server may extract a form input problem in the history form data, that is, a form input problem corresponding to the cell header data displayed in the above-described form page. The server may also extract header data in the history table data, i.e., cell header data in the header cell bars of the history table data.
Step S303, word segmentation is carried out by adopting maximum forward matching based on the existing dictionary;
specifically, the server may perform word segmentation on the extracted form input problem and header data in a manner of maximum forward matching word segmentation, so as to obtain a plurality of word segmentation words. The server may match each word segment in the existing dictionary and indicate that the word segment is a keyword if the word segment exists in the existing dictionary. If the word is not present in the existing dictionary, the word is not a keyword. The existing dictionary may be a dictionary created in advance by a developer.
Step S304, extracting keywords and updating a keyword database;
specifically, the process server can extract and obtain the form input problem and keywords in the header data. The server may update the keyword database by the extracted keywords, for example, by directly adding the extracted keywords 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 keywords. Wherein the update time of the ranking list can be set, for example, updated every 24 hours. Thus, when 24 hours have arrived from the beginning of the time counting, it indicates that the ranking list needs to be updated, and when 24 hours have not arrived from the beginning of the time counting, 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 which appear in a keyword database in one day, the monthly keyword ranking list is obtained by ranking keywords which appear in a keyword database in one month, and the annual keyword ranking list is obtained by ranking keywords which appear in a keyword database in one year. The more times a keyword appears, the more front it is in the ranking list.
The intelligent filling keyword library can be obtained through a plurality of keywords with the forefront positions in the ranking list, for example, the intelligent filling keyword library can comprise 1 ten thousand keywords with the forefront positions in the ranking list. The intelligent filling keyword library is the keyword library in the step S102, and the keyword library can be used for detecting the key cells in the form data, and by detecting the key cells in the form data, the header in the form data can be detected, specifically referring to the step S102. Keywords in the keyword library may be referred to as header keywords.
Fig. 11b is a schematic flow chart of a method for detecting a key cell according to the present application. As shown in fig. 10, the method includes:
step S401, a user inputs a cell text;
specifically, when the user finishes entering data into a certain cell in the initial table data, the target terminal device can acquire the data entered by the user in the cell, namely the cell entering data, namely the cell text.
Step S402, whether in the 1 st line to the 3 rd line;
specifically, the target terminal device may determine whether the current cell is within the 1 st to 3 rd rows in the initial table data. If yes, the following step S404 is executed, and if not, the following step S403 is executed.
Step S403, not a critical cell;
specifically, the target terminal device determines that the current cell is not the keyword cell, and the process ends. Explanation of the key cells can be found in step S102 described above.
Step S404, whether the cell contains a keyword;
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 it is determined that the current cell does not contain the keyword, the following step S405 is executed, and if it is determined that the current cell contains the keyword, the following step S406 is executed.
Step S405, not a critical cell;
specifically, the target terminal device detects that the current cell is not a key cell, and the current process ends.
Step S406, whether the front and the back contain a plurality of non-keywords;
specifically, the target terminal device continues to determine whether the front and rear of the keyword in the current cell include a plurality of non-keywords, that is, the non-header keywords, that is, the 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 critical cell;
specifically, the target terminal device detects that the current cell is not a key cell, and the current process ends.
Step S408, key cells;
specifically, the target terminal device detects that the current cell is a key cell, and the current process ends.
Fig. 11c is a schematic flow chart of an intelligent recommendation method provided by the 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 inputs 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 copy and paste is performed;
specifically, the target terminal device may determine whether the user operation type is copy-paste. If yes, go to step S504, if not, go to step S503.
Step S503, whether to input;
specifically, the target terminal device may determine whether the user operation type is an input type again, and in general, the user operation type is not a copy-paste type, but is an input type. When the target terminal apparatus determines that the user operation type is the input type, step S505 may be performed.
Step S504, analyzing copy-paste content;
specifically, the target terminal device may analyze copy-paste content entered in the form data by the user through copy-paste operation. Wherein the copy-and-paste content may include content copy-and-paste 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 in the cells by the user through the input operation, and further determine whether the key cells exist in the table data according to the analysis result. If so, step S507 is performed.
Step S506, whether the position is smaller than the 3 rd line;
Specifically, the target terminal device may determine whether the position of the cell where the copy-and-paste content is located is smaller than line 3, that is, whether the cell is in lines 1 to 3.
Step S507, the number of key cells is greater 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 line is greater than or equal to a specified value, that is, the second number threshold for the key cells in step S102 described above. If yes, it indicates that the header cell bar in the table data is detected, step S508 is executed, and if not, the process ends without any operation.
Step S508, triggering intelligent filling recommendation;
specifically, triggering the intelligent filling recommendation means that the setting prompt information is output at the position of the cell bar where the cell bar of the header is located. The target terminal device may set a form editing function for the form data in response to a confirmation operation by the user for the setting prompt information.
Fig. 12 is a flow chart of a region adding method according to the present application. As shown in fig. 12, the method includes:
step S701, a user selects batch addition of filling persons;
Specifically, the user selecting the batch addition filler may refer to, for example, that the user realizes the batch addition filler by clicking on the "batch addition filler" control 105a in the terminal page 124a in fig. 2 b.
Step S702, removing repeated addition to obtain a newly added filling person;
specifically, a new filling person, namely a collaborative account selected for the form data, if a plurality of collaborative accounts of the form data are selected from a third party application, the third party application comprises 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 added filling person selects the first communication account number in the first communication application and the second communication account number in the second communication application at the same time, the newly added filling person corresponding to the first communication account number and the second communication account number is the same finally, namely the first communication account number and the second communication account number correspond to the same cooperative account number. In this way, the duplicate addition can be removed, that is, only one cooperative account number can be obtained through the first communication account number and the second communication account number, but two duplicate cooperative account numbers cannot be obtained.
Step S703, designating line filling;
specifically, for example, when the user selects "designate line filling person" in the selection frame 101a in the terminal page 122a in fig. 2a, this indicates that the table data designate line filling. The appointed row filling indicates that corresponding authority cooperation areas are allocated to each cooperation account number according to the behaviors in the form data. If the line is specified, step S704 is executed, and if the line is not specified, indicating that the column is specified, step S705 is executed. The appointed column filling indicates that a corresponding authority cooperation area is allocated to each cooperation account number according to the column in the form data.
Step S704, processing row allocation;
specifically, a permission cooperation area is allocated for the cooperation account by using a unit row unit.
Step S705, processing column allocation;
specifically, a permission cooperation area is allocated for the cooperation account by taking the unit column as a unit.
Step S706, adding a row of protection areas;
specifically, a protection area is newly added one row at a time, and the protection area is the newly added authority cooperation area.
Step S707, assigning the area with a new filling person editing authority;
specifically, the newly added authority cooperation area is randomly allocated to one cooperation account, namely, the area editing authority of the newly added authority cooperation area is allocated to one cooperation account.
Step S708, whether the newly added filling person remains unprocessed;
specifically, whether a collaboration account number is not assigned with a permission collaboration area is judged. If yes, the step S706 is executed, and the corresponding rights coordination area is continuously allocated to the collaboration account number not allocated with the rights coordination area. If not, indicating that the rights coordination areas of all the coordination accounts are allocated, step S712 is performed.
Step S709, adding a list of protection areas;
specifically, a list of protection areas is newly added each time, and the protection areas are the newly added authority collaboration areas.
Step S710, endowing the area with a new filling person editing authority;
specifically, the newly added authority cooperation area is randomly allocated to one cooperation account, namely, the area editing authority of the newly added authority cooperation area is allocated to one cooperation account.
Step S711, whether newly added filling persons remain unprocessed;
specifically, whether a collaboration account number is not assigned with a permission collaboration area is judged. If yes, the step S709 is executed, and the corresponding rights coordination area is continuously allocated to the collaboration account number not allocated with the rights coordination area. If not, indicating that the rights coordination areas of all the coordination accounts are allocated, step S712 is performed.
Step S712, completing distribution;
specifically, it is indicated that the authority collaboration areas of all collaboration accounts are allocated, and allocation is completed.
Fig. 13 is a flow chart of a table data processing method according to the present application. As shown in fig. 12, the method includes:
step S601, rapidly distributing row/column rights;
specifically, the creator a data layer refers to data interaction between creator a (refer to the document account number of the target user) and a server (a background server of the document application), and the server identifies creator a through account number identification of the collaborative account number of creator a. The target terminal device (can be understood as creator a) can send the obtained collaboration account of the form data to a server (a background server of the document application), and the server can start to allocate a corresponding row/column authority for each collaboration account, that is, allocate a corresponding authority collaboration area for each collaboration account, where the authority collaboration area can be a unit row or a unit column.
Step S602, traversing users to be added;
specifically, the user to be added refers to the collaborative account of the form data, and the server can sequentially traverse a plurality of collaborative accounts synchronized by the target terminal device.
Step S603, a row of 'areas' is generated on the table;
specifically, when the server traverses to the first collaboration account, a row of "regions" may be generated in the table data, that is, a permission collaboration region is generated.
Step S604, designating authority for the region;
specifically, the server may assign a corresponding collaboration account to the generated row of authority collaboration areas, that is, assign the area editing authority of the row of authority collaboration areas to the traversed collaboration account.
Step S605, whether the user has set up;
specifically, whether all the cooperative accounts have been traversed or not is detected, and a corresponding authority cooperation area is allocated to each cooperative account. If not, the above step S603 is executed to continue generating an area in the table data, and assign the generated area to the collaboration account number that has not been assigned to the authority collaboration area. If yes, the fact that the authority cooperation areas of all the cooperation accounts are distributed is indicated, and the process of distributing the authority cooperation areas for the cooperation accounts is finished.
The above process can be known that the terminal device allocates the authority collaboration area of each collaboration account through the server, and the data layer in the server can store all data generated in the generation process of the table data, including which row in the table data is allocated to which collaboration account.
Step S606, storing the data in the 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 area generated in the table data, and broadcast each generated area (i.e., each authority collaboration area) to each collaboration account, where the collaboration account of the collaborator B and the collaboration account of the collaborator C are included.
Step S607, storing the authority background and broadcasting the set authority;
specifically, the rights background also belongs to the data layer of the server. The rights background may store a binding relationship between each region in the table data and the collaborative account, i.e., store which regions in the table data each collaborative account has region editing rights. 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 data layer of the collaborator B refers to data interaction between the document account of the collaborator B and the server. The terminal device where the document account number of the collaborator B is located can receive each region in the form data synchronized by the data background, and each region in the same form data is correspondingly generated in the terminal page of the terminal device.
Step S609, receiving the synchronized authority and assigning the authority to the area;
specifically, the terminal device where the document account of the collaborator B is located may also receive the collaboration account having the region editing authority for each region and synchronized by the authority background, and may assign, according to the obtained collaboration account corresponding to each region, a corresponding collaboration account to each region generated in the terminal page, that is, assign, to each region, the region editing authority of the corresponding collaboration account.
Step S610, whether the current row/column has authority;
specifically, the terminal device where the document account of the collaborator B is located may determine, according to the region editing rights given to each region in the terminal page, whether the current collaboration account has the region editing rights to the row/column that is attempting to operate (i.e., edit). If yes, step S612 is executed, and if not, step S613 is executed.
Step S611, operable;
specifically, the terminal device where the document account number of the collaborator B is located judges that the document account number of the collaborator B has the region editing authority on the row/column attempting to be operated, and the terminal device where the document account number of the collaborator B is located can respond to the data editing operation of the user to edit the row/column currently operated.
Step S612, the operation is disabled, and the non-authority 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 region editing authority for the row/column that is attempted to be operated, and the terminal device where the document account of the collaborator B is located may output the no-authority prompt message to inform that the collaborator B does not have the region editing authority for the row/column that is currently operated.
Step S613, receiving the synchronized data to generate an area;
specifically, the data layer of the collaborator C refers to data interaction between the document account number of the collaborator C and the server. The terminal device where the document account number of the collaborator C is located can receive each region in the form data synchronized by the data background, and correspondingly generates each region in the same form data in the terminal page of the terminal device.
Step S614, receiving the synchronized authority and assigning the authority to the area;
specifically, the terminal device where the document account of the collaborator C is located may also receive the collaboration account having the region editing authority for each region and synchronized by the authority background, and may assign, according to the obtained collaboration account corresponding to each region, a corresponding collaboration account to each region generated in the terminal page, that is, assign, to each region, the region editing authority of the corresponding collaboration account.
Step S615, whether the current row/column has authority;
specifically, the terminal device where the document account of the collaborator C is located may determine, according to the region editing rights given to each region in the terminal page, whether the current collaboration account has the region editing rights to the row/column that is attempting to operate (i.e., edit). If yes, go to step S617, if not, go to step S618.
Step S616, operable;
specifically, the terminal device where the document account number of the collaborator C is located determines that the document account number of the collaborator C has the region editing authority on the row/column that is attempted to be operated, and the terminal device where the document account number of the collaborator C is located can respond to the data editing operation of the user to edit the row/column that is currently operated.
Step S617, the operation is impossible, and the non-authority is informed;
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 region editing authority for the row/column that is attempted to be operated, and the terminal device where the document account of the collaborator C is located may output the no-authority prompt message to inform that the collaborator C does not have the region editing authority for the row/column that is currently operated.
More, the technical framework for realizing the method provided by the application comprises three layers, namely a rendering layer, a control layer and a data layer. The rendering layer is responsible for rendering out data of a user, displaying the data in a terminal page, and displaying the data to the user for viewing. The rendering layer may include two views, one for the creator and one for the collaborators. The view angle of the creator can include adding authority collaboration areas corresponding to a plurality of collaborators in batches in the form data, and the like. The perspective of the collaborators may include editing form data in the form of form pages, and the like.
The control layer is understood to be, among other things, the bridge between the rendering layer and the data layer. The control layer can be responsible for processing the data of the user and then synchronizing the processed data to the rendering layer, namely, the control layer can acquire the data related to the form data from the data layer and resynchronize the acquired data to the rendering layer, so that the rendering layer can display the data related to the form data for the user in the terminal page. The control layer may synchronize the operation behavior of the user (e.g., editing behavior of a form page or behavior of adding collaboration accounts in batches, etc.) acquired at the front end (e.g., a terminal device) with data (e.g., a plurality of collaboration accounts selected and data filled in by the user in the form data, etc.) to the data layer, and the data layer may store the data synchronized by the control layer.
The data layer is responsible for storing the data and the behavior after the user operation into the background, and can synchronize the data after the user operation to other users. For example, since the target form data is shared online form data, the contents of each collaborator filling the target form data are 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.
Fig. 14 is a schematic diagram of a technical framework according to 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 and presenting the table data to a user, the control layer is used for transmitting the data related to the table data required by the rendering layer and the data layer, and the data layer is used for storing the data related to the table data. The control layer acts as a bridge, or intermediary, between the rendering layer and the data layer. The functions that the control layer needs to contain include: new rights (such as assigning additional rights to a collaboration account), keyword settings (such as setting a keyword library), intelligent recognition of keywords, form recommendation filling, quick assignment of row/column rights, intelligent conversion of forms into forms, and the like.
Fig. 15 is a schematic structural diagram of a table data processing device according to the present application. As shown in fig. 15, the tabular data processing apparatus 1 may include: a table acquisition module 11, an area addition module 12, and a synchronization module 13;
the table obtaining module 11 is configured to obtain initial table data, and obtain at least two cooperative accounts corresponding to the initial table data;
The region adding module 12 is configured to respond to a triggering operation for at least two cooperative accounts, and add an authority cooperation region for each of the at least two cooperative accounts in the initial table data, so as to obtain target table data;
and the synchronization module 13 is configured to synchronize the target table 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 edit the corresponding rights collaboration areas in the target table data respectively.
The specific function implementation manner of the table obtaining module 11, the area adding module 12 and the synchronizing module 13 is please refer to step S101-step S103 in the embodiment corresponding to fig. 3, and no further description is given here.
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 mapped 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 obtain at least two communication accounts in the communication application in response to a batch addition operation for the initial form data in the document application;
A mapping account obtaining unit 113, configured to obtain mapping document accounts of at least two communication accounts in a document application respectively;
the account determining unit 114 is configured to determine the mapped document accounts corresponding to the at least two communication accounts as at least two cooperative accounts.
The specific function implementation manner of the table obtaining unit 111, the batch response unit 112, the mapping account obtaining unit 113, and the account determining unit 114 is please refer to step S101 in the embodiment corresponding to fig. 3, and a detailed description is omitted herein.
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 a first communication application and a second communication account in a second communication application; the first communication account number and the second communication account number have account number binding relation in the document application; the first communication account number and the second communication account number with account number binding relation correspond to the same mapping document account number.
Wherein the region adding module 12 includes: a number setting unit 121, an area adding unit 122, and a mapping relation adding unit 123;
a number setting unit 121, configured to obtain the number of regions of each collaboration account for the rights collaboration region;
The region adding unit 122 is configured to add a corresponding authority collaboration region for each collaboration account in the initial table data according to the number of regions corresponding to each collaboration account;
a mapping relationship adding unit 123, configured to add a mapping relationship between an account identifier of each cooperative account and a corresponding authority collaboration area in the initial table data, so as to obtain target table data; the mapping relationship is used for indicating that each cooperative account has the region editing authority for the affiliated authority cooperation region.
The specific function implementation manner of the number setting unit 121, the area adding unit 122, and the mapping relation adding unit 123 is referred to step S102 in the embodiment corresponding to fig. 3, and will not be described herein.
Wherein the at least two cooperative accounts include a cooperative account s i Wherein i is a positive integer less than or equal to the total number of the accounts of the at least two cooperative accounts, and the initial value of i is 1;
the area adding module 12 is further configured to:
in the initial table data, the collaboration account number s is in turn i And adding the authority cooperation area until i is equal to the total number of the accounts, and obtaining target table data.
Wherein the at least two collaborative accounts include a first collaborative account;
The form data processing apparatus 1 further includes: a form expansion module 14 and a position location module 15;
a form expansion module 14, configured to expand the target form data in response to an expansion operation of the first collaboration account with respect to the target form data;
the location positioning module 15 is configured to locate, in the expanded target table data, a region location of the rights coordination region corresponding to the first collaboration account, and highlight the rights coordination region in the located region location.
In the specific function implementation manner of the table expanding module 14 and the position locating module 15, please refer to step S103 in the embodiment corresponding to fig. 3, and a detailed description is omitted herein.
The target table data includes header data, and the table data processing apparatus 1 further includes: form output module 16, form entry module 17 and data addition module 18;
the form output module 16 is configured to respond to a form editing operation for a permission collaboration 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 collaboration area corresponding to the first collaboration account;
the form input module 17 is used for responding to the data input operation aiming at the form page and acquiring form input data;
The data adding module 18 is configured to add the form entry data to a permission collaboration area corresponding to the first collaboration account in the target form data.
The specific function implementation manner of the form output module 16, the form input module 17, and the data adding module 18 is please refer to step S103 in the embodiment corresponding to fig. 3, and no further description is given here.
The authority collaboration area corresponding to the first collaboration account is a unit row in the target table data; the unit row corresponding to the first collaborative account comprises authority unit cells;
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 cell existing data in at least two target cells among the target table data; the target cell and the authority cell are cells in the same cell column; the cell existing data in the at least two target cells are the collaborative account numbers except the first collaborative account number in the at least two collaborative account numbers, and the data is recorded in the at least two target cells;
a cell determining unit 162, configured to determine, as a calling cell, a target cell having the same cell existing data, from among at least two target cells;
The form output unit 163 is configured to output a form page corresponding to the first collaboration account according to the existing data of the cells in the calling unit, the header data of the target table data, and the permission collaboration area corresponding to the first collaboration account when the number of the cells in the calling unit is greater than the threshold of the calling number; the cells in the calling cell have data displayed in the data entry area in the form page.
In the specific function implementation manner of the existing data obtaining unit 161, the unit cell determining unit 162 and the form output unit 163, please refer to step S103 in the embodiment corresponding to fig. 3, and a detailed description is omitted here.
Wherein, the header data of the target table data comprises at least two cell header data;
form output module 16, comprising: a format recognition unit 164 and a format form output unit 165;
a format identifying unit 164, configured to obtain data entry formats corresponding to at least two cell header data respectively;
the format form output unit 165 is configured to output a form page corresponding to the first collaboration account according to a data entry format corresponding to each cell header data, and a permission collaboration area corresponding to the first collaboration account; the form page comprises data input areas corresponding to the header data of each unit cell respectively; each data entry area in the form page is provided with a data entry format corresponding to the data of the corresponding cell header.
The specific functional implementation manner of the format identifying unit 164 and the format form output unit 165 is please refer to step S103 in the embodiment corresponding to fig. 3, and a detailed description is omitted herein.
Wherein the format recognition unit 164 includes: a data type recognition subunit 1641 and a format acquisition unit 1642;
a data type identifying subunit 1641, configured to identify a data type of each cell header data, and determine a data entry format corresponding to each cell header data according to the data type of each cell header data; or alternatively
The format acquiring unit 1642 is configured to acquire, as the data entry format corresponding to each cell header data, the target entry format added to each cell header data.
In step S103 in the embodiment corresponding to fig. 3, the specific function implementation manner of the data type identifying subunit 1641 and the format obtaining unit 1642 is described herein, and no further description is given here.
Wherein the region adding module 12 includes: a transition acquisition unit 124, a prompt output unit 125, and a prompt response unit 126;
the transition obtaining unit 124 is configured to add the permission collaboration area to the at least two collaboration accounts synchronously in the initial table data, so as 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 form data;
a prompt response unit 126, configured to set a form editing function for the transition form data in response to a confirmation operation for setting prompt information, to obtain target form data; the form editing function is used for triggering a form editing operation in the target form data.
The specific function implementation manner of the transition obtaining unit 124, the prompt output unit 125, and the prompt response unit 126 is please refer to step S102 in the embodiment corresponding to fig. 3, and a detailed description is omitted herein.
Wherein the hint output unit 125 includes: a first entry response subunit 1251, a combined cell detection subunit 1252, and a first hint output subunit 1253;
a first entry response subunit 1251 configured to obtain cell entry data in response to a data entry operation for a cell in the transition form data;
a combined cell detection subunit 1252 configured to determine, when it is detected that the transition form data includes a combined cell according to the cell entry data and the combined cell is in a target cell stripe of the transition form data, the target cell stripe as a header cell stripe; the unit cells included in the combined unit cell are adjacent unit cells which are not empty; the number of cells included 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 the starting position of the transition table data;
The first prompt output subunit 1253 is configured to output setting prompt information for the transition table data according to the cell bar position of the header cell bar.
The specific functional implementation manner of the first input response subunit 1251, the combined unit cell detection subunit 1252, and the first prompt output subunit 1253 is please refer to step S102 in the embodiment corresponding to fig. 3, and no further description is given here.
Wherein the hint output unit 125 includes: a second entry response subunit 1254, a key cell detection subunit 1255, and a second hint output subunit 1256;
a second entry response subunit 1254 for obtaining cell entry data in response to a data entry operation for a cell in the transition form data;
a key cell detection subunit 1255, configured to determine, when detecting, according to the cell entry data, that the target cell stripe in the transition table data includes a number of key cells greater than or equal to the second number threshold, the target cell stripe as a header cell stripe; the target cell bar is a cell row or a cell column at a starting position in the transition table data; the key cells are cells containing header keywords and containing non-header keywords with the number smaller than a third number threshold;
The second prompt output subunit 1256 is configured to output setting prompt information for the transition table data according to the cell bar position of the header cell bar.
The specific functional implementation manner of the second input response subunit 1254, the key cell detection subunit 1255, and the second prompt output subunit 1256 is please refer to step S102 in the embodiment corresponding to fig. 3, and no further description is given here.
Wherein the key cells are detected based on a keyword library; the keyword library comprises at least two header keywords; the at least two header keywords are obtained by word segmentation of header data in the historical table data.
Wherein, the table data processing device 1 is further used for:
responding to the editing operation of the first collaboration account aiming at the non-authority collaboration area in the target form data, and outputting prompt information without editing authority; the non-authority cooperation area refers to an authority cooperation area except the authority cooperation area corresponding to the first cooperation account in the target table data.
Wherein the at least two collaborative accounts include a second collaborative account; the table data processing apparatus 1 is further configured to:
adding a new region authority for the second cooperative account, synchronizing the new region authority to a cooperative terminal to which the second cooperative account belongs, so that the cooperative terminal to which the second cooperative account belongs adds a corresponding authority cooperative region for the new cooperative account in the target table data according to the new region authority.
The method comprises the steps of obtaining initial form data, and obtaining at least two cooperative accounts corresponding to the initial form data; responding to triggering operation aiming at least two cooperative accounts, and respectively adding an authority cooperation area for each of the at least two cooperative accounts in the initial form data to obtain target form data; synchronizing the target table 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 edit the corresponding authority collaboration areas in the target table data respectively. Therefore, according to the method provided by the application, the authority 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 authority cooperation areas is improved. Meanwhile, as the corresponding authority cooperation areas are respectively allocated to each cooperation account, each cooperation account can edit the authority cooperation areas belonging to the user in the target form data, so that the filling accuracy of the target form data is improved.
Fig. 16 is a schematic structural diagram of a computer device according to the present application. As shown in fig. 16, the computer device 1000 may include: processor 1001, network interface 1004, and memory 1005, in addition, computer device 1000 may further comprise: a user interface 1003, and at least one communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display) and a Keyboard (Keyboard), and the user interface 1003 may also include a standard wired interface and a 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 also optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 16, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 1005, which is one type of computer storage medium.
In the computer device 1000 shown in fig. 16, the network interface 1004 may provide network communication functions; while user interface 1003 is primarily used as an interface for providing input to a user; and the processor 1001 may be used to invoke the 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 previously. It should be understood that the computer device 1000 described in the present application may also perform the description of the table data processing apparatus 1 in the embodiment corresponding to fig. 15, which is not described herein. In addition, the description of the beneficial effects of the same method is omitted.
Furthermore, it should be noted here that: the present application further provides a computer readable storage medium, in which the computer program executed by the table data processing apparatus 1 mentioned above is stored, and the computer program includes program instructions, when executed by a processor, can execute the description of the table data processing method in the corresponding embodiment of fig. 3, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer storage medium according to the present application, please refer to the description of the method embodiments of the present application.
Those skilled in the art will appreciate that all or part of the processes in implementing the methods of the embodiments may be implemented by a computer program for instructing the relevant hardware, and the program may be stored in a computer readable storage medium, and the program may include processes as embodiments of the methods when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random-access Memory (Random Access Memory, RAM), or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.

Claims (19)

1. A method of table data processing, the method comprising:
displaying the target table data; the target table data comprise authority cooperation areas and header data corresponding to the first cooperation account;
responding to a form editing operation of the target form data aiming at a right 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 right cooperation area corresponding to the first cooperation account;
Responding to the data input operation aiming at the form page, and acquiring form input data;
adding the form input data into a right cooperation area corresponding to the first cooperation account in the target form data;
wherein, the header data of the target table data comprises at least two cell header data; the outputting the form page corresponding to the first collaboration account according to the header data of the target form data and the authority collaboration area corresponding to the first collaboration account includes:
acquiring data entry formats respectively corresponding to the at least two unit cell header data;
outputting the form page corresponding to the first collaborative account according to a data input format corresponding to each piece of cell header data, each piece of cell header data and a permission collaboration area corresponding to the first collaborative account; the form page comprises data input areas corresponding to the header data of each cell respectively; each data input area in the form page is respectively provided with a data input format corresponding to the data of the corresponding cell header.
2. The method of claim 1, wherein the permission collaboration area corresponding to the first collaboration account is a row of cells in the target table data; the unit row corresponding to the first collaborative account comprises authority unit cells;
The outputting the form page corresponding to the first collaboration account according to the header data of the target form data and the authority collaboration area corresponding to the first collaboration account includes:
acquiring cell existing 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 cell existing data in the at least two target cells are data which are 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 a target cell with the same cell existing data in the at least two target cells as a calling cell;
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 collaborative account according to the existing data of the cells in the calling cells, the header data of the target table data and the authority collaboration area corresponding to the first collaborative account; the cell existing data in the calling cell is displayed in the data entry area of the form page.
3. The method of claim 1, wherein the obtaining the data entry format respectively corresponding to the at least two cell header data comprises:
identifying the data type of each cell header data, and determining the data entry format respectively corresponding to each cell header data according to the data type of each cell header data; or alternatively
And acquiring target input formats respectively added for the table header data of each cell as data input formats respectively corresponding to the table header data of each cell.
4. The method according to claim 1, wherein the method further comprises:
acquiring initial form data, and acquiring at least two cooperative accounts corresponding to the initial form data; the at least two cooperative accounts comprise the first cooperative account;
and responding to the triggering operation aiming at the at least two cooperative accounts, and respectively adding an authority cooperation area for each cooperative account in the at least two cooperative accounts in the initial table data to obtain the target table data.
5. The method according to claim 4, wherein adding a permission collaboration area to each of the at least two collaboration accounts in the initial table data to obtain the target table data includes:
Synchronously adding authority cooperation areas for the at least two cooperation accounts in the initial table data to obtain transition table data corresponding to the at least two cooperation accounts;
selecting a header unit bar in the transition table data;
setting a form editing function for the selected header unit bar, and determining the transition form data with the form editing function as the target form data; the form editing function is used for triggering the form editing operation in the target form data.
6. The method according to claim 4, wherein adding a permission collaboration area to each of the at least two collaboration accounts in the initial table data to obtain the target table data includes:
synchronously adding authority cooperation areas for the at least two cooperation accounts in the initial table data to obtain transition table data corresponding to the at least two cooperation accounts;
outputting setting prompt information aiming at the transition form data;
responding to the confirmation operation aiming at the setting prompt information, setting a form editing function for the transition form data, and obtaining the target form data; the form editing function is used for triggering the form editing operation in the target form data.
7. The method of claim 6, wherein the outputting the setup prompt for the transition form data comprises:
responding to data entry operation aiming at cells in the transition form data, and acquiring cell entry data;
when the transition form data comprises combined cells according to the cell entry data and the combined cells are in target cell bars of the transition form data, determining the target cell bars as header cell bars; the unit cells included in the combined unit cell 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 the starting position of the transition table data;
and outputting the setting prompt information aiming at the transition table data according to the determined unit bar position of the header unit bar.
8. The method of claim 6, wherein the outputting the setup prompt for the transition form data comprises:
responding to data entry operation aiming at cells in the transition form data, and acquiring cell entry data;
When detecting that the target cell bar in the transition table data comprises key cells with the number larger than or equal to a second number threshold according to the cell entry data, determining the target cell bar as a header 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 cells are cells containing header keywords and containing non-header keywords with the number smaller than a third number threshold;
and outputting the setting prompt information aiming at the transition table data according to the determined unit bar position of the header unit bar.
9. The method of claim 8, wherein the method further comprises:
acquiring header data of historical table data;
performing word segmentation on header data of the historical table data, and constructing a keyword library according to word segmentation results;
detecting the key cells in the transition table data according to the key word stock; the keyword library contains header keywords.
10. The method of claim 4, wherein the initial form data is created based on a document application;
the obtaining initial table data and obtaining at least two cooperative accounts corresponding to the initial table data includes:
Acquiring the initial form data;
responding to batch adding operation of the document application aiming at the initial form data, and acquiring at least two communication accounts in the communication application;
obtaining mapping document accounts of the at least two communication accounts in the document application respectively;
and determining the mapping document account numbers corresponding to the at least two communication account numbers as the at least two cooperative account numbers.
11. The method of claim 10, wherein the communication applications include 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 number and the second communication account number have account binding relation in the document application; the first communication account number and the second communication account number with account number binding relation correspond to the same mapping document account number.
12. The method according to claim 4, wherein adding a permission collaboration area to each of the at least two collaboration accounts in the initial table data to obtain the target table data includes:
Acquiring the region number of each cooperative account for the authority cooperation region;
adding corresponding authority collaboration areas for each collaboration account in the initial table data according to the number of the areas corresponding to each collaboration account respectively;
adding a mapping relation between the account identification of each cooperative account and the corresponding authority cooperation area in the initial table data to obtain the target table data; the mapping relationship is used for indicating that each cooperative account number has the region editing authority for the affiliated authority cooperation region.
13. The method of claim 4, wherein the at least two collaborative accounts comprise a collaborative account s i Wherein i is a positive integer less than or equal to the total number of the at least two cooperative accounts, and the initial value of i is 1;
the adding the authority collaboration area to each of the at least two collaboration accounts in the initial table data to obtain the target table data includes:
in the initial table data, the collaborative account number s is sequentially i And adding an authority cooperation area until i is equal to the total number of the accounts, and obtaining the target table data.
14. The method of claim 4, wherein the at least two collaborative accounts comprise a second collaborative account;
the method further comprises the steps of:
adding a new region authority for the second cooperative account, and synchronizing the new region authority to a cooperative terminal to which the second cooperative account belongs, so that the cooperative terminal to which the second cooperative account belongs adds a corresponding authority cooperative region for the new cooperative account in the target table data according to the new region authority.
15. The method of claim 1, wherein displaying the target form data comprises:
responding to the unfolding operation of the first collaboration account for the target table data, and displaying the target table data;
and positioning the region position of the authority cooperation region corresponding to the first cooperation account in the displayed target table data, and highlighting the authority cooperation region on the positioned region position.
16. The method according to claim 1, wherein the method further comprises:
responding to the editing operation of the first collaboration account aiming at the non-authority collaboration area in the target form data, and outputting prompt information without editing authority; the non-authority cooperation area is an authority cooperation area except for the authority cooperation area corresponding to the first cooperation account in the target table data.
17. A tabular data processing apparatus, said apparatus comprising:
the form unfolding module is used for displaying target form data; the target table data comprise authority cooperation areas and header data corresponding to the first cooperation account;
the form output module is used for responding to a form editing operation of the target form data aiming at the authority cooperation area corresponding to the first cooperation account, and outputting a form page corresponding to the first cooperation account according to the header data of the target form data and the authority cooperation area corresponding to the first cooperation account;
the form input module is used for responding to the data input operation aiming at the form page and acquiring form input data;
the data adding module is used for adding the form input data to a right cooperation area corresponding to the first cooperation account in the target form data;
wherein, the header data of the target table data comprises at least two cell header data; the form output module outputs a flow of a form page corresponding to the first collaboration account according to header data of the target form data and a permission collaboration area corresponding to the first collaboration account, and the flow comprises the following steps:
Acquiring data entry formats respectively corresponding to the at least two unit cell header data;
outputting the form page corresponding to the first collaborative account according to a data input format corresponding to each piece of cell header data, each piece of cell header data and a permission collaboration area corresponding to the first collaborative account; the form page comprises data input areas corresponding to the header data of each cell respectively; each data input area in the form page is respectively provided with a data input format corresponding to the data of the corresponding cell header.
18. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1-16.
19. 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-16.
CN202111124081.2A 2020-06-01 2020-06-01 Table data processing method and device and computer readable storage medium Active CN113779942B (en)

Priority Applications (1)

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

Applications Claiming Priority (2)

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

Related Parent Applications (1)

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

Publications (2)

Publication Number Publication Date
CN113779942A CN113779942A (en) 2021-12-10
CN113779942B true CN113779942B (en) 2023-08-18

Family

ID=75300071

Family Applications (2)

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

* 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
US9798889B1 (en) * 2015-08-12 2017-10-24 Workday, Inc. Spreadsheet shared region and cell permissions
CN109522533A (en) * 2018-10-12 2019-03-26 平安科技（深圳）有限公司 Table edit method, apparatus, equipment and medium based on web data
CN109814944A (en) * 2018-12-25 2019-05-28 深圳云天励飞技术有限公司 Configuring management method and Related product
WO2019104447A1 (en) * 2017-12-03 2019-06-06 Thomas Stachura Spreadsheet-based software application development
CN110019279A (en) * 2019-04-11 2019-07-16 北京字节跳动网络技术有限公司 Collaboration update method, device, equipment and the storage medium of online document
CN110096679A (en) * 2013-06-15 2019-08-06 微软技术许可有限责任公司 Show that multiple authors' is on the scene in electrical form
CN111144074A (en) * 2018-11-05 2020-05-12 腾讯科技（深圳）有限公司 Document cooperation method and device, computer readable storage medium and computer equipment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
KR20160062565A (en) * 2014-11-25 2016-06-02 삼성전자주식회사 Device and method for providing handwritten content
CN105023188B (en) * 2015-01-07 2019-12-10 泰华智慧产业集团股份有限公司 Digital city management data sharing system based on cloud data
US20170124043A1 (en) * 2015-11-02 2017-05-04 Microsoft Technology Licensing, Llc Sound associated with cells in spreadsheets
CN107680690B (en) * 2016-08-02 2021-01-26 四川智康科技有限责任公司 Clinical information system based on metadata
US10083162B2 (en) * 2016-11-28 2018-09-25 Microsoft Technology Licensing, Llc Constructing a narrative based on a collection of images
US10565403B1 (en) * 2018-09-12 2020-02-18 Atlassian Pty Ltd Indicating sentiment of text within a graphical user interface
CN110008447A (en) * 2019-03-26 2019-07-12 湖南华美信息系统有限公司 The processing method and processing device of electrical form
CN111126022A (en) * 2020-01-06 2020-05-08 深圳维格智数科技有限公司 Data synchronization protocol and method for real-time cooperation on-line electronic form

Patent Citations (8)

* 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
CN110096679A (en) * 2013-06-15 2019-08-06 微软技术许可有限责任公司 Show that multiple authors' is on the scene in electrical form
US9798889B1 (en) * 2015-08-12 2017-10-24 Workday, Inc. Spreadsheet shared region and cell permissions
WO2019104447A1 (en) * 2017-12-03 2019-06-06 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
CN111144074A (en) * 2018-11-05 2020-05-12 腾讯科技（深圳）有限公司 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
CN110019279A (en) * 2019-04-11 2019-07-16 北京字节跳动网络技术有限公司 Collaboration update method, device, equipment and the storage medium of online document

Also Published As

Publication number Publication date
CN113779942A (en) 2021-12-10
CN112632928B (en) 2021-09-28
CN112632928A (en) 2021-04-09

Similar Documents

Publication Publication Date Title
CN113779942B (en) Table data processing method and device and computer readable storage medium
CN106682219B (en) Associated document acquisition method and device
CN110475140B (en) Bullet screen data processing method and device, computer readable storage medium and computer equipment
CN112632942A (en) Document processing method, device, equipment and medium
CN107465599A (en) Schedule method to set up and device in a kind of instant messaging
CN111654429A (en) To-do-list creating method, display method, terminal device and storage medium
EP2919097A1 (en) Information processing system and information processing method for character input prediction
CN111541946A (en) Automatic video generation method and system for resource matching based on materials
CN111666740A (en) Flow chart generation method and device, computer equipment and storage medium
CN105528451A (en) Method and device for processing photos in photo album
CN103649947A (en) Method for supporting collection of an object comprised in a generated image, and a recording medium able to be read by terminal devices and computers
CN111639503A (en) Conference data processing method and device, storage medium and equipment
CN110990700A (en) Comment information display method, device, client, server and system
US8074176B2 (en) Electronic communications dialog using sequenced digital images stored in an image dictionary
CN114239524A (en) Questionnaire generation method, questionnaire generation device, computer equipment and storage medium
CN115662019A (en) Method, apparatus, device and medium for guiding user to open storage cabinet lattice
CN109189293B (en) Evaluation interaction method and device for rich media content, electronic equipment and storage medium
CN112668300B (en) Formula editing method, device, computer equipment and storage medium
CN110768896B (en) Session information processing method and device, readable storage medium and computer equipment
CN107133204B (en) Terminal shortcut input method
CN112035113A (en) Navigation bar loading method, device, equipment and medium of H5 page
CN115695543A (en) Microscopic image sharing method and microscope system
CN112449072A (en) Information processing apparatus, information processing system, and information processing method
CN112328140A (en) Image input method, device, equipment and medium thereof
KR101817532B1 (en) Media making system and method thereof

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
GR01 Patent grant
GR01 Patent grant