JP2016051324A - Conference information management system and control method and program for the same - Google Patents

Abstract

PROBLEM TO BE SOLVED: To carry out state management and visualization easily recognized by a user by hierarchic structuring of tasks in total project from task management information across conferences.SOLUTION: A conference information management system includes: means for storing conference information and information of tasks occurring during a conference associated to a storage unit; means for carrying out hierarchic structuring associating tasks occurring in different conferences from the tasks store to a storage unit based on an instruction by a user; means for accepting selection of the task from among the tasks stored in the storage unit; means for identifying the task associated to the selected task based on the association among the tasks and determining the parent a parent-child relationship between the conferences to which respective identified tasks belong; and means for providing a display screen for displaying association between the determined parent-child relationship in conferences and the information of the task in which delay occurs in its progress among the tasks belonging to respective conferences.SELECTED DRAWING: Figure 12

Description

  The present invention relates to a conference information management system, a control method therefor, and a program, and more particularly to a technique for managing and visualizing the state of a hierarchically structured task related to a conference.

  A conventional conference information management system includes a system that associates a plurality of conferences and performs status management of required items called tasks that are discussed and determined in the conference (for example, see Patent Document 1). Patent Document 1 has means for defining task states and means for associating tasks between different conferences, and task state management can be performed from any of a plurality of conferences. In other words, task status can be managed across meetings. In addition, in a system that manages tasks for each group, a system that counts and presents task states for each group is known in order to grasp the progress of each group (see, for example, Patent Document 2).

JP 2011-28443 A JP 2005-258772 A

  In general, in order to make task management of a project composed of a large number of tasks more efficient, tasks may be hierarchically structured and a plurality of task states may be managed. Hierarchical structure of tasks means that a plurality of hierarchies are provided according to the granularity of tasks and each task is arranged in a hierarchy suitable for the granularity. This makes it possible to improve the efficiency of task management even when a large number of tasks are included, such as making it easy to grasp the overall picture of a project by referring to only tasks in a coarse-grained hierarchy.

  Also, it is generally known to use a conference as a means of task management within a certain scale. In a project composed of many tasks, task management of the entire project is performed by integrating task management of a plurality of meetings having different purposes and attendees.

  Based on the above, it is important to combine the task management information held in each single meeting and make the tasks hierarchically structured throughout the project. In other words, it is important to hierarchically structure the tasks of the entire project from task management information across meetings and to manage the state. However, in Patent Document 1, task status management is possible when a task does not cross a conference, but it is not possible to perform status management by hierarchically structuring tasks of the entire project from task management information across conferences. Further, Patent Document 2 does not show a method for counting and visualizing the task state in association with the group state, which may cause inconvenience. For example, when the progress method of a specific meeting is not appropriate, it is assumed that the progress of many tasks belonging to this meeting is delayed. In Patent Document 2, it is possible to grasp such a state in association with the task state. Can not.

  In order to solve the above problems, the present invention has the following configuration. That is, in the conference information management system, the conference information and the task information generated in the conference are associated with each other and stored in the storage unit, and stored in the storage unit based on a user instruction. An association means for associating tasks that occurred at different meetings among the tasks, and a hierarchical structure, a selection means for accepting a task selection from the tasks stored in the storage unit, and an association between the tasks Based on the above, a task associated with the task selected by the selection unit is specified, and a determination unit that determines a parent-child relationship between conferences to which each of the specified tasks belongs, and the determination unit determines Providing a display screen that displays the relationship between the parent-child relationship between meetings and information on tasks that are delayed in progress among tasks belonging to each meeting And a stage.

  According to the present invention, the tasks of the entire project are hierarchically structured from the task management information across the meetings, and the state is managed, and visualization that is easy for the user to recognize is possible.

