JP2007328650A - Information sharing device and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To share information to be shared among a plurality of groups while controlling information disclosure. <P>SOLUTION: A sharing management part 21 acquires in a task 1, electronic specifications to be copied, action items corresponding to the electronic document, annotation relating to the action items, and message information. A shared information generation part 30 copies these information to be shared with a task 2 to share the information with the task 2. When information of the task 2 is generated by copying, the disclosure of a part of information is limited by replacing information to be kept secret with the other information in accordance with a sharing condition of an access right or the like of a task member. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to management of information related to a shared electronic document in which document processing such as editing is performed by a plurality of groups.

  Documents such as reports, specifications, manuals, etc. created in an organization are often shared by multiple parties, and there are many cases where authors cross divisions. The written document is reviewed mutually by each person in a plurality of departments, and is completed.

  In such a document creation process, there are situations in which a plurality of organizations and related departments (hereinafter collectively referred to as “groups”) simultaneously edit or review a single document in a closed world. For example, when the development department creates a functional specification and the quality assurance department reviews it. If there is an item that is still under consideration, the development department issues the first edition with the description about the item being put on hold, and requests the quality assurance department to review it. While the Quality Assurance Department is reviewing the first edition, the Development Department will review the items that were previously suspended for the publication of the second edition and their descriptions, and proceed with editing. At this time, it is better to inform the quality assurance department of the status of the examination regarding the pending matters in the development department, but the details of the examination contents may not be known to the quality assurance department.

  In such a situation, joint editing, a progress management system, a task management system, and the like that enable concurrent editing by a plurality of people simultaneously in each organization have been conventionally proposed (for example, Patent Documents 1 and 2). .

JP 2004-280321 A JP 2002-245034 A

  However, in the past, it was only possible to select whether to share all information or not all, so multiple groups were involved in editing at the same time, and the progress status and contents of the items. Even when it is desired to keep the information partially secret from other groups, etc., the information cannot be partially secreted according to the progress of the document editing work. For this reason, in the past, when the entire electronic document was kept confidential and information desired to be shared with other groups was created, for example, e-mail was used or a task including both members was created separately. In this case, some means must be taken every time, and the work for that is troublesome and inconvenient. In addition, when information transmission is delayed, editing work may be delayed or efficiency may be reduced.

  An object of the present invention is to share information to be shared among a plurality of groups while controlling information disclosure.

  An information sharing apparatus according to the present invention includes a first document related information storage unit that stores first document related information as information related to a first electronic document shared by users belonging to a first group, The first implementation item information including the first implementation item identification information and the related information of the implementation item is set to correspond to each of the implementation items for which the user belonging to one group is to manage the progress of the first electronic document. A first message that stores first message information relating to a message related to each of the items that are to be managed by the user belonging to the first group and the progress of the first electronic document; Information storage means and information related to the second electronic document generated by duplicating the first electronic document for sharing with users belonging to the second group; Second document related information storage means for storing the second document related information, and a user belonging to the second group is set corresponding to each of the implementation items whose progress should be managed with respect to the second electronic document, The second implementation item information storage means for storing the second implementation item information including the implementation item identification information and the related information of the implementation item, and the user belonging to the second group manages the progress of the second electronic document Second message information storage means for storing second message information relating to messages related to each of the implementation matters, and when the second electronic document is generated by duplicating the first electronic document, the first and second Document-related information sharing means for setting the identification information of the first and second electronic documents to correspond to each of the document-related information, and the actual information managed by the first implementation item information storage means. An action item specifying means for specifying an action item to be shared with the second group from among the matters, and a sharing condition in which information that is not subject to disclosure is set, and corresponding to the action item specified by the action item specifying means. The second action item information is generated by referring to the one action item information and is stored in the second action item information storage means, and the first and second action information are respectively stored in the first and second action item information. Refers to the first message information related to the action item identified by the action item identification means according to the sharing condition in which the item identification information is set correspondingly and the sharing condition in which the information not to be disclosed is set And message information sharing means for generating the second message information and storing the second message information in the second message information storage means.

  An information sharing program according to the present invention includes a first document related information storage unit that stores first document related information as information related to a first electronic document shared by users belonging to a first group. A first implementation item that is set in correspondence with each implementation item for which the user belonging to the first group should manage the progress of the first electronic document, and includes the first implementation item identification information and related information of the implementation item A first implementation item information storage unit for storing information; a first message unit for storing first message information relating to a message associated with each implementation item for which a user belonging to the first group should manage progress with respect to the first electronic document; Message information storage means, a second electronic document generated by duplicating the first electronic document for sharing with users belonging to the second group Second document related information storage means for storing second document related information as related information, a user belonging to the second group is set corresponding to each of the implementation items whose progress should be managed with respect to the second electronic document, Second implementation item information storage means for storing second implementation item information including second implementation item identification information and related information of the implementation item, and a user belonging to the second group manages the progress of the second electronic document Second message information storage means for storing second message information relating to a message related to each of the implementation matters to be performed; when the second electronic document is generated by duplicating the first electronic document, the first and second Managed by the document related information sharing means for setting the identification information of the first and second electronic documents in correspondence with the document related information, and the first implementation information storing means. The action item specifying means for specifying the action items to be shared with the second group from among the action items specified, and the action items specified by the action item specifying means in accordance with the sharing condition in which the information not to be disclosed is set The second action item information is generated by referring to the first action item information to be stored in the second action item information storage means, and the first and second action item information are respectively stored in the first and second action item information. In accordance with a sharing condition in which information that is not subject to disclosure is set, the first message information related to the implementation item identified by the implementation item identification unit It is made to function as message information sharing means for generating second message information by reference and storing it in the second message information storage means.

  Further, the implementation item specifying means may specify an implementation item for which the first implementation item information that matches the input sharing condition is set as an implementation item shared with the second group. .

  Furthermore, each of the first and second implementation item information may include at least one item information of the user identification information, implementation deadline information, or implementation state information of the implementation item.

  Further, the implementation item information sharing unit and the message information sharing unit may generate each information according to a sharing condition of following access authority information set for each group or group member.

  Further, when each information sharing means detects that the second group does not have access authority to the information of the corresponding first group when storing the information for the second group May be set by replacing the information of the first group with information that can be disclosed.

  In addition, the date information when the information was updated synchronously last time is set in the first and second implementation item information, and the date information when updated is set in the first and second message information. When the information sharing means detects that the implementation item information has been updated in one of the first group and the second group, the information sharing means corresponds to the update content of the other corresponding information. You may make it update.

  Further, when the user who belongs to both the first and second groups accesses the shared electronic document, the user refers to the computer according to the access right set for the user in each group. You may make it function as a display information preparation means which produces display information.

  According to the present invention, in a situation where a plurality of collaborative workplaces edit or review an electronic document having the same content, it is possible to share information to be shared while restricting disclosure of confidential information.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

