WO2023124377A1

WO2023124377A1 - Document review method and apparatus

Info

Publication number: WO2023124377A1
Application number: PCT/CN2022/124690
Authority: WO
Inventors: 付婧语; 康上明学; 姜淑芬; 墨影; 于志超; 董旭; 刘欣欣; 董鹏
Original assignee: 钉钉(中国)信息技术有限公司
Priority date: 2021-12-31
Filing date: 2022-10-11
Publication date: 2023-07-06
Also published as: CN114416968A

Abstract

Provided in the present application are a document review method and apparatus. The method comprises: in response to a review instruction that is triggered on the basis of the current document, acquiring a document list, and presenting the document list in the current document; in response to a selection instruction for any one document in the document list, acquiring the any one document to serve as a target document; and extracting specified content from the target document, and presenting the specified content in the current document.

Description

Document review method and device

This application claims the priority of the Chinese patent application No. 202111682052.8 entitled "Document Review Method and Apparatus" filed with the China Patent Office on December 31, 2021, the entire contents of which are incorporated herein by reference.

technical field

This specification relates to the field of Internet technologies, and in particular to a document review method and device.

Background technique

With the rapid development of the Internet, the types of documents used to carry data information tend to be diversified. At the same time, the cumulative number of documents gradually affects the efficiency of users' query of historical documents they have browsed. It will consume a lot of meaningless manpower cost and time cost when the user reviews a specific document, and the user experience is poor.

Contents of the invention

In view of this, this specification provides a document review method and device to solve the deficiencies in related technologies.

According to the first aspect of the embodiments of this specification, there is provided a document review method, including: in response to a review instruction triggered based on the current document, obtaining a document list, and displaying the document list in the current document; A document selection instruction, obtain any document as a target document; extract the specified content in the target document, and display the specified content in the current document.

According to the second aspect of the embodiments of this specification, there is provided a document review device, including: a document list display unit, configured to acquire a document list in response to a review instruction triggered based on the current document, and display the document list in the current document; The target document obtaining unit is used to obtain 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 specified content in the target document and display the specified content in the current document content.

According to a third aspect of the embodiments of this specification, there is provided a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the method in the first aspect are implemented.

According to the fourth aspect of the embodiments of this specification, there is provided an electronic device, including a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the method in the first aspect when executing the program A step of.

In the technical solution provided in this manual, the user can obtain the document list by triggering the review command in the current document, and at the same time, the user can select any document in the document list and directly obtain the specified content in the document to display in the current document. It effectively shortens the time for the user to query the specified content in any document, thereby improving the user experience while improving the efficiency of the user's review of the document.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of this specification or related technologies, the following will briefly introduce the drawings that need to be used in the embodiments or descriptions of the prior art. Obviously, the drawings in the following description are only For some embodiments described in this specification, those skilled in the art can also obtain other drawings according to these drawings.

Fig. 1 is a schematic flowchart of a document review method according to an exemplary embodiment of the present disclosure.

Fig. 2 is an interactive diagram of document review according to an exemplary embodiment of the present disclosure.

Fig. 3 is a schematic diagram of a display interface triggering a document review instruction according to an exemplary embodiment of the present disclosure.

Fig. 4 is a schematic diagram of a presentation interface of a document review homepage according to an exemplary embodiment of the present disclosure.

Fig. 5 is a schematic diagram of a presentation interface of a document review homepage according to an exemplary embodiment of the present disclosure.

Fig. 6 is a schematic diagram of a presentation interface of a document review homepage according to an exemplary embodiment of the present disclosure.

Fig. 7 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Fig. 8 is a schematic structural diagram of a document review device according to an exemplary embodiment of the present disclosure.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present specification as recited in the appended claims.

The terms used in this specification are for the purpose of describing particular embodiments only, and are not intended to limit the specification. As used in this specification and the appended claims, the singular forms "a" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be noted that in other embodiments, the steps of the corresponding methods may not necessarily be performed in the order shown and described in this specification. In some other embodiments, the method may include more or less steps than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; multiple steps described in this specification may also be combined into a single step in other embodiments describe. Hereinafter, unless otherwise specified, "this specification" has the same meaning as "this disclosure" and "this application".

Fig. 1 is a schematic flowchart of a document review method 100 shown in an exemplary embodiment of this specification.