The figure which shows the example of whole structure of the meeting information management system which concerns on this invention. The figure which shows the structural example of the client terminal which concerns on this invention. The figure which shows the structural example of meeting information management DB which concerns on this invention. The figure which shows the structural example of each DB contained in the meeting information management DB which concerns on this invention. The figure which shows an example of the screen displayed when creating a new meeting. The figure which shows an example of the screen displayed when browsing meeting information. The flowchart of the process which sets the parent task with respect to a certain task. The figure which shows an example of the display screen at the time of setting a parent task. The figure which shows an example of the screen for displaying a task state. The flowchart which shows the process which concerns on this invention. The figure which shows the example of the data in the case of the process of FIG. The figure which shows the example of a display of the display screen which concerns on 1st embodiment. The figure which shows the example of the data in the case of the process of FIG. 10 which concerns on 2nd embodiment. The figure which shows the example of a display of the display screen which concerns on 2nd embodiment. The figure which shows the example of a display of the display screen which concerns on 3rd embodiment. The figure which shows the example of a display of the display screen which concerns on 3rd embodiment.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

<First embodiment>
FIG. 1 is a diagram showing an example of the overall configuration of a conference information management system 100 according to the present invention. Client terminals 101 and 102 and a conference information management server 103 are connected to the conference information management system 100 via a network 104. In FIG. 1, two client terminals are shown, but the present invention is not limited to this, and more client terminals may be connected. In addition, although one conference information management server 103 is shown, a configuration may be used in which a plurality of information processing apparatuses physically distribute the processing of the conference information management server 103 to provide a service.

  FIG. 2 is a diagram illustrating an example of the overall configuration of the client terminal 101. A network I / F unit 201 is connected to the network 104 and inputs / outputs information to / from the conference information management server 103. The display unit 202 includes display means such as a liquid crystal display and display control means for controlling the display means, and displays the image data generated by the control unit 205. The storage unit 203 is a large-capacity storage device such as an HDD (Hard Disk Drive), and stores an OS (Operating System) that operates the client terminal 101, an application that displays information of the conference information management server 103, and the like. The operation input unit 204 includes an input unit that receives an operation from a user, such as a mouse, a keyboard, or a touch panel, and an operation control unit that sends the input operation to the control unit 205. The control unit 205 includes a CPU (Central Processing Unit) and a RAM (Randan Access Memory) that is a volatile storage unit, and controls the client terminal 101. Further, the CPU according to the present embodiment implements the processing according to the present embodiment by developing a program such as an OS or an application stored in the storage unit 203 in the RAM and executing the program.

  It is assumed that the entire configuration of the client terminal 102 and the conference information management server 103 is the same as that in FIG. Although not shown, the conference information management server 103 includes a network I / F unit 211, a display unit 212, a storage unit 213, an operation input unit 214, and a control unit 215. Furthermore, the storage unit 213 of the conference information management server 103 stores a conference information management DB 301 and a conference information management application that performs processing according to the present embodiment.