Embodiment 1 FIG.
FIG. 1 is an overall configuration diagram of a document information processing system according to the present embodiment. FIG. 1 shows a document management server 20 that collectively manages electronic documents handled by the system, a client 12 used by each user belonging to any group such as a department in the organization, the document management server 20 and each client 12. A network 14 is shown.

  FIG. 2 is a hardware configuration diagram of the document management server 20 in the present embodiment. The document management server 20 used in the present embodiment can be realized by a hardware configuration of a general-purpose server computer that has existed in the past. That is, as shown in FIG. 2, the document management server 20 includes a CPU 1, a ROM 2, a RAM 3, an HDD controller 5 connected to a hard disk drive (HDD) 4, a mouse 6 and a keyboard 7 provided as input means, and a display device. An input / output controller 9 for connecting the respective displays 8 is connected to an internal bus 10. Since the client 12 can be realized by a general-purpose personal computer, the hardware configuration can be illustrated as in FIG.

  FIG. 3 is a block diagram of the document management server 20 in the present embodiment. The document management server 20 in this embodiment includes a sharing management unit 21, a document management unit 22, an annotation management unit 23, a message management unit 24, an action item management unit 25, a task management unit 26, and a user interface (UI) unit 27. Have. The document management unit 22 stores and manages document related information related to a shared electronic document in a document database (DB) 31. Annotations are, for example, notes attached to an electronic document using a document editing application having a function for writing and editing documents such as DocuWorks (registered trademark) manufactured by Fuji Xerox Co., Ltd. Stores and manages information related to annotation added to an electronic document by a client user in an annotation database (DB) 32. The message management unit 24 stores and manages information related to messages written in an electronic document or annotation by a client user using a document editing application in a message database (DB) 33. Annotations and messages are stored and managed by the document management unit 22 in relation to the electronic document main body, whereas the annotation management unit 23 and the message management unit 24 store message information (annotations and messages) added to the electronic document main body. Perform retention management.

  In the present embodiment, an issue related to an electronic document and an action item to be progress managed such as TODO are referred to as an action item. However, the action item management unit 25 stores information related to an action item for an electronic document in an action item database (DB). ) 34 and stored and managed. In a system that provides a place for collaboration such as ArcSuite (registered trademark) manufactured by Fuji Xerox Co., Ltd., the items to be implemented using this system, such as the items to be reviewed for electronic documents, are the concept of “task” for each item. Can be managed. Each task is executed by a member composed of one or more users who perform the task. That is, when a task (document review, etc.) is generated, the task is executed by a group (development department, quality assurance department, etc.). The task management unit 26 stores and manages information regarding this task in a task database (DB) 35. When editing to the functional specification is performed in parallel in a plurality of groups, a task is generated and managed for each group. The user interface unit 27 provides a user interface used by an administrator of the system.

  The sharing management unit 21 in this embodiment is a means for managing information shared between tasks, and includes a shared action item determination unit 28, a shared information determination unit 29, and a shared information creation unit 30. Yes. The shared action item determination unit 28 determines an action item to be shared between tasks by copying and moving the electronic document. The shared information determination unit 29 determines a message or annotation to be copied in order to share information with other tasks by sharing action items. The shared information creation unit 30 restricts information to be copied with an access right when copying information between tasks. Further, the content of information displayed on the user interface unit 27 is controlled by the access right.

  The components 21 to 27 in the document management server 20 are realized by a cooperative operation of the document management server 20 and a program that operates on the CPU 1 mounted on the document management server 20. The various databases 31 to 35 are realized by an external storage device mounted on the document management server 20 or an external storage device connected so as to be accessible via the network 14. Further, the program used in this embodiment can be provided not only by communication means but also by storing it in a recording medium such as a CD-ROM.

  Next, the operation in this embodiment will be described. In the present embodiment, in order to have the electronic document created in task 1 also reviewed in task 2, information sharing in the case of copying the electronic document reviewed in task 1 (here, the functional specification) to task 2 The processing will be described with reference to the flowchart shown in FIG. 4 and examples of setting contents of various information set and registered in the databases 31 to 35 shown in FIGS. The data structure of various information will be described with reference to FIG. 5 showing the setting contents of various information before copying.

  The document related information stored in the document database 31 includes a document ID, document name, electronic document, and shared document ID as identification information of each electronic document. Among these, the shared document ID is a document ID for identifying an electronic document used in another task when the electronic document is copied.

  Information related to the action item stored in the action item database 34 includes an action item ID (AIID) as identification information of each action item, a name as identification information of a person in charge for executing the action item, and an implementation deadline The delivery date in which the date and time are set, the message ID as message identification information set in the action item, the status indicating the current state of the action item, and the shared action item ID (shared AIID) are included. Among these, the shared action item ID is an action item ID for identifying an action item disclosed in another task by copying the action item.

  The annotation-related information stored in the annotation database 32 includes an annotation ID (AnnID) as identification information of each annotation, a document ID of an electronic document to which the annotation is added, and in this example, the number of pages and coordinate information on the page. The position information for specifying the position where the annotation is added in the electronic document and the actual content of the annotation are included.

  Information related to messages stored in the message database 33 includes message ID as identification information of each message, user name, parent ID, cooperation annotation (Ann) ID, and actual contents of the message as identification information of the user who wrote the message. Is included. The messages are written in a chain by responding to the written message in some cases, and in this case, the parent ID is set to identify the message to which the message is to be responded. That is, the message ID of the response source message is set as the parent ID. Similarly, a linkage annotation ID is set in order to specify in which annotation the message is described.

  Although not shown in FIG. 5, the task information stored in the task database 35 includes a task ID as identification information of each task, the task is a processing target, and an electronic document in this example is specified. A document ID, a user ID as identification information of a user constituting the task member, access right information for each task member, and the like are included. In addition to this, personal information including a user ID or the like is used in the present embodiment in order to specify a user belonging to each task member.

  Hereinafter, the operation will be described. As shown in FIG. 5, task 1 is a state in which a functional specification is edited and a task called review of the functional specification is being executed. Strictly speaking, as is clear when referring to the status of the action item information, the review by Mr. A who belongs to the task 1 is finished, and Mr. B is in the state of conducting the review. Note that the task 2 is requested to be reviewed from now on, but in FIG. 5, since the request has already been determined, the status is already set to “in progress”.

  Here, when any task member of task 1 (T1 task) requests review of the functional specification to task 2 (T2 task), the document management server 20 is set to task 1 as described below. Of the various types of information, only information necessary for information sharing is copied to the task 2 side, and necessary information such as identification information is set and registered. By performing this process, the electronic document to be reviewed is copied.

  As shown in FIG. 4, the sharing management unit 21 first obtains an electronic document to be copied for review, in this example, information on the functional specification from the document management unit 22 and information on the task from the task management unit 26. (Step 110). Here, information necessary for specifying the information to be copied, specifically, the document ID “0001” of the functional specification and the identification information “T2 task” of the task executed by the group 2 as the copy destination are acquired. To do. Subsequently, the share management unit 21 acquires information about the action item corresponding to the functional specification to be copied (step 120). Here, the action item IDs “1”, “2”, and “3” are acquired. Subsequently, the shared action item determination unit 28 in the sharing management unit 21 determines an action item to be shared between tasks by copying and moving the electronic document from the acquired action items according to the input sharing condition. (Step 130). In the present embodiment, a sharing condition of an action item whose status included in the action item information is not “finished” is set and registered in the system in advance, and the shared action item determination unit 28 sets the sharing condition as the action item information. Read from the system and extract action items that meet this condition. In this example, it is possible to specify action items with action item IDs “2” and “3” whose status is not “end”.

  In the present embodiment, a sharing condition of an action item whose status is not “finished” is set in the system in advance as in the above example. However, the user is requested to input the condition from the user interface unit 27. It may be. Further, the delivery date and the person in charge may be set as sharing conditions by inputting and specifying the date and time, the user ID, and the like. In this way, information to be copied to another task 2 can be selected in accordance with the sharing condition, so that part of information related to the electronic document, such as information that should be kept confidential, is not disclosed to other tasks. it can.

  When the action item to be copied is specified, the shared information determination unit 29 specifies the annotation and message to be copied by determining according to the input sharing condition (step 140). In this embodiment, the sharing condition “annotation and message corresponding to the specified action item” is set and registered in the system in advance, and the shared information determination unit 29 reads the sharing condition from the system. Then, annotations and messages that match this condition are extracted. In this example, the message IDs “4” and “5” included in the action item information with the action item IDs “2” and “3” can be specified. However, as apparent from the message information, the parent ID “3” is set in the message information of the message ID “4”, and the parent ID “2” is set in the message information of the message ID “3”. Since the message is set, the messages corresponding to the action item with the action item ID “2” are the messages with the message IDs “4”, “3”, and “2”. On the other hand, although the parent ID is not set in the message information of message ID “5”, the message information of message ID “6” having message ID “5” as the parent ID exists, so shared information determination unit 29 The messages with the message IDs “5” and “6” are extracted as the messages corresponding to the action item with the action item ID “3”.

  Then, when the shared information determination unit 29 refers to the cooperation annotation ID of the message information with the message IDs “4”, “3”, and “2”, since the cooperation annotation ID “2” is set, the action item ID “ An annotation with a linked annotation ID “2” is extracted as an annotation corresponding to the action item 2 ”. Similarly, when the shared information determination unit 29 refers to the cooperation annotation ID of the message information with the message IDs “5” and “6”, since the cooperation annotation ID “3” is set, the action item ID “3” is set. An annotation having a linkage annotation ID “3” is extracted as an annotation corresponding to the action item.

  The various information identified as the copy target by the above processing is shown in FIG. 6, but the shared information creation unit 30 creates various information in the task 2 by copying these information to the task 2 (step 150). However, in order to share an electronic document, information having the same content is also set in task 2. However, in task 2, information is managed separately, such as an annotation added separately from task 1, Various IDs (document ID, action item ID, message ID, and annotation ID) for identifying information are assigned separately from the task 1. In this way, as various IDs are newly assigned, the shared information creation unit 30 causes the message ID included in the action item information, the parent ID and linkage annotation ID included in the message information, and the document included in the annotation information. The ID is updated to various newly assigned IDs. Then, by setting the document ID “0001” of the electronic document used in task 1 to the shared document ID included in the document related information, the electronic document shared in task 2 and task 1 is associated. Similarly, by setting IDs “2” and “3” of action items executed in task 1 to the shared action item ID included in each action item information, the action items shared by task 2 and task 1 are associated with each other.

  Further, in the present embodiment, since it is desired to treat the member 1 of the task 1 as confidential without disclosing personal information, the shared information creation unit 30 satisfies this condition according to the sharing condition set as confidential. Corresponding information, specifically, the person in charge included in the action item information and the writer included in the message information are changed to the task name “T1 task”. More specifically, when the shared information creation unit 30 creates the task 2 information, the task 2 does not have the access right (reference right) to the personal information of the members of the task 1. Upon detection, information is generated by replacing the personal information (user name) with the task name “T1 task” to which the user belongs as information that can be disclosed. As a result, the personal information in task 1 is not disclosed in task 2. In this example, the personal information of the member of task 1 is taken as an example, but the information that is subject to access right control is not limited to personal information.

  Furthermore, when the shared information creation unit 30 sets various IDs in the task 2, the shared information creation unit 30 sets the document ID “0002” of the electronic document used in the task 2 to the shared document ID included in the document related information of the task 1. The electronic document shared by task 1 and task 2 is associated. Similarly, by setting the action item IDs “11” and “12” executed in the task 2 to the shared action item IDs included in the action item information of the action item IDs “2” and “3”, respectively, the task Associate action items shared between 1 and task 2.

  When the generation and update of information are completed as described above, the information management units 22 to 25 update the databases 31 to 34 with the corresponding information shown in FIGS. 6 and 7 (step 160). FIG. 8 shows an example of setting contents of various information after the electronic document and various information related to the electronic document are copied as described above.

  According to the present embodiment, when copying an electronic document for review purposes as described above, only action items related to the electronic document that meet the sharing condition can be shared between tasks. In addition, various types of information related to shared action items can be shared. As described above, since the information sharing process can be performed according to the sharing condition, it is possible to share the information to be shared while keeping the information to be kept secret. In addition, it is possible to share information while keeping a part of the information in a secret state using another means or without performing another work, so that it is possible to prevent a delay in information transmission and a decrease in work efficiency such as editing. it can.

