JP2012252586A - Document data management device, document data inheritance method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document data management device, a document data inheritance method and a program which enable members of a new virtual community generated by inheriting threads of an existing virtual community to recognize a thread to be preferentially handled among the inherited threads.SOLUTION: A document data management device of an embodiment comprises an information acquisition part, a member difference detection part, a priority determination part and a task screen display control part. The information acquisition part acquires setting information for generating an inheritance destination task. The member difference detection part detects a member difference between an inheritance source task and the inheritance destination task, on the basis of the acquired setting information. The priority determination part determines priority of each inherited thread, on the basis of the member difference. The task screen display control part displays a task screen including a thread list in which a title of each thread is arranged in a priority order, on a user terminal.

Description

  Embodiments described herein relate generally to a document data management apparatus, a document data inheritance method, and a program.

  2. Description of the Related Art Conventionally, a system that enables information to be shared among a plurality of users through a virtual community such as an electronic bulletin board is known. In this system, for example, a document data management device realized as a server on a communication network posts and posts document data to a virtual community to a user terminal (client) of a user registered as a member of the virtual community. This is realized as a server-client system that provides a community screen for browsing document data. The document data management apparatus manages document data posted to the virtual community from the community screen of the user terminal for each thread that is a set of document data related to a common topic, and members of the virtual community can manage document data in units of threads. Can be viewed.

  A virtual community is generated according to a predetermined purpose, such as providing a forum for discussion among development members who are involved in a product development project, taking for example the virtual community used in corporate activities. Is common. Therefore, when a new purpose occurs, such as when a new product development project is launched, a new virtual community is generated in accordance with the new purpose. At this time, when the newly developed product is related to other products, the discussions made in the existing virtual community generated in the development of the other products are useful information for the new product development. There are many cases. From such a viewpoint, when a new virtual community is generated, an attempt has been made to generate a new virtual community by inheriting an existing virtual community thread.

  When a new virtual community is generated by inheriting a thread of an existing virtual community, a difference often occurs between the existing virtual community and the newly generated virtual community. In this case, simply inheriting a thread of an existing virtual community to a new virtual community does not tell the members of the new virtual community which thread should be treated preferentially among the inherited threads. For example, if the user who posted the document data included in the inherited thread is not a member of the new virtual community, it may be necessary to make an early conclusion on the topic of the thread. Such a virtual community member cannot recognize such a thread to be preferentially handled.

Japanese Patent No. 4040849

  A problem to be solved by the present invention is a document that allows a member of a new virtual community generated by inheriting a thread of an existing virtual community to recognize a thread to be preferentially handled among the inherited threads. To provide a data management device, a document data inheritance method, and a program.

  The document data management apparatus according to the embodiment provides a community screen for posting the document data to the virtual community and browsing the document data to a user terminal of a user who is a member of the virtual community. This is a document data management apparatus that manages each thread that is a set of document data. The document data management apparatus includes an acquisition unit, a detection unit, a determination unit, and a first display control unit. The acquisition unit acquires setting information for generating a second virtual community inheriting a thread belonging to the existing first virtual community. The detecting means detects a difference between the member of the first virtual community and the member of the second virtual community based on the setting information. The determining unit determines a priority of a thread inherited from the first virtual community to the second virtual community based on the difference. The first display control means causes the user terminal to display a community screen of the second virtual community including a thread list in which threads inherited from the first virtual community are arranged in descending order of priority.