Database configuration
FIG. 3 is a diagram illustrating a configuration example of the conference information management DB 301 held by the conference information management server 103. The meeting information management DB 301 includes a meeting DB 310, a meeting content DB 311, a task DB 312, an agenda DB 313, an organization information DB 314, and an employee information DB 315. In the following IDs (identification information), when the same object is indicated, a common value is used for cooperation between the DBs.

  FIG. 4A is a diagram illustrating a configuration example of data stored in the conference DB 310. The conference DB 310 is a database that stores information related to conferences managed by the conference information management server 103. The conference DB 310 includes a conference ID for uniquely identifying the conference, a conference name, a leader employee ID, a member employee ID, and a conference content ID. A member employee ID and a meeting content ID may store a plurality of values.

  FIG. 4B is a diagram illustrating a configuration example of data stored in the conference content DB 311. The conference content DB 311 is a database that stores information related to conference content managed by the conference information management server 103. The conference content DB 311 includes a conference content ID for uniquely identifying the conference content, a participating employee ID, a holding date, a holding place, an agenda content, a generated task ID, and an agenda ID. A plurality of values may be stored for the participating employee ID, the generated task ID, and the agenda ID. By holding the generated task ID in the conference content DB 311, it becomes possible to manage the state of the task held in the conference DB 310.

  The relationship between the conference DB 310 and the conference content DB 311 will be briefly described. The conference DB 310 is created only once when a new conference is started. The conference DB 310 has attributes such as a conference leader and constituent members. On the other hand, the conference content DB 311 is created every time a conference is actually held after the conference DB 310 is created. The conference DB 310 has the same number of conference content DBs 311 as the number actually held. Therefore, the relationship between the conference DB 310 and the conference content DB 311 is 1: 1 or 1: multiple.

  FIG. 4C is a diagram illustrating a configuration example of data stored in the task DB 312. The task DB 312 is a database that stores information related to tasks managed by the conference information management server 103. The task DB 312 includes a task ID for uniquely identifying a task, a staff employee ID, contents, a progress rate, a work start date, a work completion date, a child task ID, a dependency source task ID, and a dependency destination task ID. It is. A plurality of values may be stored in the person-in-charge employee ID, child task ID, dependency source task ID, and dependency destination task ID.

  A child task is a task that belongs to a layer one layer below the target task when a plurality of tasks form a hierarchical structure. Furthermore, the task below is also called a grandchild task. In addition, a task belonging to a hierarchy one level higher than the target task is defined as a parent task. The dependency source task refers to a task that must be executed before the target task is executed. The dependency destination task refers to a task that can be executed only after the target task is executed. Therefore, in the present embodiment, description will be made using the parent-child relationship and the dependency relationship between tasks in the hierarchical structure. A parent-child relationship may be established between meetings.

  FIG. 4D is a diagram illustrating a configuration example of data stored in the agenda DB 313. The agenda DB 313 is a database that stores information related to the agenda of the conference managed by the conference information management server 103. The agenda DB 313 stores an agenda ID, a title, a presenter employee ID, a material URL, a start date / time, and an end date / time for uniquely identifying the agenda. A plurality of values may be stored for the presenter employee ID and the material URL.

  FIG. 4E is a diagram illustrating a configuration example of data stored in the organization information DB 314. The organization information DB 314 is a database that stores information related to the organization managed by the conference information management server 103. The organization information DB 314 stores an organization ID for uniquely identifying the organization information, a name, a child organization ID, a leader employee ID, a member employee ID, and a work in charge. A plurality of values may be stored for the child organization ID and member employee ID. The child organization refers to an organization located under the target organization. That is, a parent-child relationship is established between organizations.

  FIG. 4F is a diagram illustrating a configuration example of data stored in the employee information DB 315. The employee information DB 315 is a database that stores information about employees managed by the conference information management server 103. The employee information DB 315 stores an employee ID, name, title, and organization ID for uniquely identifying employee information.

[interface]
FIG. 5 is a diagram illustrating an example of a screen displayed on the display unit 202 when a new conference is created in the conference DB 310 by an application executed by the control unit 205 of the client terminal 101. The user performs input to the system using a GUI (Graphical User Interface) operation. The application to be executed performs processing in cooperation with the conference information management server 103, and the execution form thereof is not limited, such as a WEB browser or a desktop application. The new conference creation screen 501 displays a conference ID 502, a conference name 503, a leader employee ID 504, and a member employee ID 505, which are information constituting the conference DB 310. In the conference ID display area 506, the conference ID determined by the conference information management server 103 is displayed. Of course, the user may input an arbitrary meeting ID.

  The new meeting creation screen 501 includes a meeting name input area 507, a leader employee ID input area 508, and a member employee ID input area 509. The user inputs information to these input areas using the operation input unit 204. In the new meeting creation screen 501 shown in FIG. 5, “*” is displayed for items that require input. Furthermore, the new conference creation screen 501 includes a new conference creation button 510. When the user presses a new conference creation button 510, information necessary for creating a conference input by the user is transmitted to the conference information management server 103, and a new conference is created and registered.

  FIG. 6 shows an example of a screen displayed on the display unit 202 when browsing the details of the conference content stored in the conference content DB 311 by an application executed by the control unit 205 of the client terminal 101. On the conference content browsing screen 601, information constituting the conference content DB 311 is displayed. The displayed contents are a meeting title 602 (meeting ID and meeting name), holding information 603 (meeting contents ID, holding date / time, holding place, leader name, and participating employee name), agenda information 604, agenda contents 605, and tasks. Information 606 is included. In the meeting content browsing screen 601, the file path in which the minutes file is stored is described as the meeting contents 605, but it may be a URL or text information where the minutes file is stored.

  The task information 606 displays information on each task that occurred in the meeting held on the date and time specified by the meeting content ID. For example, a task ID 607, a responsible employee name 608, a task content 609, a work start date 610, a work completion date 611, a parent task ID 612, a child task ID 613, a dependence source task ID 614, and a dependence destination task ID 615 are included. A parent task ID pull-down button 616 displayed adjacent to the parent task ID 612 is used when the parent task ID 612 is selected.