Embodiment 2. FIG.
The present embodiment is a process performed after the electronic document reviewed in task 1 in the first embodiment is copied to task 2, and each task when action item information in task 1 is changed A process for maintaining the consistency of information of 1 and 2 will be described. In order to implement the present embodiment, it is necessary to additionally set the following items for each piece of information used in the first embodiment. This added information is clear from the diagram shown in FIG. That is, in the action item information, by setting and registering the action item ID of the annotation copied to the other task in the shared action item ID (step 150 in FIG. 4), the date and time when the action item is shared is set. The previous synchronization time is included. The annotation information includes an update date and time for setting the date and time when the annotation is updated, and the message information includes an update date and time for setting the date and time when the message is updated.

  Next, the operation in the present embodiment will be described using the flowchart shown in FIG. 9 and examples of setting contents of various information set and registered in the databases 31 to 35 shown in FIGS. First, FIG. 10 shows a state before the action item is changed, and it is assumed that the action item with the action item ID “2” of task 1 is completed from this state. The end of the action item can be recognized by a predetermined end operation by the user. As a result, as shown in FIG. 11A, the action item management unit 25 changes the status of the corresponding action item information to “finished”. When it is detected that the item information set in any of the action item information has been changed, the share management unit 21 acquires information on the changed action item from the action item management unit 25 (step 210). Here, the action item ID “2” and the status “end” are acquired from the action item information. Furthermore, the sharing management unit 21 acquires the shared action item ID “11” from the action item information (step 220).

  The processing performed after this is basically the same as the processing (steps 140 to 160) in the first embodiment. That is, when the action item to be processed is specified, the shared information determination unit 29 specifies the change target annotation and the message by determining according to the input sharing condition (step 240). Also in the present embodiment, as in the first embodiment, the action item is referred to by referring to the update date and time that are the annotation and message corresponding to the identified action item and set in the annotation information and the message information, respectively. The sharing condition “information updated after the previous synchronization time set in the information” is set and registered in the system in advance, and the shared information determination unit 29 reads the sharing condition from the system, and this condition Extract annotations and messages that match In this example, as shown in FIG. 10, message IDs “4”, “3”, “2”, “21” correspond to the action item with the action item ID “2” whose status has been changed. Among them, only the message information of the message ID “21” whose update date is “2006/2/10” is updated after the previous synchronization time “2006/2/1”. is there.

  As described above, when the shared information determination unit 29 specifies a message to be copied from the annotations and messages of the selection candidates, the shared information creation unit 30 copies various pieces of information to the task 2 so that various tasks in the task 2 can be performed. Information is created (step 250). At this time, as described in the first embodiment, since unique identification information is assigned to each task and the information is managed separately, the message information created in task 2 by copying is uniquely A message ID is assigned. Also, the task member name is replaced with the task name according to the access right. The message information of task 2 created by copying the message information of task 1 is shown in FIG. Furthermore, the shared information creation unit 30 changes the status included in the action item information of the corresponding task 2 to “finished” as the action item of the task 1 is updated, and both tasks become action item information. The previous synchronization time included is updated with the current time when the update process is completed. The updated action item information is shown in FIG.

  When the generation and update of information are completed as described above, the information management units 22 to 25 update the databases 31 to 34 with the corresponding information shown in FIG. 11 (step 260). In the present embodiment, the action item information and message information are updated. FIG. 12 shows an example of setting contents of various information after the related information is updated and copied as information related to the electronic document (in this example, action item information) is changed as described above.

  According to the present embodiment, when an action item is shared by a plurality of tasks and information on the shared action item is updated in any task, the information on the shared action item of the other task is also synchronized. Can be updated. In addition, a part that has been changed since the previous synchronization can be updated for information related to the action item. Thereby, information can be shared between tasks.

