Document review method and apparatus

Abstract

The present specification provides a document review method and device, comprising: in response to a review instruction triggered based on a current document, obtaining a document list and displaying the document list in the current document; in response to a selection instruction for any document in the document list, obtaining the any document as a target document; extracting specified content in the target document and displaying the specified content in the current document.

Description

TECHNICAL FIELD

[0001] The present specification relates to the technical field of Internet, and particularly relates to a document review method and device. BACKGROUND

[0002] With the rapid development of the Internet, the types of documents used to carry data information tend to be diversified, and the increasing number of documents gradually affects the efficiency of users querying historical documents once browsed. When the user reviews a specific document, a large amount of meaningless human and time costs will be consumed, and the user experience is poor. SUMMARY

[0003] Therefore, the present specification provides a document review method and device to solve the problems in the related art.

[0004] Specifically, the present specification is realized by the following technical solutions:

[0005] According to a first aspect of the present specification, a document review method is provided, comprising:

[0006] In response to a review instruction triggered based on a current document, a document list is obtained, and the document list is displayed in the current document;

[0007] In response to a selection instruction for any document in the document list, the any document is obtained as a target document;

[0008] The specified content in the target document is extracted, and the specified content is displayed in the current document.

[0009] According to a second aspect of the present specification, a document review device is provided, comprising:

[0010] A document list display unit is configured to obtain a document list in response to a review instruction triggered based on a current document, and display the document list in the current document;

[0011] A target document obtaining unit is configured to obtain any document in the document list as a target document in response to a selection instruction for the any document;

[0012] A document content display unit is configured to extract specified content in the target document, and display the specified content in the current document.

[0013] According to a third aspect of the present specification, a computer readable storage medium is provided, which stores a computer program. When the program is executed by a processor, the steps of the method according to the first aspect are implemented.

[0014] According to a fourth aspect of the embodiments of the present specification, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to the first aspect when executing the program.

[0015] In the technical solutions provided in the present specification, the user triggers a review instruction in the current document to obtain a document list, and the user can select any document in the document list and directly obtain specified content in the document to display in the current document. The time for the user to query the specified content in any document is effectively shortened, thereby improving the user's review efficiency and user experience.

[0016] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present specification. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the present specification, and other drawings can also be obtained by those skilled in the art based on these drawings.

[0018] Figure 1 is a flowchart of a document review method according to an exemplary embodiment of the present specification;

[0019] Figure 2 is an interaction diagram of a document review according to an exemplary embodiment of the present specification;

[0020] Figure 3 is a display interface of a document review instruction triggering interface according to an exemplary embodiment of the present specification;

[0021] Figure 4 is a display interface of a document review homepage according to an exemplary embodiment of the present specification;

[0022] Figure 5 is a display interface of a document review homepage according to an exemplary embodiment of the present specification;

[0023] Figure 6 is a display interface of a document review homepage according to an exemplary embodiment of the present specification;

[0024] Figure 7 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present specification;

[0025] Figure 8 is a structural schematic diagram of a document review device according to an example embodiment of the present specification. DETAILED DESCRIPTION

[0026] The example embodiments will be described in detail below with reference to the accompanying drawings. In the following description, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following example embodiments are not meant to represent all implementations consistent with the present specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present specification as detailed in the appended claims.

[0027] The terminology used in the present specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the present specification. As used in the present specification and the appended claims, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0028] It should be noted that the steps of the methods in other embodiments need not necessarily be performed in the order shown and described in the present specification. In some other embodiments, the steps included in the methods can be more or less than those described in the present specification. Furthermore, a single step described in the present specification can be broken down into multiple steps in other embodiments; and multiple steps described in the present specification can be combined into a single step in other embodiments.

[0029] Figure 1 is a flowchart of a document review method according to an example embodiment of the present specification.