In this embodiment, documents can be divided into meeting documents and non-meeting documents according to whether they are applied to meeting scenarios, and meeting documents can be used as documents for displaying or recording meeting content of any meeting. Non-conference documents can exist in the form of papers, experimental reports, etc., and do not need to contain conference-related content like the above-mentioned conference documents. In fact, the non-conference documents can also be stored in a variety of formats, such as PDF documents, tables, patterns, etc. Or geometric figures and other forms, which are not limited in this specification.

Further, conference files that existed and were recorded in the past can be represented by historical conference files.

At the same time, the above conference files can be divided into periodic conference files and non-periodic conference files according to whether the conference corresponding to the conference files is periodic. Wherein, the above-mentioned periodical meeting file can be used to record meetings with periodicity and content continuity. The aperiodic meeting files described above can be used to record any individual meeting. Documents have document attributes used to characterize the basic features of documents. Document attributes can be determined according to the attribute identifier carried by the document, or confirmed according to the preset correspondence between the current document and document attributes, which is not limited in this specification.

As shown in FIG. 1 , the document review method 100 may include the following steps S101 to S103. Each step in the document review method 100 will be described below.

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

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

The above-mentioned review command can trigger the operation of obtaining the document list through control clicks, voice recognition and other technologies, and its specific implementation method can be adjusted according to the actual usage scenario, which is not limited in this specification.

The above document list can be used to display documents that the user may need to review, and the documents included in the document list can be determined according to the last access time, document attributes of the current document, or user-defined rules, which is not limited in this specification.

In some embodiments, hypothetical document attributes can be divided into: periodic meeting documents, non-periodic meeting documents and non-meeting documents. Then, after the document attribute of the current document is detected and determined, the corresponding document list can be obtained based on the document attribute.

In an embodiment, when the document attribute is a periodic meeting document, a list of historical meeting documents within the period is determined. Assume that there is a recurring meeting named "Product Operation Biweekly Meeting" that started two weeks ago, and the recurring meeting is held every two weeks, and a recurring meeting document is recorded each time, then when creating a new When the periodic meeting document is used as the current document, if you click a specific review document control in the interface of the current document, you can obtain a list of historical meeting documents within two weeks before the current moment. Since periodic meeting documents have stronger relevance and content coherence than ordinary documents, it can improve the reference significance of reviewing documents as users in actual scenarios. Therefore, this embodiment can display the historical meeting documents corresponding to the periodic meeting documents for the periodical meeting documents, so as to shorten the time for reviewing the documents required by the user query and improve the user experience.

Those skilled in the art can conceive that, in the case that the above-mentioned document attribute is a periodic meeting document, the determined historical meeting document list may change the determined range of documents contained therein according to other methods or rules. For example, set a meeting theme for any document to represent a periodic meeting with a specific theme to which the current document belongs, and obtain a list of historical meeting documents matching the meeting theme after the meeting theme of the current document is determined. This is not limited in this specification.

In yet another embodiment, when the document attribute is an aperiodic meeting document, a list of historical meeting documents is obtained. Assuming that there is an aperiodic meeting whose meeting name is "new product launch", and there is an aperiodic meeting document as the current document, then the historical meeting document list can be obtained based on the current document. Since the list of historical meeting documents obtained when reviewing documents for the aperiodic meeting documents is no longer limited by periodic time, this embodiment can have higher scalability and flexibility in terms of the scope of reviewing documents.

In another embodiment, when the document attribute is a non-meeting document, a document access list within a predetermined time period is acquired. When the above-mentioned current document triggers the review instruction, a document access list within a predetermined time period can be obtained, and the document access list can preferentially obtain documents whose document names contain specified keywords such as "meeting" and "record", so that the document access The documents in the list are closer to the documents actually needed by the user.

The specific content of the above document attributes can be divided according to the actual application scenario or nature of the current document. For example, in an office scenario where an enterprise or company uses documents to coordinate or record meeting content, document attributes can be divided into periodic meeting documents, non-periodic meeting documents, and non-meeting documents. Or according to the actual storage location of the document, the document attribute can be divided into: online cloud document, local document. This is not limited in this specification.

Those skilled in the art can imagine that the above document list and document access list can change the scope of acquisition according to the identity and authority of the user, wherein the user can represent a creating user or an accessing user. For example: "Document 1" created by a user A contains the content of a high-level meeting of an enterprise, and "Document 2" created by a user B contains the summary content of a department's weekly meetings of each group in the enterprise. The general manager of the department of the enterprise belongs to the direct supervisor of the above department and has the identity authority to access the documents of each group. Then, when user A creates "document 3", if the scope of obtaining the document list is determined according to the identity and authority of the creating user, the document created by the creating user can be obtained, that is, user A can obtain the "document 1" created by himself list of documents. If the scope of obtaining the document list is determined according to the identity and authority of the accessing user, and "document 3" allows user A to access, then the documents that can be accessed according to the identity and authority of the accessing user can be obtained, that is, user A can obtain "document 1 ” and a list of documents for “Document 2”. The user's identity and authority can be determined according to preset settings or user-defined, which is not limited in this manual.