Embodiment 3 FIG.
As described in the first and second embodiments, information that is to be kept confidential in task 1 among information related to the electronic document is not shared and information is shared with other tasks 2 without being disclosed. Can be planned. The reverse is also true. However, the user who belongs to both task 1 and task 2 is originally in a position to be able to refer to the confidential information of both tasks, but if the electronic document is accessed as a member of task 1, the confidential information of task 2 cannot be referred to. Accessing the electronic document as a member of task 2 is inconvenient because the secret information of task 1 cannot be referred to. Therefore, in the present embodiment, various types of information are set so that information that can be referred to by the user according to the setting of the access right of each user can refer to both information regardless of which task member the electronic document is to be reviewed. Was created. Hereinafter, the operation in the present embodiment will be described with reference to the flowchart shown in FIG. 13 and examples of setting contents of various information set and registered in the databases 31 to 35 shown in FIGS. First, as illustrated in FIG. 14, Mr. C is a member of both tasks 1 and 2 and has the authority to refer to all information related to task 1 as a member of task 1. In the various information of task 2, information that task 1 keeps confidential as shown to the person in charge or the writer is stored as it is.

  Here, it is assumed that any member of task 2 logs in. At this time, the share management unit 21 acquires information related to the logged-in user and information related to the task 2 (step 310). Subsequently, the sharing management unit 21 determines whether or not an action item ID is set in the shared action item ID of the action item information from the information related to the acquired task 2, and if it is set, An action item ID is acquired (step 320). According to the example shown in FIG. 14, the shared action item IDs “2” and “3” can be acquired. The task 1 having the action item information is specified from the shared action item IDs “2” and “3” (step 330), and the setting contents of the login user access right in the task 1 are confirmed (step 340).

  When the logged-in user is Mr. C, Mr. C has the access right to refer to all information related to task 1 (Y in step 350), so the information set in task 2 as shown in FIG. Is displayed as it is, it is possible to refer to the contents of the information set in the task 1 (step 380). On the other hand, if the logged-in user is not Mr. C (Ms. D in this example), Mr. D is not a member of Task 1 and does not have the access right to refer to all information related to Task 1 (N in Step 350). ) And a message and annotation corresponding to the shared action item are identified (step 360). Then, the shared information creation unit 30 replaces the information corresponding to the secret information of the task 1, specifically, the writer information included in the message information with the message IDs “13” to “17” with “T1 task”. Thus, the display information for Mr. D is created (step 370), and the user interface unit 27 displays the display information on the screen (step 380).

  According to this embodiment, when an action item is shared by a plurality of tasks as described above, the information copied from other tasks is determined according to the access right of the user's copy source or copy destination task. The contents to be displayed can be changed every time.

  In this embodiment, information that the task 1 side wants to conceal is set in advance on the task 2 side, and the user who refers to the display information when displaying the information does not have a reference access right. On the other hand, when the user has the reference access right without setting the information that the task 1 side wants to conceal on the task 2 side, various information from other tasks is displayed. Display information may be created and displayed after obtaining. In this embodiment, in the case of a user who has both access rights, information with superior access rights is selected and displayed. However, the information may be merged and displayed. Good.