[0030] In this embodiment, the documents can be divided into conference documents and non-conference documents according to whether they are applied to conference scenarios. The conference documents can be used to demonstrate or record the conference content of any conference. The non-conference documents can exist in the form of papers, experimental reports, etc., and do not need to contain conference-related content like the conference documents described above. In fact, the storage format of the non-conference documents can also be diverse, such as represented in the form of PDF documents, tables, patterns, or geometric figures, etc., which is not limited in the present specification.

[0031] Further, the conference documents that have existed and been recorded in the past can be characterized by historical conference documents.

[0032] Meanwhile, the conference document can be divided into a periodic conference document and a non-periodic conference document according to whether the conference corresponding to the conference document has periodicity. The periodic conference document can be used to record a conference with periodicity and coherence. The non-periodic conference document can be used to record any independent conference. The document has a document attribute used to represent the basic characteristics of the document. The document attribute can be determined according to the attribute identifier carried by the document, or can be confirmed according to the preset correspondence between the current document and the document attribute. This specification does not limit this.

[0033] As shown in Figure 1 The method can include the following steps:

[0034] S101, in response to a review instruction triggered based on a current document, a document list is obtained, and the document list is displayed in the current document.

[0035] The current document is a document displayed in an operation interface of a current user. When a review instruction triggered based on a current document is received, a document list corresponding to the current document can be obtained, and the document list can be displayed in the operation interface.

[0036] The review instruction can trigger the operation of obtaining the document list through control clicking, voice recognition and other technologies. The specific implementation manner can be adjusted according to the actual use scene, and this specification does not limit this.

[0037] The document list can be used to display documents that the user may need to review. The documents included in the document list can be determined according to the last access time, the document attribute of the current document or the user-defined rule, and this specification does not limit this.

[0038] In an embodiment, assuming that the document attribute can be divided into a periodic conference document, a non-periodic conference document and a non-conference document. Then, after detecting and determining the document attribute of the current document, the corresponding document list can be obtained based on the document attribute.

[0039] For example, in the case that the document attribute is a periodic meeting document, a list of historical meeting documents in the period is determined. Assuming that a periodic meeting with the meeting name "Product Operation Biweekly Meeting" was held two weeks ago, and the periodic meeting is held once every two weeks, and a periodic meeting document is recorded each time, when a brand new periodic meeting document is created as the current document, if a specific review document control is clicked in the interface of the current document, a list of historical meeting documents in the two-week period before the current time can be obtained. Since periodic meeting documents have stronger relevance and content continuity compared to ordinary documents, the reference value of the review document in actual scenarios can be improved. Therefore, the embodiment can display the historical meeting documents corresponding to the periodic meeting document in the period of the periodic meeting document, thereby shortening the time required by the user to query the review document and improving the user experience.

[0040] It can be envisaged by those skilled in the art that the list of historical meeting documents determined in the case that the document attribute is a periodic meeting document can change the determination range of the documents contained therein according to other manners or rules. For example, a meeting theme representing a periodic meeting with a specific theme to which the current document belongs is set for any document, and after the meeting theme of the current document is determined, a list of historical meeting documents meeting the meeting theme is obtained. This is not limited in the specification.

[0041] For another example, in the case that the document attribute is a non-periodic meeting document, a list of historical meeting documents is obtained. Assuming that there is a non-periodic meeting with the meeting name "New Product Launch Meeting", and there is a non-periodic meeting document as the current document, a list of historical meeting documents can be obtained based on the current document. Since the list of historical meeting documents obtained when reviewing the non-periodic meeting document is no longer limited by the periodic time, the embodiment can have higher expansibility and flexibility in the scope of reviewing the document.

[0042] For another example, in the case that the document attribute is a non-meeting document, a document access list in a predetermined time period is obtained. When the review instruction is triggered by the current document, a document access list in a predetermined time period can be obtained. The document access list can preferentially obtain documents with specified keywords such as "meeting" and "record" in the document name, so that the documents in the document access list are closer to the actual needs of the user.