The system block diagram which shows the outline | summary of an information sharing system. The functional block diagram which shows the internal structure of a document data management apparatus. The functional block diagram which shows the detail of a task inheritance part. The figure which shows an example of the task screen of the inheritance origin task. The figure which shows an example of a setting screen. The figure which shows an example of a member setting screen. The figure which shows an example of the task screen of an inheritance destination task. The figure which shows an example of a task details screen. 6 is a flowchart showing a flow of a series of processing executed by the document data management apparatus when generating an inheritance destination task. The figure which shows an example of the hardware constitutions of a document data management apparatus.

  Hereinafter, a document data management apparatus, a document data inheritance method, and a program according to an embodiment will be described with reference to the drawings.

  FIG. 1 is a system configuration diagram showing an overview of an information sharing system including a document data management apparatus according to the present embodiment. As shown in FIG. 1, the information sharing system includes a document data management apparatus 1 that functions as a server, and a plurality of user terminals 2-1, 2-2,. 2-n (hereinafter collectively referred to as “user terminal 2”) is connected via the communication network 3.

  The document data management apparatus 1 is an apparatus used by a service provider that provides a service using a virtual community (in this embodiment, such a virtual community is referred to as a “task”) that is used for exchanging information among a plurality of users. It is. On the other hand, the user terminal 2 is a terminal used by a user who receives a service from a service provider, that is, a user registered as a member of at least one of a plurality of tasks provided by the service provider. Note that the form of the communication network 3 is arbitrary, and for example, the Internet, a LAN (local area network), or the like can be applied.

  The document data management apparatus 1 provides a task screen (see FIG. 4) to the user terminal 2, and document data (hereinafter simply referred to as “document”) posted to the task from this task screen is a document related to a common topic. Managed for each thread that is a set of. A user registered as a member of a task can view the posted document in units of threads through a task screen displayed on the user terminal. The document data management apparatus 1 displays a setting screen (see FIG. 5) for inputting setting information on the user terminal 2 when there is a request to generate a new task by inheriting the thread of the existing task. Let Then, the document data management apparatus 1 acquires the setting information input from this setting screen, and based on the acquired setting information, a new task that inherits a thread of an existing task (hereinafter referred to as “inheritance source task”). A task (hereinafter referred to as “inherited task”) is generated and the task screen of the inherited task is displayed on the user terminal 2. At this time, the document data management apparatus 1 determines the priority of the thread inherited from the inheritance source task to the inheritance destination task. Then, the document data management apparatus 1 causes the user terminal 2 to display a task screen (see FIG. 7) including a thread list in which threads are arranged in descending order of priority. Thereby, the member of the inheritance destination task can recognize which thread should be preferentially handled among the threads inherited from the inheritance source task.

  FIG. 2 is a functional block diagram showing the internal configuration of the document data management apparatus according to this embodiment. As shown in FIG. 2, the document data management apparatus 1 includes a Web server 10, an information acquisition unit 20, a task inheritance unit 30, a task generation unit 40, a user database (hereinafter, the database is abbreviated as DB) 51, and a task DB 52. A document DB 53 and an important word DB 54. Note that the user terminal 2 includes at least a web browser 60.

  The Web server 10 accumulates screen information necessary for generating various display screens, transmits screen information corresponding to a request from the Web browser 60 of the user terminal 2 to the user terminal 2, and sends the screen information to the user terminal 2. The screen corresponding to is displayed. In the present embodiment, the Web server 10 includes a setting screen display control unit 11 and a task screen display control unit 12. The setting screen display control unit 11 causes the user terminal 2 to display the setting screen described above. The task screen display control unit 12 causes the user terminal 2 to display the above-described task screen.

  The information acquisition unit 20 acquires setting information input from the setting screen. This setting information includes, for example, the task name of the inheritance destination task, the account, the description of the task, and the user name of the member to be registered. In addition, the information acquisition unit 20 searches the task DB 52, the user DB 51, and the document DB 53 based on the task ID of the inheritance source task, thereby regarding the user names of members belonging to the inheritance source task and the threads belonging to the inheritance source task. Various types of information (text of a document included in a thread, additional information of a document, thread ID, past number of inheritance of a thread, etc.) are acquired. The task ID of the inheritance source task can be specified from the task screen, for example, if the setting screen has a screen transition from the task screen of the inheritance source task. Alternatively, setting information for specifying the inheritance source task may be input from the setting screen, and the task ID of the inheritance source task may be specified from the setting information. The information acquisition unit 20 passes the acquired information to the task inheritance unit 30.

  The task inheritance unit 30 generates information necessary for generating the inheritance destination task based on the information received from the information acquisition unit 20, and passes the information to the task generation unit 40. The information necessary to generate the inheritance destination task includes the task name of the inheritance destination task, account, description of the task, user name of the member to be registered, etc. entered as setting information, as well as inheritance from the inheritance source task Threads inherited by the previous task and information for generating a thread list in which threads are arranged according to priority (order of threads) are included. Details of the task inheritance unit 30 will be described later.

  The task generation unit 40 generates an inheritance destination task that inherits a thread from the inheritance source task based on the information received from the task inheritance unit 30. The inheritance destination task generated by the task generation unit 40 is registered in the task DB 52. The members of the inheritance destination task are registered in the user DB 51, and the inherited thread document is registered in the document DB 53. In addition, the task generation unit 40 passes screen information necessary for generating the task screen of the inheritance destination task to the task screen display control unit 12. The task screen includes the above-described thread list (see FIGS. 4 and 7). The task generation unit 40 passes screen information including a thread list in which these threads are arranged according to the priority of the thread inherited from the inheritance source task to the inheritance destination task to the task screen display control unit 12.

  The user DB 51 stores user information. The user information is information related to a user registered as a user who receives a service from the document data management apparatus 1. The user information includes, for example, a user ID, a user name, an account, a password, a display name, and a profile. The user information includes a task ID of a task to which the user belongs as a member. When a certain user becomes a member of a task, the task ID of the task that has become a member is added to the user information of the user. That is, if the user ID includes a task ID, it means that the user is registered as a member of the task identified by the task ID.

  The task DB 52 stores task information. The task information is information relating to a task provided by the document data management apparatus 1. The task information includes a task ID, a task name, an account, a description about the task, and the like. The task information includes the task ID of the inheritance source task in the case of the inheritance destination task generated by inheriting the thread of another task.

  The document DB 53 stores the text of the document posted to the task and additional information. The additional information includes a document ID, a document title, a document creator, a document posting date, a task ID of a task to which the document belongs, a file associated with the document, and the like. Further, the additional information includes the thread ID of the thread to which the document belongs. Therefore, by specifying the thread ID, the text and additional information of the document included in the thread identified by this thread ID can be extracted from the document DB 53. That is, the document DB 53 stores the text of the document and additional information so that the posted document can be managed for each thread. The thread ID is associated with information indicating the number of times that the thread identified by this thread ID has been inherited in the past (the number of times that the thread has been inherited between tasks). Therefore, by specifying this thread ID, it is possible to acquire the number of times the thread identified by this thread ID has been inherited in the past.

  The important word DB 54 stores words designated as important words in advance. The important words stored in the important word DB 54 are words that members are expected to pay particular attention to as important words in discussions exchanged in tasks provided by the document data management apparatus 1. Since such important words vary depending on the environment to which the information sharing system is applied, an appropriate word may be selected according to the environment to which the information sharing system is applied and stored in the important word DB 54.

  FIG. 3 is a functional block diagram showing details of the task inheritance unit 30. As illustrated in FIG. 3, the task inheritance unit 30 includes a member difference detection unit 31, a priority determination unit 32, and a thread arrangement order setting unit 33.

  The member difference detection unit 31 compares the user name of the member of the inheritance destination task included in the setting information received from the information acquisition unit 20 with the user name of the member of the inheritance source task received from the information acquisition unit 20, and inherits A difference (member difference) between a member of the original task and a member of the inheritance destination task is detected. Then, the member difference detection unit 31 passes the detected member difference to the priority determination unit 32.

  The priority determination unit 32, for example, from the member difference received from the member difference detection unit 31, the posting date and time of the document included in the thread inherited from the inheritance source task received from the information acquisition unit 20 to the inheritance destination task, from the inheritance source task The priority of each thread inherited from the inheritance source task to the inheritance destination task is determined using information such as the past inheritance count of the thread inherited by the inheritance destination task and the important word registered in the important word DB 54. In the following, an example of a specific method for determining the priority by the priority determination unit 32 based on the consideration on the priority of the thread will be described. In the following example, the score of each thread is obtained for each of several indicators for determining priority, and the total value of these scores is treated as priority, but this example is only an example. The method for determining the priority of the thread is not limited to this example.

  If the user who posted the document included in the thread inherited from the inheritance source task is not included in the members of the inheritance destination task, it is inferred that the topic being handled in that thread is likely to need an early conclusion. Is done. Therefore, the priority determination unit 32 uses the member difference received from the member difference detection unit 31 to determine whether the inheriting thread includes a document posted by a user who is not included in the members of the inheritance destination task. When a simple document is included, the ratio is used as one index for determining the priority of the thread.

  That is, the priority determination unit 32 determines the priority of a thread that includes a document posted by a user who is not included in a member of the inheritance destination task, Set higher than priority. In addition, for the thread including the document posted by the user not included in the members of the inheritance destination task, the priority determination unit 32 has a higher ratio of the document posted by the user not included in the members of the inheritance destination task. Increase priority. For example, the priority determination unit 32 sets score “0” for a thread that does not include a document posted by a user who is not included in a member of the inheritance destination task, and a document posted by a user who is not included in the member of the inheritance destination task. The score is “1” for threads with a percentage of less than 50%, and the score “2” for threads with a percentage of documents submitted by users not included in the inheritance task members of 50% to less than 80%. A score “3” is given to a thread in which the ratio of a document posted by a user who is not included in the members of the inheritance task is 80% or more.

  In addition, threads that have posted documents over a long period of time, that is, threads that have been posted until recently and the first document has an old posting date, dealt with topics that have been discussed for a long time. It is a thread, and it is presumed that the importance as a thread is high. Therefore, the priority determination unit 32 uses the information on the posting date of the document received from the information acquisition unit 20, and uses the length of the period during which the document is posted as one index for determining the priority of the thread. To do. For example, the priority determination unit 32 scores a thread for which the difference between the date and time when the first document was posted and the date and time when the last document was posted (hereinafter referred to as “posting duration”) is six months or more. “3”, a score “2” is given to a thread having a posting duration of less than six months and one month or more, and a score “1” is given to a thread having a posting duration of less than one month.

  Further, it is presumed that a thread in which a follow document is regularly posted is a thread that deals with a continuous topic and is highly important as a thread. Therefore, the priority determination unit 32 uses the document posting date / time information received from the information acquisition unit 20 and uses the document posting count for each predetermined period as one index for determining the thread priority. For example, the priority determination unit 32 has a score “0” for a thread with a month in which no document is posted, a score “1” for a thread with a document posted once a month, and 2 for each month. The score “2” is given to the thread in which the document is posted, and the score “3” is given to the thread in which the document is posted three times or more every month.

  In addition, if the inherited thread is inherited between multiple generations of 2/3 generations and then inherited to the inheritance destination task, it is assumed that the topic of the thread is highly difficult to solve. The Therefore, the priority determination unit 32 uses the information on the past inheritance number of the thread received from the information acquisition unit 20, and uses the past inheritance number as one index for determining the priority of the thread. For example, the priority determination unit 32 has a score “0” for a thread that has not been inherited in the past, a score “1” for a thread that has a past inheritance count of 1, and a past inheritance count of 2 times. A score of “2” is given to the thread of No. 1, and a score of “3” is given to a thread having a past inheritance count of 3 or more.

  Further, it is presumed that a thread including many documents including important words registered in the important word DB 54 is a thread dealing with an important topic. Therefore, the priority determination unit 32 uses the ratio of documents including the important word registered in the important word DB 54 as one index for determining the priority of the thread. For example, the priority determination unit 32 has a score of “0” for a thread that does not include any document including the important word registered in the important word DB 54, and the important word in which less than 50% of the documents are registered in the important word DB 54. For threads that contain important words whose score is "1" and whose documents are 50% or more and less than 80% are registered in the important word DB 54, those whose scores are "2" and 80% or more are important words A score “3” is given to a thread including an important word registered in the DB 54.

  The priority determination unit 32 obtains a score based on each of the above indices for each thread inherited from the inheritance source task to the inheritance destination task, adds the obtained scores, and determines the total value as the thread priority. . Then, the priority determination unit 32 passes the determined priority of each thread to the thread arrangement order setting unit 33.

  In accordance with the priority determined by the priority determination unit 32, the thread arrangement order setting unit 33 sets the thread arrangement order when generating the above thread list for each thread inherited from the inheritance source task to the inheritance destination task. Set. Specifically, the thread arrangement order setting unit 33 sets the thread arrangement order so that the higher priority threads are arranged higher in the thread list. As described above, the thread arrangement order set by the thread arrangement order setting unit 33 is passed to the task generation unit 40 as one piece of information for generating the inheritance destination task.

  Next, the operation of the document data management apparatus 1 according to the present embodiment will be specifically described with reference to FIGS. 4 to 8 showing specific examples of display screens displayed on the user terminal 2.

  FIG. 4 is a diagram illustrating an example of the task screen of the inheritance source task displayed on the user terminal 2. When display of the task screen of the inheritance source task is requested from the user terminal 2 in accordance with the operation of the user registered as a member of the inheritance source task, the document data management apparatus 1 is subjected to a predetermined procedure such as user authentication. The task screen display control unit 12 of the Web server 10 included in the server transmits screen information necessary for generating the task screen of the inheritance source task to the user terminal 2. When the screen information from the web server 10 is received by the user terminal 2, the web browser 60 of the user terminal 2 draws a display screen based on the received screen information. As a result, the task screen 400 of the inheritance source task as shown in FIG. 4 is displayed on the user terminal 2.

  The task screen 400 of the inheritance source task includes a thread list 401 in which threads belonging to the inheritance source task (thread titles in this embodiment) are arranged. The inheritance source task task screen 400 includes a “post” button 402, a “task inheritance” button 403, and a “task details” button 404. The “post” button 402 is a button operated when posting a document to the inheritance source task. A “task inheritance” button 403 is a button operated when requesting generation of an inheritance destination task that inherits the thread of the inheritance source task. The “task details” button 404 is a button operated when requesting detailed information of the inheritance source task.

  FIG. 5 is a diagram illustrating an example of a setting screen displayed on the user terminal 2. When the “task inheritance” button 403 is pressed on the task screen 400 of the inheritance source task illustrated in FIG. 4, the setting screen display control unit 11 of the Web server 10 provided in the document data management apparatus 1 causes the user terminal 2 to Screen information necessary for generating the setting screen. When the screen information from the web server 10 is received by the user terminal 2, the web browser 60 of the user terminal 2 draws a display screen based on this screen information. Thereby, a setting screen 500 as shown in FIG. 5 is displayed on the user terminal 2.

  The setting screen 500 is a screen for inputting setting information necessary for generating the inheritance destination task. This setting screen 500 includes a text box 501 for inputting a task name of an inheritance destination task, a text box 502 for inputting an account, a text box 503 for inputting a description of the inheritance destination task, and the like. . The setting screen 500 also includes a display area 504 in which member user names are displayed. In the display area 504, user names of members of the inheritance source task are displayed in the initial state.

  The setting screen 500 includes a “member change” button 505, an “inherit” button 506, a “cancel” button 507, and the like. “Change member” button 505 is a button operated when changing the member of the inheritance destination task from the member of the inheritance source task. The “inheritance” button 506 is a button operated when confirming the input setting information. The “cancel” button 507 is a button operated when canceling the generation of the inheritance destination task. When this “cancel” button 507 is pressed, the display screen displayed on the user terminal 2 returns from the setting screen 500 of FIG. 5 to the task screen 400 of the inheritance source task shown in FIG.

  FIG. 6 is a diagram illustrating an example of the member setting screen. When the “change member” button 505 is pressed on the setting screen 500 shown in FIG. 5, the setting screen display control unit 11 of the Web server 10 included in the document data management apparatus 1 changes the member to the user terminal 2. Send screen information necessary for screen generation. When the screen information from the web server 10 is received by the user terminal 2, the web browser 60 of the user terminal 2 draws a display screen based on this screen information. As a result, a member change screen 600 as shown in FIG. 6 is displayed on the user terminal 2.

  The member change screen 600 includes a display area 601, a “delete” button 602, a text box 603, a “search” button 604, a display area 605, an “add” button 606, and the like. A display area 601 is an area in which member user names are displayed together with check boxes. The “delete” button 602 is a button operated when deleting a user whose check box is checked from the members. A text box 603 is a text box for inputting a keyword for user search. A “search” button 604 is a button operated when executing a user search. A display area 605 is an area where the result of the user search is displayed. The “add” button 606 is a button that is operated when a specified user is added as a member among the user names displayed in the display area 605. When the “delete” button 602 is pressed while a check box of any user name displayed in the display area 601 is checked, the user name is deleted from the display area 601. Further, when an “add” button 606 is pressed in a state where any user name displayed in the display area 605 is specified, the user name is added to the display area 601.

  The member change screen 600 includes a “confirm” button 607. The “confirm” button 607 is a button operated when confirming the user displayed in the display area 601 as a member of the inheritance destination task. When the “confirm” button 607 is pressed, the display screen displayed on the user terminal 2 returns from the member change screen 600 of FIG. 6 to the setting screen 500 shown in FIG. In the display area 504 of the setting screen 500, the user name displayed in the display area 601 of the member change screen 600 is displayed as the user name of the member of the inheritance destination task.

  Thereafter, when the “inherit” button 506 is pressed on the setting screen 500 shown in FIG. 5, the task name, account name, description of the task, members of the inheritance destination task input from the setting screen 500 The setting information such as the user name is confirmed. The determined setting information is acquired by the information acquisition unit 20 of the document data management apparatus 1. At this time, the information acquisition unit 20 also acquires the ID of the inheritance source task, and searches the task DB 52, the user DB 51, and the document DB 53 based on the task ID of the inheritance source task, thereby obtaining members and inheritance belonging to the inheritance source task. Acquire various information about threads belonging to the original task.

  Then, as described above, based on the information acquired by the information acquisition unit 20, information for generating the inheritance destination task is generated by the task inheritance unit 30, and the inheritance destination task is generated by the task generation unit 40. The Then, the screen information necessary for generating the task screen of the inheritance destination task is transmitted from the task screen display control unit 12 to the user terminal 2, and the Web browser 60 of the user terminal 2 draws the display screen based on this screen information. By doing so, the task screen of the inheritance destination task is displayed on the user terminal 2.

  FIG. 7 is a diagram illustrating an example of a task screen of the inheritance destination task. The task screen 700 of the inheritance destination task shown in FIG. 7 includes a thread list 701 in which threads inherited from the inheritance source task (thread titles in this embodiment) are arranged in descending order of priority. Compared to the thread list 401 included in the task screen 400 of the inheritance source task illustrated in FIG. 4, the third thread from the top in the inheritance source task is a thread having a high priority. It can be seen that the thread list 701 is the first from the top (the position indicated by the one-dot chain line in the figure). In addition, since the fifth thread from the top in the inheritance source task is a thread having a high priority, the thread list 701 of the inheritance destination task is second from the top (position indicated by a two-dot chain line in the figure). I understand that

  Further, the task screen 700 of the inheritance destination task shown in FIG. 7 is similar to the task screen 400 of the inheritance source task shown in FIG. 4, a “post” button 702, a “task inheritance” button 703, and “task details”. Button 704 and the like. A “post” button 702 is operated when posting a document to the inheritance destination task. The “task inheritance” button 703 is a button operated when requesting generation of a new task that further inherits the thread of the inheritance destination task. The “task detail” button 704 is a button operated when requesting detailed information of the inheritance destination task.

  FIG. 8 is a diagram illustrating an example of a task detail screen. When the “task details” button 704 is pressed on the task screen 700 of the inheritance destination task illustrated in FIG. 7, the task screen display control unit 12 of the Web server 10 included in the document data management apparatus 1 Screen information necessary for generating the task detail screen. When the screen information from the web server 10 is received by the user terminal 2, the web browser 60 of the user terminal 2 draws a display screen based on this screen information. As a result, a task detail screen 800 as shown in FIG. 8 is displayed on the user terminal 2.

  The task detail screen 800 includes, as detailed information of the inheritance destination task, the task name of the inheritance destination task, the account name, the description of the task, the number of members, the number of registered articles, the task name of the inheritance source task, and the user name of the task creator And information such as task creation date and time. The user can confirm the inheritance source task by referring to the task name of the inheritance source task (one-dot chain line in the figure) on the task detail screen 800. The task details screen 800 includes a “member details” button 801. The “member details” button 801 is operated when it is desired to know details of members of the inheritance destination task. When the “member details” button 801 is pressed, a list of user names of members of the inheritance destination task is displayed.

  Next, a series of operations when generating the inheritance destination task will be described with reference to FIG. FIG. 9 is a flowchart showing a flow of a series of processing executed by the document data management apparatus 1 when generating the inheritance destination task.

  First, when a setting screen is displayed on the user terminal 2 and setting information for generating an inheritance task is input from the setting screen, the information acquisition unit 20 acquires setting information input from the setting screen. The task ID of the inheritance source task is acquired (step S101).

  Next, the information acquisition unit 20 searches the document DB 53 based on the task ID of the inheritance source task, and acquires various types of information related to threads belonging to the inheritance source task from the document DB 53 (step S102).

  In addition, the information acquisition unit 20 searches the user DB 51 based on the task ID of the inheritance source task, and acquires the names of users who are members of the inheritance source task from the user DB 51 (step S103).

  Next, the member difference detection unit 31 of the task inheritance unit 30 compares the user name that is a member of the inheritance source task acquired by the information acquisition unit 20 with the user name that is a member of the inheritance destination task. The member difference between the inheritance source task and the inheritance destination task is detected (step S104).

  Next, the priority determination unit 32 of the task inheritance unit 30 includes the member difference detected by the member difference detection unit 31, the posting date and time of the document included in the inheriting thread, the number of inheritances of the past thread, and the important word. The priority is determined for each of the inherited threads based on the ratio of (S105).

  Next, the thread arrangement order setting unit 33 of the task inheritance unit 30 sets the thread arrangement order when generating a thread list in which the threads are arranged according to the priority determined by the priority determination unit 32 ( Step S106).

  Next, the task generation unit 40 generates an inheritance destination task that inherits the thread of the inheritance source task based on various information generated by the task inheritance unit 30, and a screen necessary for generating the task screen of the inheritance destination task Information is passed to the task screen display control unit 12 of the Web server 10 (step S107).

  Next, the task screen display control unit 12 of the Web server 10 transmits screen information necessary for generating the task screen of the inheritance destination task to the user terminal 2, and is set by the thread arrangement order setting unit 33 of the task inheritance unit 30. The task screen of the inheritance destination task including the thread list in which the threads are arranged in the arranged order is displayed on the user terminal 2 (step S108).

  As described above in detail with specific examples, the document data management apparatus 1 according to the present embodiment causes the user terminal 2 to display a setting screen for inputting setting information for generating the inheritance destination task. Based on the setting information input from the setting screen, member differences between the inheritance source task and the inheritance destination task are detected, and each thread inherited from the inheritance source task to the inheritance destination task based on the detected member difference The task screen of the inheritance destination task including the thread list in which threads are arranged in descending order of the determined priority is displayed on the user terminal 2. Therefore, the user who becomes a member of the inheritance destination task refers to the thread list included in the task screen of the inheritance destination task displayed on the user terminal 2, and determines the inherited thread from the order of the threads in the thread list. Among them, it is possible to recognize which thread should be preferentially handled.

  The document data management apparatus 1 according to the present embodiment inherits from the inheritance source task based on the posting date of the document included in the thread, in addition to the member difference between the inheritance source task and the inheritance destination task. Since the priority of each thread inherited by the previous task is determined, the priority of the thread can be accurately determined.

  In addition to the member difference between the inheritance source task and the inheritance destination task, the posting date and time of the document included in the thread, the document data management apparatus 1 according to the present embodiment is further based on the past inheritance count of the thread. Thus, since the priority of each thread inherited from the inheritance source task to the inheritance destination task is determined, the priority of the thread can be determined with higher accuracy.

  In addition to the member difference between the inheritance source task and the inheritance destination task, the posting date and time of the document included in the thread, and the past inheritance count of the thread, the document data management apparatus 1 according to the present embodiment further includes The priority of each thread that is inherited from the inheritance source task to the inheritance destination task is determined based on the percentage of documents that contain registered important words, so that the priority of the thread can be determined more accurately. Can do.

  As described above, according to the present embodiment, a member of an inheritance destination task generated by inheriting a thread of an inheritance source task can recognize a thread to be preferentially handled among the inherited threads.

  Each function described above in the document data management apparatus 1 according to the present embodiment can be realized, for example, by executing a predetermined program in the document data management apparatus 1. The hardware configuration of the document data management apparatus 1 at this time will be described with reference to FIG. FIG. 10 is a diagram illustrating an example of a hardware configuration of the document data management apparatus 1 according to the present embodiment.

  A document data management apparatus 1 according to the present embodiment is connected to a control device such as a CPU (Central Processing Unit) 101, a storage device such as a ROM (Read Only Memory) 102 and a RAM (Random Access Memory) 103, and a network. Communication I / F 104, an external storage device such as an HDD (Hard Disk Drive) and a CD (Compact Disc) drive device, a display device such as a display device, an input device such as a keyboard and a mouse, A bus 110 for connection is provided, and a hardware configuration using a normal computer is employed.

  A program executed by the document data management apparatus 1 according to the present embodiment is an installable or executable file, which is a CD-ROM (Compact Disk Read Only Memory), a flexible disk (FD), a CD-R ( The program is recorded on a computer-readable recording medium such as a Compact Disk Recordable (DVD) or a Digital Versatile Disc (DVD) and provided as a computer program product.

  The program executed by the document data management apparatus 1 according to the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Further, the program executed by the document data management apparatus 1 according to the present embodiment may be provided or distributed via a network such as the Internet.

  Further, the program executed by the document data management apparatus 1 according to the present embodiment may be provided by being incorporated in advance in the ROM 102 of the document data management apparatus 1 or the like.

  The program executed by the document data management apparatus 1 according to the present embodiment includes processing units (setting screen display control unit 11, task screen display control unit 12, information acquisition unit 20, and member difference detection unit of the document data management device 1. 31, a priority determination unit 32, a thread arrangement order setting unit 33, a task generation unit 40, and the like). As actual hardware, for example, the CPU 101 (processor) executes a program from the recording medium. By reading and executing, each processing unit described above is loaded on the main storage device, and each processing unit described above is generated on the main storage device. Note that the document data management apparatus 1 according to the present embodiment uses a dedicated hardware such as an application specific integrated circuit (ASIC) or a field-programmable gate array (FPGA) for some or all of the processing units described above. It can also be realized.

  As mentioned above, although embodiment of this invention was described, embodiment described here is shown as an example and is not intending limiting the range of invention. The novel embodiments described herein can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. The embodiments and modifications described herein are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 1 Document data management apparatus 2 User terminal 11 Setting screen display control part 12 Task screen display control part 20 Information acquisition part 30 Task inheritance part 31 Member difference detection part 32 Priority determination part 33 Thread arrangement order setting part 40 Task generation part

Claims (9)

A user interface of a user who is a member of a virtual community is provided with a community screen for posting document data to the virtual community and browsing the document data, and the document data is provided for each thread that is a set of document data A document data management device for managing
Acquisition means for acquiring setting information for generating a second virtual community that inherits a thread belonging to an existing first virtual community;
Detecting means for detecting a difference between a member of the first virtual community and a member of the second virtual community based on the setting information;
Determining means for determining a priority of a thread inherited from the first virtual community to the second virtual community based on the difference;
A document comprising: a first display control unit configured to display a community screen of the second virtual community on the user terminal including a thread list in which threads inherited from the first virtual community are arranged in descending order of priority. Data management device. A second display control means for causing the user terminal to display a setting screen for inputting the setting information;
The document data management apparatus according to claim 1, wherein the acquisition unit acquires the setting information input from the setting screen.   The determination means determines a priority of a thread including the document data posted by a user who is not included in a member of the second virtual community among threads inherited from the first virtual community to the second virtual community. The document data management apparatus according to claim 1, wherein the document data management device is set higher than a thread that does not include the document data posted by a user who is not included in a member of the second virtual community.   The determination unit is configured to determine a priority of a thread including the document data posted by a user not included in the second virtual community member, and the document posted by a user not included in the second virtual community member. The document data management apparatus according to claim 3, wherein a thread having a higher data ratio is set higher.   The said determination means further determines the priority of the thread | sled inherited from the said 1st virtual community to the said 2nd virtual community based on the posting date of the said document data contained in a thread | sled. Document data management device.   2. The document data management according to claim 1, wherein the determination unit further increases a priority of a thread inherited from the first virtual community to the second virtual community as a thread having a higher number of inheritances in the past. apparatus.   The determination means further increases the priority of a thread inherited from the first virtual community to the second virtual community as a thread having a higher ratio of document data including pre-registered important words. Document data management device described in 1. A user interface of a user who is a member of a virtual community is provided with a community screen for posting document data to the virtual community and browsing the document data, and the document data is provided for each thread that is a set of the document data. A document data inheriting method executed in a managing system,
Obtaining setting information for generating a second virtual community inheriting a thread belonging to an existing first virtual community;
Detecting a difference between a member of the first virtual community and a member of the second virtual community based on the setting information;
Determining priority of threads inherited from the first virtual community to the second virtual community based on the difference;
Causing the user terminal to display a community screen of the second virtual community including a thread list in which threads inherited from the first virtual community are arranged in descending order of priority. A user interface of a user who is a member of a virtual community is provided with a community screen for posting document data to the virtual community and browsing the document data, and the document data is provided for each thread that is a set of the document data. On the computer you want to manage
A function of acquiring setting information for generating a second virtual community inheriting a thread belonging to an existing first virtual community;
A function of detecting a difference between a member of the first virtual community and a member of the second virtual community based on the setting information;
A function for determining a priority of a thread inherited from the first virtual community to the second virtual community based on the difference;
A program for realizing a function of displaying, on the user terminal, a community screen of the second virtual community, which includes a thread list in which threads inherited from the first virtual community are arranged in descending order of priority.

Images