Embodiment 4 FIG.
In the present embodiment, when a new action item is added on the task 2 side, the action item is copied to the task 1 for sharing. Hereinafter, the operation in the present embodiment will be described with reference to the flowchart shown in FIG. 17 and examples of setting contents of various information set and registered in the databases 31 to 35 shown in FIGS. In the present embodiment, a case where an action item with an action item ID “13” is added to task 2 will be described as an example. FIG. 18 shows a state before the action item with the action item ID “13” is shared.

  When it is detected that any action item information has been added to the action item database 34, the sharing management unit 21 acquires information on the added action item from the action item management unit 25 (step 410). Here, the action item ID “13” and the task 2 “T2” as the addition destination are acquired from the action item information. Furthermore, the share management unit 21 acquires the document ID “0002” of the electronic document corresponding to the action item information and the shared document ID “0001” corresponding thereto from the document management unit 22 (step 420).

  The processing performed after this is basically the same as the processing (steps 140 to 160) in the first embodiment. That is, when the action item to be processed is specified, the shared information determination unit 29 specifies the copy target annotation and message by determining according to the input sharing condition (step 440). In the present embodiment, as in the first embodiment, the sharing condition “annotation and message corresponding to the identified action item” is set and registered in the system in advance, and the shared information determination unit 29 The annotation is read from the system, and annotations and messages that match this condition are extracted. In this example, as shown in FIG. 19, the action item with the added action item ID “13” corresponds to the message information with the message ID “18” and the annotation ID corresponding to this message information. The annotation information is “13”.

  When the shared information determination unit 29 specifies the annotation and message to be copied as described above, the shared information creation unit 30 creates various information in the task 1 by copying these information to the task 1 (step 450). ). At this time, as described in the first embodiment, since unique identification information is assigned to each task and the information is managed separately, the message information created in task 1 by copying is uniquely A message ID is assigned. Also, the task member name is replaced with the task name according to the access right. Furthermore, the action item ID “13” of the corresponding task 2 is set in the shared action item ID included in the action item information, and the current time set and registered as the previous simultaneous time is set. The contents of various information at this time are shown in FIG. Further, as the action item of task 1 is updated, the shared information creation unit 30 includes the action item ID “20 of the corresponding task 1 as the shared action item ID included in the action item information of the corresponding task 2. "Is set, and the current time set and registered as the previous simultaneous time is set. Basically, it becomes the same value as task 1. Various information of the task 2 after the update is shown in FIG.

  When the generation and update of information are completed as described above, the information management units 22 to 25 update the databases 31 to 34 with the corresponding information shown in FIG. 21 (step 460).

  According to this embodiment, even when an action item is added to any task after sharing an electronic document, information related to the action item is shared by copying the corresponding information to another task. be able to.