At the same time, the sorting order of the documents in the above document list may be determined according to the last modification time of the document, the last access time of the user or user-defined priority rules, which is not limited in this specification.

After the document list is obtained, documents matching keywords in the document list may be filtered according to the received document search request for the document list. A document search request can contain one or more keywords. In this way, the problem that a specific document cannot be accurately located due to the excessive number of documents in the document list is solved, and the efficiency for users to query any document in the document list is improved.

Those skilled in the art can imagine that, in addition to the local search method for the obtained document list, the above document search request can also be used for other conference documents that are not in the obtained document list through keywords, URL addresses, etc. Search method. The above document search request may use different search methods according to specific usage scenarios to implement document search, which is not limited in this specification.

Next, go to step S102. In step S102, any document is acquired as a target document in response to a selection instruction for any document in the document list.

The select command is used to select the specified document in the document list. Similar to the review command above, the selection command can realize the selection operation of any document through technologies such as clicking controls, voice recognition, and eyeball capture. This is not limited in this specification. At the same time, the target document is usually stored in a specific storage space and can only be obtained through a corresponding legal request.

In some embodiments, any document is assigned a docKey (document identifier) as the unique identifier of any document, and the OSS (Object Storage Service, Object Storage Service, Object Storage Service) address. Since the OSS certificate contains the OSS address, access permission and credentials, the OSS address of any document can be obtained according to the OSS certificate corresponding to the docKey, and the actual document of any document can be obtained from the OSS address as the target document.

Then go to step S103. In step S103, the specified content in the target document is extracted, and the specified content is displayed in the current document.

The specified content is the document content of the specified type in the target document, for example: a to-do item with a checkbox (selection box), a line of @someone, a line of a certain keyword, a line with a certain text attribute (such as : Heading 1, Heading 2, Heading 3, citations, etc.), hyperlinks, uploaded files, video, audio, etc. As long as the text, style attributes, and types of the target document have certain common characteristics, they can be used as the extracted document content, which is not limited in this specification. Wherein, the to-do items can be judged by means of checkbox, text strikethrough, etc., which are not limited in this manual. Common features can be identified, divided by type below.

In some embodiments, each piece of document content and the type of each piece of document content in the target document can be obtained by parsing the target document, and document content whose type conforms to a preset type is extracted as specified content. For example: there is a target document that contains 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, then the obtained specified content includes the above two items with checkboxes There is no other content outside of the to-do list for . The preset type can be adjusted according to the actual application scenario, which is not limited in this manual.

When operations such as modifying the document content of the target document are performed in the current document, the corresponding synchronization operation can also be performed on the document content in the target document.

In some embodiments, an operation instruction for any document content in the current document is received, and if any document content is specified content, the operation instruction is respectively executed for the current document and the target document. In the case that the content of any document is not the specified content, the operation instruction is only executed on the current document. The operation instruction may be used to represent operations such as modifying the text of the specified content, to-do status, etc., which is not limited in this specification. This enables two-way synchronization of the specified content shared by the current document and the target document, thereby ensuring real-time content between the two. This avoids the situation that after the above-mentioned current document modifies the specified content in the above-mentioned target document, users who are still using the target document cannot know the modified content in time.

The specified content can be regarded as a task and handed over to the designated person in charge for processing. 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 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, so as to urge the person in charge to complete the processing as soon as possible.

In some embodiments, the current document provides an individual reminder option for any document content and a batch reminder option for multiple document contents. When the individual reminder option is triggered, send reminder information to the processing personnel corresponding to any document content. When the batch reminder option is triggered, reminder information is sent to the processing personnel corresponding to the contents of multiple documents.

The above-mentioned tasks can be divided into high, medium, and low reminder levels according to their urgency, so as to assist the user in judging which task has a higher processing priority.

The above-mentioned persons in charge can be increased, decreased or modified according to the actual situation. For example, the original person in charge A who handles a task cannot handle it for some reason, and can assign the task to another person in charge B to handle it, which is not limited in this manual.

