JP2002342339A - Knowledge accumulation support system and link control method of summary message in the system - Google Patents

Abstract

(57) [Summary] [Problem] A knowledge accumulation support system that can easily associate another summary message or an attached file of another message when a summary message is created. A community server 122 classifies and exchanges messages exchanged between users on a virtual community for each topic. The community server 122 includes a summary link control unit 129.
When creating a summary message that categorizes and accumulates messages for each topic, the community management information 124
Provides a user interface for associating other summary messages and attachments of other messages managed by the summary message being created with the summary message created there, and other summary messages and other messages associated therewith. Is managed using the community management information 124.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a knowledge accumulation support system used in a knowledge management system and a link control method of a summary message in the knowledge management system, and more particularly to a knowledge storage system using a virtual community in which an unspecified number of users participate. TECHNICAL FIELD The present invention relates to a knowledge accumulation support system for supporting accumulation of information and a link control method of a summary message in the system.

[0002]

2. Description of the Related Art In recent years, the introduction of groupware for sharing information among a plurality of users, mainly in companies, has been promoted. E-mail systems and workflow systems are known as typical groupware,
Recently, a knowledge management system for sharing knowledge and information has been developed.

This knowledge management system is called W
It is used to store and manage personal know-how as a knowledge database in addition to eb information and electronic file information, etc. Combined with search functions such as natural language search, knowledge and information can be used efficiently. Becomes

[0004] In such a knowledge management system, how to collect and accumulate knowledge such as individual know-how is important. 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 accumulate it. .

Therefore, recently, there has been a demand for the development of a knowledge management system having a knowledge accumulation support function. By implementing a mechanism that automatically collects and accumulates knowledge such as individual know-how, the knowledge as tacit knowledge can be used in the same way as formal knowledge such as Web information and electronic file information Becomes possible.

[0006]

In this knowledge management system, generally, knowledge such as individual know-how is collected and accumulated, and then, in order to summarize the knowledge, a so-called summary is created for each topic, for example. However,
In the past, when creating a summary, there was no mechanism for associating other existing summaries or incorporating attached information added to a piece of knowledge into the summary. A cumbersome operation had to be performed, such as opening the attached information and copying the contents into the summary being created.

[0007] When a large amount of other summary or attached information is to be taken in, the user is repeatedly forced to perform such troublesome work, and in some cases, an inconsistent and meaningless summary may be created. There was a fear.

[0008] The present invention has been made in view of such circumstances, and enables the realization of a mechanism for automatically and efficiently collecting and accumulating knowledge, such as personal know-how, and sharing various knowledge. It is an object of the present invention to provide a knowledge accumulation support system and a summary message revision management method in the system.

[0009]

In order to achieve the above object, the present invention is configured to be connectable to a plurality of client terminals via a network, and to classify messages posted from each client terminal to a virtual community. Access control means for performing user authentication on a client terminal of an access request source, in order to permit message posting from the client terminal, Community processing means for managing a virtual community in which a plurality of client terminals can participate, classifying messages posted to the virtual community from each client terminal permitted to access by the access control means for each topic, and accumulating the messages; The community processing means is for each of the topics Class provides a collaborative knowledge system characterized by comprising a link control means for associating attachments other summary message or other message in the summary message summarizing the accumulated messages.

In this knowledge accumulation support system, by having a mechanism for associating another summary message or an attached file of another message, it is possible to prevent the user from having to perform a complicated operation, This makes it possible for the user to easily understand the relationship between the message and the other summary message or the attached file of the other message.

[0011]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 shows a configuration of a knowledge accumulation 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 accumulation support system according to the present embodiment will be described with reference to FIGS. 2 to 5.

As shown in FIG. 2, there are “formal knowledge” and “implicit knowledge” in knowledge. Currently, formalized information (formal knowledge) such as document management systems and Web servers
The system of organizing and managing is being completed. However, they do not actually cover all of the "knowledge accumulation" points. This is because there is very unclear information, such as light conversations simply exchanged by e-mail and knowledge only in each person's head. This is what is called "tacit knowledge". It is important to handle this tacit knowledge well and to share it. With conventional systems, it is difficult to support the accumulation of tacit knowledge, and a system for handling tacit knowledge is needed.