Embodiment 5 FIG.
In this embodiment, even if an electronic document is not shared, action items for the electronic document can be shared. Therefore, while the second to fourth embodiments are processes related to information change after sharing of the electronic document and information related to the electronic document described in the first embodiment, the present embodiment is This is processing performed in a state before sharing an electronic document as in the first mode.

  FIG. 23 shows the state of each task T1, T2 in which the same information as in FIG. 5 is set. However, it is different in that the person in charge of the action item whose action item ID is “3” is unknown, and in this embodiment, an action item whose person in charge is not determined in task 1 is The task 2 that is not sharing the electronic document (functional specification) is to be taken over. Hereinafter, the operation in the present embodiment will be described with reference to the flowchart shown in FIG. 22 and examples of setting contents of various information set and registered in the databases 31 to 35 shown in FIGS.

  First, an action item (in this example, an action item ID “3”) that can be taken over by any member belonging to the task 1 from the user interface unit 27, and a takeover destination task (“task 2” in this example) Is input and designated, the share management unit 21 obtains the information by receiving the information (step 510). That is, the copy destination and the action item to be copied are specified. The subsequent processing is basically the same as the processing in steps 140 to 160 in the first embodiment. That is, the shared information determination unit 29 specifies the annotation and message to be copied by determining according to the input sharing condition (step 540). In this embodiment, the sharing condition “annotation and message corresponding to the specified action item” is set and registered in the system in advance, and the shared information determination unit 29 reads the sharing condition from the system. Then, annotations and messages that match this condition are extracted. In this example, message information “5” included in the action item information with the action item ID “3” and message information “6” corresponding to a child of this message can be specified. Then, when the shared information determination unit 29 refers to the cooperation annotation ID of the message information with the message IDs “5” and “6”, since the cooperation annotation ID “3” is set, the action with the action item ID “3” An annotation having a linkage annotation ID “3” is extracted as an annotation corresponding to the item.

  FIG. 24 shows various types of information identified as copy targets by the above processing, but the shared information creation unit 30 creates various types of information in task 2 by copying these pieces of information to task 2 (step 550). However, as described above, various IDs are uniquely assigned. In this embodiment, since the personal information related to the task 1 member is set to be kept secret, the shared information creation unit 30 uses a replacement prepared in advance to keep the task 1 member secret. Information, that is, the person in charge included in the action item information and the writer included in the message information are changed to the task name “T1 task”. In this embodiment, since the electronic document is not shared, a shared document ID is not set for each document related information. However, only a part of the electronic document text corresponding to the action item and the additional position is copied.

  Furthermore, when the shared information creation unit 30 sets various IDs in the task 2, the shared action item ID “12” included in the action item information of the action item ID “3” is added to the action item ID “12”. By setting, the action items shared by task 1 and task 2 are associated.

  When the generation and update of information are completed as described above, the information management units 22 to 25 update the databases 31 to 34 with the corresponding information shown in FIGS. 24 and 25 (step 560). FIG. 26 shows an example of setting contents of various information after the electronic document and various information related to the electronic document are copied as described above.

  According to the present embodiment, since the information related to the action item with ID “3” of the action item in task 1 is copied to the task 2 as the takeover destination, the action item in task 1 is copied to the other task. Can be taken over. In the present embodiment, the electronic document itself is not duplicated, but at least a part to which the inherited action item (annotation corresponding to it) is not displayed can be associated with the electronic document and the action item. Becomes unknown. Therefore, as illustrated in FIG. 26, at least a portion of the electronic document to which the action item is added is copied to task 2 so that it can be displayed. In the present embodiment, the task 2 has one paragraph of the electronic document corresponding to the position information of the annotation corresponding to the action item.

  Since the person in charge is unknown in the above processing, the present embodiment has been described as the case where the action item with the person in charge unknown is handed over to another task. However, although it differs depending on whether or not the person in charge is set, it is basically the same as the process in the fourth embodiment in which the action item of task 2 for which the person in charge is set is shared with task 1, and this embodiment Even in the form, it can be said that the action item is shared between tasks.

