JP5194581B2 - Document processing apparatus and document processing program - Google Patents

Description

  The present invention relates to a document processing apparatus and a document processing program.

  In a conventional technique, there is a support tool for reviewing and checking by sharing an electronic document (hereinafter sometimes simply referred to as a document) with a plurality of users. Examples of products that can use such a tool include DocuWorks (trademark) of Fuji Xerox Co., Ltd. and Adobe Acrobat (trademark) of Adobe Systems Inc., USA. In these tools, the document creator gives the review document to the reviewer, and the reviewer pastes additional information (hereinafter, also referred to as annotation) into the document, fills in the points and instructions, and then creates the document creator. Return to.

  The review support can be realized by the configuration of the server client, and a plurality of users can review at the same time and share the document and annotation as a result.

  As a conventional technique for managing annotations, a method for giving attributes such as color to attached annotations, a method for assisting understanding by structurally displaying many attached annotations (Patent Document 1), a system There are known types that prepare types for annotation, post-processing is set for each annotation, and the user selects (Patent Document 2).

  By the way, in tasks such as manual check, a plurality of users often paste a large number of the same indications and instructions as annotations in a document. At this time, when there are multiple review documents, it is troublesome to repeatedly write a comment with the same gist (in reality, someone else may be diverted). In the case of collaborative work, there is a case where the expression is shaken by the user, and a result that is difficult to understand for the review requester may be returned. Also, when listing the contents of annotation, it is difficult to understand because a lot of similar comments are displayed. Furthermore, there are variations in review items (check items) depending on the user.

  In short, the reusability of annotations among multiple users is not fully considered. Even if they are reused, it is difficult to understand if there are too many annotations if they are simply arranged.