The knowledge accumulation support system of this embodiment is
It is a tool that formalizes such information called tacit knowledge and promotes the accumulation of knowledge. Discussions in groups are conducted in a virtual community in the form of electronic bulletin boards, messages (posted articles) are classified by topic,
accumulate. A summary can be created for one topic (hereinafter referred to as a thread). A thread represents a bundle of related knowledge on a virtual community. The summary is a message that serves as a kind of minutes that summarizes the discussion in the group, and can be created for each thread.

The posting of the message can be made by e-mail or W
The posted message made by input from the web browser is stored in a server constituting the knowledge storage support system. In this knowledge accumulation support system, it is also possible to post a message by e-mail, and it has an aspect as a mailing list. Just by each user having a conversation by e-mail, tacit knowledge is accumulated without knowing it. This is shown in FIG.

FIG. 3 shows a “sports community” which is a virtual community related to sports, an “English study group” which is a virtual community related to an English study group, and a “○ × development member” which is a virtual community between certain development members. Community ". Post messages from each user are classified and accumulated for each of these virtual communities, and are classified for each thread within each virtual community. In FIG. 3, messages about three types of topics, threads 1, 2, and 3, are currently stored in the "sports community", and messages about two types of topics, threads 1 and 2, are stored in the "English study community". The message is accumulated, and the case where a message relating to one topic of the thread 1 is accumulated in the “XX development member community” is shown. The messages posted to each of these virtual communities are based on other knowledge (w
eb, workflow, formal knowledge collected from a filing system, etc.), and stored as knowledge information in a knowledge database (knowledge DB). In particular, by collecting the "summary" created for each thread in the knowledge DB and applying it to other messages as a search target, for example, a full-text search or a natural language search, so as to be called flow information, "Message flow" can be efficiently used as static stock information.

<Site> In this specification, the server function of this knowledge accumulation support system is called a "site". The site has an administrator user (Administrator)
Exists and manages site information. The site information includes the following.

(1) User information Information about users who can use the site. A site administrator can register, delete, and change the information. (2) Authority information for creating a community Authority information for creating a virtual community , Just say community)
Is a kind of electronic bulletin board that can be used in common by a plurality of users for posting and browsing a message, and indicates a "place" where people gathering with the same purpose communicate. Each user gains necessary knowledge and posts a message (article) by accessing a community with a theme that meets the purpose.
Each community has at least one administrator (community creator is the default administrator but can be changed).
The authority for community creation can be selected from the following two.

All registered users can create a community.

[0020] Only users approved by the site administrator
Create communities.

(3) Category information of community Category information for classifying communities This can be registered, deleted, or changed by a site administrator.

<Community> Next, the community will be described. Community information (community properties) for managing each community includes the following.

(1) Name The name of the community.

(2) Posting mail address A mail address for each community. When the user sends an e-mail to this address, the contents are automatically registered as a new posted message in the corresponding community.