[0043] The specific content of the above document attribute can be divided according to the actual application scenario or nature of the current document, for example: in the office scenario where the enterprise or company uses the document to cooperate or record the meeting content, the document attribute can be divided into: periodic meeting document, non-periodic meeting document and non-meeting document. Or according to the actual storage location of the document, the document attribute can be divided into: online cloud document, local document. This specification does not limit this.

[0044] The person skilled in the art can conceive that the above document list and document access list can change the acquisition range according to the identity permission of the user, wherein the user can represent a creation user or an access user. For example: there is a "document 1" created by a user A, which contains the content of a high-level meeting of an enterprise, and a "document 2" created by a user B, which contains the content of a weekly meeting summary of each group of a department of the enterprise, and the user A is the general manager of the department of the enterprise, and belongs to the direct superior of the above department, and has the identity permission of accessing each group document. Then when the user A creates "document 3", if the acquisition range of the document list is determined according to the identity permission of the creation user, the document created by the creation user itself can be acquired, that is, the user A can acquire the document list containing "document 1" created by himself. If the acquisition range of the document list is determined according to the identity permission of the access user, and "document 3" allows the user A to access, the document that can be accessed according to the identity permission of the access user can be acquired, that is, the user A can acquire the document list of "document 1" and "document 2". The identity permission of the user can be determined according to pre-setting or user self-definition, and this specification does not limit this.

[0045]

[0046]

[0047] Meanwhile, the arrangement order of the documents in the above document list can be determined according to the last modification time of the document, the last access time of the user or the priority rule defined by the user, and this specification does not limit this.

[0048] After the document list is acquired, the documents in the document list that match the keywords can be filtered according to the received document search request for the document list. The document search request can contain one or more keywords. In this way, the problem of being unable to accurately locate a specific document due to too many documents in the document list is solved, and the efficiency of the user querying any document in the document list is improved.

[0049] ​​It can be conceived by those skilled in the art that, in addition to the local search manner for the acquired document list, the document search request can also be in an online search manner for conference documents not in the acquired document list by keywords, URL addresses, etc. The document search request can use different search manners to realize document search according to specific use scenarios, which is not limited in the specification.

[0050] S102, in response to a selection instruction for any document in the document list, acquiring the any document as a target document.

[0051] The selection instruction is used to select a specified document in the document list. Similar to the review instruction above, the selection instruction can realize the selection operation of the any document by clicking the control, voice recognition, eye capture, etc. This is not limited in the specification. At the same time, the target document is usually stored in a specific storage space and needs to be acquired through a corresponding legal request.

[0052] In an embodiment, the any document is assigned a docKey (document identifier) as a unique identifier of the any document, and the OSS (Object Storage Service) address for representing the actual storage location of the any document can be queried according to the docKey carried by the any document. Since the OSS certificate contains the OSS address and access permissions and credentials, the OSS address of the any document can be acquired according to the OSS certificate corresponding to the docKey, and the actual document of the any document can be acquired from the OSS address as the target document.

[0053] S103, extracting the specified content in the target document and displaying the specified content in the current document.

[0054] The specified content is the document content of the target document that meets the specified type, such as: to-do items with checkboxes, lines with @ someone, lines with a keyword, lines with a certain text attribute (such as: title 1, title 2, title 3, quotation, etc.), hyperlinks, uploaded files, videos, audios, etc. As long as the text, style attribute, and type of the target document have some common features, they can be extracted as document content, which is not limited in the specification. Among them, the to-do status of the to-do item can be determined by checkbox, text strikethrough, etc., which is not limited in the specification. The common features can be determined and divided by the type below.

[0055] In an embodiment, the specified content can be obtained by parsing the target document to obtain each piece of document content in the target document and the type of each piece of document content, and extracting the document content of the type conforming to the preset type as the specified content. For example, there is a target document containing two to-do items with checkboxes, a video, and a piece of text. Assuming that the preset type is only to-do items with checkboxes, the specified content obtained does not contain other content in addition to the above two to-do items with checkboxes. The preset type can be adjusted according to the actual application scenario, and the present specification does not limit this.