Note that the above-described prior art and its problems are described for the purpose of explaining a part of the background of the present invention. It should be noted that the present invention is not limited to the above-described prior art and problems.
JP 2005-283622 A JP-A-5-225194

  SUMMARY OF THE INVENTION An object of the present invention is to provide a document processing apparatus and a document processing program that make it possible to reuse additional information added to an electronic document.

  The invention according to claim 1 is a document storage means for storing an electronic document, an adding means for adding additional information to the electronic document in relation to position information in the electronic document based on a user operation input, and the addition Additional information storage means for storing information, generation means for generating reuse information from the additional information based on a predetermined rule, reuse information storage means for storing the reuse information, and display of the reuse information Display means to be displayed on the apparatus, wherein the adding means adds new additional information to the electronic document based on a user operation input for the displayed reuse information.

  According to a second aspect of the present invention, in the first aspect of the present invention, the generation means is based on the frequency at which the same or similar additional information added to the electronic documents included in the predetermined electronic document group is added. And generating reuse information.

  According to a third aspect of the present invention, in the second aspect of the present invention, the predetermined electronic document group is determined by an attribute assigned to the electronic document.

  According to a fourth aspect of the present invention, in the second aspect of the present invention, the predetermined electronic document group is determined by the similarity of the electronic document itself.

  The invention according to claim 5 is the invention according to claim 2, wherein the predetermined electronic document group is composed of electronic documents managed by a predetermined external device.

  The invention according to claim 6 is the invention according to any one of claims 1 to 5, wherein the reuse information storage means associates additional information generated from the same reuse information with the reuse information. It further has means for storing and displaying the additional information generated from the same reuse information together on the display device.

  According to a seventh aspect of the present invention, there is provided an adding means for adding additional information related to positional information in the electronic document to the electronic document stored in the storage device based on a user operation input, and the additional information. Additional information storage means for storing the information in the storage device, generation means for generating reuse information from the additional information based on a predetermined rule, reuse information storage means for storing the reuse information in the storage device, and The reusable information is made to function as a display unit for displaying on the display device, and the adding unit adds new additional information to the electronic document based on a user operation input for the displayed reusable information. To do.

  According to the present invention, additional information added to an electronic document can be reused.

  First, a principle configuration example of the present invention will be described. However, the present invention is not limited to this configuration example.

  The principle configuration example of the present invention provides a function of reusing an annotation once attached as a template after managing the document and the annotation on the server. It also provides a function for managing templates in document units, document group units, and task units. In addition, it provides a function to present templates and annotations together for each work item to the user.

  In this basic configuration example, annotations can be reused among a plurality of users. Furthermore, it is not necessary for the system administrator to prepare information for reuse. Templates can be used properly according to the attributes of the target document, the type of work place (hereinafter sometimes simply referred to as a task), and the like. In other words, a template group is accumulated as check items / know-how for each purpose of work. In addition, a list of annotations can be presented for each template in an easy-to-understand manner.

  In a specific configuration example of the present invention, the document processing system has a client device and a server computer, and the client device has a function of attaching an annotation to a document acquired from the server computer, and the attached annotation is attached to the server computer. save. The server computer accumulates and manages documents and attached annotations. This document processing system includes a template generation function that generates templates from highly reusable annotations attached to documents, a function that retains created templates, and an annotation creation function that creates annotations from templates. And have.

  In this configuration, annotations can be reused.

  Furthermore, the document processing system has a function of storing annotations that are stored and managed in association with generated templates. This makes it possible to present related annotations to the user in a batch using the template.

  The server computer has a means for transmitting a document and a means for transmitting a template, and the client apparatus has a means for receiving a document and a means for receiving a template.

  The template generation function is generated based on the frequency of the same annotation in the document. Basically, the one that is used a lot is selected. The template generation function may be generated based on the frequency of similar annotations in the document.

  Templates are grouped in units for each document. The server computer can group and hold a plurality of documents, and a template is held in units of groups. Further, the server computer provides a work place for a plurality of users, and each work place can hold a plurality of documents according to work. In this case, the template can be held for each workplace.

  Hereinafter, a group of templates may be referred to as a template group. The document-based grouping can be performed based on document attributes such as a user, a user group, and a category, or can be performed based on the content of the document. The contents of the document can be determined based on keywords, word vectors, and the like. The documents in the workplace can be distinguished by owner attributes, management databases, etc., and can be handled as a kind of grouping.

  When annotating another document, a template group can be applied by selecting a document / group / workplace. Documents, groups, and workplaces are held together with attributes. When attributes are assigned to documents, groups, and workplaces, they have the same attributes. Therefore, for example, a template group is automatically selected based on attributes. Alternatively, the system may search for similar documents, groups, and workplaces, and a template group associated with a similar document, group, or workplace with a high degree of similarity may be automatically selected.

  Templates are shared among users who share the same document / group / workplace.

  Further, in this configuration example, annotations can be processed in association with work items (action items).

  The annotation is associated with the user's work item. Annotations generated from the same template are associated with one work item. When a work item is assigned to an annotation created from a template, the attributes of the work item are stored together with the template. Annotations generated from the same template can be assigned automatically or collectively in accordance with user instructions.

  In this configuration, an annotation list display function is provided, which is classified and displayed for each template. In addition, a work item list display function is provided, and the work item list display function is displayed together with a list of attribute information (for example, document name page) of the corresponding annotation.

  In addition, notifications regarding annotations generated from the same template may be sent as a single email collectively.

  Alternatively, after an annotation is attached to a document by a client device, the document may be stored on a server computer and replaced by specifying a template for the annotation on a Web application. The user may directly specify the annotation himself and make it a template.

  1 and 2 schematically show a processing example of this configuration example. In the processing example of FIG. 1, a manual creator creates a document (annual) (processing 1) and requests a review from a reviewer (creates a task. Processing 2). The reviewer retrieves the document from the server computer, reviews it, and attaches an annotation as appropriate (writes a comment. Process 3). After the review, the document and template are stored in the server computer (process 4). The document processing system generates a template from the annotation and stores it so that it can be reused (process 5). Reviewers can create annotations using a template if it already exists. A template group that can be applied is automatically extracted and displayed based on the document, document group, and workplace, and can be reused. The template may be generated from the document being processed, or may be generated from another document.

  In the processing example of FIG. 2, templates are used in the manual check task for product X and the manual check task for product Y. In this example, as shown in FIG. 2A, the users A, B, and C review the X manual created by the manual creator, and the manual creator corrects the X manual according to this review. FIG. 2B shows the Y manual creation / review / correction tasks. Since these tasks are the same, users D, E, and F can easily create annotations using templates when reviewing the Y manual. I am doing so.

  As described above, in this configuration example, when the annotation is made into a template, when a plurality of users review the same document, the template can be shared and the check items can be shared. Further, by applying the manual check template for the product X to the task of the product Y, the past check items can be used for similar tasks. Furthermore, when a work item is assigned from the annotation attached in the review, the association with the work item can be diverted for similar work.

  Examples of the present invention will be described below.

  FIG. 3 shows an embodiment of the present invention. In this figure, the document processing system 100 includes a document client 10 and a document / annotation sharing server 20. The document client 10 is realized by executing a client application that provides a user with a document editing function or the like on a client device such as a personal computer, DocumentWorks (trademark), Adobe Acrobat (trademark), or the like. The document client 10 uses well-known hardware resources of the client device, such as a CPU, main memory, bus, BIOS, auxiliary storage device, input / output device and the like. The document / annotation sharing server 20 is a server that provides a document processing function and an annotation management function for document review by sharing a document and annotation among a plurality of users. The server 20 also has known hardware resources such as a CPU, a main memory, a bus, a BIOS, an auxiliary storage device, and an input / output device.

  In FIG. 3 and FIG. 12 described later, the document processing system 100 or 100A is represented by using functional units. Each functional unit is typically configured by the cooperation of computer hardware resources and computer program software resources.

  The document client 10 includes a user interface unit (display unit / operation unit) 11, a document transmission / reception unit 12 and the like in terms of functional configuration. The user interface unit 11 is a part that manages the user interface. The document transmission / reception unit 12 is a part that transmits and receives documents between the server and the client.

  The document / annotation sharing server 20 includes a document transmission / reception unit 21, a document database 22, an annotation database 23, a document management unit 24, an annotation integration unit 25, an annotation management unit 26, an annotation separation unit 27, and the like.

  The document transmission / reception unit 21 corresponds to the document transmission / reception unit 12 of the document client 10 and is a part that transmits / receives a document between the server and the client.

  The document database 22 holds documents, and is composed of, for example, a table shown in FIG. The document table (FIG. 4A) holds a document ID, a document name, contents, and the like, and the contents of the document are the files themselves. The document address may be stored. Other attributes may be stored, which are not shown.

  The annotation database 23 holds annotations (examples of additional information) and templates (reuse information), and includes, for example, an annotation table shown in FIG. 4B and a reuse information table shown in FIG. Is done. The annotation table includes the annotation ID, the document ID of the document to which the annotation is attached, the position information in the document of the annotation, the content of the annotation, and the reuse information ID (if the annotation has been generated from the reuse information, it is reused. Information ID is given). The position on the document is expressed by, for example, “page, horizontal (pixel) −vertical (pixel)”. The reuse information table includes a reuse information ID, its contents, and the like. When an annotation is targeted for reuse by the system, a record is added to the reuse information table. Note that the frequency can be calculated dynamically and the reuse information can be acquired by counting the annotation table. In the database, in terms of DB, it is represented by a view rather than a table. Alternatively, instead of preparing a reuse information table, there is a method of identifying reuse information by adding a field to the annotation table and setting a reuse flag.

  The annotation integration unit 25 integrates the document and the annotation. In the user interface unit 11, annotations are integrated and displayed on a document. The annotation separation unit 27 separates the annotation from the document. The annotation changed by the user interface unit 11 is recorded separately from the document. The document management unit 24 manages documents. The annotation management unit 26 manages annotations. In order to enable document review by a plurality of users, a process of resolving the conflict of update operations between users with respect to the annotation is also performed.

  In this embodiment, the server 20 manages documents and annotations in association with each other (see FIG. 4). The document client 10 provides functions for displaying and operating documents and annotations. When a user reviews a document, the client 10 requests a document from the server 20. The server 20 combines the base document and the annotation and returns them to the client 10.

  The user can paste an annotation on the document on the client 10, and enters the review content as an annotation comment. The document is saved by uploading the document to the server 20. The document uploaded to the server 20 is stored after separating the base document and the annotation.

  The annotation management unit 26 also supports collaborative work by a plurality of users, and reflects only annotations added or updated by the user in the annotation database 23.

  Annotations attached by reviews can also be managed as work items. For example, when an annotation is an item to be pointed out for replacing a screen in a manual, the annotation is used as a work item and is presented to the user or used for progress management.

  Various attributes can be assigned to documents, annotations, reuse information, etc. for management.

  Next, template generation will be described. The document review requester designates a plurality of reviewer users, creates a task, and registers the document. Each user who becomes a reviewer individually writes comments in annotations and attaches them to the document. In relation to this, a template is appropriately generated as shown in FIG. 5, for example, and the procedure is as follows.