(3) Subject Information of Received Mail In the form of participation in the community, a message is browsed and posted via a web browser, and "subscribe by web"
In addition to browsing and posting messages through the web browser, there is "subscribe by e-mail" in which an automatic mail distribution service for newly posted messages can be received. When a new message is posted to the community for a user who has selected "subscribe by e-mail", the newly posted message is automatically distributed by e-mail. that time,
The Subject information of the delivered e-mail includes the “Subject information of the received e-mail” (for example, {community name,
Information such as message number｝) is added.

(4) Creator Name of the user who created the community.

(5) Creation Date The date when the community was created.

(6) Introduction of community A brief introduction sentence of the community.

(7) Categories of Communities As described above, communities can be classified into categories according to their contents, and information on categories to be classified is held for each community. The category is
Use the one registered by the site administrator.

(8) Community type It means the public level of the community. There are three public levels of the community: a "public system" of free participation, a "member system" consisting of a group of approved participants, and a "private system" that is not disclosed to anyone other than the approved participants.

(9) Statistical information The statistical information includes, for each community, the number of users belonging to the community, the number of utterances by participant, and the like.

(10) Administrator The name of the administrator who manages this community.

(11) Member A user belonging to (accessible to) this community.

(12) Message deletion authority A user who is allowed to delete posted messages. You can select one of the following.

Community managers only Community managers and contributors <Messages and threads> Next, messages and threads will be described.

A message is an individual statement (posting of an article) exchanged in a conversation in a community. It is possible to attach multiple files to the message. The message can be posted by inputting from a web browser or sending an e-mail to an e-mail address of the community.

On the other hand, a thread is a bundle of messages related to a certain topic as described above. Conversation proceeds with various opinions (messages) for one topic, and comes to a conclusion. This conclusion is the “summary”.
This knowledge accumulation support system also has a creation support function for “summary”. By using the creation support function, it is possible to easily create a “summary” as a conclusion of a topic while using the message or the attached file in the corresponding thread.

FIG. 4 shows an example of a hierarchical structure of messages constituting a thread. In FIG. 4, a thread 1 includes five messages 1, 2, 3, 4, and 5. The structure of the thread 1 is as follows. First, a message 1 is posted, and a reply (response) to the message 1 is made.
Messages 2 and 3 are posted as messages, message 4 is posted as a reply (response) message to message 3, and message 5 is posted as a reply (response) message to message 1.

Thread 2 also has five messages 1,
2, 3, 4, and 5, in which messages 2 and 3 are posted as reply (response) messages to message 1 posted first, and messages are returned as reply (response) messages to message 3 This corresponds to the case where 4, 5 are posted.

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. Will be.

<Summary>"Summary" is the "conclusion" for a conversation (thread) as described above. In meetings such as workplaces, it is equivalent to "minutes", and for example, in the case of development, it is equivalent to "specifications" for reviews. As shown in FIG. 5, one “summary” corresponds to one thread. In other words, a "summary" is created for each thread by the user or the administrator, and is managed as a special form of a message constituting the corresponding thread. A plurality of files can be attached to the “summary” similarly to other ordinary messages.

The "summary" can be revised,
A new “summary” can be created by updating the already created “summary” and registered as the latest “summary”.

<Posting of Messages by E-mail> Messages posted to each community by e-mail
It is processed in the following procedure.

(1) The user posts a message by mail to the mail address assigned to the posting destination community.

(2) The server of the knowledge accumulation support system
Get all mails sent to all communities from the mail server.

(3) The server of the knowledge accumulation support system
Judgment to which community the message is sent is made according to the posting destination email address, and sorting is performed.

(4) The server of the knowledge accumulation support system
Based on the header information (or title) of the obtained mail, it is determined which thread and which layer in the corresponding community is to be registered, and the body of the obtained mail is registered as a message there.

The message posted to the community by e-mail is automatically stored in the corresponding place by the above processing. The user need only post the message in the same manner as posting to the mailing list.

<Message Subscription Type> A user using the knowledge accumulation support system can select the following two types of message subscription types as described above.

Subscription by Web Browser (Access to URL (Uniform Resource Locator) of Knowledge Storage Support System) Subscription by E-mail Subscription (including posting) from Web browser is performed regardless of which subscription type the user selects. It is possible. That is, when a new message is posted, whether to automatically distribute the message by mail is selected. When a new message is posted, the message is delivered to the user who has selected the mail subscription. The user can post a reply message only by replying to the delivered mail. The selection of the subscription type can be made for each community to which the user belongs.

<System Configuration> Next, referring to FIG.
A system configuration of the knowledge accumulation support system according to this embodiment will be described.

The knowledge accumulation support system of this embodiment is
It is implemented 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 include 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.

In the client terminal 11, one or both of the Web browser 111 and the mail client 112 are operating. URL indicating a resource for supporting knowledge accumulation built on server computer 12
(Uniform Resource Locato
r) is designated from the Web browser 111 or the mail client 12 sends an e-mail to the e-mail address of each community managed by the community server 122 to use the knowledge accumulation support processing from each client terminal 11. be able to.

The knowledge storage support function of the server computer 12 mainly includes the control unit 121 and the community server 12.
2. It is realized by software such as a web server 126 and a mail server 128, and management information and actual data used for posting and browsing messages by the software. The management information includes login management information 123 for performing user authentication for each client terminal 11 and community management information 124 for performing the management for each community. Message data 125
And the attached file 126.

The control unit 121 is for controlling the entire operation related to the knowledge accumulation support. The community server 122, the web server 127 and the mail server 128 which are the core programs of the knowledge accumulation support system.
Starting with the mediation function between them, the web server 127
And a user authentication function when each client terminal 11 logs in to the community server 122 through the mail server 128. For this user authentication, the control unit 121 manages the login management information 123. The login management information 123 stores the user IDs and passwords of the users participating in the knowledge accumulation support system. By this user authentication, access permission / prohibition to the community server 122 for posting a message from each client terminal 11 is controlled.

The community server 122 manages and operates a community in which a plurality of client terminals 11 can participate, and stores messages posted from each client terminal 11 for each community and for each topic (thread). Classify and accumulate. The management and operation of each community by the community server 122 are performed using community management information 124, message data 125, and attached files 126. That is, the community management information 124 and the message data 12
5, and the attached file 126 are used as a database for storing and managing messages for each community.

Further, the community server 122
A summary link control unit 129 is provided. The consolidation link control unit 129 includes the community management information 124
To manage the correspondence between the summary message, the other summary message associated with the summary message, and the attachment of the other message.

Next, each table constituting the community management information 124 will be described.

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 an attached file. It is composed of a table 208 and the like. Hereinafter, each of these tables will be described.

<User Table> FIG. 6 is a diagram showing a configuration example of a user table 201 for managing users. The user table 201 stores a user ID, a user name, and a mail address for each user participating in the knowledge accumulation support system. In FIG. 6, a user with a user ID “U00001”, a user name “Ichiro Tanaka”, a mail address “ichiro.tanaka@xxxx.co.jp”, a user ID “U00002”, a user name “Taro Yamada”, and a mail address "Taro.yamada@xxxx.co.jp"
The example in which the user is registered is shown.

<Community Table> FIG. 7 is a diagram showing a configuration example of a community table 202 for managing a community. The community table 202 is a table for managing each community created on the present knowledge accumulation support system and users participating in each community, and includes a community created on the knowledge accumulation support system. A community ID, a community name, a community type, and a member ID list of each member participating in the community are stored for each. In FIG. 7, a community having a community ID “C001” and a community name “Community A” has a disclosure level of “Public” and member IDs “M000001” and “M00000”.
, The community with the community ID “C002” and the community name “Community B” has the public level “member system” and the member ID “M00000”.
2 ”,“ M000003 ”,... Are assigned. The member ID is unique (unique) throughout the entire community, and each user is assigned the same number of member IDs as the number of participating communities.

<Subscription Type Table> FIG. 8 is a diagram showing a configuration example of a subscription type table 203 for managing subscription types. The subscription type table 203 contains a user ID, a user name, a community ID of a community in which the user participates in the knowledge accumulation support system, a subscription type for the community, and a user type when the subscription type is e-mail. Email address is stored. In the case where the mail address is managed in the user table 201, it is not always necessary to register the mail address in the subscription type table 203. Conversely, the mail address is not managed in the user table 201, and the subscription type is not registered. In the case of mail, only the mail address of the user may be managed in the subscription type table 203.

In FIG. 8, the user ID is “U000
01, and the user with the user name “Ichiro Tanaka” has joined two communities with community IDs “C001” and “C002”, and the community ID “C001”
The subscription type for the community of the community is web, the subscription type for the community of the community ID “C001” is e-mail, and the user ID is “U0000”.
2, the user with the user name "Taro Yamada" has joined the community with the community ID "C005".
The case where the subscription type for the community is web is shown.

<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 regarding a community in which the member ID participates, and a user name of a user participating as a member. Member types include:
"Participants" who have been approved for participation, "Temporary registrants" who are temporarily registered as participants, "Applicants who have applied for participation but have not been approved," There is "anonymous" to participate as a guest.

In FIG. 9, the user having the user name "Ichiro Tanaka" has the member type "participant" for the community in which the member ID is "M000001" and the member ID "M000003". The member type of the participating community is “applicant to join”, and the user with the user name “Taro Yamada” has the member type of the participating community with the member ID “M000002”. Is a “temporary registrant”, and the member type is “anonymous” for a community participating as a member ID “M000004”.

<Thread Table> FIG. 10 is a diagram showing a configuration example of the 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 created in the community. As the thread ID, a unique value is used for all communities.

In FIG. 10, the community ID “C
The thread ID “T0100” is assigned to the community “001”.
, "T01002",..., And the thread with the thread ID "T02001",... Are included in the community with the community ID "C002".

<Message Table> FIG. 11 is a diagram showing a configuration example of the message table 206 for managing messages. The message table 206 stores, for each thread ID, a message ID of each of the messages constituting the thread ID and a URL indicating the location of the actual data of the corresponding message stored as the message data 125. The URL may be uniquely identified from the corresponding thread ID and message ID. In this case, the URL field is unnecessary.

<Summary Table> FIG. 12 shows a summary table 20 for managing “summary” created for each thread.
7 is a diagram illustrating a configuration example of FIG. The summary table 207 includes, for each thread ID, a message ID of a message created and registered as a "summary" of the thread, a version number of each message when a plurality of "summaries" are created and registered, and message data. The URL indicating the location of the actual data of the message related to the “summary” stored as 125 is stored.

As in the case of the message table 206, the URL of the summary table 207 may be uniquely specified from the corresponding thread ID and the message ID. In this case, the URL field is unnecessary. Become.

<Attached File Table> FIG. 13 is a diagram showing a configuration example of an attached file table 208 for managing attached files. In the attached file table 208,
The attachment ID of each attached file of all the posted messages and the URL indicating the location of the actual data of the attached file stored as the attached file 126 are stored.

Here, the link control processing of the summary message in the knowledge accumulation support system, which is executed by the summary link control unit 129 of the community server 122, will be described.

First, referring to FIGS. 14 and 15, in this knowledge accumulation support system,
An example of the state transition of the screen displayed by the Web browser 111 will be described.

FIG. 14 and FIG. 15 are diagrams showing the state transition of the Web browser screen when the content of another summary or attached file is incorporated as the link URL in the creation of the summary. ) Shows a screen display for creating a summary of a thread “YYY” with a community name of “XXX”, for example. In this situation, in order to input the contents of the summary and incorporate the link URL of the other summary into a necessary place, click the “Other summary link” button, and as shown in FIG. Summary List "is displayed on the screen. Here, the check box of the “summary title” to be imported is checked and the “import” button is clicked, and as shown in FIG. 14C, the link URL of this summary is, for example, “URL-summary01” and “URL-summary01”. URL-
It is embedded like "summary03" (a).