It can be seen from the above embodiments that the document review method 100 in this specification ensures that the user does not need to manually review any content in the past documents, and can directly browse the existing document by selecting the target document to be reviewed in the operation interface of the current document. The specified content that is automatically extracted greatly reduces the user's operating costs and improves the user experience in the document review process. At the same time, the operation instructions on the specified content in the current document can be automatically synchronized to the target document, which saves redundant operations while ensuring data consistency. In addition, this manual also proposes a reminder function for document content, which effectively improves the efficiency of document processing.

The technical solutions in this specification can be applied to a C/S (Client-Server, client-server) architecture. Fig. 2 is an interactive schematic diagram of a document review shown in an exemplary embodiment of this specification. As shown in FIG. 2 , the client and the server (that is, the above-mentioned C/S architecture) may interact through various types of wired or wireless connections, which is not limited in this specification. The interaction process between the client and the server may include steps S201 to S213.

In step S201, a review instruction triggered based on the current document is received.

In some embodiments, it is assumed that a client receives a review instruction initiated by a user to review a document in a display interface of a current document. The display interface of the above-mentioned current document is shown in Figure 3, which displays the document name 310 named "Product Operation Biweekly Meeting" in the current document, the user who created the current document, the creation time, and the name of the current document. The document basic information 320 of the corresponding meeting place, the quick document review control 331 and the common document review control 332 . Among them, the quick document review control 331 is similar to the normal document review control 332, the difference is that the review instruction triggered by the quick document review control 331 is directed to the meeting document whose creation time is closest to the current document, while the normal document review control 332 triggers the review command when the user The documents to be reviewed can be further selected.

Next, go to step S202. In step S202, a document list acquisition request including document attributes of the current document is sent.

In some embodiments, after the user clicks the common document review control 332, the client may send a document list acquisition request to the server. Assuming that the meeting "Product Operation Biweekly Meeting" corresponding to the current document is planned to be carried out from May 5 to the end of the year, and it is held every two weeks, and a document is created each time, then the document attribute of the current document can be determined as cycle sex meeting documents. The client can send the document attribute to the server together with the above request for obtaining the document list.

Then go to step S203. In step S203, the corresponding document list is acquired according to the document list request.

In some embodiments, when the server receives the above-mentioned document list request, it determines that the above-mentioned current document is a periodic meeting document according to the document attributes, and searches for other meeting documents within two weeks before the current moment to form a history List of conference documents.

Then go to step S204. In step S204, the document list is returned.

In some embodiments, the server returns the above-mentioned historical meeting document list to the client.

Then go to step S205. In step S205, a document list is rendered based on the current document.

In some embodiments, 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. The document search box 410 of the document, the document list 420 , the document name 421 of any document in the document list, and the document information including the creation time 422 and the number of to-do items of the any document. Wherein, since the user does not input any information in the document search box 410, and the above-mentioned current document belongs to a periodic meeting document, the document list 420 may default to display other meeting documents within the periodic time of the meeting corresponding to the current document, that is, display Existing meeting documents from May 5 to the current moment.

Then go to step S206. In step S206, a selection instruction for any document in the document list is received.

In some embodiments, the "Product Operation Biweekly Meeting" document created on May 19 in the above document list 420 is selected by clicking.

Then go to step S207. In step S207, a document acquisition request including any document docKey is sent.

In some embodiments, the client obtains the docKey of the "Product Operation Biweekly Meeting" document created on May 19, and the client may include the docKey in the above document acquisition request and send it to the server.

Then go to step S208. In step S208, the OSS certificate of the corresponding target document is acquired according to the document acquisition request.

In some embodiments, when the server receives the above document acquisition request, it can query the corresponding OSS certificate containing the document OSS address according to the docKey contained in the document acquisition request, and return it in the form of an OSS certificate containing the document OSS address To the client, so that the client can initiate a document acquisition request to the server again based on the above OSS certificate.

Then go to step S209. In step S209, the OSS certificate is returned.

In some embodiments, the server returns the OSS certificate to the client.

Then go to step S210. In step S210, the corresponding target document is obtained according to the OSS certificate.

In some embodiments, the client accesses a specific OSS server according to the received OSS certificate to obtain the corresponding target document.

Then go to step S211. In step S211, parse and extract the to-do items in the target document, and display the to-do items in the current document.