[Processing flow]
(Association process)
FIG. 7 is a flowchart showing processing for setting a parent task for a certain task in the conference content browsing screen 601. S701 to S711 in this flowchart are executed by the control unit 205 of the client terminal 101. S712 to S716 are executed by the control unit 215 of the conference information management server 103. Regardless of the configuration of FIG. 7, for example, the flow of S712 to S716 may be centrally controlled on the client terminal 101 side. Alternatively, the input from the operation input unit 204 of the client terminal 101 may be transmitted to the conference information management server 103 via the network 104 and centrally controlled on the conference information management server 103 side.

  In step S <b> 701, the client terminal 101 receives a user operation input from the user via the operation input unit 204.

  In step S <b> 702, the client terminal 101 determines whether the received user operation is a pressing operation of the parent task ID pull-down button 616. When the operation is a pressing operation of the parent task ID pull-down button 616 (YES in S702), in S703, the client terminal 101 sets the value of the task ID 607 in the same row as the selected parent task ID pull-down button 616 to the conference information management. Transmit to the server 103. On the other hand, if it is not a pressing operation of the parent task ID pull-down button 616 (NO in S702), the client terminal 101 performs processing corresponding to the user operation in S711. Since the process according to the user operation here is not particularly limited, the description is omitted. Then, this processing flow ends.

  In step S712, the conference information management server 103 waits for a request from the client terminal 101. When the request is received together with the task ID from the client terminal 101, the result of completion of reception of the task ID is returned to the client terminal 101 in step S713. To do. The task ID received in S713 is stored in the storage unit of the conference information management server 103, and is used as appropriate in the flowchart of FIG.

  In step S <b> 704, the client terminal 101 displays a parent task search screen on the display unit 202 after receiving the task ID reception completion from the conference information management server 103. FIG. 8A is an example of a search screen displayed on the display unit 202. The related conference ID input area 801 is an area for allowing the user to input the related conference ID using an input unit such as a keyboard. A search button 802 is a button for instructing start of search when pressed by the user. In FIG. 8A, the related conference ID input area 801 and the search button 802 are displayed in the vicinity of the parent task ID pull-down button 616, but this is not restrictive. When the user inputs a conference ID in the related conference ID input area 801 and presses the search button 802, the control unit 205 accepts the input in S705. Further, the client terminal 101 transmits a conference ID search instruction input to the conference information management server 103.

  In step S <b> 714, upon receiving a search instruction from the client terminal 101, the conference information management server 103 searches the conference information management DB 301 for task information included in the conference content ID associated with the received conference ID. Then, the conference information management server 103 returns task information that matches the search to the client terminal 101. At this time, the task information returned by the conference information management server 103 may be handled and arranged as an array and returned to the client terminal 101, or the searched task information may be sequentially transmitted in units that can be transmitted. This may be switched according to the environment, since an appropriate implementation method differs depending on the network operating environment.

  In step S <b> 706, the client terminal 101 determines whether task information is included in the response from the conference information management server 103. If the task information is included (YES in S706), the client terminal 101 displays a response task list on the display unit 202 in S707. FIG. 8B is an example of a response task list display screen displayed on the display unit 202. The response task list display area 803 displays task information returned from the conference information management server 103 in a list format. In this embodiment, the contents of the task DB 312 and information on the person in charge are displayed as task information, but this is not restrictive. A task selection area 804 is a button indicating that a task has been selected by being pressed by the user. In this embodiment, the task selection area 804 is displayed as a radio button that switches to an image indicating that the task selection area 804 has been selected. However, buttons having other configurations may be used.

  On the other hand, if no task information is returned or the task information is not included in the search result received from the conference information management server 103 (NO in S706), the control unit 205 displays the task in S710. Absent. Or you may display that a task does not exist. Then, this processing flow ends.

  In step S <b> 708, when the client terminal 101 receives an input operation for selecting a task to be a parent task from the displayed tasks, the client terminal 101 transmits the task ID of the selected task to the conference information management server 103.

  In S715, when the conference information management server 103 receives the task ID of the task that becomes the parent task from the client terminal 101, the conference ID management server 103 inserts the task ID as the parent task of the task ID received in S713. That is, a new value is inserted into the child task ID of the corresponding task included in the task DB 312.

  In S716, the conference information management server 103 stores the dependency relationship in various DBs and updates the DB information. Thereafter, the conference information management server 103 transmits the updated DB information to the client terminal 101 together with the update completion.

  In S709, when the client terminal 101 receives the updated DB information, the client terminal 101 explicitly displays the parent task of the task selected in S703 in the parent task ID 612. In this embodiment, since the task ID “0001” is selected as the parent task, the task ID “0001” is displayed in the parent task ID 612 after the selection.

  A method for visualizing tasks across conferences structured according to the above procedure will be described using a Gantt chart generally used in task state management. FIG. 9 is a diagram illustrating a configuration example of a task status display screen 901 that the conference information management server 103 provides to the user through the display unit 202 of the client terminal 101 in the present embodiment. In FIG. 9, arrows indicate dependency relationships between tasks. On the task status display screen 901, the hierarchical structure of tasks across meetings can be defined, and the status of tasks having a hierarchical structure can be managed. Specifically, for example, the user can recognize that the tasks with task IDs “0004”, “0005”, and “0006” are child tasks of the task with task ID “0001”, and visualize the hierarchical structure of tasks across conferences. It becomes possible to do. That is, even when the conference to which the task belongs is different, the relationship between the tasks is shown.