[0056] When a document content of the target document is modified or the like in the current document, the corresponding synchronization operation can also be performed on the document content in the target document.

[0057] In an embodiment, an operation instruction for any document content in the current document is received, and in a case where the any document content is the specified content, the operation instruction is executed on the current document and the target document respectively. In a case where the any document content is not the specified content, the operation instruction is only executed on the current document. The operation instruction can be used to represent operations such as modifying the text of the specified content, the to-do state, and the like, and the present specification does not limit this. This makes the specified content common to the current document and the target document realize bidirectional synchronization, thereby ensuring the real-time content between the two. The situation that the user still uses the target document after the current document modifies the specified content in the target document cannot be timely understood is avoided.

[0058] The specified content can be a task and be handed over to a designated person in charge, for example, the above purpose can be achieved by setting the corresponding relationship between the task and the person in charge. When the specified content is close to the time when it needs to be completed, a reminder message can be sent to the person in charge through the user account of the corresponding person in charge to urge the person in charge to complete the processing as soon as possible.

[0059] In an embodiment, the current document provides a separate reminder option for any document content and a batch reminder option for multiple document contents. In a case where the separate reminder option is triggered, the reminder information is sent to the processing personnel corresponding to the any document content. In a case where the batch reminder option is triggered, the reminder information is sent to the processing personnel corresponding to the multiple document contents.

[0060] The above task can be divided into high, medium, and low reminder levels according to its urgency to assist the user in judging which task has a higher processing priority.

[0061] The above-mentioned person in charge can be increased or modified according to actual conditions, for example, the original person in charge A who handles a task cannot handle it due to reasons, and another person in charge B can be assigned to handle the task. This specification does not limit this.

[0062] As can be seen from the above embodiments, the document review method of the specification can ensure that the user does not need to manually review any content in the past document, and can directly browse the specified content that has been automatically extracted by selecting the target document that needs to be reviewed in the operation interface of the current document, greatly reducing the operation cost of the user and improving the user experience in the document review process. At the same time, the operation instruction of the specified content in the current document can be automatically synchronized to the target document, which guarantees data consistency while saving redundant operations. In addition, the specification also proposes a document content follow-up function, which effectively improves the document processing efficiency.

[0063] The technical solution of the specification can be applied to a C / S (Client-Server) architecture. Figure 2 is an interactive diagram of a document review according to an example embodiment of the specification. As shown in Figure 2 , the client and the server (i.e. the above-mentioned C / S architecture) can interact through various types of wired or wireless connections, which are not limited by the specification. The interaction process between the client and the server can include the following steps:

[0064] S201, receiving a review instruction triggered based on a current document.

[0065] In an embodiment, it is assumed that a client receives a review instruction initiated by a user in order to review a document in the display interface of a current document. As shown in Figure 3 , the interface displays the document name 310 of the current document named "Product Operation Biweekly Meeting", the document basic information 320 for displaying the creation user, creation time, and meeting location corresponding to the current document, and the quick document review control 331 and the ordinary document review control 332. Among them, the quick document review control 331 and the ordinary document review control 332 have similar functions, the difference is that the review instruction triggered by the quick document review control 331 is directed to the meeting document with the closest creation time to the current document, and when the ordinary document review control 332 triggers the review instruction, the user can further select the document that needs to be reviewed.

[0066] S202, sending a document list request containing the document properties of the current document.

[0067] In an embodiment, when the user clicks the normal document review control 332, the client can send a document list acquisition request to the server. Assuming that the current document corresponds to a meeting "Product Operation Biweekly Meeting" which is scheduled to be held from May 5th to the end of the year, and is held once every two weeks, and a document is created each time, the document attribute of the current document can be determined as a periodic meeting document. The client can send the document attribute to the server together in the above-mentioned document list acquisition request.