1 is an overall configuration diagram of a document information processing system in Embodiment 1. FIG. 2 is a hardware configuration diagram of a document management server according to Embodiment 1. FIG. 2 is a block configuration diagram of a document management server in Embodiment 1. FIG. 4 is a flowchart illustrating information sharing processing when an electronic document is copied to another task in the first embodiment. 6 is a diagram illustrating an example of setting contents of various types of information before execution of processing set in correspondence with each task in Embodiment 1. FIG. 6 is a diagram illustrating an example of setting contents of various information updated during processing in Embodiment 1. FIG. 6 is a diagram illustrating an example of setting contents of various information updated during processing in Embodiment 1. FIG. 6 is a diagram showing an example of setting contents of various information set in correspondence with each task after execution of processing in Embodiment 1. FIG. 10 is a flowchart showing a process for changing information set in a task in the second embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various types of information before execution of processing set corresponding to each task in the second embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various information updated during processing in the second embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various types of information set corresponding to each task after execution of processing in the second embodiment. 14 is a flowchart illustrating a process for disclosing information set in a task in the third embodiment. FIG. 10 is a diagram illustrating a setting content example of various types of information before execution of processing set in association with each task in the third embodiment. FIG. 10 is a diagram showing an example of setting contents of various information in a screen display table for task members having access authority in the third embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various types of information in a screen display table for task members who do not have access authority in the third embodiment. 14 is a flowchart illustrating processing for adding information related to an electronic document in the fourth embodiment. FIG. 16 is a diagram illustrating an example of setting contents of various types of information before execution of processing set corresponding to each task in the fourth embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various information updated during processing in the fourth embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various information updated during processing in the fourth embodiment. FIG. 10 is a diagram illustrating an example of setting contents of various types of information set in correspondence with each task after execution of processing in the fourth embodiment. 10 is a flowchart showing action item takeover processing in the fifth embodiment. FIG. 20 is a diagram illustrating an example of setting contents of various types of information before execution of processing set corresponding to each task in the fifth embodiment. FIG. 20 is a diagram illustrating an example of setting contents of various information updated during processing in the fifth embodiment. FIG. 20 is a diagram illustrating an example of setting contents of various information updated during processing in the fifth embodiment. FIG. 16 is a diagram illustrating an example of setting contents of various types of information set in correspondence with each task after execution of processing in the fifth embodiment.