[Step S10]: The user obtains a document from the task, attaches the pointed item as an annotation to the document, and saves it on the server 20. This is the start of processing.
[Step S11]: When the annotation is stored in the annotation database 23 of the server 20, the server 20 calculates the appearance frequency of the annotation in all the review documents in the task for each text content. In this case, the document is managed in association with the task, and a task ID may be assigned to the annotation in the annotation table (FIG. 4B).
[Step S12]: When the appearance frequency exceeds a predetermined threshold, a template is created from the annotation.
[Step S13]: The template is stored in the template table (FIG. 4C). Templates are managed on a task basis.

  Alternatively, instead of a task unit, a document unit or a document unit within a group in which documents are grouped (for example, managed by a directory configuration) may be used. Further, instead of using a threshold value, a method may be used in which a predetermined number of templates are selected in descending order of frequency.

  In this example, the condition for calculating the frequency is that the contents of the text in the annotation match. However, the frequency is calculated for each similar annotation after calculating the similarity even if they do not match completely. Various methods can be adopted. In this case, matching of a predetermined ratio of characters in the text or matching of a predetermined number or ratio of words may be considered.

  Next, template selection will be described. In this example, a template group (including the case of one template) is managed on a task basis. If templates are already registered, they can be shared among users. Even if the template group is not yet registered, the template group can be found from the attributes and similarities of the document management unit (single document, document group, task).

  When managing a template group in units of tasks, if a template group has already been generated for a task, the template group is selected. Even if a template does not exist in the task being worked on, by assigning an attribute to the task, the user has access rights and can refer to the template group from other tasks having the same attribute.

  Alternatively, the user may select a specific task and select a template group. Alternatively, a specific template group may be directly selected.

  When managing a template group in document group units, the task may be replaced with a group in the above example. When the group has a directory structure, a method of applying a template group of a higher hierarchy to a certain document can be adopted.

  When managing a template group in document units, an attribute is assigned to the document, and the template group is referenced from a document that is accessible and has the same attribute. The similarity of the documents may be calculated, and a template group may be selected from documents similar to the document to be reviewed.

  Further, when a plurality of templates are selected, a template group may be used in which both can be applied without duplication.

  Furthermore, when an annotation created from a template in the past exists in the document, a template group including the template may be selected.

  FIG. 6 shows an operation example of template selection, and the procedure is as follows. Here, the following points are assumed.