[0068] S203, acquiring a corresponding document list according to the document list request.

[0069] In an embodiment, when the server receives the above-mentioned document list acquisition request, it determines that the current document is a periodic meeting document according to the document attribute therein, and searches for other meeting documents within a two-week period before the current time to form a historical meeting document list.

[0070] S204, returning the document list.

[0071] In an embodiment, the server returns the above-mentioned historical meeting document list to the client.

[0072] S205, rendering the document list based on the current document.

[0073] In an embodiment, after receiving the above-mentioned document list, it can be rendered and displayed in the display interface of the current document. The display interface of the above-mentioned document list is shown in FIG. 4B, which displays a document search box 410 for searching documents, a document list 420, a document name 421 of any document in the document list, and document information including the creation time of the any document and the number of to-do items, based on the display interface of FIG. 4A. Figure 4 Figure 3 Since the user has not input any information in the document search box 410, and the current document belongs to a periodic meeting document, the document list 420 can display other meeting documents within the periodic time of the meeting corresponding to the current document by default, i.e., the meeting documents from May 5th to the current time.

[0074] S206, receiving a selection instruction for any document in the document list.

[0075] In an embodiment, the "Product Operation Biweekly Meeting" document created on May 19th in the above-mentioned document list 420 is selected by clicking.

[0076] S207, sending a document acquisition request containing the docKey of the any document.

[0077] ​In one embodiment, the client obtains the docKey of the "Product Operation Bi-weekly Meeting" document created on May 19. The client can include the docKey in the document retrieval request and send it to the server together.

[0078] S208, Obtain the OSS certificate of the corresponding target document according to the document acquisition request.

[0079] In one embodiment, when the server receives the document retrieval request, it can query the corresponding OSS certificate containing the document OSS address based on the docKey contained in the document retrieval request, and return it to the client in the form of an OSS certificate containing the document OSS address, so that the client can initiate another document retrieval request to the server based on the OSS certificate.

[0080] S209, Return the OSS certificate.

[0081] In one embodiment, the server returns the aforementioned OSS certificate to the client.

[0082] S210, Obtain the corresponding target document based on the OSS certificate.

[0083] In one embodiment, the client accesses a specific OSS server based on the received OSS certificate to obtain the corresponding target document.

[0084] S211, parse and extract the to-do items from the target document, and display the to-do items in the current document.

[0085] In one embodiment, after the client obtains the target document, it parses the document to obtain three to-do items of type checkbox. The client then displays these to-do items in the current document. The display interface for these to-do items is as follows: Figure 5 As shown, this interface is in Figure 3 Based on this, a one-click reminder control 510 for expediting all pending tasks is shown, along with a text created in the current document and a meeting review section 530 for the target document. The meeting review section 530 for the target document may include a local one-click reminder control 531 for expediting pending tasks in any target document, a document name 532 representing the target document, and pending task entries 533 representing whether preset tasks in the target document have been completed.

[0086] S212, Modify the pending status of the pending item.

[0087] In an embodiment, when a user clicks on any to-do item 533 in the meeting review section 530 of the target document, the checkbox state in the to-do item can be changed, and when the checkbox is in an unselected state, it represents that the to-do item has not been completed. When the checkbox is in a selected state, it represents that the to-do item has been completed. Meanwhile, the to-do state of the corresponding to-do item in the target document is also changed.

[0088] S213, receiving a reminder instruction for the responsible person corresponding to the to-do item.

