JP4146101B2 - Knowledge accumulation support system and public summary providing method in the same system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a knowledge accumulation support system used in a knowledge management system and a public summary providing method in the system, and more particularly to a knowledge accumulation support system that supports accumulation of knowledge using a virtual community in which an unspecified number of users participate. And a public summary providing method in the system.
[0002]
[Prior art]
In recent years, introduction of groupware for sharing information among a plurality of users has been promoted mainly by companies. As typical groupware, an e-mail system, a workflow system, and the like are known, but recently, a knowledge management system for supporting sharing of knowledge and information has begun to be developed.
[0003]
This knowledge management system is for accumulating and managing personal know-how as a knowledge database in addition to Web information and electronic file information. By combining it with a search function such as natural language search, knowledge and information Efficient use is possible.
[0004]
By the way, in such a knowledge management system, it is important how to collect and accumulate knowledge such as individual know-how. This is because knowledge such as personal know-how is so-called tacit knowledge and is not formalized like Web information or electronic file information, so it is difficult to automatically collect and store it. .
[0005]
Therefore, recently, there is a demand for the development of a knowledge management system having a knowledge accumulation support function. Utilize knowledge as tacit knowledge in the same way as formal knowledge such as Web information and electronic file information by realizing a mechanism for automatically collecting and accumulating knowledge such as personal know-how Is possible.
[0006]
[Problems to be solved by the invention]
In such a knowledge management system, in order to accumulate knowledge such as individual know-how, usually a large number of virtual communities are prepared as a place for many users to actively exchange opinions, and further in that community After collecting the conversations to be exchanged, it is necessary to create a “summary” that summarizes the contents. This is because by making it possible to browse this “summary”, it becomes possible to easily grasp the content of discussion within the community.
[0007]
However, conventionally, since discussions are individually performed for each community, it is difficult to effectively utilize the information even if, for example, similar communities exist.
[0008]
The present invention has been made in view of such circumstances, and can automatically provide effective information from one community to another, and efficiently share knowledge across communities. It is an object of the present invention to provide a knowledge storage support system and a public summary providing method in the system.
[0009]
[Means for Solving the Problems]
In order to solve the above problems, the present invention is configured to be connectable to a plurality of client terminals via a network, and supports accumulation of knowledge by classifying and accumulating messages posted to the virtual community from each client terminal. In the knowledge storage support system, in order to allow message posting from the client terminal, an access control unit that performs user authentication with respect to the access request source client terminal and a place for discussion between the plurality of client terminals A plurality of virtual communities are managed, community processing means for classifying and storing messages posted to each virtual community from each client terminal permitted to access by the access control means, and stored in the virtual community. Summarize the message group by topic Discriminating similarities between a means for managing summary information for each virtual community and a predetermined virtual community having public summary information having public attributes and other virtual communities, and other similar virtual communities Public summary information providing means for providing the public summary information to the community The public summary information providing means determines the similarity of the discussion between the virtual communities based on the similarity between the public summary information in the predetermined virtual community and all the summary information in the other virtual communities. Discriminate It is characterized by that.
[0010]
In this knowledge storage support system, messages exchanged between users in a virtual community are classified and stored for each topic, and thus individual knowledge included in conversations exchanged between a plurality of users is automatically collected. In addition, since there is a public summary information provision means, if there is another virtual community that has a similar discussion with the virtual community that already has the public summary information, the public summary information is automatically separated. It is provided as reference information for the virtual community. Therefore, in the virtual community under discussion, more dense discussion can be performed, and in some cases, the conclusion of the discussion can be easily derived. Further, the existence of a similar virtual community is clarified, and it becomes possible to perform cooperation or integration between similar communities as necessary.
[0011]
The similarity of discussion between virtual communities is determined from the similarity between public summary information in a predetermined virtual community and all summary information in the other virtual communities. So It is possible to determine the similarity of discussion more efficiently than when comparing all messages.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 shows the configuration of a knowledge storage support system according to an embodiment of the present invention. This knowledge accumulation support system is used as a knowledge management system having a knowledge accumulation support function, and classifies and accumulates knowledge using a virtual community that can be commonly used by a plurality of client terminals 11. Before describing a specific configuration, first, an outline of the knowledge storage support system according to the present embodiment will be described with reference to FIGS. 2 to 5.
[0013]
As shown in FIG. 2, knowledge includes “formal knowledge” and “implicit knowledge”. Currently, a system for organizing and managing formalized information (formal knowledge) such as a document management system and a Web server is being completed. However, in fact, they do not cover all of the “knowledge accumulation”. This is because there is very unclear information, such as light conversations that are exchanged by e-mail and knowledge that is only in each person's head. This is what we call “Tacit Knowledge”. How to handle this tacit knowledge and share it is important. In the conventional system, it is difficult to support the accumulation of tacit knowledge, and a system for handling tacit knowledge is required.
[0014]
The knowledge accumulation support system according to this embodiment is a tool for formalizing information called tacit knowledge and promoting the accumulation of knowledge. A group discussion is performed in a virtual community in the form of an electronic bulletin board, and a message ( Articles) are classified and accumulated for each topic. A “summary” can be created for one topic (hereinafter referred to as a thread). A thread means a bundle of related knowledge on a virtual community. “Summary” is a message having a role as a kind of minutes for summarizing discussions in a group, and can be created for each thread.
[0015]
Posting a message is performed by input from an e-mail or a Web browser, and the posted message is stored in a server constituting the knowledge storage support system. In this knowledge accumulation support system, it is possible to post messages by e-mail, and it also has a side as a mailing list. Each user simply has a conversation by e-mail, and tacit knowledge is accumulated without knowing it. This is shown in FIG.
[0016]
FIG. 3 shows a “sports community” that is a virtual community related to sports, an “English study group community” that is a virtual community related to English study groups, and a “XX development member community” that is a virtual community between development members. It is shown. Post messages from each user are classified and stored for each virtual community, and are classified for each thread in each virtual community. In FIG. 3, “sports community” currently stores messages related to three types of topics, threads 1, 2, and 3. Also, “English study community” relates to two types of topics, threads 1 and 2. A message is accumulated, and “○ × development member community” shows a case where a message relating to one topic of thread 1 is accumulated. Messages posted to these virtual communities are accumulated as knowledge information in a knowledge database (knowledge DB) in the same way as other knowledge (form knowledge collected from webs, workflows, filing systems, etc.). In particular, by collecting the “summary” created for each thread in the knowledge DB and applying it in preference to other messages as search targets such as full-text search and natural language search, It is possible to efficiently use “message flow” as static stock information.
[0017]
<Site>
In this specification, the server function of this knowledge storage support system is called a “site”. An administrator user (Administrator) exists in the site and manages site information. The site information includes the following.
[0018]
(1) User information
Information about who can use the site
Can be registered, deleted or changed by site administrator
(2) Community creation authority information
Permission information for creating a virtual community
A virtual community (hereinafter simply referred to as a community) is a kind of electronic bulletin board that can be used in common by multiple users for posting and viewing messages, and people who gather for the same purpose communicate with each other. Indicates “place”. Each user obtains necessary knowledge or posts a message (article) by accessing a community having a theme suitable for the purpose. Each community has at least one administrator (the community creator is the administrator by default but can be changed). Authority regarding community creation can be selected from the following two.
[0019]
・ All registered users can create communities.
[0020]
・ Only users who are approved by the site administrator can create a community.
[0021]
(3) Community category information
Category information for classifying communities
This can be registered, deleted, and changed by the site administrator.
[0022]
<Community>
Next, the community will be described. Community information (community properties) for managing each community includes the following.
[0023]
(1) Name
The name of the community.
[0024]
(2) Posting email address
An email address for each community. When the user sends an email to this address, the content is automatically registered as a new post message in the corresponding community.
[0025]
(3) Subject information of received mail
In the form of participation in the community, “subscribe on the web” for viewing and posting messages through a web browser, and automatic mail distribution service for newly posted messages in addition to viewing and posting messages through the web browser are available. "Subscribe via email". For users who have selected “subscribe by email”, when a new message is posted to the community, the new posted message is automatically delivered by e-mail. At that time, the “subject information of received mail” (for example, information such as {community name, message number}) is added to the subject information of the distributed electronic mail.
[0026]
(4) Creator
User name that created the community.
[0027]
(5) Creation date
The date when the community was created.
[0028]
(6) Community introduction
A brief introduction to the community.
[0029]
(7) Community category
As described above, communities can be classified into categories according to their contents, and information related to the category to be classified is held for each community. The category registered by the site administrator is used.
[0030]
(8) Community type
It means the public level of the community. There are three community disclosure levels: a “public system” for free participation, a “member system” consisting of a group of approved participants, and a “private system” that is not open to non-approved participants.
[0031]
(9) Statistical information
This includes the number of users belonging to each community and the number of utterances by participant.
[0032]
(10) Administrator
The name of the administrator who manages this community.
[0033]
(11) Member
Users belonging to (accessible to) this community.
[0034]
(12) Message deletion authority
Users who are allowed to delete posted messages. One of the following can be selected.
[0035]
・ Community manager only
・ Community managers and contributors
<Messages and threads>
Next, messages and threads will be described.
[0036]
A message is an individual statement (posting of articles) exchanged in a conversation within a community. A plurality of files can be attached to the message. A message can be posted by input from a web browser or by sending mail to a mail address held by the community.
[0037]
On the other hand, a thread is a bundle of messages related to a certain topic as described above. Conversation progresses with various opinions (messages) on one topic, and a conclusion is drawn. This conclusion is a “summary”. This knowledge storage support system has a creation support function related to “summary” and an information providing function. By using the creation support function, it is possible to easily create a “summary” as a conclusion of a topic while using a message or an attached file in the corresponding thread. In addition, by using the information providing function, reference information can be automatically provided from a community in which a “summary” has already been created to another community having a similar discussion.
[0038]
FIG. 4 shows an example of a hierarchical structure of messages constituting a thread. In FIG. 4, thread 1 includes five messages 1, 2, 3, 4, and 5. The thread 1 has a structure in which a message 1 is first posted, messages 2 and 3 are posted as reply (response) messages to the message 1, and a message 4 is posted as a reply (response) message to the message 3, Furthermore, it corresponds to the case where message 5 is posted as a reply (response) message to message 1.
[0039]
The thread 2 is also composed of five messages 1, 2, 3, 4, and 5. This is because messages 2 and 3 are posted as reply (response) messages to the first posted message 1, This corresponds to the case where messages 4 and 5 are posted as reply (response) messages to message 3.
[0040]
When a message different from the reply to each message of threads 1 and 2 is newly posted to the same community as threads 1 and 2, thread 3 is assigned to the newly posted message. .
[0041]
<Summary>
“Summary” is a “conclusion” for conversation (thread) as described above. Speaking at a meeting such as a workplace, it corresponds to a “minutes”, and for example, a development corresponds to a “specification” for a review. As shown in FIG. 5, one “summary” corresponds to one thread. That is, a “summary” summed up for each thread is created by a user or an administrator, and managed as a special form of a message constituting the corresponding thread. A plurality of files can be attached to the “summary” in the same manner as other normal messages.
[0042]
The “summary” can be revised, and a new “summary” can be created by updating the already created “summary” and registered as the latest “summary”.
[0043]
<Posting messages by email>
Messages posted to each community by mail are processed in the following procedure.
[0044]
(1) A user posts a message by e-mail to an e-mail address assigned to a post-destination community.
[0045]
(2) The server of the knowledge storage support system collects all mails addressed to all communities from the mail server.
[0046]
(3) The server of the knowledge storage support system determines which message is addressed to which community based on the posting destination mail address, and distributes it.
[0047]
(4) Based on the header information (or title) of the acquired mail, the server of the knowledge storage support system determines which level of which thread in the corresponding community is registered, and sends the text of the acquired mail there Register as
[0048]
Messages posted to the community by e-mail are automatically stored in the corresponding locations by the above processing. The user only needs to post a message with the same feeling as posting to the mailing list.
[0049]
<Message subscription type>
As described above, the user using the knowledge storage support system can select the following two types as the message subscription type.
[0050]
・ Subscription by web browser (access to URL (Uniform Resource Locator) of knowledge storage support system)
・ Email subscription
Regardless of the subscription type selected by the user, subscription (including posting) from the web browser is possible. In other words, when a new message is posted, it is selected whether or not the message is automatically delivered by mail. When a new message is posted, the message is delivered to the user who has selected mail subscription. Further, the user can post a reply message only by replying to the distributed mail. This subscription type can be selected for each community to which the user belongs.
[0051]
<System configuration>
Next, the system configuration of the knowledge accumulation support system according to this embodiment will be described with reference to FIG.
[0052]
The knowledge storage support system of this embodiment is realized by a server computer 12 that can be connected to a plurality of client terminals 11 via a computer network 13 such as a LAN. Although not shown, the server computer 12 and the client terminal 11 each have a CPU, a main memory, a magnetic disk device as a storage device, and an input / output device having an input unit such as a keyboard and a mouse and a display unit such as a display. Is provided.
[0053]
In the client terminal 11, either one or both of the Web browser 111 and the mail client 112 are operating. A URL (Uniform Resource Locator) indicating a resource for supporting knowledge accumulation constructed on the server computer 12 is designated from the Web browser 111, or a mail client addressed to a mail address of each community managed by the community server 122 By transmitting mail from 12, the knowledge accumulation support process can be used from each client terminal 11.
[0054]
The knowledge accumulation support function of the server computer 12 mainly includes software such as the control unit 121, the community server 122, the web server 127, and the mail server 128, and management used for posting and browsing messages by these software. Realized by information and real data. The management information includes login management information 123 for performing user authentication for each client terminal 11 and community management information 124 for performing management for each community. Message data 125 and an attached file 126 exist.
[0055]
The control unit 121 is for controlling the overall operation related to knowledge accumulation support, and has a mediation function between the community server 122, the web server 127, and the mail server 128, which is the core program of this knowledge accumulation support system. First, each client terminal 11 has a user authentication function when logging in to the community server 122 through the web server 127 and the mail server 128. For this user authentication, the control unit 121 manages login management information 123. The login management information 123 stores user IDs and passwords of the users participating in the knowledge storage support system. By this user authentication, control of permission / prohibition of access to the community server 122 performed for posting a message from each client terminal 11 is performed.
[0056]
The community server 122 is for managing and operating a community in which a plurality of client terminals 11 can participate, and classifies and stores messages posted from each client terminal 11 for each community and for each topic (thread). To do. Management and operation of each community by the community server 122 is performed using the community management information 124, the message data 125, and the attached file 126. That is, the community management information 124, the message data 125, and the attached file 126 are used as a database for storing and managing messages for each community.
[0057]
Further, the community server 122 is provided with a summary management image 129 and a summary providing unit 130. The summary management unit 129 performs summary management for managing messages classified and accumulated for each community and for each topic (thread). “Summary” is posted as one message. For example, a summary of all messages in a thread may be automatically created and posted as “summary” of the corresponding thread. In addition, when there are communities that have discussions similar to each other, the summary providing unit 130 performs processing for automatically providing “summary” in a certain community to another similar community as reference information. . This “summary” information provision is performed by posting a message related to “summary” accumulated in one community to another community.
[0058]
Next, each table constituting the community management information 124 will be described.
[0059]
As shown in FIG. 1, the community management information 124 includes a user table 201, a community table 202, a subscription type table 203, a member table 204, a thread table 205, a message table 206, a summary table 207, and the like. . Hereinafter, each of these tables will be described.
[0060]
<User table>
FIG. 6 is a diagram illustrating a configuration example of a user table 201 for managing users. The user table 201 stores a user ID, a user name, and an e-mail address for each user participating in the knowledge storage support system. In FIG. 6, the user ID “U00001”, the user name “Ichiro Tanaka”, the mail address “ichiro.tanaka@xxxx.co.jp”, the user ID “U00002”, the user name “Taro Yamada”, the mail address An example in which the user “taro.yamada@xxxx.co.jp” is registered is shown.
[0061]
<Community table>
FIG. 7 is a diagram illustrating a configuration example of the community table 202 for managing communities. The community table 202 is a table for managing each community created on the knowledge accumulation support system and users participating in each community. Here, the community table 202 is created on the knowledge accumulation support system. For each, a community ID, a community name, a community type, and a member ID list of each member participating in the community are stored. In FIG. 7, a community having a community ID “C001” and a community name “community A” has a public level “public”, and users assigned member IDs “M000001”, “M000004”,. In addition, the community with the community ID “C002” and the community name “community B” has a public level of “member system”, and users who are assigned member IDs “M000002”, “M000003”,. It shows the case. The member ID is unique across all communities, and each user is assigned the same number of member IDs as the number of participating communities.
[0062]
<Subscription type table>
FIG. 8 is a diagram illustrating a configuration example of a subscription type table 203 that manages subscription types. In the subscription type table 203, the user ID, the user name, the community ID of the participating community, the subscription type for the community, and the user type when the subscription type is e-mail for each user participating in the knowledge accumulation support system are displayed in the subscription type table 203. An email address is stored. When managing e-mail addresses in the user table 201, it is not always necessary to register e-mail addresses in the subscription type table 203. Conversely, the e-mail address is not managed in the user table 201, and the subscription type is Only the user's mail address in the case of mail may be managed in the subscription type table 203.
[0063]
In FIG. 8, the user with the user ID “U00001” and the user name “Ichiro Tanaka” participates in two communities with community IDs “C001” and “C002”, and the community with the community ID “C001” The subscription type for web is the web, the subscription type for the community with the community ID “C001” is email, and the user with the user ID “U00002” and the user name “Taro Yamada” is the community with the community ID “C005”. It shows a case where the user is participating and the subscription type regarding the community is web.
[0064]
<Member table>
FIG. 9 is a diagram showing a configuration example of the member table 204 for managing members. The member table 204 stores, for each member ID, a member type indicating a participation attribute relating to a community in which the member ID participates, and user names of users who participate as members. Member types include “participants” who have been approved for participation, “temporary registrants” who have been temporarily registered as participants, “participants who have applied for participation but have not been approved”, and procedures regarding participation. There is “anonymous” who participates as a kind of guest without going.
[0065]
In FIG. 9, the user with the user name “Ichiro Tanaka” participates in the community participating as the member ID “M000001” with the member type “participant” and the member ID “M000003”. The member type of the user who has the user name “Taro Yamada” is “provisional” for a community that is participating as the member ID “M000002”. The case where the member type is “anonymous” is shown for a community participating as “registrant” and member ID “M000004”.
[0066]
<Thread table>
FIG. 10 is a diagram illustrating a configuration example of a thread table 205 for managing threads. The thread table 205 stores a community ID for each community and a thread ID list including thread IDs of the threads generated in the community. The thread ID is also a unique value for all communities.
[0067]
In FIG. 10, the community with the community ID “C001” includes threads with the thread IDs “T01001”, “T01002”,..., And the community with the community ID “C002” has the thread IDs “T02001”,. This shows the case where the thread is included.
[0068]
<Message table>
FIG. 11 is a diagram showing a configuration example of the message table 206 for managing messages. The message table 206 stores a message ID of each message constituting each thread ID and a URL indicating the location of actual data of the corresponding message stored as the message data 125. This URL may be uniquely specified from the corresponding thread ID and message ID. In this case, the URL field is unnecessary.
[0069]
<Summary table>
FIG. 12 is a diagram illustrating a configuration example of a summary table 207 for managing “summary” created for each thread. In the summary table 207, for each thread ID, the message ID of the message created and registered as the “summary” of the thread, the version number of each message when a plurality of “summary” is created and registered, and the message data The URL indicating the location of the actual data of the message regarding the corresponding “summary” stored as 125 is stored.
[0070]
Similarly to the case of the message table 206, the URL of the summary table 207 may be uniquely specified from the corresponding thread ID and message ID. In this case, the URL field is unnecessary.
[0071]
Here, a summary message management process in the knowledge storage support system executed by the summary management unit 129 of the community server 122 will be described.
[0072]
First, an example of the state transition of the screen displayed by the Web browser 111 of the client terminal 11 in this knowledge storage support system will be described with reference to FIGS. 13 and 14.
[0073]
FIG. 13 is a diagram showing the state transition of the Web browser screen when the summary is revised, and (A) shows the display of a thread that is the unit of the first conversation whose community name is “public”. In this situation, if you click the “New Summary” button, the screen will move to the screen for creating a summary message summarizing this thread, and the message created on that screen will be posted as a summary message. The summary data 207 is stored in the summary table 207 of the information 124 and the message data 125.
[0074]
(B) “Summary revision” button to create a new summary message and revise it when more messages are posted and knowledge is accumulated in the thread after the first summary message is created Shows the situation of clicking. If you click the “Summary revision” button here, you will be redirected to a screen for creating a summary message that summarizes this thread, and the message created on that screen will be posted as a summary message. The summary data 207 is stored in the summary table 207 of the management information 124 and the message data 125. The summarizing unit 129 of the community server 122 manages the revision of the summary message and the version management thereof.
[0075]
(C) shows a situation in which after the creation of the summary message and subsequent posting of the message are repeated several times, the “summary revision” button is clicked to recreate and revise the summary message again. Show.
[0076]
In other words, for a plurality of summary messages created in this way, when a new summary message is created in this knowledge accumulation support system, the existing summary message is buried as a single message equivalent to other messages. Instead, revision / version management is performed to enable tracking of summary messages.
[0077]
FIG. 14 is a flowchart showing the procedure of the summary message revision and its version management process.
[0078]
When the user makes a login request to the control unit 121 of the server computer 12 via the Web browser 111 (step A1), the control unit 121 logs in to manage whether the user ID and password input by the user are registered. 123 is accessed (step A2), and user authentication is performed to determine whether or not this login is permitted (step A3). If the user ID and password are not registered in the login management information 123 and the login fails (NO in step A3), the control unit 121 returns a login failure to the web browser 111 through the web server 127 and ends this process. (Step A4).
[0079]
On the other hand, when the user ID and password are registered in the login management information 123 and the login is successful (YES in step A3), the summary management unit 129 of the community server 122 performs community management from the specified community name and thread ID. The message of the community and the thread managed in the message table 206 and the summary table 207 of the information 124 is searched and returned to the Web browser 111 (step A5).
[0080]
When the web browser 111 displays the screen shown in FIG. 13 based on the data returned from the community server 122 (step A6), the user creates a summary message (step A7). The summary operation information (new creation or revision) including the created summary message is transmitted to the community server 123 (step A8).
[0081]
Then, the summary management unit 129 of the community server 122 issues a message ID to the summary message based on the received summary operation information, and stores the issued message ID and version number in the summary table 207. The data itself is stored in the message data 125 (step A9).
[0082]
<Community type and summary>
Next, the relationship between the “summary” created and managed for each thread in each community as described above and the community type of the community will be described.
[0083]
As described above, there are three types of community types: “open system” for free participation, “member system” consisting of a group of approved participants, and “private system” that is not open to non-approved participants. is there. A summary in a “public” community is in principle public, and a summary in a “private” community is non-public information that can only be referenced by regular participants in the community. Furthermore, in the “member system” community, there is a “public summary” that means that it is made public to members other than the participants, and a “private summary” that is not open to members other than the participants. . Whether it is “public summary” or “private summary” can be determined by the manager of the community or the contributor of the summary message.
[0084]
The provision of “summary” by the summary providing unit 130 is intended only for “public summary”, and not for “non-public summary”.
[0085]
<Provision of summary>
Next, with reference to FIG. 15, an operation of providing “public summary” by the summary providing unit 130 will be described.
[0086]
In FIG. 15, community 100 (community A) is an existing community for which “public summary” has already been created, and community 200 (community B) is a community currently under discussion in which messages from each user are posted sequentially. It is.
[0087]
In the community 100 (community A), a message file 101 storing messages posted from each user and a summary file 102 storing “summary” posted from each user have already been constructed. Each of the message file 101 and the summary file 102 includes message data registered in the message data 125. On the other hand, the community 200 (community B) has a message file 201 in which messages posted from each user are stored, and “summary” has already been created as a summary file 202 in the thread. Is also present.
[0088]
The community server 122 monitors various communities constructed in this system, and checks whether similar contents are being discussed, so that the existing community (in the case of FIG. 15, community 100) is summarized. The “public summary” is read from the summary file 102 and analyzed by the morpheme analysis unit 301 in the summary providing unit 130. Further, the message stored in the summary file 202 of the community 200 that is currently posted is also analyzed by the morpheme analysis unit 301 in the summary providing unit 130. Then, the analysis result is sent to the recommendation control unit 302 in the summary providing unit 130, and the similarity is determined. That is, in this example, in order to determine the similarity of discussion between the communities 100 and 200, the “public summary” in the community that is the information provider and all “summary” in the community that is the information provider Similarity between them is determined using morphological analysis. If the similarity is equal to or higher than a predetermined value, the “public summary” of the community 100 is recommended and posted to the community 200 as reference material under the control of the recommendation control unit 302. This “posted summary” posted as a recommendation is managed as a new thread in the community 200.
[0089]
<Public summary provision processing>
Next, the procedure of the public summary providing process will be described with reference to the flowchart of FIG.
In the morphological analysis unit 301 of the community server 122, first, one “public summary” of the existing community 100 (community A) is read from the summary file 201, and morphological analysis is executed (step S10). Further, all the summaries of the community 200 (community B) are read from the summary file 202, and morphological analysis is executed (step S11). The recommendation control unit 302 of the community server 122 compares the morpheme analysis result of one “public summary” of the community A with the morpheme analysis result of the entire summary of the community B, and determines the similarity (step S12). . In this case, specifically, by performing morphological analysis on each summary to be analyzed, and performing comparison processing for calculating similarity after performing lexical weighting processing on the analysis result The similarity between the “public summary” in the community A and all the “summary” in the community 200 is checked.
[0090]
When the similarity is higher than a predetermined value determined in advance (Yes in step S13), the community server 122 sends the “public summary” of the community A to the community B as a reference material. Is automatically provided (step S14).
[0091]
The provision to the community B is performed in the form of message posting, and the user of the community B can easily refer to it by a normal message subscription means. As described above, “summary” of existing communities to be provided is limited to public summary, and private summary is excluded.
[0092]
As described above, according to the present embodiment, when there is another community that has a discussion similar to a community that already has public summary information, the public summary information is automatically converted to the other community. In the virtual community under discussion, more dense discussions can be made, and in some cases, the conclusion of the discussion can be easily derived. Further, the existence of a similar virtual community is clarified, and it becomes possible to perform cooperation or integration between similar communities as necessary.
[0093]
Since all functions of the knowledge storage support system of this embodiment are realized by a computer program, the computer program is stored in a computer-readable storage medium, and the computer program is connected to a computer network through the storage medium. The effects similar to those of the present embodiment can be obtained simply by installing the system in a possible ordinary computer.
[0094]
Further, the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the invention in the implementation stage. Further, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, the problem described in the column of the problem to be solved by the invention can be solved, and the effect described in the column of the effect of the invention Can be obtained as an invention.
[0095]
【The invention's effect】
As described above in detail, according to the present invention, effective information can be automatically provided from one community to another, and knowledge can be efficiently shared between communities. Become.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a system configuration of a knowledge accumulation support system according to an embodiment of the present invention.
FIG. 2 is a view for explaining knowledge handled by the knowledge accumulation support system of the embodiment;
FIG. 3 is an exemplary view for explaining the principle of knowledge accumulation processing in the knowledge accumulation support system of the embodiment;
FIG. 4 is a view for explaining the relationship between messages and threads managed by the knowledge accumulation support system of the embodiment.
FIG. 5 is an exemplary view for explaining a relationship between a message managed by the knowledge accumulation support system of the embodiment and “summary”.
FIG. 6 is an exemplary view showing an example of a user table used in the knowledge accumulation support system of the embodiment.
FIG. 7 is an exemplary view showing an example of a community table used in the knowledge storage support system of the embodiment.
FIG. 8 is a view showing an example of a subscription type table used in the knowledge accumulation support system of the embodiment.
FIG. 9 is a view showing an example of a member table used in the knowledge accumulation support system of the embodiment.
FIG. 10 is an exemplary view showing an example of a thread table used in the knowledge storage support system of the embodiment.
FIG. 11 is an exemplary view showing an example of a message table used in the knowledge accumulation support system of the embodiment.
FIG. 12 is a view showing an example of a summary table used in the knowledge accumulation support system of the embodiment.
FIG. 13 is a diagram showing a state transition of a Web browser screen when a summary is revised in the knowledge storage support system of the embodiment.
FIG. 14 is a flowchart showing summary creation and management processing in the knowledge storage support system of the embodiment;
FIG. 15 is a view for explaining a summary providing operation in the knowledge accumulation support system of the embodiment;
FIG. 16 is an exemplary flowchart showing the procedure of a summary providing process in the knowledge storage support system of the embodiment;
[Explanation of symbols]
11 ... Client terminal
12 ... Server computer
111 ... Web browser
112 ... Mail client
121 ... Control unit
122 ... Community server
123 ... Login management information
124 ... Community management information
125 ... Message data
126 ... Attached file
127 ... Web server
128 ... Mail server
129 ... Summary Management Department
130 ... Summary providing department
201 ... user table
202 ... Community table
203 ... Subscription type table
204: Member table
205 ... Thread table
206 ... Message table
207 ... Summary table