Further, to take in the attached file, the user clicks the “link of attached file” button.
Then, as shown in FIG. 15A, an “attached file list” of another message is displayed. Here, check the checkbox of “Attached file name” you want to import,
When the “Import” button is clicked, the link URL of the attached file is changed to, for example, “URL-tem” as shown in FIG.
It is embedded like “pu1-01” and “URL-tempu1-03” (b).

When the "complete" button is clicked, the creation of a plurality of other summaries and a summary including a link URL to an attached file is completed.

FIG. 16 and FIG. 17 are flowcharts showing the procedure of the process of taking in another summary and capturing an attached file when creating the summary.

When the user requests the control unit 121 of the server computer 12 to log in using the Web browser 111 (step A1), the control unit 121 checks whether the user ID and password input by the user have been registered. The user accesses the login management information 123 (step A2), and performs user authentication for determining whether to permit the login (step A3).
The user ID and the password are the login management information 123
If the login has failed and the login has failed (NO in step A3), the control unit 121 reports that the login has failed
The process is returned to the web browser 111 via the b server 127, and the process is terminated (step A4).

On the other hand, if the user ID and the password are registered in the login management information 123 and the login is successful (YES in step A3), the community server 122 sends the message table of the community management information 124 from the designated community name. The message of the community managed by the 206 and the summary table 207 is searched and returned to the Web browser 111 (step A5).