[0089] In an embodiment, in order to timely process the uncompleted to-do item, a user can send a reminder instruction to the responsible person corresponding to the to-do item to remind the responsible person to process it in time. The display interface of the to-do item is shown in FIG. 6, which displays a to-do item operation control group 610, a to-do item detailed section 620, a to-do item creation control 621, a to-do item priority selection control 622, and a separate reminder control 623 for any to-do item 533 on the basis of Figure 6 Figure 5 The to-do item operation control group 610 includes a to-do item responsible person setting control, a to-do item processing time setting control, and a more information display control. By clicking on the to-do item responsible person setting control, a user can add or modify the responsible person information corresponding to the to-do item. By clicking on the to-do item processing time setting control, a user can set the expected completion time of the to-do item. By clicking on the more information display control, a user can view the to-do item detailed section 620 that was not displayed before. The to-do item detailed section 620 is used to display detailed contents that are not displayed in the to-do item operation control group 610, which can include the to-do item creation control 621, the to-do item priority selection control 622, and the separate reminder control 623. By clicking on the to-do item creation control 621, a user can create a brand new to-do item in the corresponding meeting review section 530. By selecting the sub-controls such as “high”, “medium”, “low”, and “none” in the to-do item priority selection control 622, a user can set the processing priority of the to-do item. When a user does not need to send a reminder to all to-do items, the separate reminder control 623 in the selected to-do item can be used to separately notify the responsible person of the to-do item to process it in time.

[0090] Figure 7 FIG. 1 is a schematic structural diagram of an electronic device in an exemplary embodiment. Please refer to Figure 7 ​At the hardware level, the electronic device comprises a processor, an internal bus, a network interface, a memory and a non-volatile memory, and can further comprise other required hardware. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs, and forms the document review device at the logical level. Of course, the present specification does not exclude other implementation manners, such as a logic device or a combination of software and hardware, in addition to the software implementation manner. That is, the execution subject of the following processing flow is not limited to each logical unit, but can also be hardware or a logic device.

[0091] Corresponding to the foregoing embodiments of the conference joining method, the present specification also provides embodiments of a conference joining device.

[0092] Reference is made to Figure 8 , Figure 8 is a structural diagram of a document review device according to an example embodiment. As shown in Figure 8 , in the software implementation manner, the conference joining device can comprise:

[0093] a document list display unit 801 configured to acquire a document list and display the document list in a current document in response to a review instruction triggered based on the current document;

[0094] a target document acquisition unit 802 configured to acquire any document in the document list as a target document in response to a selection instruction for the any document;

[0095] a document content display unit 803 configured to extract specified content in the target document and display the specified content in the current document.

[0096] Optionally, the device further comprises:

[0097] a document attribute acquisition unit 804 configured to determine a document attribute of the current document;

[0098] a document list acquisition unit 805 configured to acquire the document list based on the document attribute.

[0099] Optionally, the document list display unit 801 is specifically configured to:

[0100] in a case where the document attribute is a periodic conference document, acquire a historical conference document list in the period;

[0101] in a case where the document attribute is a non-periodic conference document, acquire a historical conference document list;

[0102] in a case where the document attribute is a non-conference document, acquire a document access list in a predetermined time period.

[0103] Optionally, after the list of documents is acquired, the apparatus further includes:

[0104] a document searching unit 806 configured to receive a document search request for the list of documents, the document search request comprising one or more keywords;

[0105] filtering documents in the list of documents that match the keywords.

[0106] Optionally, the apparatus further includes:

[0107] a designated content extraction unit 807 configured to parse a target document to obtain each piece of document content in the target document and a type of each piece of document content;

[0108] extracting document content of the type as the designated content.

[0109] Optionally, the apparatus further includes:

[0110] a document content synchronization unit 808 configured to receive an operation instruction for any piece of document content in the current document;

[0111] in a case where the any piece of document content is the designated content, executing the operation instruction in the current document and the target document respectively.

[0112] Optionally, the document list display unit 801 is specifically configured to:

[0113] the designated content comprises a to-do list.

[0114] Optionally, the apparatus further includes:

[0115] a document content follow-up unit 809 configured to provide a single follow-up option for any piece of document content and a batch follow-up option for multiple pieces of document content in the current document;

[0116] in a case where the single follow-up option is triggered, sending follow-up information to a handler corresponding to the any piece of document content.

[0117] in a case where the batch follow-up option is triggered, sending follow-up information to handlers corresponding to the multiple pieces of document content.