(Display processing)
On the other hand, on the task state display screen 901 shown in FIG. 9, the user can grasp the state of each task and the relation between tasks, but cannot grasp the relation between the task and the meeting. For example, if there is a problem with the progress method of a specific conference, it is considered that many tasks belonging to this conference are delayed, but the task status display screen 901 shown in FIG. It cannot be grasped with.

  In order to deal with such a problem, in the present embodiment, a relationship between conferences is calculated and visualized from a specific task and related tasks. Then, it is provided to the user in association with the association between the meetings and the state of the task. Hereinafter, a method for generating a display screen (hereinafter referred to as a conference-task display screen) in which associations between conferences and task states are linked will be described.

  FIG. 10 is a flowchart showing a process for displaying the conference-task display screen according to the present embodiment. This flowchart is executed by the control unit 215 of the conference information management server 103.

  In step S <b> 1001, the conference information management server 103 prompts the user to specify a task that is a starting point of a task group to be displayed on the conference-task display screen through the display unit 202 of the client terminal 101, and accepts the task specification. Here, the task designated by the user is one of the tasks stored in the task DB 312. In the following description, it is assumed that the user has designated the task with the task ID “0001” shown in FIG.

  In S1002, the conference information management server 103 extracts tasks related to the designated task. Specifically, the conference information management server 103 extracts the task having the task specified in S1001 as a parent, repeats the process of extracting the task having the task as a parent, and performs the process until no task is extracted. Do. By this processing, subordinate tasks such as child tasks and grandchild tasks of the task specified in S1001 (that is, tasks positioned at lower positions in the hierarchical structure) are acquired recursively. The acquired information is stored in the storage unit in a form in which each task and a child task of each task are associated with each other. FIG. 11A illustrates an example of task information acquired in step S1002 in a table format. In each column of the table, each task in FIG. 4A and a task ID of a child task associated with each task are stored.

  In S1003, the conference information management server 103 specifies the conference to which the task and the child task belong using the conference DB 310 and the conference content DB 311 for each task extracted in S1002. FIG. 11B is a diagram in which an example of information on a conference to which each task extracted by the conference information management server 103 in S1003 and its child task belongs is expressed in a table format. In each column of the table, a conference to which each task in FIG. 11A and its child tasks belong is stored.

  In S1004, the conference information management server 103 counts the information specified in S1003 by the conference name. That is, in FIG. 11B, the number of rows having the same parent conference ID and child conference ID is counted. FIG. 11C is a diagram in which information after the processing of S1004 is expressed in a table format. FIG. 11C counts the number of each row having the same parent conference ID and child conference ID in FIG. 11B as the number of nodes. By performing such processing, it is possible to derive the conference relationship corresponding to the task relationship for the task specified in S1001 and its descendant tasks.

  In S1005, the conference information management server 103 generates data to be displayed on the client terminal 101 based on the information related to the conference derived in S1004. In the processing of S1005, the conference information management server 103 counts the number of tasks that are delayed in the conference for each conference stored in S1004. In this embodiment, whether or not there is a delay in the progress of the task is derived from the relationship between the work start date, the work completion date and the progress rate stored in the task DB 312 and the current date and time. For example, in the case of a task having a work start date of January 1 and a work completion date of January 10, the work period is 10 days, so it is desirable to progress 10% a day. For this reason, when the progress rate is 60% or less as of January 7, it is considered that the progress is delayed with respect to the schedule. In addition to the method of calculating from the work period, the progress rate, and the current date and time as described above, any method can be used as long as it can determine whether or not the task progress is delayed.

  In step S <b> 1006, the conference information management server 103 transmits the generated data to the client terminal 101. FIG. 12 is a diagram illustrating a configuration example of the conference-task display screen 1200 displayed on the display unit 202 of the client terminal 101 that has received the display data transmitted in S1006. The conference-task display screen 1200 is configured based on the information in FIG. 11C and the number of delayed tasks in each conference counted in the process of S1005. On the conference-task display screen 1200, conference information corresponding to the task specified in S1001 and its descendant tasks is displayed as a conference display area 1201. The conference display area 1201 may display conference summary information in addition to the conference name. Further, the number of delayed tasks in each meeting is displayed in the delayed task area 1202 in a form superimposed on the meeting display area 1201. In addition, a conference relation line 1203 representing a relationship between conferences is displayed between the conference display areas 1201 corresponding to the parent conference and the child conference derived in S1004. In this embodiment, the conference related line 1203 has the start point of the arrow as the parent conference and the end point as the child conference. In the example of FIG. 12, for example, a display indicating that “product A development software conference” and “product A development hardware conference” exist as child conferences of “product A development steering conference” is performed. Among these, it is shown that a delayed task occurs in the “Product A Development Software Conference”. Displaying in the format as shown in FIG. 12 makes it easy for the user to grasp the structure of the conference related to the task and the fact that the delayed task is concentrated in the “Product A development software conference”.

  The configuration of the screen is not limited to the above, and other methods may be adopted as long as the display format is such that it can be understood how many tasks are delayed in which conference. For example, information for identifying a meeting (for example, a meeting name and a meeting ID), information indicating the number of tasks delayed in the meeting (for example, a number, a ratio between the total number of tasks and the number of delayed tasks, etc.) Instead of overlapping and displaying, they may be arranged and displayed within a predetermined distance. Alternatively, for example, the display color of the conference display area and the size of the display area may be changed according to the number and ratio of tasks that are delayed.

  As described above, according to the present embodiment, it is possible to create a structured task across conferences and visualize the structure between tasks and the structure of a conference related to the task.

