JP2006301851A - Progress management support device, progress management support method and progress management support program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To make a schedule consistent with the end limit of an electronic document preparation job. <P>SOLUTION: When the management of the progress of the preparation work of an electronic document attached with annotation for instructing a calibrating work is supported, an acquisition part 41A of a progress management server 40 acquires end limit information showing the end limit of the preparation work of the electronic document, and a schedule setting part 41B derives the execution schedule of the calibrating work instructed by the annotation until the end limit shown by the end limit information, and a secondary storage part 45 stores it, and a display part 53 of a client device 50 displays information showing the execution schedule stored in the secondary storage part 45. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a progress management support device, a progress management support method, and a progress management support program. More specifically, the present invention supports management of the progress of creation of an electronic document attached with a work instruction comment that instructs a proofreading work. The present invention relates to a progress management support device, a progress management support method, and a progress management support program.

  In recent years, a technique for attaching additional information such as character information, image information, audio information, and link information to an arbitrary position of an electronic document without affecting the text of the electronic document has been widely used. Note that the additional information is collectively referred to as an annotation in this specification.

  Examples of systems that can attach this annotation to an electronic document include DocuWorks (registered trademark) of Fuji Xerox Co., Ltd. and Acrobat (registered trademark) of Adobe Corporation in the United States.

  By the way, as a form of use of a system that can attach annotations as described above to an electronic document, an annotation for instructing the proofreading operation of the electronic document is attached to the proofreading part when executing the task of creating the electronic document. Thus, a form in which the proofreading operation is instructed to the proofreader can be considered.

  In this embodiment, managing the progress of individual proofreading operations instructed by the annotation is important for carrying out the work of creating the electronic document without delay.

  For this reason, it is effective to register the execution schedule of the calibration work in advance and advance the calibration work in accordance with the schedule.

  As a conventional technique that can be applied to support such business forms, the purpose is to determine whether a newly registered schedule is feasible from the relationship with a schedule that has already been registered, and to perform reasonable scheduling In a schedule management system for registering and updating individual schedule information, it is determined whether or not a predetermined individual schedule can be executed based on the registered schedule information, and the individual schedule information is updated based on the determination result. There is a technique (hereinafter referred to as “first technique”) (see, for example, Patent Document 1).