Explanation of symbols

  1 CPU, 2 ROM, 3 RAM, 4 hard disk drive (HDD), 5 HDD controller, 6 mouse, 7 keyboard, 8 display, 9 I / O controller, 10 internal bus, 12 client, 14 network, 20 document management server, 21 Shared management unit, 22 Document management unit, 23 Annotation management unit, 24 Message management unit, 25 Action item management unit, 26 Task management unit, 27 User interface (UI) unit, 28 Shared action item determination unit, 29 Shared information determination unit 30 shared information creation unit, 31 document database, 32 annotation database, 33 message database, 34 action item database, 35 task database.

Claims (8)

First document related information storage means for storing first document related information as information related to a first electronic document shared by users belonging to the first group;
First implementation item information including first implementation item identification information and related information of the implementation item, which is set corresponding to each of the implementation items whose progress of the first electronic document is to be managed by the user belonging to the first group First implementation item information storage means for storing
First message information storage means for storing first message information relating to messages relating to each of the implementation items whose users should belong to the first electronic document and whose progress should be managed with respect to the first electronic document;
Second document related information storage for storing second document related information as information related to a second electronic document generated by duplicating the first electronic document for sharing with users belonging to the second group Means,
Second implementation item information that is set corresponding to each of the implementation items whose progress should be managed with respect to the second electronic document by a user belonging to the second group, and includes second implementation item identification information and related information of the implementation item Second implementation item information storage means for storing
Second message information storage means for storing second message information relating to a message associated with each of the implementation matters for which a user belonging to the second group should manage progress with respect to the second electronic document;
When the second electronic document is generated by duplicating the first electronic document, the document is set by associating the identification information of the first and second electronic documents with the first and second document related information, respectively. Related information sharing means,
An implementation item identification unit that identifies an implementation item shared with the second group from the implementation items managed by the first implementation item information storage unit;
Second implementation information is generated by referring to the first implementation information corresponding to the implementation item identified by the implementation item identification means in accordance with the sharing condition in which the information not to be disclosed is set, and the second implementation Execution item information sharing means for storing in the item information storage means and setting the first and second implementation item identification information in correspondence with each of the first and second implementation item information;
Second message information is stored by generating second message information by referring to the first message information related to the implementation item specified by the implementation item specifying unit according to the sharing condition in which the information not to be disclosed is set Message information sharing means stored in the means;
An information sharing apparatus comprising: Computer
First document related information storage means for storing first document related information as information related to a first electronic document shared by users belonging to the first group;
First implementation item information including first implementation item identification information and related information of the implementation item, which is set corresponding to each of the implementation items whose progress of the first electronic document is to be managed by the user belonging to the first group First implementation information storage means for storing
First message information storage means for storing first message information relating to a message associated with each of the implementation items for which a user belonging to the first group should manage progress with respect to the first electronic document;
Second document related information storage for storing second document related information as information related to a second electronic document generated by duplicating the first electronic document for sharing with users belonging to the second group means,
Second implementation item information that is set corresponding to each of the implementation items whose progress should be managed with respect to the second electronic document by a user belonging to the second group, and includes second implementation item identification information and related information of the implementation item Second implementation item information storage means for storing
Second message information storage means for storing second message information relating to a message associated with each of the implementation items for which a user belonging to the second group should manage the progress of the second electronic document;
When the second electronic document is generated by duplicating the first electronic document, the document is set by associating the identification information of the first and second electronic documents with the first and second document related information, respectively. Related information sharing means,
An action item specifying means for specifying an action item shared with the second group from the action items managed by the first action item information storage means;
Second implementation information is generated by referring to the first implementation item information corresponding to the implementation item identified by the implementation item identification unit according to the sharing condition in which the information not to be disclosed is set. Execution item information sharing means for storing in the item information storage unit and setting the first and second implementation item identification information in association with each of the first and second implementation item information,
The second message information is stored by generating the second message information by referring to the first message information related to the implementation item specified by the implementation item specifying unit according to the sharing condition in which the information not to be disclosed is set. Message information sharing means stored in the means;
Information sharing program to function as The information sharing program according to claim 2,
The implementation item identification unit is an information sharing program that identifies an implementation item for which first implementation item information matching the input sharing condition is set as an implementation item to be shared with the second group. In the information sharing program according to claim 3,
An information sharing program in which each of the first and second implementation item information includes at least one item information of user identification information, implementation deadline information, or implementation state information of the implementation item. The information sharing program according to claim 2,
The implementation item information sharing means and the message information sharing means are each an information sharing program for generating each information according to a sharing condition of following access authority information set for each group or group member. The information sharing program according to claim 5,
When each information sharing means detects that the second group does not have access authority to the information of the corresponding first group when storing the information for the second group, An information sharing program for setting information of the first group by replacing it with information that can be disclosed. The information sharing program according to claim 2,
In the first and second implementation information, the date and time information when the information was updated in synchronization with the previous time is set,
In the first and second message information, date information when updated is set,
When the information sharing means detects that the implementation item information has been updated in one of the first group and the second group, the information sharing unit updates the corresponding information on the other side according to the update content. Program. 3. The information sharing program according to claim 2, further comprising:
When the users belonging to both the first and second groups access the shared electronic document, display information for creating display information referred to by the user in accordance with the access right set for the user in each group An information sharing program that functions as a creation means.

Images