<Second Embodiment>
Next, the second embodiment according to the present invention will be described focusing on differences from the first embodiment. In the first embodiment, a method for creating a hierarchically structured task across meetings, a structure between tasks, and a method for visualizing the structure of a meeting related to the task have been described. In the second embodiment, a method for visualizing a conference structure when the conference structure is not a tree, that is, a simple (one-way) parent-child relationship will be described.

  FIG. 13 shows an example of aggregated conference information corresponding to FIG. 11B in the present embodiment. In the example of FIG. 13, the conference with the conference ID “0002” and the conference with “0003” have a parent-child structure. If this structure is visualized, the structure may be difficult to grasp. Here, the meeting with the meeting ID “0002” will be described as “product A development software meeting”, and the meeting with the meeting ID “0003” will be described as “product A development hardware meeting”.

  FIG. 14 is a diagram illustrating a configuration example of a conference-task display screen displayed on the display unit 202 of the client terminal 101 in the present embodiment. In this embodiment, when the conference information management server 103 detects that there are two conferences having a parent-child relationship with each other (bidirectionally), the conference information management server 103 performs a process of switching the type of line displayed between these conferences. That is, a conference relation line 1401 indicating that there is a mutual relationship is displayed between the conference display area 1201 representing the conference with the conference ID “0002” and the conference with “0003”. In FIG. 14, the conference related line 1401 is expressed by a broken line, but a specific expression format is not limited as long as it can be distinguished from the conference related line 1203. For example, a line with arrows attached to both ends may be used.

  As described above, according to the present embodiment, even when the relationship between conferences is a tree shape, that is, not a simple parent-child relationship, the user can grasp the relationship between conferences.