When the Web browser 111 displays the screen shown in FIG. 14 based on the data returned from the community server 122 (step A6), the user puts another summary in the summary currently being created. Click on the “Other Summary Link” button (step A
7). Here, the Web browser 111 displays a “list of other summaries” (step A8).
Check the check box of the "summary title" to be imported and click the "import" button (step A9). Then, the Web browser 111 transmits the operation information input from the screen to the community server 122 (Step A10).

On the other hand, the summary link control unit 129 of the community server 122 searches the summary table 207 for a summary link URL corresponding to the summary based on the received operation information, embeds the link URL in the summary text, and writes the link URL.
b Return to the browser 111 (step A11). And
The Web browser 111 displays a summary text on which a plurality of other summary URLs are fetched on the screen (step A12 in FIG. 17).

Similarly, when the attached files are fetched at once, the “attached file link” is displayed on the screen shown in FIG.
Click the button (step A13). Where W
The web browser 111 displays the "list of attached files" (step A14), and the user checks the checkbox of the "attached file name" to be imported and clicks the "import" button (step A15). . Then, the Web browser 111 transmits the operation information input from the screen to the community server 122 (Step A16).

On the other hand, the summary link control unit 129 of the community server 122 searches the attached file table 208 for the link URL of the attached file corresponding to the summary based on the received operation information, and links the plurality of attached files. Embed the URL in the summary text and Web
It returns to the browser 111 (step A17). The Web browser 111 transmits the URLs of the received plurality of attached files.
The captured summary text is displayed on the screen (step A18). Then, click the "Finish" button,
A new summary is newly stored in the summary table 207 (step A19).