[0118] The functions and roles of the units in the apparatus are implemented in the processes described above, and thus will not be repeated here.

[0119] For apparatus embodiments, since they basically correspond to the method embodiments, relevant parts are explained by referring to the parts of the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed to multiple network units. Some or all of the modules can be selected to achieve the purposes of the schemes of the present specification according to actual needs. Those skilled in the art can understand and implement without creative effort.

[0120] Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions can be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0121] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit), and the apparatus can be implemented as special purpose logic circuitry.

[0122] Computers suitable for the execution of a computer program include, by way of example, general and / or special purpose microprocessors, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory and / or a random access memory. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.

[0123] Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0124] While this specification contains many specifics, these should not be construed as limitations on the scope of any invention or on the required scope of patentable subject matter, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also combine in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a sub-combination or variation of a sub-combination.

[0125] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring or implying that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products.

[0126] Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0127] The above-described embodiments are merely possible implementations of the present disclosure, and do not limit the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure shall fall within the scope of the present disclosure.

Claims

1. A document review method, characterized in that, include: In response to a review instruction triggered based on the current meeting document, a list of historical meeting documents is retrieved and displayed in the current meeting document; wherein, retrieving the document list includes: determining the document attributes of the current meeting document; retrieving the document list based on the document attributes; the document attributes characterize the application scenario or nature of the current meeting document; the step of retrieving the document list based on the document attributes includes: if the document attributes are periodic meeting documents, retrieving a list of historical meeting documents within that period; if the document attributes are non-periodic meeting documents, retrieving a list of historical meeting documents. In response to a selection instruction for any document in the document list, the document is selected as the target document. Extract the to-do items from the target document and display them in the current meeting document; the extraction of to-do items from the target document includes: parsing the target document to obtain the content of each document and the type of each document content; extracting the document content whose type is to-do item. If the reminder option in the current meeting document is triggered, send a reminder message to the person in charge of the pending task; Receive operation instructions for the content of any document in the current meeting documents; If the content of any of the documents is the to-do item, the operation instructions are executed in the current meeting document and the target document respectively.

2. The method according to claim 1, characterized in that, After obtaining the document list, the following is also included: A document search request is received for the document list, the document search request containing one or more keywords; Filter the document list to find documents that match the specified keywords.

3. The method according to claim 1, characterized in that, Also includes: The current meeting document provides individual reminder options for any document content and batch reminder options for multiple document contents; When the individual reminder option is triggered, a reminder message is sent to the person in charge of any pending task. When the batch reminder option is triggered, reminder information is sent to the personnel responsible for handling multiple pending tasks.

4. A document review device, characterized in that, include: The document list display unit is used to respond to a review instruction triggered based on the current meeting document, obtain a list of historical meeting documents, and display the document list in the current meeting document; wherein, obtaining the document list includes: determining the document attributes of the current meeting document; obtaining the document list based on the document attributes; the document attributes characterize the application scenario or nature of the current meeting document; obtaining the document list based on the document attributes includes: if the document attributes are periodic meeting documents, obtaining a list of historical meeting documents within that period; if the document attributes are non-periodic meeting documents, obtaining a list of historical meeting documents. The target document acquisition unit is configured to acquire any document as the target document in response to a selection instruction for any document in the document list; The document content display unit is used to extract the to-do items from the target document and display the to-do items in the current meeting document; the extraction of the to-do items from the target document includes: parsing the target document to obtain each document content and the type of each document content; and extracting the document content whose type is a to-do item. The document content reminder unit is used to send reminder information to the personnel responsible for handling the pending items when the reminder option in the current meeting document is triggered. The document content synchronization unit is used to receive operation instructions for any document content in the current meeting document; if any document content is the to-do item, the operation instructions are executed in the current meeting document and the target document respectively.

5. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method as described in any one of claims 1 to 3.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method as described in any one of claims 1 to 3.

Images