In some embodiments, after the client obtains the target document, it parses the target document to obtain 3 document contents of the type of to-do items with checkboxes, and the client displays the to-do items in the above-mentioned current document. The display interface of the above-mentioned to-do items is shown in Figure 5. Based on Figure 3, this interface shows a one-click reminder control 510 for reminders of all to-do items, the text 520 created in the current document, and the meeting of the target document. The review block 530, wherein the meeting review block 530 of the above-mentioned target document may include a local one-click reminder control 531 for pressing any to-do items in any target document, a document name 532 representing the target document, and a A to-do item 533 indicating whether the preset task is completed.

Then go to step S212. In step S212, modify the to-do status of the to-do items.

In some embodiments, when the user clicks any to-do item item 533 in the meeting review section 530 of the above-mentioned target document, the state of the checkbox carried in the to-do item item can be changed. When the checkbox is in an unselected state, Indicates that the todo has not been completed. When the checkbox is selected, it means that the to-do item has been completed. At the same time, change the to-do status of the corresponding to-do item in the target document.

Then go to step S213. In step S213, a reminder instruction for the person in charge corresponding to the to-do item is received.

In some embodiments, in order to deal with unfinished to-do items in time, the user may send a reminder instruction to the person in charge corresponding to the to-do item, so as to remind the person in charge to deal with it in time. The display interface of the above reminder to-do items is shown in Figure 6. On the basis of Figure 5, this interface shows the to-do item operation control group 610, the to-do item detail section 620, A to-do item creation control 621 , a to-do item priority selection control 622 and an individual reminder control 623 . The above-mentioned to-do item operation control group 610 includes the to-do item responsible person setting control, the to-do item processing time setting control and more information display controls, wherein, by clicking the above-mentioned to-do item responsible person setting control, the user can increase, decrease or modify The person in charge of the to-do item corresponds to the information. By clicking the to-do item processing time setting control, the user can set the expected completion time of the to-do item. By clicking the above-mentioned more information display control, the user can view the details of the previously undisplayed to-do item. Plate 620. The to-do item detail section 620 is used to display detailed content not displayed in the to-do item operation control group 610, and the detailed content may include the above-mentioned to-do item creation control 621, the above-mentioned to-do item priority selection control 622, and the above-mentioned individual reminder control 623 . Wherein, a new to-do item can be created in the corresponding meeting review section 530 by clicking the above-mentioned to-do item creation control 621 . The processing priority of the to-do item item can be set by selecting sub-controls such as "high", "medium", "low" and "none" in the above-mentioned to-do item priority selection control 622 . When the user does not need to remind all the to-do items, the individual reminder control 623 in the selected to-do item item can be used to individually notify the person in charge of the to-do item to handle it in time.

Fig. 7 is a schematic structural diagram of an electronic device in an exemplary embodiment. Please refer to FIG. 7 , at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and of course may include other required hardware. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a document review device on a logical level. Of course, in addition to the software implementation, this specification does not exclude other implementations, such as logic devices or the combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic device.

Corresponding to the foregoing embodiment of the conference joining method, this specification also provides an embodiment of a document review device.

Please refer to FIG. 8 , which is a schematic structural diagram of a document review device 800 shown in an exemplary embodiment. As shown in FIG. 8, in one embodiment, the document review device 800 may include: a document list display unit 801, configured to obtain a document list in response to a review instruction triggered based on the current document, and display the document in the current document list; the target document acquisition unit 802, used to obtain any document as the target document in response to a selection instruction for any document in the document list; and the document content display unit 803, used to extract the specified content in the target document, and Display the specified content in the current document.

In some embodiments, the document review device 800 further includes: a document attribute obtaining unit 804, configured to determine the document attribute of the current document; and a document list obtaining unit 805, configured to obtain the document list based on the document attribute.

In some embodiments, the document list display unit 801 is specifically configured to: if the document attribute is a periodic meeting document, obtain a list of historical meeting documents in the period; if the document attribute is a non-periodic meeting document, Acquiring a list of historical conference documents; and obtaining a document access list within a predetermined time period when the document attribute is a non-conference document.

In some embodiments, after obtaining the document list, the document review device 800 further includes: a document search unit 806, configured to receive a document search request for the document list, where the document search request contains one or more keywords; and Filter documents matching keywords in the document list.

In some embodiments, the document review device 800 further includes: a specified content extraction unit 807, configured to parse the target document to obtain each piece of document content and the type of each piece of document content in the target document; and the extraction type is a preset type The content of the document as the specified content.

In some embodiments, the document review device 800 further includes: a document content synchronization unit 808, configured to receive an operation instruction for any document content in the current document; Execute the operation instructions in the and target documents respectively.

In some embodiments, the document list display unit 801 is specifically configured to: specify that the content includes: to-do items.