<Third embodiment>
Next, a third embodiment according to the present invention will be described focusing on differences from the first and second embodiments. In the third embodiment, a method of displaying task information related to each displayed conference on a display screen that visualizes the conference structure from the relationship between tasks will be described.

  FIG. 15 shows an example of a screen displayed on the display unit 202 of the client terminal 101 when the user selects a specific conference display area 1201 on the conference-task display screen 1200 of FIG. When the conference information management server 103 detects that the user has selected the conference display area 1201, the conference information management server 103 selects tasks belonging to the conference corresponding to the selected conference display area 1201 based on the conference DB 310, the conference content DB 311, and the task DB 312. To search. Subsequently, the conference information management server 103 identifies only the descendant tasks of the task accepted in S1001 from the retrieved tasks as data to be displayed, and creates display data of the screen based on this information. The in-conference task list display area 1501 is an area displayed by performing the above processing. Here, detailed information of each task belonging to the conference is displayed.

  FIG. 16 is a diagram showing an example of a screen displayed on the display unit 202 of the client terminal 101 when the user selects a specific delayed task area 1202 on the conference-task display screen 1200 of FIG. When it is detected that the user has selected the delayed task area 1202, the conference information management server 103 searches the conference DB 310, the conference content DB 311 and the task DB 312 for tasks belonging to the conference corresponding to the selected delayed task area 1202. To do. Subsequently, the conference information management server 103 identifies only the tasks that are descendants of the task accepted in S1001 from the retrieved tasks and are delayed, and displays them based on this information. Create data. The in-meeting delayed task list display area 1601 is an area displayed by performing the above processing. Here, detailed information of a task whose progress is delayed is displayed.

  As described above, in this embodiment, when a specific area on the screen that visualizes the structure between meetings related to a task is selected, the meeting information management server displays the information on the task related to the meeting to the user. It is possible to present the conference structure and the task state in association with each other.

<Fourth embodiment>
Next, the fourth embodiment according to the present invention will be described focusing on differences from the first to third embodiments. In the first embodiment, it has been described that the user who has confirmed the conference-task display screen 1200 shown in FIG. 12 grasps the status of the conference, but this may be difficult when there are many related conferences. . In the present embodiment, an example in which the conference information management server 103 identifies and presents a target conference to be noted will be described.

  In the present embodiment, the conference information management server 103 determines which conference has many delayed tasks based on the number of delayed tasks for each conference calculated in S1005. Specifically, the following processing is performed.

  The conference information management server 103 divides the number of delayed tasks for each conference managed in the conference DB 310 by the number of conferences to be displayed. That is, the conference information management server 103 calculates the average number of delayed tasks in the entire conference to be displayed. Note that the number of conferences to be displayed may be specified in advance by the user, or may be defined according to the size of the display area of the screen.

  Subsequently, the meeting information management server 103 calculates a deviation value from the number of delayed tasks and the average number of delayed tasks for each meeting, and is a meeting having a large number of delayed tasks for a meeting having a certain deviation value or more. judge. Thereafter, the conference information management server 103 creates screen display data including information on the conference determined to have a large number of delayed tasks. In the present embodiment, a meeting with a large number of delayed tasks is determined using the average value and the deviation value. However, other determination methods may be used, for example, a meeting having a certain number of delayed tasks may be targeted. In the present embodiment, as an example of the display method, the area may be displayed so as to be superimposed on the conference-task display screen 1200 shown in FIG. Thus, a screen showing the relationship between the conference and the delayed task is displayed without accepting the task selection by the user in S1001 of FIG.

  As described above, in the present embodiment, the conference information management server determines a conference with a large number of delayed tasks and provides it to the user, so that even if the display screen includes a large number of conferences, the user can display the conference structure and task status. It becomes possible to grasp.