In addition, schedule information can be managed centrally by linking the registered schedule and related items, and schedule errors can be prevented by notifying the expiration of related items in the schedule. For this purpose, an input means for inputting information for scheduling, operation information, etc., a schedule information management means for registering / changing / deleting schedule information according to information from the input means, and a schedule for storing the schedule information In a schedule management system comprising information storage means and schedule display means for causing the display means to display schedule information stored in the schedule information storage means, a method having an association with the schedule information stored in the schedule information storage means Memo information storage means for storing information, memo information management means for registering / changing / deleting the contents of the memo information storage means, memo display means for displaying the contents of the memo information storage means on the display means, A technology provided with memo notification means for displaying and notifying the memo content on the display means when the memo notification deadline is reached due to unsupported information of the memo information items stored in the memo information storage means ( (Hereinafter, referred to as “second technique”) (see, for example, Patent Document 2).
Japanese Patent Laid-Open No. 5-13489 Japanese Patent Laid-Open No. 5-266028

  By the way, in performing the task of creating an electronic document as described above, a form in which the proofreading operation is instructed to the proofreader by attaching an annotation indicating the proofreading operation of the electronic document to the proofreading location. In the business mode in which the calibration work schedule and the electronic document creation work end deadline are registered in advance and the calibration work is performed in accordance with the registered schedule, all the calibration work is completed at least by the end deadline. Need to be.

  On the other hand, there may be a case where only a plurality of proofreading work schedules for electronic documents to be created are registered in advance, and the plurality of proofreading works are collectively executed as the electronic document creation work. Since the final deadline of each proofreading work is considered as the deadline for ending the above-mentioned electronic document creation work, the compiled electronic document creation work must be completed at least by the final deadline for the plurality of proofreading work .

  However, the first technique described above mainly targets the schedule management of each individual when holding a meeting, and when the technique is applied to schedule management for electronic document creation work, the schedule of each proofreader individual However, there is a problem in that it is not possible to perform scheduling consistent with the end date of the electronic document creation work.

  In the second technique, it is possible to prevent scheduling mistakes by announcing the expiration of related items in the schedule, but it is not possible to perform scheduling that is consistent with the end date of electronic document creation work. There was a problem that.

  The present invention has been made to solve the above-described problems, and a progress management support apparatus, progress management support method, and progress management capable of performing scheduling consistent with an end date of an electronic document creation task. The purpose is to provide support programs.

  In order to achieve the above object, a progress management support apparatus according to claim 1 is a progress management support apparatus that supports management of a progress status of an electronic document creation work attached with a work instruction comment for instructing a proofreading work. Acquisition means for acquiring end deadline information indicating an end deadline of the creation work of the electronic document, and an execution schedule of the calibration work or the electronic document creation work instructed by the work instruction comment is indicated by the end deadline information. And a schedule setting means for deriving and storing in the storage means so as to end by the end deadline.

  The progress management support apparatus according to claim 1 supports management of a progress status of an electronic document creation work to which a work instruction comment for instructing a calibration work is attached, and an end time limit for the creation of the electronic document Is acquired by the acquisition means. The acquisition by the acquisition means includes acquisition through an input device such as a keyboard and a pointing device, as well as acquisition by reading out the expiration date information from a storage means in which the expiration date is stored in advance, the Internet, an intranet, a LAN (Local Acquisition from an external device via a communication line such as Area Network).

  Here, in the present invention, the schedule setting means derives the execution schedule of the proofreading work or the electronic document creation work instructed by the work instruction comment so as to be completed by the end deadline indicated by the end deadline information. Is stored in the storage means. The storage means includes a RAM (Random Access Memory), an EEPROM (Electrically Erasable and Programmable Read Only Memory), a semiconductor storage element such as a flash EEPROM (Flash EEPROM), a smart media (SmartMedia (registered trademark)), a flexible Examples include a portable recording medium such as a disk, a fixed recording medium such as a hard disk, or an external storage device provided in a server computer connected to a network.

  As described above, according to the progress management support apparatus according to claim 1, the creation of the electronic document is supported in supporting the management of the progress of the creation of the electronic document to which the work instruction comment for instructing the calibration work is attached. End date information indicating the end date of the work is acquired, and the execution schedule of the proofreading work or the electronic document creation work instructed by the work instruction comment is derived to be finished by the end time indicated by the end time information. Therefore, it is possible to perform scheduling that is consistent with the end date of the electronic document creation work.

  The schedule setting means according to the present invention includes a plurality of work instruction comments attached to the electronic document, and a plurality of proofreadings specified by the plurality of work instruction comments. When deriving a work execution schedule, the plurality of calibration works are executed in parallel within a period up to an end deadline indicated by the end deadline information, or the execution schedules are executed in series one by one. It may be derived.

  Further, according to the present invention, when the execution schedule of the calibration work is derived by the schedule setting unit as in the invention according to claim 3, the acquisition unit indicates an instruction to correct the execution schedule derived result. Further, correction instruction information may be acquired, and the schedule setting unit may correct the execution schedule derivation result according to the correction instruction indicated by the correction instruction information acquired by the acquisition unit.

  Further, as in the invention according to claim 4, the present invention may further comprise display means for displaying information indicating the execution schedule stored in the storage means by the schedule setting means. The display by the display means includes visible display, permanent visible display, audible display, and the like.

  According to a fourth aspect of the present invention, as in the fifth aspect of the present invention, the acquisition unit further acquires progress level information indicating a progress level of the calibration work, and the display unit includes the acquisition unit. The progress indicated by the progress information acquired by the means may be further displayed.

  In particular, the invention described in claim 5 further includes correction means for correcting the degree of progress so that the degree of progress becomes lower as the end date approaches the end date indicated by the end date information, as in the invention described in claim 6. You may prepare.

  On the other hand, in order to achieve the above object, the progress management support method according to claim 7 is a progress management support method for supporting the management of the progress status of the creation work of an electronic document attached with a work instruction comment for instructing a proofreading work. Completion time limit information indicating an end time limit of the creation work of the electronic document is acquired, and an execution schedule of the calibration work or the creation work of the electronic document indicated by the work instruction comment is indicated by the end time limit information. It is derived so as to end by the end deadline and stored in the storage means.

  Therefore, according to the progress management support method according to the seventh aspect, it operates in the same manner as the invention according to the first aspect. Scheduling without contradiction can be performed.

  On the other hand, in order to achieve the above object, the progress management support program according to claim 8 is a progress management support program that supports the management of the progress of the creation of an electronic document attached with a work instruction comment for instructing a proofreading work. An acquisition step of acquiring end deadline information indicating an end deadline of the electronic document creation work, and an execution schedule of the calibration work or the electronic document creation work instructed by the work instruction comment is the end deadline information. And a schedule setting step for deriving the program so as to be completed by the end deadline and storing the schedule in the storage means.

  Therefore, according to the progress management support program of the eighth aspect, it is possible to cause the computer to act in the same manner as the first aspect of the invention. Scheduling can be performed consistently with the deadline of the end.

  According to the present invention, in supporting the management of the progress of the creation of an electronic document to which a work instruction comment for instructing a calibration work is attached, end deadline information indicating an end deadline of the creation of the electronic document is acquired. Since the execution schedule of the calibration work instructed by the work instruction comment or the creation work of the electronic document is derived and stored in the storage means so as to be completed by the end deadline indicated by the end deadline information, There is an effect that it is possible to perform scheduling without contradiction with the end date of the document creation work.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Here, a case where the present invention is applied to a document processing system configured as a client / server system will be described.

〔System configuration〕
FIG. 1 is a diagram showing an overall schematic configuration of a document processing system 90 according to the present embodiment.

  As shown in the figure, the document processing system 90 includes electronic data used in the document processing system 90 (including not only document data but also all other electronic data supported by the document processing system 90). And a client system 94 used by users of the document processing system 90 (including reviewers and work performers described later).

  The server system 92 includes a document management server 10 that manages electronic documents (hereinafter also simply referred to as “documents”) and an annotation management server 20 that manages annotations. The document management server 10 is a server that mainly stores and retrieves documents, and the annotation management server 20 is a server that mainly stores and retrieves annotations attached to documents.

  As described above, by providing the document management server 10 that manages the entire document and the annotation management server 20 that manages the annotations attached to the electronic document, additional corrections to a plurality of electronic documents can be independently performed by a plurality of users. Even when it is performed, it is possible to avoid a contradiction in the contents of the final electronic document, correction of correction, and the like.

  For example, even if one user adds a supplementary explanation as an annotation to a certain part of the original electronic document, while another user makes a modification that deletes the same part, the edited part Is registered in the annotation management server 20 in association with the electronic document main body managed by the document management server 10, so that there is no inconsistency in the electronic document main body and content such as additional correction corresponding thereto. Management can be performed.

  As shown in the figure, the document management server 10 includes a control unit 11 that controls the overall operation of the document management server 10, a main storage unit 12 that is used as a work area when various programs are executed, and a display such as a liquid crystal display. , A display unit 13 including a keyboard, an operation unit 14 including a mouse and a pointing device, a document database DB1 to be described later, various programs, secondary parameters for storing various parameter information, and the like. A storage unit 15 and a transmission / reception unit 16 for exchanging various types of information between external devices are provided, and these units are electrically connected via a system bus S1. That is, the document management server 10 according to the present embodiment is configured by a normal personal computer (hereinafter also referred to as “PC”).

  The annotation management server 20 also includes a control unit 21 that controls the overall operation of the annotation management server 20, a main storage unit 22 that is used as a work area when various programs are executed, and a display such as a liquid crystal display. Secondary storage for storing a display unit 23, an operation unit 24 including a keyboard and a mouse, a sticky note annotation database DB2, a pen input annotation database DB3, various programs, various parameter information, etc. And a transmission / reception unit 26 for exchanging various types of information with an external device. These units are electrically connected via a system bus S2. That is, the annotation management server 20 according to the present embodiment is also configured by a normal PC.

  On the other hand, the server system 92 according to the present embodiment has a message sharing server 30 that functions as an electronic bulletin board (Bulletin Board System). The message sharing server 30 is a server that mainly stores and retrieves messages exchanged on the electronic bulletin board.

  As shown in the figure, the message sharing server 30 also includes a control unit 31 that controls the overall operation of the message sharing server 30, a main storage unit 32 that is used as a work area when various programs are executed, and a display such as a liquid crystal display. A display unit 33 configured to include a keyboard and a mouse, a secondary storage unit 35 to store a message database DB4, various programs, various parameter information, and the like, which will be described later, And a transmission / reception unit 36 that exchanges various types of information with an external device, and these units are electrically connected via a system bus S3. That is, the message sharing server 30 according to the present embodiment is also configured by a normal PC.

  By the way, the document processing system 90 according to the present embodiment is assumed to be reviewed by a plurality of predetermined reviewers (reviewers) starting from the annotation attached to the electronic document. This is performed using an electronic bulletin board provided by the message sharing server 30.

  Then, the server system 92 according to the present embodiment manages the progress of the proofreading work performed on the electronic document, which is executed based on the annotation and the review, and the worker who executes the proofreading work (hereinafter, “ It has a progress management server 40 that manages “work performers”).

  As shown in the figure, the progress management server 40 also includes a control unit 41 that controls the overall operation of the progress management server 40, a main storage unit 42 that is used as a work area when various programs are executed, and a display such as a liquid crystal display. A display unit 43 including an operation unit 44 including a keyboard and a mouse, a worker database DB5, a progress management database DB6, a schedule management database DB7, various programs, various parameter information, and the like which will be described later. A secondary storage unit 45 for storing and a transmission / reception unit 46 for exchanging various types of information with an external device are provided, and these units are electrically connected via a system bus S4. . That is, the progress management server 40 according to the present embodiment is also configured by a normal PC.

  The client system 94 includes a plurality of client devices 50 provided for each user of the document processing system 90, each having a pen-type annotation device 57 used when performing pen input (handwriting input). It is configured.

  As shown in the figure, the client device 50 is also configured to include a control unit 51 that controls the operation of the entire client device 50, a main storage unit 52 that is used as a work area when various programs are executed, and a display. Various information is exchanged between the display unit 53, an operation unit 54 including a keyboard and a mouse, a secondary storage unit 55 for storing various programs, various parameter information, and the like. And a transmission / reception unit 56 that controls them, and these units are electrically connected via a system bus S5.

  The client device 50 is configured to display an image on the display unit 53 based on data read from the main storage unit 52 or the secondary storage unit 55 or data acquired from the server system 92 or the like via the transmission / reception unit 56. ing.

  The client device 50 according to the present embodiment is configured as a so-called tablet PC that employs a display unit 53 provided with a touch panel display that is configured by overlapping a touch panel (not shown) on the display surface. Therefore, the annotation device 57 can directly instruct (handwritten input) on the display surface of the display unit 53.

  As described above, when the client device 50 reads a paper document, the client device 50 writes the document using the annotation device 57 in the same way as adding a mark such as an underline or a circle to the document and writing a comment. Input is possible.

  In addition to the handwriting input function using the annotation device 57 as described above, the client device 50 can display a predetermined shape (in this embodiment) at an arbitrary position of the document in a state in which the display unit 53 displays the document. , A rectangular sticky note attached function is provided. Here, an arbitrary comment can be directly described in the tag, or link information indicating a link destination such as a comment or a related article can be associated with the tag. When link information is associated with a tag, the link destination information indicated by the link information is displayed on the tag. In this case, in the document processing system 90 according to the present embodiment, the tag attached to the document by the tag attachment function is used as an annotation.

  As described above, the client device 50 attaches a sticky note to an arbitrary position such as a point to be noted or a point requiring calibration work, in the same manner as sticking a sticky note to a paper document when reading the paper document. State.

  The document processing system 90 includes a network 60 that includes the document management server 10, the annotation management server 20, the message sharing server 30, the progress management server 40, and a plurality of client devices 50 that are provided in each of them. It is configured to be electrically connected by. In the document processing system 90 according to the present embodiment, the Internet is applied as the network 60. However, the present invention is not limited to this, and is not limited to this. Intranet, LAN, VAN (Value Added Network), telephone line network, Echonet, HomePNA, etc. These networks can be applied alone or in combination.

  The document management server 10, annotation management server 20, message sharing server 30, and progress management server 40 according to the present embodiment function as an HTTP (Hypertext Transfer Protocol) server, and each client device 50 functions as an HTTP client. The document management server 10, the annotation management server 20, the message sharing server 30, the progress management server 40, and each client device 50 can access each other via the network 60.

  Information relating to annotations handwritten by the client device 50 using the annotation device 57 (hereinafter also referred to as “handwritten input annotations”) and annotations attached as sticky notes (hereinafter also referred to as “sticky note annotations”). Is temporarily stored in the main storage unit 52, then transmitted to the annotation management server 20 via the network 60 at a predetermined timing, and stored in association with the document body. Then, when the document is read and displayed later on the client device 50, the annotation can be displayed together with the document based on the information regarding the annotation attached to the document in the past.

[Configuration of Display Screen of Client Device 50]
FIG. 2 is a diagram illustrating a schematic configuration of a display screen related to annotation attachment by the display unit 53 of the client device 50 according to the present embodiment.

  As shown in the figure, in the display screen, a button display area 53B that is an area for displaying a plurality of buttons each having a predetermined role on the display area 53A in the display unit 53 of the client device 50; A document display area 53C, which is an area for displaying the document 84 to be attached with the annotation, is provided.

  In the client device 50 according to the present embodiment, a document reading button 70 specified when reading a document managed (stored) in the document management server 10 and a tag annotation are attached to the document as the plurality of buttons. The annotation button 72 specified at the time, the save button 74 specified when saving the tag annotation 86 and the handwritten input annotation 88 displayed in the document display area 53C, and managed (stored) in the annotation management server 20. A search button 76 that is specified when an annotation is searched for and displayed in the document display area 53C is displayed in the button display area 53B.

  Further, as the plurality of buttons, a schedule setting button 78 specified when executing a scheduling function to be described later, and a progress management screen showing the progress status of the calibration work designated by the annotation are displayed on the display unit 53. A progress button 80 specified at the time, and a page turning button 82 including a previous page forward button 82A and a next page forward button 82B for turning the page of the displayed document forward and backward are displayed in the button display area 53B. The

  The client device 50 is equipped with a function (page turning display function) for switching the display in units of pages while turning a page so as to read a book. By using this page turning display function, for example, capturing is performed. It is configured so that desired information can be quickly searched from a large number of information.

  That is, when searching for information in the client device 50, the page turning operation is performed by specifying pointing with the annotation device 57, the keyboard of the operation unit 54, the mouse, or the like with the two buttons of the previous page forward button 82A and the next page forward button 82B. The desired page information can be displayed on the display unit 53 while performing the above.

  Further, the client device 50 can execute the function assigned to the button by designating the buttons other than the page turning button 82 using the annotation device 57, the keyboard of the operation unit 54, the mouse, or the like. .

  As described above, in the client device 50 according to the present embodiment, buttons for executing various functions by being displayed in the display area 53A of the display unit 53 are provided in software. It goes without saying that hardware buttons may be provided on the display unit 53, the operation unit 54, or the like, or predetermined keys on the keyboard of the operation unit 54 may be used as the buttons.

  In the client device 50 according to the present embodiment, as described above, when link information is associated with a tag annotation, the link destination information indicated by the link information is displayed on the tag annotation. The review starting from the information is performed using an electronic bulletin board provided by the message sharing server 30 by a plurality of predetermined reviewers.

  Messages exchanged by each reviewer using the electronic bulletin board are displayed in the display area 53A of the display unit 53 by pointing the corresponding tag annotations with the annotation device 57, the keyboard of the operation unit 54, the mouse, or the like. be able to.

  The review can be performed starting from a sticky note annotation in which a comment is directly described or a handwritten input annotation. However, in order to avoid complications, the electronic review provided by the message sharing server 30 will be described below. A description will be given assuming that the review is performed only on the tag annotation associated with the link information with the bulletin board as the link destination.

  On the other hand, a general-purpose application program for document editing (hereinafter referred to as “document editing AP”) is installed in the client device 50 according to the present embodiment. By executing the document editing AP, the editing operation is performed in a state where a document editing screen (not shown) in a state where an electronic document to be edited is displayed is displayed in the display area 53A of the display unit 53. Become.

  The client device 50 according to the present embodiment is configured so that a plurality of screens can be displayed in the display area 53A, and an editing operation on the electronic document is performed with reference to the annotation attached to the electronic document. In this case, both the document editing screen by the document editing AP and the display screen related to the annotation attachment shown in FIG. 2 are displayed in the display area 53A.

[Document Management Server 10 and Document Database DB1]
By the way, the document management server 10 according to the present embodiment accepts “registration” for registering an electronic document and “document reading” for reading an electronic document in accordance with an instruction from the outside.

  The “registration” is, for example, “http: // datacenter. company. co. jp / access. cgi? As shown in DocumentID = 8gjk3cl3 ′, it is given from the outside by a path such as a URL (Uniform Resource Locators) or a directory to a document to be registered indicating an address indicating a storage location of the document in the document database DB1. .

  The document management server 10 sequentially assigns a document ID (Identification) to the document (group) indicated by the given path, and registers the document name and the document text in the document database DB1 for each document ID. In the document management server 10 according to the present embodiment, a unique ID number is assigned to each document stored in the document database DB1 as the document ID. Further, the document management server 10 registers with different document IDs as long as the document file name of the document instructed for registration is the same as long as it has been posted to the document database DB1 multiple times.

  On the other hand, in the document processing system 90 according to the present embodiment, a unit in which a plurality of users jointly use a registered document in order to achieve a common purpose using the document processing system 90 is a “task”. The task information indicating to which task a registered document belongs can be registered in the document database DB1 for each document. The task information can be registered via the client device 50 or directly by the document management server 10 when the corresponding document is registered in the document database DB1 or at an arbitrary timing after registration.

  In the document processing system 90 according to the present embodiment, a business ID is individually assigned to a registered document for managing the progress of the proofreading work, and the business ID is also assigned to the registered document. Will be registered.

  At this time, the data structure in the document database DB1 is as shown in FIG. 3 as an example. Here, the document name or the document text may be a path to a document such as a URL.

  In the document processing system 90 according to the present embodiment, the reviewer is assumed to be a user belonging to a task to which a document attached with a tag annotation that is a starting point of review belongs.

  On the other hand, when detecting that the document reading button 70 is designated in any of the client devices 50, the client device 50 notifies the document management server 10 of information indicating that. In response to this, the document management server 10 creates a list of document names in the document database DB1 and transmits it to the client device 50 that is the access source.

  In response to this, the client device 50 displays a list of document names in a list box or the like, and prompts the user to select. In response to this, when the user designates a desired document name with the annotation device 57 or the keyboard or mouse of the operation unit 54, the client device 50 transmits the designated document name to the document management server 10. .

  In response to this, the document management server 10 reads the document text and document ID corresponding to the document name received from the client device 50 from the document database DB1, and transmits the document text to the client device 50. As a result, the text of the document corresponding to the designated document name is displayed in the document display area 53C of the display unit 53 of the client device 50.

[Annotation management server 20, annotation database for sticky note DB2, annotation database for pen input DB3]
On the other hand, the annotation management server 20 according to the present embodiment accepts “save” and “search” according to instructions from the outside.

  That is, when it is detected that an annotation is attached to the document in a state where the document is displayed on the display unit 53 in any client device 50 and the save button 74 is designated, the client device 50 notifies that fact. Is sent to the annotation management server 20. As a result, the annotation management server 20 associates the information related to the annotation instructed to be saved with the document to which the annotation is attached, and when the annotation is a tag annotation, the annotation is stored in the tag annotation database DB2. If it is a handwritten input annotation, it is registered (stored) in the pen input annotation database DB3.

  That is, for example, when the annotation management server 20 receives a “save” instruction from any of the client devices 50 and the annotation to be saved is a sticky note annotation, an annotation registration process is performed as shown below. Is done.

  First, the annotation management server 20 stores position information indicating a position where an annotation to be stored is attached, a link destination when the annotation is linked, a document ID of the document with the annotation attached, and the storage The client device 50 is given the terminal ID of the client device 50 that issued the instruction. At this time, the user name (or user ID) of the user to which the annotation to be stored is attached and the time (generation time) at which the annotation is attached are also given from the client device 50.

  The annotation management server 20 stores the annotation ID, terminal ID, user ID (or user name), document ID, position information, link destination, generation time, and progress management ID in the tag annotation database DB2 in a table format. To do.

  At this time, the data structure in the tag annotation database DB2 is as shown in FIG. 4 as an example.

  In the figure, the annotation ID is used to manage individual annotations, and a unique ID number is assigned to each annotation for one tag. Here, the annotation ID includes a method issued on the client system 94 side and a method issued on the annotation management server 20 side. It should be noted that at least two sets of annotation ID and document ID need to be unique. If the given annotation ID or the above-mentioned two-tuple is not new, the line indicated by that annotation ID or the above-mentioned two-tuple is overwritten.

  The terminal ID is an ID number that uniquely identifies the client device 50. Here, the terminal ID may directly indicate the hardware of the client device 50 used by the user, or may correspond to an IP (Internet Protocol) address or a host name. The user ID (or user name) is information for uniquely identifying the user who is operating the client device 50, and corresponds to, for example, a login user name. Further, the document ID is a document ID registered in the document database DB1 of a document to which a corresponding annotation is attached.

  On the other hand, the position information is information indicating the attachment position of the annotation for one sticky note. In the present embodiment, the page number in the document indicated by the corresponding document ID and the position coordinates on the page indicated by the page number (here, the coordinates of the two points of the upper left corner point and the lower right corner point of the annotation) Indicated by a combination of In the present embodiment, the document display area 53C is set in the horizontal and vertical directions, and the size based on the horizontal size and vertical size of the document displayed in the document display area 53C (here, in the horizontal direction). A rectangular area of 1/50 (1/50) of the horizontal size of the display document and 1/60 (1/60 of the vertical size of the display document) in the vertical direction is divided into a matrix. For each segmented area, a consecutive number is assigned in advance in the order from the area at the upper left corner position in the horizontal direction and from the area at the right end position to the area at the left end position of the next row, and the number is assigned to the above position. Applied as coordinates.

  The link destination indicates link information associated with the annotation. In the document processing system 90 according to the present embodiment, as an example, the link information is represented as 'http: // MessageServer / threadViewer?' It is assumed that a path such as a URL or a path to a directory such as MessageId = 1517 'is given.

  The user can set a link destination for each attached annotation. This link destination can be set every time an annotation is attached or every time an annotation save instruction is issued.

  In the document processing system 90 according to the present embodiment, a tag annotation with a link is displayed in a state where the information of the link destination is displayed inside. For example, in the example illustrated in FIG. 2, “content review”, “unknown”, and “delete” are displayed on the tag annotation 86 as link destination information.

  The generation time is the time when an annotation for one sticky note is attached (drawn in the display area 53A) in the client device 50, and includes a date and time. This is managed for each annotation for one tag by the server separately from the time when the save button 74 is designated and saved on the client device 50.

  Further, the progress management ID is for managing the progress status of the proofreading work executed on the basis of the link destination information and the review performed using the information as a starting point for the tag annotation linked to the electronic bulletin board. A unique ID is assigned to each sticky note annotation for one sticky note that is linked. Here, the progress management ID includes a method issued on the client system 94 side and a method issued on the annotation management server 20 side. In the document processing system 90 according to the present embodiment, the progress management ID for the sticky note annotation is used for the sticky note at the timing when the message on the electronic bulletin board provided by the message sharing server 30 is linked to the sticky note annotation. It is registered in the annotation database DB2.

  The above is a description of the case where the annotation to be saved is a tag annotation, but when the annotation to be saved is a handwritten input annotation, the annotation management server 20 uses the annotation as shown below. Registration processing is performed.

  First, the annotation management server 20 includes the annotation content of the annotation to be saved, the positional information and color and shape of the annotation, the document ID of the document with the annotation attached, and the terminal ID of the client device 50 that has given the saving instruction. Is provided from the client device 50. At this time, the client device 50 also gives the user name (or user ID) of the user who attached the annotation to be saved and the time when the annotation was attached.

  Then, the annotation management server 20 includes an annotation ID, terminal ID, user ID (or user name), document ID, position information, annotation content, color shape, line type, and generation time in a pen input annotation database. Save to DB3. At this time, the data structure in the pen input annotation database DB3 is as shown in FIG. 5 as an example.

  In the figure, the annotation ID, terminal ID, user ID, document ID, position information, and generation time are the same as those in the above-mentioned tag annotation database DB2. However, regarding the annotation ID, what is registered in the annotation database for sticky note DB2 is assigned for each sticky note, whereas it is assigned for each stroke in the annotation database DB3 for pen input. Different.

  On the other hand, the annotation content in the figure is the trajectory information of one-stroke annotation, and is data used to reproduce the drawn annotation, for example, data such as bitmap or vector data. The color shape is the color of the ink used for the annotation and shape information such as a circle or a square. Further, the line type indicates a line type such as the thickness of the annotation, a solid line, or a dotted line.

  On the other hand, when the client device 50 detects that the search button 76 is specified in a state where the document is displayed in the document display area 53C of the display unit 53, the client device 50 notifies the annotation management server 20 of information indicating that. In response to this, the annotation management server 20 reads information related to the annotation for which the search has been instructed from the tag annotation database DB2 and the pen input annotation database DB3.

  That is, the annotation management server 20 receives a “search” instruction from the client device 50. At this time, the annotation management server 20 receives information regarding the document ID and the annotation attachment range from the client device 50. Then, the annotation management server 20 searches the tag annotation database DB2 and the pen input annotation database DB3 based on the information (search conditions), reads out information related to annotations that can be displayed, and accesses the client device 50 as the access source. Send to.

  In response to this, the client device 50 displays the annotation indicated by the information received from the annotation management server 20 so as to overlap the document being browsed. FIG. 2 shows an example of a state in which the tag annotation 86 and the handwritten input annotation 88 are displayed superimposed on the document 84 by the above processing.

[Message sharing server 30 and message database DB4]
On the other hand, the message sharing server 30 according to the present embodiment functions as an electronic bulletin board by a user of the document processing system 90.

  That is, when a message is written from one of the client devices 50 to be handled by the document processing system 90 to the electronic bulletin board, the message sharing server 30 registers information about the message in the message database DB4.

  In an electronic bulletin board, the first message is usually written together with the title by one of the users, a message about the message is written from another user who refers to the message, and the message about the message is also sent to other users or The message is first written by the user who wrote the message first. At this time, a message other than the first message is provided with a title corresponding to the title provided in the first message, so that the reply message is referred to as a parent by referring to the title or when creating a reply. By embedding the ID of the received message, the parent-child relationship of each message can be grasped.

  The message sharing server 30 sequentially registers the messages written from the users on the electronic bulletin board in this way in the message database DB4 together with the titles corresponding to the messages. At this time, the data structure in the message database DB4 is as shown in FIG. 6 as an example.

  In the figure, a message ID manages each message, and a unique ID number is assigned to each message. Here, there are a method of issuing the message ID on the client system 94 side and a method of issuing on the message sharing server 30 side.

  The update time is the time when the message is written on the electronic bulletin board, and consists of date and time. In this embodiment, the update time is registered using date and time information measured by a timer (not shown) provided in the control unit 31 of the message sharing server 30. However, the present invention is not limited to this, and information indicating the message writing time is given from the client device 50 that is the message writing source, and this can be registered.

  Further, the immediately preceding message ID is information indicating the message ID assigned to the message corresponding to the parent of the corresponding message, and the immediately following message ID is information indicating the message ID assigned to the message corresponding to the child of the corresponding message. In the document processing system 90 according to the present embodiment, the corresponding message is the first message, the immediately preceding message ID when there is no parent message, and the corresponding message is the last message for a common title. Information that cannot be taken as the message ID ('0' in the present embodiment) is registered as the message ID immediately after no child message.

  In the example shown in the figure, the messages with message IDs “1517”, “1518”, and “1519” are the first message because the immediately preceding message ID is “0”. The message with the message ID '1519' is the first message and has no child message because both the immediately preceding message ID and the immediately following message ID are '0'. It turns out that it is. Further, since the message ID is set to “1520”, the message ID is set to “1517” because the message ID is set to “1517” and the message ID immediately after is set to “0”. It can be seen that the message is a child's child message and has no child message.

  On the other hand, the title is information indicating the title provided in the corresponding message, and the message is information indicating the message text.

  When the message sharing server 30 is instructed to display the electronic bulletin board from any of the client devices 50, the message sharing server 30 reads information on each message from the message database DB4 and displays a list of the titles of each message so that the parent-child relationship can be identified. Information that can be created is generated and transmitted to the client device 50 of the access source. In response to this, the client device 50 displays a list of the titles of each message using the received information, so that the user of the client device 50 can select a desired title from the annotation device 57, the keyboard of the operation unit 54, By pointing with a mouse or the like, a message corresponding to the title is displayed, or a message is written to the displayed message.

[Progress management server 40, worker database DB5, progress management database DB6, schedule management database DB7]
On the other hand, the progress management server 40 according to the present embodiment manages the person who performs the task, and for the tag annotation that is linked to the electronic bulletin board, the link destination information and the review that is performed based on the information. The progress status of the calibration work executed based on the management is managed.

  That is, when an instruction to register a work performer is given from any client device 50, the progress management server 40 registers the work performer in the worker database DB5. In the document processing system 90 according to the present embodiment, the work performer also serves as the reviewer. However, the present invention is not limited to this, and a user of the document processing system 90 other than the reviewer can be the work performer. .

  FIG. 7 shows an example of the data structure of the worker database DB5 according to the present embodiment.

  In the figure, task information is information for specifying a task to which a work performer to be registered belongs. In the progress management server 40 according to the present embodiment, the task information is the same as the task information in the document database DB1 described above. Have applied. Further, the worker ID manages individual work performers, and a unique ID is assigned to each work performer. Here, the worker ID may be issued on the client system 94 side or on the progress management server 40 side. That is, in the document processing system 90 according to the present embodiment, work performers are managed in units of tasks.

  Also, the field in charge in the figure indicates the field of expertise of the corresponding work performer, and the field of specialization (for example, “computer field”, “natural science field”, “ Preliminary numerical information is registered for each “political field”, “history field”, and the like.

  Note that, in the document processing system 90 according to the present embodiment, when a work performer is registered by the client device 50, the work performer to be registered and the work performer to the user of the client device 50 are registered. Each information of the task to which the task belongs and the field in charge of the work performer is input, and the input information is transmitted to the progress management server 40, and the progress management server 40 receives the information from the client device 50. However, the present invention is not limited to this. For example, the information is directly input by the progress management server 40 and registered. You can also.

  On the other hand, in the progress management server 40 according to the present embodiment, the information on the link destination and the review starting from the information about the tag annotation linked to the message on the electronic bulletin board provided by the message sharing server 30. Is registered in the progress management database DB6.

  FIG. 8 shows an example of the data structure of the progress management database DB6 according to the present embodiment.

  In the figure, the progress management ID is information for specifying the calibration work to be managed. In the progress management server 40 according to the present embodiment, the progress management ID is the same as the progress management ID of the tag annotation database DB2 described above. When the progress management ID is registered in the tag annotation database DB2, it is also registered in the progress management database DB6.

  The progress degree is information indicating the progress degree of the calibration work specified by the corresponding progress management ID, and the progress management server 40 according to the present embodiment indicates the state before the start of the calibration work as a default. Information (here, “0”) is registered and information indicating the degree of progress of the calibration work by the work performer after the calibration work is started (here, the degree of completion of the calibration work is 100%) Approximate degree) is updated by inputting via the client device 50.

  The status is information indicating the progress status of the calibration work specified by the corresponding progress management ID in a plurality of predetermined stages. The progress management server 40 according to the present embodiment is accepting the review. “Reception” indicating a stage, “Review” indicating the stage in which work content is being examined, “Waiting for approval” indicating the stage of waiting for approval of the performed calibration work, and approval of the performed calibration work being obtained Four stages of “complete” indicating the stage where the work is completed are applied. In the document processing system 90 according to the present embodiment, as an approver having the authority to approve the executed proofreading work, a predetermined one of work performers belonging to the task to which the document to be proofreaded belongs belongs. However, the present invention is not limited to this, and other users predetermined as work approvers can also be applied.

  On the other hand, the work performer is information for identifying the work performer who executes the calibration work specified by the corresponding progress management ID, and the start date is information indicating the start date of the calibration work, and the end The scheduled date is information indicating the scheduled end date of the calibration work, the status change time is information indicating the date and time when the corresponding status is changed, and the status changer is information indicating the status updater. It is.

  In the progress management server 40 according to the present embodiment, information indicating “acceptance” is registered as the default of the status. Furthermore, in the progress management server 40 according to the present embodiment, the same information as the worker ID in the worker database DB5 is applied as the worker. Further, in the document processing system 90 according to the present embodiment, the status is changed to “review”, “waiting for approval”, and “completed” by the work performer himself. Further, in the document processing system 90 according to the present embodiment, the work performer is registered by a predetermined reviewer (for example, a task leader).

  Further, in the progress management server 40 according to the present embodiment, the date on which the progress management ID is registered is set as the start date, and the day after a predetermined period (for example, two weeks later) is set as the scheduled end date. Registered automatically. Furthermore, in the progress management server 40 according to the present embodiment, the same information as the worker ID in the worker database DB5 is applied as the state changer.

  By the way, the progress management server 40 according to the present embodiment receives an instruction to register a schedule for document creation work from the client device 50, and registers information indicating the schedule in the schedule management database DB7.

  FIG. 9 shows an example of the data structure of the schedule management database DB7 according to the present embodiment.

  In the figure, a business ID is an ID for identifying a business for which schedule registration is instructed via the client device 50, and different information (numerical information in the present embodiment) is assigned to each business. . In the document processing system 90 according to the present embodiment, the business management ID is generated by the progress management server 40. However, the present invention is not limited to this. For example, the client device 50 as the registration instruction source generates the business ID. You can also

  The business name is information indicating the name of the document creation business to be registered, the start date is information indicating the execution start date of the corresponding document creation business, and the end deadline is the information on the corresponding document creation business. The end date is information indicating the actual end date of the corresponding document creation job, and the member is the person who executed the corresponding document creation job (in this embodiment, the document creation date). This is information indicating a department that performs business independently.

  By the way, the progress management server 40 according to the present embodiment is configured to be able to hierarchically manage document creation tasks derived from document creation tasks.

  For this reason, the schedule management database DB 7 according to the present embodiment has two business IDs of “upstream business ID” and “downstream business ID” in order to express the hierarchical structure of the document creation business.

  “Upstream job ID” is information indicating the job ID of the document creation job when there is a document creation job at a level directly above the corresponding document creation job. “Downstream job ID” is directly below the corresponding document creation job. This is information indicating the job ID of the document creation job when there is a document creation job of a certain level. In the example shown in FIG. 9, for example, the business with the business name “report creation” to which “012345” is assigned as the business ID includes the document creation business to which “00742” is assigned as the business ID immediately above. This indicates that there is a document creation work (document creation work with the work name “A module specification creation”) to which “012355” is assigned as the work ID in the hierarchy immediately below. In addition, the document creation work with the work name “A module specification creation” to which “012355” is assigned as the work ID has a document creation work to which “012345” is assigned as the work ID immediately above the hierarchy. This indicates that there is no document creation job in the hierarchy.

  Note that in the document processing system 90 according to the present embodiment, the above-described business name, start date, end deadline, and member information from the client device 50 that is an instruction source for schedule registration, and the immediately above document creation business exist. In this case, information of “upstream business ID” is given.

  In the document processing system 90 according to the present embodiment, as a user who registers a schedule, a predetermined reader that collects tasks to be registered is applied. However, the present invention is not limited to this. For example, a document processing system 90 other arbitrary users may be registered.

[Scheduling function, progress correction function]
By the way, the document processing system 90 according to the present embodiment has a scheduling function for automatically setting the execution schedule of the proofreading work instructed by the annotation, and the progress input by the work performer and registered in the progress management database DB6. And a progress correction function that automatically corrects the degree to a more appropriate one according to the actual progress state.

  FIG. 10 is a block diagram showing a functional configuration of the document processing system 90 for realizing the scheduling function and the progress correction function.

  As shown in the figure, in order to realize the scheduling function and the progress correction function, the progress management server 40 includes an acquisition unit 41A, a schedule setting unit 41B, and a correction unit 41C.

  The acquisition unit 41A according to the present embodiment acquires (reads) information indicating the end deadline (corresponding to “end deadline information” of the present invention) from the schedule management database DB7 of the secondary storage unit 45. Yes.

  Further, the schedule setting unit 41B according to the present embodiment obtains information (corresponding to the “execution schedule” of the present invention) indicating start dates and scheduled end dates of a plurality of calibration operations instructed by the annotations 41A. Are derived so as to be completed by the end deadline indicated by the information obtained by the above, and stored in the progress management database DB6 of the secondary storage unit 45.

  In the schedule setting unit 41B according to the present embodiment, information indicating the start date and the scheduled end date is derived so that the plurality of calibration operations are executed in parallel within the period until the end deadline. ing.

  The information indicating the start date and the scheduled end date stored in the progress management database DB6 by the schedule setting unit 41B is displayed on the display unit 53 of the client device 50 in response to a request from any client device 50. Will be.

  On the other hand, the acquisition unit 41A acquires, from any client device 50, correction instruction information indicating a correction instruction of a derivation result of information indicating the start date and the scheduled end date of the plurality of calibration operations by the schedule setting unit 41B. The schedule setting unit 41B corrects the derivation result in accordance with the correction instruction indicated by the correction instruction information acquired by the acquisition unit 41A.

  The acquisition unit 41A acquires (reads) information indicating the degree of progress (corresponding to “progress level information” of the present invention) from the progress management database DB6 of the secondary storage unit 45. The progress indicated by is displayed on the display unit 53 of the client device 50 in response to a request from any of the client devices 50.

  Then, the correction unit 41C according to the present embodiment approaches the information indicating the degree of progress stored in the progress management database DB6 closer to the end date indicated by the information indicating the end date stored in the schedule management database DB7. It is supposed to be corrected so that the degree becomes low.

  By the way, in the document processing system 90 according to the present embodiment, the scheduling function and the progress correction function are realized by executing software.

  Next, prior to the description of the operation at the time of executing the scheduling function, the operation of the progress management server 40 when executing the schedule registration process will be described with reference to FIG. FIG. 11 is a flowchart showing a flow of processing of a schedule registration processing program executed by the control unit 41 of the progress management server 40 when a document creation job schedule registration instruction is received from any of the client devices 50. The program is stored in advance in a predetermined area of the secondary storage unit 45.

  First, in step 100 in the figure, information indicating a predetermined schedule registration screen is transmitted to the client device 50 that is the access source, and in the next step 102, reception of predetermined information from the client device 50 is awaited. .

  FIG. 12 shows an example of a schedule registration screen displayed on the display unit 53 of the client device 50 in accordance with the processing of step 100 described above. As shown in the figure, on this schedule registration screen, a message prompting entry of each item related to the document creation work to be registered is displayed, and the above-described upstream work ID and work name are included as the items to be entered. A rectangular frame for inputting the start date, end deadline, and member information is displayed. When a schedule registration screen as shown in the figure is displayed on the display unit 53, the user of the client device 50 (a reader who collects work to be registered) displays information corresponding to each rectangular frame in the operation unit. After inputting with the keyboard 54, mouse, etc., the end button displayed at the bottom of the screen is designated for pointing. In response to this, each information input by the user is transmitted to the progress management server 40. As a result, step 102 becomes affirmative and the process proceeds to step 104.

  In step 104, a business ID not registered in the schedule management database DB7 is generated, and in the next step 106, the information received in step 102 and the business ID generated in step 104 are registered in the schedule management database DB7. .

  In the next step 108, it is determined whether the information received in step 102 includes an upstream job ID. If the determination is affirmative, the process proceeds to step 110, and the job ID generated in step 104 is determined. Is registered in the schedule management database DB7 as a downstream business ID of a business whose business ID is the upstream business ID received in step 102, and then the process proceeds to step 112. If the determination at step 108 is negative, the process proceeds to step 112 without executing the process at step 110.

  In step 112, the business ID generated in step 104 is transmitted to the access source client device 50 to display the business ID generated by the display unit 53 of the client device 50, and then the schedule registration processing program is terminated. To do.

  By executing the schedule registration processing program as described above, the schedule management database DB7 shown in FIG. 9 as an example is sequentially constructed, and the schedule registrant (hereinafter referred to as “schedule registrant”) is himself / herself. Can present the business ID assigned to the business that registered the schedule. The timing of presenting the business ID to the schedule registrant is not limited to the time when the schedule is registered as described above. For example, when the schedule registrant requests presentation of the business ID at an arbitrary timing, the progress management server 40 It is also possible to adopt a form presented by

  The schedule registrant notifies the document creator that the schedule of the document creation work has been registered, together with the work ID presented from the progress management server 40. The notification may be made electronically by e-mail or the like via the network 60, or may be made by directly contacting the document creator without going through the network 60.

  The document creator who has received the notification refers to the schedule corresponding to the notified business ID, creates a corresponding document within a period according to the schedule, and then creates the document together with the notified business ID. In addition to registering in the database DB1, it notifies each reviewer that a document to be reviewed has been registered, together with a business ID. The notification may also be performed electronically by e-mail or the like via the network 60, or may be made by directly contacting each reviewer without going through the network 60.

  Then, each reviewer who has received the notification exchanges messages (discussion) regarding the business (document creation business) indicated by the notification on the electronic bulletin board provided by the message sharing server 30.

  Next, the operation of the progress management server 40 when the scheduling function is executed will be described with reference to FIG. In FIG. 13, the schedule setting button 78 displayed on the display unit 53 of the client device 50 is designated by a predetermined user (for example, a reader of a task to which the document displayed on the display unit 53 belongs). 4 is a flowchart showing a flow of processing of a schedule setting processing program executed by the control unit 41 of the progress management server 40 when the processing is performed, and the program is stored in advance in a predetermined area of the secondary storage unit 45.

  First, in step 200 in the figure, information indicating all statuses regarding a document (hereinafter referred to as “processing target document”) displayed on the client device 50 of the access source is read from the progress management database DB6. At 202, it is determined whether or not there is a calibration work whose information indicating the read status is not “completed”. If the determination is negative, the schedule setting processing program is terminated, and an affirmative determination is made. If YES, step 204 follows.

  In step 204, the business ID of the document to be processed is read from the document database DB1, and information indicating the end deadline corresponding to the read business ID is read from the schedule management database DB7.

  In the next step 206, the execution schedule (start date and scheduled end date) of the calibration work whose information indicating the status read in step 200 is not “completed” is the end deadline indicated by the information read in step 204. Derived to finish by.

  In the schedule setting processing program according to the present embodiment, the calibration work execution schedule is derived such that the current date is the start date and the end deadline is the scheduled end date. Therefore, when there are a plurality of calibration operations to be derived from the schedule, the execution schedule is derived so that the plurality of calibration operations are all performed in parallel.

  In the next step 208, using the execution schedule derived by the above processing, image data indicating a schedule board having a predetermined format is created and transmitted to the client device 50 of the access source. A process of displaying the board by the display unit 53 is performed, and then the next step 210 waits for input of predetermined information.

  FIG. 14 shows an example of the display state of the schedule board displayed on the display unit 53 of the client device 50 by the process of step 208 described above. As shown in the figure, in the schedule board according to the present embodiment, for each calibration work corresponding to the derived execution schedule, information indicating the content of the calibration work (here, a message linked to the corresponding annotation) and , A diagram showing the derived execution schedule (a diagram with the derived start date as the left end and the derived end date as the right end) is displayed.

  When the schedule board as shown in the figure is displayed on the display unit 53, the user (task leader) of the client device 50 modifies the displayed execution schedule as an example in FIG. As shown, the execution schedule can be changed by moving or changing the size of the diagram indicating the execution schedule to be corrected with respect to the time lapse direction (horizontal direction in the example shown in the figure) using the mouse of the operation unit 54. If you specify the correction button displayed at the bottom of the screen with the mouse and register it without correcting the displayed execution schedule, it will be displayed at the bottom of the screen. Pointing to the end button is specified with the mouse. Accordingly, step 210 is affirmative and the process proceeds to step 212.

  In step 212, it is determined whether or not the user has instructed correction of the execution schedule by determining whether or not a correction button has been designated on the schedule board by the user. The process proceeds to step 214, and it is determined whether or not the scheduled end date of the execution schedule corrected by the user is before the end date of the processing target document. It is determined whether or not it is consistent with the schedule, and if a negative determination is made, the process proceeds to step 216, and a warning screen having a predetermined format is accessed for a predetermined period (here, 5 seconds). The processing to be displayed on the display unit 53 of the original client device 50 is executed, and then the process returns to step 208. If the determination in step 214 is affirmative, the process proceeds to step 218.

  FIG. 16 shows an example of a warning screen displayed on the display unit 53 of the access source client device 50 by the process of step 216. By referring to the warning screen as shown in the figure, the user can easily grasp that the correction content designated by the user is incorrect.

  In step 218, the execution schedule derived by the processing in step 206 is corrected according to the correction contents by the user, and then the process proceeds to step 220. If a negative determination is made in step 212, the process proceeds to step 220 without executing the processes in steps 214 to 218.

  In step 220, information indicating the execution schedule (information indicating the start date and the scheduled end date) obtained by the above processing is stored (updated) in the corresponding column of the progress management database DB6, and then this schedule setting processing program Exit.

  By executing the scheduling function as described above, it is possible to schedule a proofreading operation that is consistent with the end date of the electronic document creation work, and to correct the scheduling result as necessary. .

  Next, with reference to FIG. 17, an operation of the progress management server 40 at the time of executing the progress correction function will be described. Note that FIG. 17 shows a progress status presentation processing program executed by the control unit 41 of the progress management server 40 when the progress button 80 displayed on the display unit 53 of the client device 50 is designated by any user. This process is also stored in advance in a predetermined area of the secondary storage unit 45.

  First, in step 300 in the figure, a task that matches a predetermined condition is specified as a presentation target task. In the present embodiment, as the predetermined condition, a sticky note to which a progress management ID is assigned by a sticky note attached to an electronic document belonging to a task to which the user of the access source client device 50 belongs. The condition of calibration work based on annotation is applied.

  In the next step 302, information relating to the progress status corresponding to the presentation target work specified in step 300 is read from each database including the progress management database DB6, and in the next step 304, the read information is read according to a predetermined condition. Sort by. In the present embodiment, sorting for each electronic document is applied as the predetermined condition, and sorting for each work performer in the same document is applied.

  In the next step 306, the information indicating the degree of progress obtained by the above processing is corrected so that the degree becomes lower as it approaches the end time limit indicated by the information indicating the corresponding end time limit stored in the schedule management database DB7. To do.

  Here, in the progress status presentation processing program according to the present embodiment, the correction is performed by the following equation (1). Here, SX is the degree of progress registered in the progress management database DB6 (the degree of progress declared by the work performer), NN is the number of days from the start date to this point, and NT is from the start date to the scheduled end date. , S represents the degree of progress after correction.

S = SX / (NN / NT) (1)
The arithmetic expression for correcting the degree of progress is not limited to that shown in the expression (1). For example, it is a value obtained by multiplying (NN / NT) in the expression (1) by a predetermined weight value. Any arithmetic expression can be applied as long as it can correct the degree of progress stored in the progress management database DB6 so that the degree becomes lower as it approaches the end deadline, such as an arithmetic expression for dividing the progress degree SX. Needless to say.

  In the next step 308, image data indicating a progress management screen having a predetermined layout is created using the information obtained by the above processing, and in the next step 310, the created image data is stored in the access source. To the client device 50, the progress management screen is displayed on the display unit 53 of the client device 50, and then the progress status presentation processing program is terminated.

  FIG. 18 shows an example of a progress management screen displayed by the display unit 53 of the client device 50 that is the access source by the process of step 310 described above. As shown in the figure, in this progress management screen, the document name and the comment content (here, the message displayed in the tag annotation) are displayed, and each comment content is executed based on the comment content. The progress of the calibration work (the progress corrected by the processing in step 306), the status, the person in charge, the delivery date, the status change date and time, the status changer (the “progress”, “status”, Information corresponding to “work performer”, “scheduled end date”, “status change time”, “status changer”) and comment date (corresponding to “update time” in the message database DB4) is displayed.

  By referring to such a progress management screen, the user of the client device 50 can accurately grasp the progress status of a plurality of operations included in the task to which the client device 50 belongs in a short time.

  As described above in detail, in this embodiment, management of the progress of the creation of an electronic document attached with a plurality of work instruction comments (here, messages linked to annotations) each instructing a calibration work is performed. , End date information indicating an end date of the creation of the electronic document is acquired, and execution schedules of a plurality of proofreading operations instructed by the plurality of operation instruction comments are ended by the end date indicated by the end date information Since the information indicating the execution schedule stored in the storage unit (here, the secondary storage unit 45) and stored in the storage unit is displayed. Scheduling that is consistent with the end deadline can be performed.

  Also, in the present embodiment, when deriving a plurality of calibration work execution schedules, the execution schedules are executed in parallel within a period up to the end deadline indicated by the end deadline information. Therefore, the execution schedule can be easily derived.

  Further, in the present embodiment, correction instruction information indicating a correction instruction for the execution schedule derivation result is further acquired, and the execution schedule derivation result is corrected in accordance with the correction instruction indicated by the correction instruction information. Therefore, the derived execution schedule can be optimized.

  In the present embodiment, since progress information indicating the progress of the calibration work is acquired and displayed, the progress of the calibration work with respect to the execution schedule can be easily grasped.

  In particular, in the present embodiment, since the degree of progress is corrected so that the degree of progress becomes lower as it approaches the end deadline indicated by the end deadline information, the degree of progress more in line with the actual situation can be grasped.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. Various changes or improvements can be added to the above-described embodiment without departing from the gist of the invention, and embodiments to which such changes or improvements are added are also included in the technical scope of the present invention.

  Further, the above embodiments do not limit the invention according to the claims (claims), and all combinations of features described in the embodiments are not necessarily essential to the solution means of the invention. Absent. The embodiments described above include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. Even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, as long as an effect is obtained, a configuration from which these some constituent requirements are deleted can be extracted as an invention.

  For example, in the above embodiment, the end deadline information indicating the end deadline of the electronic document creation work is acquired, and the execution schedules of a plurality of calibration work specified by the annotation are finished by the end deadline indicated by the end deadline information However, the present invention is not limited to this, and the execution schedule of the electronic document creation work is derived so as to be completed by the end deadline indicated by the end deadline information. It can also be.

  In this case, the execution schedule (information indicating the start date and the scheduled end date) of the plurality of calibration operations is registered in advance in the progress management database DB6, and the final deadline (latest scheduled end date) in the execution schedule is set as the above Considering the end date of the electronic document creation work, information indicating the end date of the electronic document creation work for which the plurality of proofreading operations are performed is derived and registered in the schedule management database DB7.

  FIG. 19 shows an example of the processing flow of the schedule setting processing program in this embodiment. It should be noted that the schedule setting processing program is a user whose schedule setting button 78 displayed on the display unit 53 of the client device 50 is predetermined (for example, a task leader to which the document displayed on the display unit 53 belongs, etc. ) Is executed by the control unit 41 of the progress management server 40 in the same manner as in the above embodiment.

  First, in step 400 of the figure, information indicating all statuses regarding the document (processing target document) displayed on the client device 50 that is the access source is read from the progress management database DB6, and is read in the next step 402. It is determined whether there is a calibration work whose status information is not “completed”. If the determination is negative, the schedule setting processing program is terminated, and if the determination is affirmative, step 404 is performed. Migrate to

  In step 404, the execution schedule (start date and scheduled end date) of the calibration work whose information indicating the status read in step 400 is not “completed” is read from the progress management database DB6, and in the next step 406, The execution schedule of the processing target document is derived so as to end before the final scheduled end date (latest scheduled end date) of the read execution schedule.

  In this schedule setting processing program, the execution schedule of the processing target document is derived so that the current date is the start date and the final scheduled end date is the end date.

  In the next step 408, information indicating the execution schedule of the processing target document derived by the processing in step 406 (information indicating the start date and the end deadline) is stored (updated) in the corresponding column of the schedule management database DB7. Then, the schedule setting processing program is terminated.

  Even by executing the scheduling function as described above, it is possible to perform scheduling that is consistent with the end date of the electronic document creation work.

  In the above-described embodiment, a case has been described in the schedule setting processing program in which the execution schedule of each proofreading work is derived so that a plurality of proofreading work is executed in parallel within the period until the end date of the document creation work. However, the present invention is not limited to this. For example, the execution schedule of each proofreading work is derived so that a plurality of proofreading work is executed one by one within a period until the end date of the document creation work. It can also be in the form.

  FIG. 20 shows an example of the display state of the execution schedule of each calibration work on the schedule board in this case. In this case as well, the same effects as in the above embodiment can be obtained.

  Further, a workflow template indicating the flow of the proofreading process in the document creation work of the department that executes the document creation work is registered in advance in the progress management server 40, and the flow indicated by the workflow template is followed. In addition, it is also possible to derive a plurality of proofreading execution schedules so as to fit within the processing target document creation work schedule. In this case, it is possible to derive an execution schedule corresponding to the actual flow of the calibration work, and it is possible to improve convenience.

  In the above-described embodiment, a case has been described in which a plurality of calibration work execution schedules instructed by a plurality of work instruction comments are derived. However, the present invention is not limited to this, and a single electronic document is used. On the other hand, it is needless to say that one work instruction comment is attached, and an execution schedule of one calibration work instructed by the work instruction comment can be derived. In this case as well, the same effects as in the above embodiment can be obtained.

  In the above embodiment, the case where the degree of progress is presented solely on the progress management screen (see FIG. 18) has been described. However, the present invention is not limited to this, and for example, FIG. As shown, the progress may be presented alongside the actual execution schedule of the corresponding calibration work. In this case as well, the same effects as in the above embodiment can be obtained.

  In the above-described embodiment, the case where the review is performed using the electronic bulletin board has been described. However, the present invention is not limited to this. For example, the review may be performed using the annotation. In this case, since it is not necessary to use the message sharing server 30, the document processing system 90 can be constructed at a low cost.

  In the above embodiment, the case where the review is performed using the information displayed on the tag annotation as a starting point has been described. However, the present invention is not limited to this. For example, the information indicated by the handwritten input annotation A review may be performed as a starting point. In this case, information similar to the progress management ID provided in the tag annotation database DB2 is provided in the pen input annotation database DB3. In this case as well, the same effects as in the above embodiment can be obtained.

  Further, in the above embodiment, the case where the link destination message (starting message on the electronic bulletin board) is displayed on the tag annotation has been described. However, the present invention is not limited to this, and for example, the tag annotation On the other hand, it is possible to directly input a comment (comment for instructing calibration work) and display the comment. In this case, it is also possible to associate link information for linking a starting message of a message exchanged on the electronic bulletin board regarding the comment with the tag annotation. In this case as well, the same effects as in the above embodiment can be obtained.

  Further, in the above embodiment, a case has been described in which the link information linked to the starting point message exchanged on the electronic bulletin board is associated with the tag annotation, but the present invention is not limited to this, for example, the starting point Instead of the message, link information linked to another message exchanged with the origin message as the origin may be associated. In this case, the most important message, the latest message, and the like can be displayed on the tag annotation, and convenience can be improved.

  In the above-described embodiment, the case where handwritten input is realized using the pen-type annotation device 57 has been described. However, the present invention is not limited to this, and for example, input / instructions such as a keyboard and a mouse It can also be realized by using a device. In this case, since it is not necessary to use a tablet PC as the client device 50, the document processing system 90 can be constructed at a low cost.

  Further, although cases have been described with the above embodiment where the present invention is applied to a client / server system, the present invention is not limited to this, for example, a mode applied to a P2P (Peer to Peer) system, The present invention can also be applied to a single information processing apparatus. Here, when the present invention is applied to the P2P system, the processing of each server in the server system 92 described in the above embodiment can be executed in each client device. In addition, when the present invention is applied to a single information processing apparatus, the processing of each server described in the above embodiment can be executed in the information processing apparatus. There is no need for processing and configuration for sending and receiving. In these cases, the same effects as those of the above embodiment can be obtained.

  In the above embodiment, the case where the document management server 10, the annotation management server 20, the message sharing server 30, and the progress management server 40 are configured as separate bodies has been described. However, the present invention is not limited to this. For example, the function of each server may be realized by a single (stand-alone) information processing apparatus such as a PC or a workstation. In this case as well, the same effects as in the above embodiment can be obtained.

  In the above embodiment, the case where the scheduling function and the progress correction function are realized by software has been described. However, the present invention is not limited to this. For example, the function is realized by hardware. You can also As an example of the form in this case, the form which provides the progress management server 40 with the functional device which acts similarly to the acquisition part 41A, the schedule setting part 41B, and the correction part 41C shown in FIG. 10 as an example can be illustrated. In this case, the scheduling function and the progress correction function can be expected to be faster than in the above embodiment.

  The data structure of each database shown in the above embodiment (see FIGS. 3 to 9) is also an example, and items to be stored may be added or unnecessary items may be deleted as necessary. Of course, it goes without saying that the contents stored in each item can be changed as appropriate.

  Further, the processing flow of the various processing programs shown in the above embodiment (see FIGS. 11, 13, 17, and 19) is also an example, and may be changed as appropriate without departing from the gist of the present invention. Needless to say, you can.

  Further, how to distribute each functional element to the server system 92 and the client system 94 in constructing the system is not limited to that described in the above embodiment, and convenient distribution in constructing the system is possible. Needless to say, you can do it.

1 is a schematic diagram showing an overall configuration of a document processing system according to an embodiment. It is the schematic which shows the structural example of the display screen regarding attachment of the annotation by the display part of the client apparatus which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the document database which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the annotation database for sticky notes which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the annotation database for pen input which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the message database which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the worker database which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the progress management database which concerns on embodiment. It is a schematic diagram which shows an example of the data structure of the schedule management database which concerns on embodiment. It is a block diagram which shows the functional structure of the document processing system for implement | achieving the scheduling function and progress correction function which concern on embodiment. It is a flowchart which shows the flow of a process of the schedule registration process program which concerns on embodiment. It is the schematic which shows an example of the display state of the schedule registration screen which concerns on embodiment. It is a flowchart which shows the flow of a process of the schedule setting process program which concerns on embodiment. It is the schematic which shows an example of the display state of the schedule board which concerns on embodiment. It is the schematic with which it uses for description of the correction procedure with respect to the execution schedule of the calibration work derived | led-out by the schedule setting process program which concerns on embodiment. It is the schematic which shows an example of the display state of the warning screen which concerns on embodiment. It is a flowchart which shows the flow of a process of the progress condition presentation process program which concerns on embodiment. It is the schematic which shows an example of the display state of the progress management screen which concerns on embodiment. It is a flowchart which shows the flow of a process of the modification of the schedule setting process program which concerns on embodiment. It is a figure with which it uses for description of the modification of the derivation | leading-out procedure of the execution schedule of the some calibration work by the schedule setting process program which concerns on embodiment, and is the schematic which shows an example of the display state by the schedule board of a derivation result. It is the schematic with which it uses for description of the modification of the presentation method of the progress which concerns on embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Document management server 20 Annotation management server 30 Message sharing server 40 Progress management server 41 Control part (acquisition means, schedule setting means, correction means)
41A acquisition unit (acquisition means)
41B Schedule setting section (schedule setting means)
41C Correction part (correction means)
43 Display unit 45 Secondary storage unit (storage means)
50 Client device 53 Display unit (display means)
60 network 90 document processing system 92 server system 94 client system

Claims (8)

A progress management support device that supports the management of the progress of creation of an electronic document attached with a work instruction comment for instructing a proofreading work,
Acquisition means for acquiring end deadline information indicating an end deadline of the creation work of the electronic document;
A schedule setting means for deriving and storing the execution schedule of the proofreading work instructed by the work instruction comment or the creation work of the electronic document by the end deadline indicated by the end deadline information;
A progress management support device. The schedule setting means includes a plurality of the work instruction comments attached to the electronic document, and when deriving an execution schedule of a plurality of calibration work instructed by the plurality of work instruction comments, The progress management support apparatus according to claim 1, wherein the execution schedule is derived so as to be executed in parallel within a period until the end deadline indicated by the end deadline information, or to be executed in series one by one. In deriving the execution schedule of the calibration work by the schedule setting means,
The acquisition unit further acquires correction instruction information indicating a correction instruction of the execution schedule derivation result,
The progress management support apparatus according to claim 1, wherein the schedule setting unit corrects the derivation result of the execution schedule according to a correction instruction indicated by the correction instruction information acquired by the acquisition unit. The progress management support apparatus according to any one of claims 1 to 3, further comprising display means for displaying information indicating the execution schedule stored in the storage means by the schedule setting means. The acquisition means further acquires progress information indicating the progress of the calibration work,
The progress management support apparatus according to claim 4, wherein the display unit further displays a progress level indicated by the progress level information acquired by the acquisition unit. The progress management support apparatus according to claim 5, further comprising a correcting unit that corrects the progress degree so that the degree of progress decreases as the end time limit indicated by the end time limit information is approached. A progress management support method for supporting the management of the progress of creation of an electronic document attached with a work instruction comment for instructing a proofreading work,
Obtaining end deadline information indicating an end deadline for the creation of the electronic document;
Deriving the execution schedule of the proofreading work instructed by the work instruction comment or the creation work of the electronic document so as to be completed by the end deadline indicated by the end deadline information and storing it in the storage means;
Progress management support method. A progress management support program that supports the management of the progress of the creation of an electronic document attached with a work instruction comment that instructs a proofreading work,
An acquisition step of acquiring end deadline information indicating an end deadline of the creation of the electronic document;
A schedule setting step for deriving the execution schedule of the calibration work instructed by the work instruction comment or the creation work of the electronic document to be completed by the end deadline indicated by the end deadline information and storing the schedule in a storage unit;
A progress management support program that causes a computer to execute.

Images