A task is created and has multiple attributes. The following two attributes are provided for convenience, but are not limited to these.
Attribute Work type = Manual review attribute Product = Product X

  In this example, it is assumed that the attribute is selected from the menu for simplicity.

[Step S20]: Starts when a document is registered.
[Step S21]: It is determined whether a template group has already been selected for the task. If selected, use it as is.
[Step S22]: When not selected, an attribute used for template group selection is calculated among the attributes assigned to the target task. For example, the frequency is calculated for each attribute to find an appropriate one. Specifically, the template group T1,..., Ti,..., TN is applied when the task attribute value is the same as that of the target task, p (i). Let q (i) be the number of
Z = √ (Σ (p (i) · q (i)) / (Σp (i) + Σq (i))
And Z is calculated for all attributes of the target task, and the attribute having the smallest value of Z is selected.
[Step S23]: For the selected attribute, the template group Ti having the largest value of p (i) -q (i) is selected.

  FIG. 7 shows a calculation example of steps S22 and S23 described above. In this example, in step S22, Z = 0 for the attribute “work type”, Z = 2 for the attribute “product”, and “type to work” is selected as the attribute. Next, in step S23, p (i) −q (i) is calculated for the short plate groups T1 to T4 to obtain “−3”, “−3”, [−2], and “+2”, respectively, and the maximum value is obtained. A template group T4 is selected.

  Although the range of the template group is all tasks in the system, it may be performed only for a specific task. Moreover, a threshold value is provided for the value of Z or the value of p (i) −q (i), and the process can be executed only in a specific range. Note that the above calculation method is merely an example.

  Next, the use of templates will be described. When the template group is created, the template can be used for the document. The document client 10 acquires a template group applicable to the document from the server 20. When an applicable template group exists, the server 20 returns the template group to the document client 10. An example of this processing is shown in FIG. An example of this processing is as follows.

[Step S30]: The task is started.
[Step S31]: A file is acquired from the server 20.
[Step S32]: If no template is selected for the document, the process ends without doing anything. If it is selected, the process proceeds to step S32.
[Step S32]: A template group is acquired from the server 20 in response to a user operation via the user interface, a usage list is displayed, and an annotation is attached to the document based on the user selection operation. An annotation can be corrected.

  FIG. 9 shows an example of a user interface using a template. To apply a template, right-click on the base document and select the “Add annotation from template” operation. A part of the comments in the template acquired from the server 20 is displayed as a list, and when the user selects, an annotation is generated from the template and attached to the document.

  The display is not limited to a list, and other display methods may be used (such as a tree when there are multiple templates to be applied).

  Alternatively, the annotations once attached may be displayed as a list on the server 20 and individually selected to execute the template application.

  Next, association with work items (action items) will be described. Among the attached annotations, those that generate work are managed as work items. An annotation generated from a template can be assigned to one work item. In addition, when an annotation generated from a template is associated with a work item, when a work item is associated with another annotation generated from the same template, it can be output as a candidate for the associated work item. An example of this processing is shown in FIG.

The process of FIG. 10 is as follows.
[Step S40]: A task, for example, a correction task is started.
[Step S41]: A work item setting screen is displayed.
[Step S42]: It is determined whether an annotation template has been created. If it has not been created, the process ends. If it has been created, the process proceeds to step S43.
[Step S43]: An annotation group created from the same template is searched.
[Step S44]: It is determined whether or not work items (annotations) are applied at a predetermined rate or more. If it has been applied, the process proceeds to step S45. If not applied, the process ends.
[Step S45]: Work items with a predetermined ratio or more are output as candidates.

  Annotations generated from templates are easy to understand because they can be displayed hierarchically. FIG. 11 is an example of display.

  Next, a specific example of the above embodiment will be shown. This specific example shows in detail a configuration for realizing a work place (task). FIG. 12 shows a document processing system 100A of this specific example. In FIG. 12, portions corresponding to those in FIG. In FIG. 12, the document processing system 100A of this specific example provides a work place (task) for joint work by a plurality of users. A task is defined by, for example, a work requester assigning (multiple) parties involved in a joint work. A collaborative review begins by defining a task and associating a document with the task. The task is typically constituted by an electronic bulletin board system, but is not limited to this.

  In FIG. 12, the workplace database 28 stores various types of information for forming tasks. The workplace management unit 29 is a part that manages the workplace, and also exchanges data with the annotation management unit 26 in order to link tasks and annotations. The work area operation unit 30 provides a processing function for displaying work items, a task registration / state change function, and the like.

  In this embodiment, documents, annotations, and templates can be managed in units of tasks. Of course, annotations attached by reviews can also be managed as work items. For example, when an annotation is an item to be pointed out for replacing a screen in a manual, the annotation is used as a work item and is presented to the user or used for progress management.

  As described above, in the document processing system according to this specific example, various attributes can be assigned to a document, a task, an annotation, and the like.

  In addition, this invention is determined based on description of a claim, and is not limited to the specific structure of the Example, a subject, and an effect. The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present invention.

It is a schematic diagram explaining the example of a fundamental process of this invention. It is another schematic diagram explaining the example of a principle process of this invention. It is a block diagram which shows the Example of this invention as a whole. It is a figure explaining the structural example of the database of the above-mentioned Example. It is a flowchart explaining the production | generation process example of the template (reuse information) of the said Example. It is a flowchart explaining the selection process example of the template (reuse information) of the above-mentioned Example. It is a figure explaining the example of a process of FIG. It is a flowchart explaining the utilization processing example of the template (reuse information) of the said Example. It is a figure explaining the example of a process of FIG. It is a flowchart explaining the process example which produces | generates the list | wrist of a work item from the template (reuse information) of the said Example. It is a figure explaining the example of a process of FIG. It is a figure explaining the specific example of the above-mentioned Example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Document client 11 User interface part 12, 21 Document transmission / reception part 20 Document / annotation sharing server 22 Document database 23 Annotation database 24 Document management part 25 Annotation integration part 26 Annotation management part 27 Annotation separation part 28 Work place database 29 Work place management part 30 Work place Operation unit 100 Document processing system

Claims (6)

Document storage means for storing electronic documents;
An adding means for adding additional information to the electronic document in relation to position information in the electronic document based on a user operation input;
Additional information storage means for storing the additional information;
Generating means for generating reusable information that is a reusable additional information candidate from the additional information;
Reuse information storage means for storing the reuse information;
Display means for displaying the reuse information on a display device;
The additional means uses the reusable additional information candidate selected based on the user operation input on the displayed reuse information as electronic additional new information related to the new position information in the electronic document. Add it to the document ,
The additional information storage means stores additional information generated from the same reuse information in association with the reuse information,
Furthermore, the document processing apparatus characterized by further have a means for displaying on the display device together additional information generated from the same reuse information. The document processing apparatus according to claim 1, wherein the generation unit generates the reuse information based on a frequency at which the same or similar additional information added to an electronic document included in a predetermined electronic document group is added. The document processing apparatus according to claim 2, wherein the predetermined electronic document group is determined by an attribute assigned to the electronic document. The document processing apparatus according to claim 2, wherein the predetermined electronic document group is determined based on a similarity of the electronic document itself. The electronic document processing apparatus according to claim 2, wherein the predetermined electronic document group includes electronic documents managed by a predetermined external apparatus. Computer
An adding means for adding additional information related to position information in the electronic document to the electronic document stored in the storage device based on a user operation input;
Additional information storage means for storing the additional information in a storage device;
Generating means for generating reusable information that is a reusable additional information candidate from the additional information;
Reuse information storage means for storing the reuse information in a storage device;
Function as display means for displaying the reuse information on a display device;
Further, the reusable additional information candidate selected based on the user operation input for the displayed reusable information is added to the reusable additional information candidate by the additional means in relation to the new position information in the electronic document. As an electronic document ,
The additional information storage means stores additional information generated from the same reuse information in association with the reuse information,
Further, a document processing program characterized in that additional information generated from the same reuse information is collectively displayed on a display device .