Claims (4)

A knowledge accumulation support system configured to be connectable to a plurality of client terminals via a network, and supporting accumulation of knowledge by classifying and accumulating messages posted from each client terminal to a virtual community,
Access control means for performing user authentication with respect to the client terminal of the access request source in order to permit message posting from the client terminal;
Community processing for managing a plurality of virtual communities as a forum for discussion between a plurality of client terminals, and classifying and storing messages posted to each virtual community from each client terminal permitted to access by the access control means. Means,
Means for managing, for each virtual community, summary information summarizing each group of messages stored in the virtual community;
Disclosure of similarity between discussions between a predetermined virtual community having public summary information having public attributes and other virtual communities, and providing the public summary information to other similar virtual communities A summary information providing means ,
The public summary information providing means determines similarity of discussion between the virtual communities based on the similarity between the public summary information in the predetermined virtual community and all the summary information in the other virtual communities. Knowledge storage support system characterized by that. The public summary information providing means includes:
Means for morphological analysis of public summary information in the predetermined virtual community and all summary information in the other virtual community;
Means for comparing the results of the morphological analysis to determine the similarity between them;
The knowledge storage support system according to claim 1, further comprising means for providing the public summary information to the other virtual community when the similarity is higher than a predetermined value. This is a public summary providing method in a knowledge accumulation support system that is configured to be connectable to a plurality of client terminals via a network and supports the accumulation of knowledge by classifying and accumulating messages posted from each client terminal to the virtual community. And
An access control step in which the knowledge storage support system performs user authentication for the client terminal of the access request source in order to allow message posting from the client terminal;
The knowledge storage support system manages a plurality of virtual communities as a forum for discussion between a plurality of client terminals, and messages posted to the virtual communities from each client terminal permitted to access by the access control step for each topic. Community processing steps to categorize and accumulate
The knowledge storage support system manages, for each virtual community, summary information summarizing the messages stored in the virtual community for each topic;
The knowledge storage support system determines similarity of discussion between a predetermined virtual community having public summary information having a public attribute and other virtual communities, and the similar virtual community A public summary information providing step for providing public summary information ;
In the public summary information providing step, the knowledge accumulation support system is configured such that, based on the similarity between the public summary information in the predetermined virtual community and all the summary information in the other virtual communities, the virtual community A public summary providing method in a knowledge accumulation support system , comprising a step of discriminating similarity of discussions . In the public summary information providing step, the knowledge storage support system performs a morphological analysis on the public summary information in the predetermined virtual community and all the summary information in the other virtual community, and the knowledge storage support system. provided but determining a therebetween similarity by comparing the results of the morphological analysis, if the similarity is higher than a predetermined value, the collaborative knowledge system, the public summary information to the other virtual communities 4. A public summary providing method in a knowledge storage support system according to claim 3 , further comprising the step of:

Images