As described above, this knowledge accumulation support system is integrated into the community server 122 and the link control unit 1
29 is provided to provide the user with a function of easily importing another summary message or an attached file of another message when creating the summary message.

Since the functions of the knowledge accumulation support system of this embodiment are all realized by a computer program, the computer program is stored in a computer-readable storage medium, and the computer program is stored through the storage medium. The same effects as those of the present embodiment can be obtained only by introducing the present invention to a normal computer that can be connected to a computer network.

The present invention is not limited to the above-described embodiment, and can be variously modified in an implementation stage without departing from the gist of the invention. Further, the 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 components are deleted from all the components shown in the embodiment, the problem described in the column of the problem to be solved by the invention can be solved, and the effects described in the column of the effect of the invention can be solved. Is obtained, a configuration from which this configuration requirement is deleted can be extracted as an invention.

[0087]

As described in detail above, according to the present invention, it is possible to prevent a user from having to perform a complicated operation by providing a mechanism for associating another summary message or an attachment of another message. It is also possible for the user to easily understand the relationship between the summary message being created and the other summary message or the attached file of the other message to be taken in.

[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 an exemplary 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 an exemplary 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 the relationship between messages 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 accumulation support system of the embodiment.

FIG. 8 is an exemplary view showing an example of a subscription type table used in the knowledge accumulation support system of the embodiment.

FIG. 9 is an exemplary 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 accumulation 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 an exemplary view showing an example of a summary table used in the knowledge accumulation support system of the embodiment.

FIG. 13 is an exemplary view showing an example of an attached file table used in the knowledge accumulation support system of the embodiment.

FIG. 14 is a first diagram showing a state transition of the Web browser screen when another summary or an attached file is incorporated into the content as a link URL in the creation of the summary in the knowledge accumulation support system of the embodiment.

FIG. 15 is a second diagram showing the state transition of the Web browser screen when the content is taken in as a link URL of another summary or a plurality of attached files in the creation of the summary in the knowledge accumulation support system of the embodiment.

FIG. 16 is an exemplary first flowchart showing a procedure of a process of capturing another summary and capturing an attached file when creating the summary in the knowledge accumulation support system of the embodiment.

FIG. 17 is a second flowchart showing a procedure of taking in another summary and capturing an attached file when creating the summary in the knowledge accumulation support system of the embodiment.

[Explanation of symbols]

 DESCRIPTION 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 link control unit 201 User table 202 Community table 203 Subscription type table 204 Member table 205 Thread table 206 Message table 207 Summary table 208 Reference file table

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Masaaki Iwata 2-9-9 Suehirocho, Ome-shi, Tokyo Inside the Toshiba Ome Plant (72) Inventor Kazunori Shimakawa 2-9-9 Suehirocho, Ome-shi, Tokyo Stock F-term in Toshiba Ome Plant (reference) 5B075 KK07 ND36 NR12 UU40

Claims (10)

[Claims] 1. A knowledge accumulation support system configured to be connectable to a plurality of client terminals via a network, and to classify and accumulate messages posted from each client terminal to a virtual community to support accumulation of knowledge. Access control means for performing user authentication on a client terminal of an access requester to permit message posting from the client terminal; and managing a virtual community in which a plurality of client terminals can participate. Community processing means for classifying and storing messages posted to the virtual community from each client terminal permitted to access by the means for each topic, wherein the community processing means summarizes the messages classified and stored for each topic. Summary message and others Collaborative knowledge system characterized by comprising a link control means for associating the attachment summary message or other message. 2. The link control means displays a list of other summary messages and, when any one of the summary messages is selected from the list, displays the summary message as the summary message. 2. The knowledge accumulation support system according to claim 1, wherein the knowledge accumulation is related. 3. The knowledge accumulation support according to claim 1, wherein the link control means executes the association by taking in address information indicating the location of another summary message into the summary message. system. 4. The link control means displays a list of attached files of another message, and, when any one of the attached files is selected from the list of attached files, summarizes the attached file. 2. The knowledge accumulation support system according to claim 1, wherein the system is associated with a message. 5. The knowledge storage support system according to claim 1, wherein the linking means executes the association by taking in address information indicating the location of the attached file into the summary message. 6. A knowledge storage support system configured to be connectable to a plurality of client terminals via a network, and to classify and store messages posted from each client terminal to a virtual community to support knowledge storage. A message link control method, comprising: an access control step of performing user authentication on an access requesting client terminal in order to permit posting of a message from the client terminal; and a virtual community in which a plurality of client terminals can participate. And a community processing step of classifying and accumulating messages posted to the virtual community from each client terminal permitted to access by the access control step for each topic, and accumulating the message. Classification, accumulated link control method of the summary message in collaborative knowledge system characterized by comprising a link control step for associating attachments other summary message or other message in the summary message that summarizes the message. 7. The link control step displays a list of other summary messages and, when any one of the summary messages is selected from the list, displays the summary message as the summary message. 7. The link control method of a summary message in the knowledge accumulation support system according to claim 6, wherein the link is related. 8. The knowledge accumulation support according to claim 7, wherein the link control step executes the association by taking in address information indicating the location of another summary message into the summary message. Link control method of summary message in the system. 9. The link control step displays a list of attached files of another message, and, when any one of the attached files is selected from the list of attached files, summarizes the attached file. 7. The link control method of a summary message in the knowledge accumulation support system according to claim 6, wherein the link is associated with the message. 10. The knowledge storage support system according to claim 6, wherein the link control step executes the association by taking in address information indicating the location of the attached file into the summary message. Link control method of summary message.