In some embodiments, the device further includes: a document content reminder unit 809, configured to include a separate reminder option for any document content and a batch reminder option for multiple document contents in the current document; when the individual reminder option is triggered , send reminder information to the processing personnel corresponding to any document content; and send reminder information to processing personnel corresponding to multiple document contents when the batch reminder option is triggered.

For the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details, and will not be repeated here.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place , or can also be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. It can be understood and implemented by those skilled in the art without creative effort.

Embodiments of the subject matter and functional operations described in this specification can be implemented in digital electronic circuitry, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or in A combination of one or more of . Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more of computer program instructions encoded on a tangible, non-transitory program carrier for execution by or to control the operation of data processing apparatus. Multiple modules. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode and transmit information to a suitable receiver device for transmission by the data The processing means executes. A computer storage medium may 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.

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 corresponding functions by operating on input data and generating output. The processing and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

Computers suitable for the execution of a computer program include, for example, general and/or special purpose microprocessors, or any other type 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 components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include, or be operatively coupled to, one or more mass storage devices for storing data, such as magnetic or magneto-optical disks, or optical disks, to receive data therefrom or to It transmits data, or both. However, a computer is not required to have such a device. In addition, a computer may be embedded in another device such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a device such as a Universal Serial Bus (USB) ) portable storage devices like flash drives, to name a few.

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

Although this specification contains many specific implementation details, these should not be construed as limiting the scope of protection claimed by the present disclosure, but mainly used to describe the characteristics of specific embodiments of specific technical concepts. Certain features that are described in this specification in multiple embodiments can also be implemented in combination in a single embodiment. On the other hand, various features that are described in a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features as above may function in certain combinations and even be initially so claimed, one or more features from a claimed combination may in some cases be removed from that combination and the claimed A composition can point to a subcomposition or a variant of a subcomposition.

Similarly, while operations are depicted in the figures in a particular order, this should not be construed as requiring that those operations be performed in the particular order shown, or sequentially, or that all illustrated operations be performed, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can often be integrated together in a single software product in, or packaged into multiple software products.

Thus, certain embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the 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 desirable results. In some implementations, multitasking and parallel processing may be advantageous.

The above are only preferred embodiments of this specification, and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in the protection of this specification. within range.

Claims

A method of document review, the method comprising:

In response to a review instruction triggered based on the current document, obtain a document list, and display the document list in the current document;

acquiring any document as a target document in response to a selection instruction for any document in the document list; and

Extract specified content in the target document, and display the specified content in the current document.
The method according to claim 1, said obtaining the list of documents, comprising:

determining document properties of said current document; and

The document list is acquired based on the document attributes.
The method according to claim 2, said obtaining said document list based on document attributes, comprising:

In the case that the document attribute is a periodic meeting document, obtain a list of historical meeting documents in the period;

If the document attribute is an aperiodic meeting document, obtain a list of historical meeting documents; and

If the document attribute is a non-meeting document, a document access list within a predetermined time period is acquired.
The method according to claim 1, after said acquiring the document list, further comprising:

receiving a document search request for the document list, the document search request including one or more keywords; and

Filter documents matching the keyword in the document list.
The method according to claim 1, said extracting specified content in said target document, comprising:

Parsing the target document to obtain each piece of document content and the type of each piece of document content in the target document; and

Extracting document content whose type is a preset type as the specified content.
The method according to claim 5, further comprising:

receiving an operation instruction for any document content in the current document; and

In the case that the content of any document is the specified content, the operation instruction is respectively executed in the current document and the target document.
The method according to claim 1, the specified content includes: to-do items.
The method according to claim 1, further comprising:

The current document provides an individual reminder option for any document content and a batch reminder option for multiple document contents;

When the individual reminder option is triggered, send reminder information to the processing personnel corresponding to any document content; and

When the batch reminder option is triggered, reminder information is sent to the processing personnel corresponding to the contents of the plurality of documents.
A document review device comprising:

A document list display unit, configured to acquire a document list in response to a review instruction triggered based on the current document, and display the document list in the current document;

a target document acquiring unit, configured to acquire any document in the document list as a target document in response to a selection instruction for any document in the document list; and

The document content display unit is configured to extract specified content in the target document and display the specified content in the current document.
A computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the method according to any one of claims 1-8 are implemented.
An electronic device, comprising a memory, a processor, and a computer program stored in the memory and operable on the processor, when the processor executes the program, the steps of the method according to any one of claims 1-8 are implemented.