<Other embodiments>
The present invention is also realized by executing the following processing. That is, software (program) for realizing the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or apparatus reads the program. It is a process to be executed.

100 conference information system, 101 client terminal, 103 conference information management server, 104 network

Claims (8)

A conference information management system,
Storage means for associating and storing in the storage unit information on the conference and information on the task that occurred in the conference;
Based on a user's instruction, among the tasks stored in the storage unit, an association unit that performs hierarchical structure by associating tasks that occurred in different meetings,
Selecting means for accepting selection of a task from the tasks stored in the storage unit;
A determination unit that identifies a task associated with the task selected by the selection unit based on the association between the tasks, and determines a parent-child relationship between conferences to which each of the identified tasks belongs;
Providing means for providing a display screen for displaying the parent-child relationship between the meetings determined by the determining means and information on tasks belonging to each of the meetings that are delayed in progress. Conference information management system characterized by   When there are a plurality of conferences determined to have a parent-child relationship with each other by the determining unit, the providing unit displays on the display screen that the plurality of conferences have a parent-child relationship with each other. The conference information management system according to claim 1.   The display screen displays the outline information of the meeting in a hierarchical structure based on the parent-child relationship between the meetings, and further displays the number of tasks in which progress is delayed in the meeting displayed in the hierarchical structure. 3. The conference information management system according to claim 1, wherein the conference information management system is displayed as outline information. When the display screen is being displayed, the display screen further includes detection means for detecting that any region of the display screen is selected,
When it is detected that an area displaying the summary information of the conference is selected from the display screen, the providing unit further displays a list of tasks belonging to the conference on the display screen,
When it is detected that an area displaying the task summary information is selected from the display screen, the providing unit further displays the task detailed information on the display screen. The conference information management system according to claim 3. Based on a predetermined determination method, the apparatus further includes a determination unit that determines a meeting having many tasks that are delayed in progress among the tasks to which the task belongs.
The said providing means provides the said display screen including the display to that effect with respect to the meeting determined that there are many tasks which have produced the delay in the progress by the said determination means. 5. The conference information management system according to any one of 4.   The conference information management system according to claim 5, wherein the determination unit performs the determination based on a deviation value with respect to an average number of tasks causing a delay in the entire conference as the predetermined determination method. A control method for a conference information management system,
A storage step of associating the information on the conference with the information on the task generated in the conference and storing the information in the storage unit;
Based on a user instruction, among the tasks stored in the storage unit, an associating step of associating tasks that occurred in different meetings to form a hierarchical structure;
A selection step of accepting a task selection from the tasks stored in the storage unit;
A determination step of identifying a task associated with the task selected in the selection step based on the association between the tasks, and determining a parent-child relationship between conferences to which each of the identified tasks belongs;
A providing step of providing a display screen that displays the parent-child relationship between the conferences determined in the determination step and information on tasks that are delayed in progress among tasks belonging to each conference; A control method of a conference information management system characterized by the above. Computer
Storage means for associating the information of the meeting with the information of the task generated in the meeting and storing it in the storage unit;
Association means for performing hierarchical structure by associating tasks generated in different meetings among the tasks stored in the storage unit based on a user instruction;
A selection means for accepting a task selection from the tasks stored in the storage unit;
A determination unit that identifies a task associated with the task selected by the selection unit based on the association between the tasks, and determines a parent-child relationship between conferences to which each of the identified tasks belongs;
In order to function as a providing unit that provides a display screen that displays the parent-child relationship between conferences determined by the determination unit and information on tasks that are delayed in progress among tasks belonging to each conference Program.

Images